Semantically correct XHTML output project

PROPOSED GUIDING PRINCIPLES FOR SIMPLER, ACCESSIBLE AND
SEMANTICALLY CORRECT XHTML OUTPUT
* Version 1.1 1.2 :) *

1. The XHTML output will comply with the W3C XHTML 1.0 Transitional
Strict recommendation, as well as current W3C Accessibility
Guidelines.

[COMMENT FROM R.H. REMOVED]

[COMMENT FROM N.R.] Somebody (I don't remember who and when) said:
"Be flexible in what you accept as input, be strict in what you
output" (or something the like). Strict 1.0 (or maybe even 1.1) XHTML
is much easier and simpler to implement than the Transitional one.

2. Included in the output will be a default CSS file with a basic
layout for screen, print and handheld devices. The CSS file should be
fully functional in current browsers: Opera 7+, Mozilla/Gecko 1.0+
based browsers and IE 6+.

[COMMENT FROM N.R.] This CSS file shouldn't be necessary, since XHTML
aims to be fully accessible and readable without any presentation.
But it would be nice to (optionally) have it, if only to give an
example on how to use the CSS hooks (see section 6).

3. Outputted XHTML code will aim to be as simple (meaning fewer tags)
as possible to facilitate CSS layout, and be completely table-less
expect for tabular data.

4. XHTML output will have four main DIVs for layout purposes: header,
navbar (for basic navigation on all pages as well as next/previous),
content and footer.

5. Unless specified via the role attribute (or some other mechanism),
The only DIV to be generated inside the main content div will be
admonitions, sidebars and highlights.

[COMMENT FROM R.H. REMOVED]

6. [ADDED BY N.R.] CSS hooks will be provided by using XML/XHTML
attributes like id="" class="" xml:id="" and so on (instead of using
too many divs), to preserve as far as possible the original
semantical meanings of the DocBook markup and to give rich CSS
layout possibilities.

7. All graphics that will be used for navigation purposes or
admonitions will be handled by the CSS stylesheet. This will ensure
maximum functionality across various mediums and facilitate meeting
accessibility standards.


Thanks for everyone who has participated in this discussion so far.
Certainly a good example of the vibrant nature of the DocBook
community.

Later,
Rene

Thu, 28 Apr 2005