Hi, I'm with Chris and Poul here. Keep it simple and just start. Add a uuid field to core tw which is initialized at tiddler creation time. Also add a core field saying something like tiddler-schema version 1. And standardize the date field to some format (or add an internal date field in some format). The important thing of these is that they have standard names, such that other people are not using these fields. Then tw can keep on working as before with just some extra fields.
Additionally I propose to add an optional journal or history field analogous to Ward's federated wiki ( https://github.com/WardCunningham/Smallest-Federated-Wiki/wiki/Story-JSON ). This field can be ignored by tw (or not) and used to record history (like add content, delete, merge, ...). Use of this field is optional and probably would require some server assistance. The main thing again is that the field name is reserved. I also think that later on some field would be required to take a cryptographic hash of tiddler contents, but let's start first and evolve. By just adding these fields nothing substantial has to change in the core. Nothing needs to change in the ui! and the use of tw. But these changes are building blocks for tiddler identification, server side integration and federation. Let's see how they are used. Keep it simple. Keep tw extensible. @Poul About your example of 42 tiddlers with 17 different uuids. I think a journal field can help in that case, but I would rather not at this moment standardize. Let's try it first and evolve. With e.g. tiddler-schema 2 it could be standardized. -- 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.
