Bob Stayton wrote: > I don't doubt there is a need for Strict XHTML, but no one has committed > to doing that work.
I have doubts. What is the real world requirement for having XHTML
Strict output apart from purely idealistic and ideological reasons?
Also please note that the current web standards development marches in
HTML5/XHTML5 direction where there is no distinction between
Transitional/Strict so spending much efforts on producing Strict XHTML
might be seen as trying to catch up train that have already departed.
Ad point of generating empty <a/> elements -- empty <a> is valid XHTML
Strict. The problem is that such markup doesn't work properly in some
browsers that parse XHTML content as it was HTML content (ie. not using
XML parser).
But in the concrete case of <a name="xxx"/> it would be better to change
it to <parentElement id="xxx">...</parentElement> as id attribute is now
widely supported by browsers.
Jirka
--
------------------------------------------------------------------
Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz
------------------------------------------------------------------
Professional XML consulting and training services
DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------
signature.asc
Description: OpenPGP digital signature
