, ,

and other block elements to mimic the original DocBook element types. This is similar to what people now call "microformats" (i.e., it was done many years before that term was coined). You could of course transform all of DocBook to simply

and elements with the 'class' attributes being the original DocBook element types and a CSS stylesheet to suit. This would in effect be more appropriate than the tag abuse of forcing DocBook's semantics into XHTML's. But HTML/XHTML has such a long history of abuse that its semantics aren't very strong anyway, in terms of normative practice. One of the issues with transforming XHTML to DocBook is that one has almost no structure to work with. There's none of the containment and almost none of the required sequences or optional structures one finds in DocBook. It's going from chaos to structure, and implying structure where none is extant is a bit of tag abuse as well. With the wiki the markup is at least a bit more regularized since it is itself a transformation from the wiki markup. We can imply *some* of the structures. What I *might* recommend is looking at transforming the XHTML output of JSPWiki into a tighter XHTML-based document type. If you look at what is available in ISO HTML the design is actually somewhat similar to DocBook, i.e., there's a set of numbered divisions ( through ) with numbered headings for each. This is about as much real structure as one finds in HTML/XHTML anyway and there's no tag abuse. Information technology — Document description and processing languages — HyperText Markup Language (HTML). ISO/IEC 15445:2000(E) https://www.cs.tcd.ie/15445/15445.HTML User's Guide to ISO/IEC 15445:2000 HyperText Markup Language (HTML) https://www.cs.tcd.ie/15445/UG.HTML The relevant part of the ISO HTML DTD is ]]> You can see how the divisions and headings mimic DocBook. The headings could either precede the division or be the first child element. I personally think ISO HTML should have put the heading inside of the division since the heading is for that division. But no matter. Now, I'm not actually suggesting use of ISO HTML since (a) it's SGML rather than XML based, so it's incompatible with XHTML, and (b) it uses uppercase element type names, and (c) I don't actually recommend using through (possibly

through

instead?). Point is, this can all be done within the existing XHTML DTD. If you actually wanted a more restrictive XHTML DTD for an output structure mimicking ISO HTML's hierarchy, I'm willing to contribute some time writing an XHTML module to do this (I might even have one somewhere from when I did that work back in the late 90s). That is, if you decided you wanted to do this and got to the point of needing it. To answer your question more directly, we've been looking into an archive format for content coming off the wiki and have considered DocBook, but are more likely to go with validated XHTML since it more closely fits with the semantics of the wiki's output markup. Murray ........................................................................... Murray Altheim === = = http://www.altheim.com/murray/ = = === SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = = Boundless wind and moon - the eye within eyes, Inexhaustible heaven and earth - the light beyond light, The willow dark, the flower bright - ten thousand houses, Knock at any door - there's one who will respond. -- The Blue Cliff Record