Wiki Meets WebArch
A single Wiki is a collection of easily-maintained documents.
- Documents are by default presented with decorations which
assist in their maintenance ( & creation )
- But they should be available in their raw (undecorated) form
- How does that interact with the URI? Maybe:
foo redir to foo?view=decorated foo?view=raw
- Names on the wiki are short, in a flat namespace
This relates to WideOpenSource.
An HTTP PUT on foo?view=raw can and should do the right thing.
How to handle MIME Content-Type and content negotiation?
It would be especially fun to manage pages with dynamic content.... Wiki uses magic syntax from time to time, but ... how about having (sandboxed) python code on the web somewhere (like in a wiki) and other pages which are generated via that? The trick is to keep it all straight, and use reversable transformations when possible. (and tie it all wonderfully into XForms, somehow.)
Maybe:
foo redir to fooGenerator?view=output
Or the decorated foo simply include a link to the generator code, which has some
other name. But something has to link the two names....
Could you just have foo?showOutput
vs foo?showSource
and if it's
executable, the default is showOutput? BUT what if the source is generated by
some other program? No, there should be a chain of documents.... And some metadata (visible in the decorations)
which says which are generated from which, and how....