> @Jeremy: For me a tiddler uuid has nothing directly to do with a > tiddler. At creation time put a uuid in a field in the tiddler is the > absolute minimum I think tw should do. A lot other stuff can be done > server side. The advantage of creating a uuid at tiddler creation > time is that then it is "uniquely" marked. Then the tiddler might > move to a server (or not).
I like the way that people explore using TiddlyWiki with different, pre-existing serversides, such as the current experimentation with CouchDB, and Zooko's experiments with Taho-LAFS. My concern is that different serversides may have somewhat different semantics for their UUIDs, and it would be bad for TiddlyWiki to get in the way of experimenters by imposing a slightly incompatible way of using UUIDs. I know it's not quite the same thing, but a related thing that I would like to see standardised is the field that identifies the global URI for the canonical copy of the content of a tiddler. It seems reasonable for future TiddlyWiki to directly support clean, RESTesque serversides like TiddlyWeb by using HTTP verbs on that URI. > My thought is that by putting the uuid in > tw, all servers should support this standard. If each server builds > up its own uuid semantics, than its hard to get federation and sharing > of tiddlers peer to peer without a server. I'm not sure that fixing an implementation within TiddlyWiki is the best way to find the optimum federation architecture. The core of the tiddler concept is pretty well established now, as Chris says, there's more than one implementation that we can use as a reference. Let's record what we've got as the core tiddler standard, and make sure we leave space for the experiments on federation and sharing. Part of my resistance is that I'm concerned that the consequences of enforcing UUID semantics on the client seem complicated. They seem straightforward enough when thinking in terms of how the synchronisation works, but I'm less confident when it comes to the user interface; on the face of it, UUIDs would allow multiple tiddlers with the same title field to exist. How would it choose the right one for navigating links? How would users access the others? I'm disinclined to start grappling with all of that when it's not strictly a prerequisite for exploring the actual underlying federation and sharing mechanisms that so many of us are interested in. Best wishes Jeremy -- Jeremy Ruston mailto:[email protected] http://www.tiddlywiki.com -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
