On Mon, 14 Nov 2011, tiddlygrp wrote:
@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). 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.
Yes, agree with all this. If any tiddlers are gonna have uuids it is far better if _all_ tiddlers have them.
And probably the uri/url's to get a tiddler will be server dependent. That is not a problem. The problem to be solved it what do you get back when you call GET /some.tiddler.json? Which fields are in the tiddler and what do they mean?
Okay that makes more sense. I'm not sure how or who to decide the syntax and semantics. -- 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.
