On Thu, 17 Nov 2011, Poul wrote:
My point about UUID's was that strictly speaking, you really need to know what it is that the uuid identifies, and that's a semantic issue.
Ah, okay, somewhere along the line I thought we had already gotten past that. I think in relation to the need for revision identifiers to be separate from identifiers for the tiddler which "has" those revisions.
I could imagine that a collection of tiddlers had the same value for a named uuid, because either: * they were different versions of the same tiddler.
This is what I was thinking. And those different versions may exist anywhere (in a tiddlywiki file, on a server, on some other server). In aggregate they are "the tiddler". How the resolution of all those revisions is handled is a _different_ issue from identifying that they are in fact the same tiddler.
on two things: 1) What the tiddler-identifying id is named (simple). 2) What it means to have identified a tiddler. Not so simple. IMHO.
Yes.
If, say, you receive a document that contains 42 more or less different tiddlers having 17 different uuids, what can be deduced about their relationships..? A plausible interpretation would be 17 tiddlers, some of which have several versions. You may of course choose not to accept such a document. Or try to figure out which is the current version - but don't assume that it's the one with the latest timestamp.
This is aligned with my thinking. -- Chris Dent http://burningchrome.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.
