Yes my examples do assume an output type thanks for pointing that out. Perhaps from a technical standpoint we should prefer descriptions like Emphasis: make a stronger presentation of content. Heading: a start to a section of content that is part of the overall content stucture, has a level and is useful in a table of contents. Perhaps we have already achieved something by identifying this distinction, and the creation of an output agnostic list of wiki markup types would be useful. Wiki is a content management tool, amongst other things! The functionality list would precede a DTD. Its an analysis whose results could then be implemented in a number of ways including a DTD if you really wanted to go down that route. All best Andrew -----Original Message----- From: wiki-bounce@xxxxxxxxxxxxx [mailto:wiki-bounce@xxxxxxxxxxxxx] On Behalf Of Jim Cheetham Sent: 07 October 2004 20:12 To: wiki@xxxxxxxxxxxxx Subject: [WMS] Re: Pre-cursor to wiki markup standard Andrew Premdas wrote: > Thanks for this, but I think I've been misunderstood. My thought was > not about listing or defining syntax but defining functionality e.g. > > Make bold: displays text with a heavier font. > Make italic: displays text with a sloping font. > Display heading: displays text as a heading. A heading has a level and > would be included in a table of contents. But surely here you're limited to the possible output types? i.e. currently wikis output to HTML, and therefore your functionality is limited to things that can be expressed in HTML (or XHTML+CSS) It might be nice to consider different output methods, like PDF and so on, but we're getting away from wiki and getting into content management ... where XML and XSLT have been playing successfully ... Now, it might be nice to come up with an "internal" XML DTD for wikis, who can implement their own front-end language, store in WikiXML, and render in HTML ... because then I'd be able to migrate data from one wiki framework to another more easily ... -jim