1st draft of the Markup Referece is up - XML w/ external links as xlink: http://moz.zope.org/Members/fantasai/reorg/markup/xml (Use Mozilla. =P)
SGML/XML source: http://moz.zope.org/Members/fantasai/reorg/markup/sgml Unfortunately, I don't know how to write Mozilla-recognizable fragment identifiers, so the table of contents doesn't work... Anyhow, the purpose of this document will be, as explained in the Preface, to define a number of semantic classes for use on mozilla.org, for marking sections, examples, code, etc. If there's anything confusing about the Preface, anything that needs to be explained further, *please* let me know. This (in HTML format) and the associated stylesheet (to be written) can go up on mozilla.org without waiting for the new site, if anyone thinks it's a good idea. As usual, all comments are welcome. I also have some questions-- Should long DocBook-based class names be abbreviated? E.g. productnumber -> prodnum or something like that. It's not so bad in DocBook, but it gets long in HTML for common inlines: <span class="productnumber">mozilla1.0</span> An alternative would be to let authors write it out as a tag (as in DocBook) and provide a Perl script for conversion. There should be a class for "keywords"--such as search keywords, bugzilla keywords, and the like. (Right now they're usually put in <tt>.) If I put 'keyword', it would have to map to something different in DocBook as <keyword> isn't appropriate. Any suggestions? A number of these map to <span> in HTML, which doesn't mean anything. Would it be better to map them to presentational markup, such as <tt class="filename"> instead of <span class="filename">? Neither element has any inherent semantics, but at least <tt> carries presentation for non-CSS enabled browsers. If the element used is standardized, the stylesheet, because it knows the exact presentation, can override the HTML.
