The wikiweb ( http://c2.com/cgi/wiki ) was probably the first application,
which used mixed case words
(wich are common for abbreviations and multiy word identifiers in some
to automatically create cross references.
This scratchpad application uses the same convention,
see HowToEditThisPage and ContextViewUsage for more details.
Future versions may support http://www.opml.org/ ,
please send comments or help, if you would like oplm support.
Somehow the structure of Wiki and hence these pages
seems simillar to
http://xanadu.com/zigzag/ , http://gzigzag.sourceforge.net/
I just found zigzag in Nov 2001 and did not dive into it.
Thanks to Roland Hjerppe, I've got to know (Oct 2004)
aims and internal which bear some simillarities in
the aim to server for global hypertext
higher level structure
(udanax could well be an Askemos application:
it's structure has a few properties I'd
implement at application level).
Shawn Rutledge wrote:
Yes as I mentioned, I wanted to build a wiki. But lately I've been
thinking that editing wiki-style text should just be one possible UI.
It's hard to say that the wiki syntax is a canonical way of storing
web content when nobody can even agree on that syntax (Alejandro's,
Felix's, MediaWiki? etc. are all different). So I want to build an
object tree that represents a web page and store that, and dynamically
generate a wiki-like editing UI. Then an alternative UI could be a
having to use wiki syntax; and another would be a full GUI; etc.
OK, that's exactly the thinking behind the wiki style I included in
Askemos/BALL. I'd never store syntax, which is hardly readable in
as Dan Bricklin has put it.
It stores plain HTML (as parsed tree in the pstore module and
standard XML syntax in the file system) plus some XML for meta data,
lock handling etc.
You can edit HTML or wiki syntax. For that to work, the XML tree is
serialised in wiki syntax from the template. (template?template=source
This might loose information and be vary of round trip problems.) So
wiki syntax applies only on the UI.
Other Wiki implementations: