Hi, Chris put some ideas forward for the tiddler definition. I like it, because it is a concrete idea. Some additional thoughts:
tiddler has a type field (content type) and maybe also needs a field for the encoding. There is probably need for a field stating the spec revision to which this tiddler conforms (for future upgrades of the tiddler communication protocol) Currently tw has some fields beginning with server. Do we need them? I thing the most important are the definition of uuid fields and their semantics and working together with tw, including the ability to track changes and the history of where the tiddler came from. I think this is non trivial. Ward has done some work on this in his federated wiki project, see: https://github.com/WardCunningham/Smallest-Federated-Wiki/wiki/Federation-Details https://github.com/WardCunningham/Smallest-Federated-Wiki/wiki/Story-JSON https://github.com/WardCunningham/Smallest-Federated-Wiki Basically his "pages" are equivalent to a tiddler. -- 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.
