I would argue that also a standard TiddlyWiki is dished out via some server, hence serving tiddlers in a predefined way.
In other words, while of course one would expect there to be some client for editing tiddlers, it always is a server that delivers these uuid's, since they are stored in tiddlers and thus delivered in whatever serialization or representation is being used. Consider this scenario: You are supposed to aggregate tiddlers from different sources by calling some webservice with a given set of parameters, e.g. qualified sources of tiddlers, parameter that asks for a specific function to be performed, and some output format the webservice is to use to dish out whatever he had aggregated / computed on the grounds of those source tiddlers. Now begins the fun... on which tiddler standard is this WebService to deal with the tiddlers in these sources? Can it actually perform his function or does it require UUIDs, versioning, branching capabilities to perform his job or include any source tiddler for that purpose? The same goes for the output... if you have no means to specify the kind of output you desire, and this output might well be (a bag of) tiddlers or some serialzation thereof... what are you going to implement? This is why a communication protocol is actually required, so that web based services know what to do with the tiddlers they get in or how to push things back once they're done doing their thing... assuming that at least one side of the function, input or output, indeed involves a requirement for a tiddler based standard to rely on. tb -- 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.
