I'm now worried that we're talking at cross purposes. I'm talking about the content type that may be stored in the 'type' field of a tiddler. It seems that you are talking about the content type used to represent a TiddlyWiki serialisation of a bunch of tiddlers. I agree that in the latter case you will need two distinct content types for the two different varieties of TiddlyWiki that will be wrapped around the serialised tiddlers.
Is there such a distinction between the two uses of content types, or am I just getting more confused? Best wishes Jeremy > This still leaves serialization as a problem. Consider the following > situation: > > * there exists a recipe containing some tiddlers > * person X wants to GET them presented in a tiddlywiki classic > * person Y wants to GET them presented in a tiddlywiki5 > > Using existing code, if person X does this: > > curl -H "Accept: text/vnd.tiddlywiki;vocabulary(tw2)" \ > http://example.com/recipes/foo/tiddlers > > and person Y does this: > > curl -H "Accept: text/vnd.tiddlywiki;vocabulary(tw5)" \ > http://example.com/recipes/foo/tiddlers > > They will _both_ get a classic TiddlyWiki. > > The option to get any arbitrary set of tiddlers in any arbitrary > representation is the _core_ of TiddlyWeb, so the above needs to have > the correct behavior. > > Options are: > > * use explicity mime types[1] > * have a tiddlywiki serialization which talks multiple vocabs, > essentially being a parent over other serializations > * (something I can't think of yet) > > [1] I'll say this a bit more strongly than I did before: Doing > something other than explicit mime types strikes me as opening a can > of complexity and confusion that will have unintended and unexpected > side effects. It is something I really don't want to see. Content > negotiation is already a murky sea of unpredictable behavior and > tooling. If you want to be able to use multiple types of tiddlers in a > way that is most flexible with the most environments, be generic, hew to > the methods and standards that people are already using. > > > -- > Chris Dent http://burningchrome.com/ > [...] > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" 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/tiddlywikidev?hl=en. > -- Jeremy Ruston mailto:[email protected] -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev?hl=en.
