On Mon, 14 Nov 2011, Tobias Beer wrote:
I would suppose there is a reason for most all database(-like) systems
to equip "records" (a tiddler being a somewhat generic record) with a
persistent id.
I'm hundred percent in favor of tiddlers having a persistent id. When
putting TiddlyWeb together I wanted to tiddlers to not only have a
unique id on the server, I wanted them to be unique across the
universe of TiddlyWeb servers _and_ for there to be, in addition to
/bags and /recipes -based tiddlers URIs, another /tiddler/{id} route.
That id would have been a uuid and would have been a first class
attribute of the tiddler.
This idea was rejected.
So given that there is at least some people who support the idea of
ids, and "tiddlygrp" says that atom might work as transport, or a
variety of other things, then the remaining open issue is tiddler
attribute handling?
--
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.
