W3C home > Mailing lists > Public > www-html-editor@w3.org > July to September 2004

XHTML1: XML Namespaces compliance

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 12 Jul 2004 06:14:01 +0200
To: www-html-editor@w3.org
Message-ID: <41881008.1817840346@smtp.bjoern.hoehrmann.de>

Dear HTML Working Group,

  Neither section 3.2 nor section 3.1.1 of the XHTML 1.0 Second Edition
Recommendation state whether strictly conforming documents are required
to be namespace-well-formed or namespace-valid and whether user agents
are required to evaluate XHTML 1.0 documents for namespace-well-formed-
ness or -validity. Could you please clarify whether they are in those
sections and in case they are, change appendix C.8 to reflect this, i.e.
remove the colon from the regular expression for legal ID values?

If they are not required to conform to the Namespaces in XML
Recommendation it seems there should be a warning for authors that due
to the uncertain situation some user agents do evaluate documents to
this effect and might fail to process documents that are not; and that
general purpose XML tools that support XML namespaces might fail to
process such documents, too. That said, there does not seem to be a good
reason why XHTML should be liberal in this regard.

Appendix C.8 further states

[...]
  Further, since the set of legal values for attributes of type ID is
  much smaller than for those of type CDATA, the type of the name
  attribute has been changed to NMTOKEN. This attribute is constrained
  such that it can only have the same values as type ID, or as the Name
  production in XML 1.0 Section 2.3, production 5.
[...]

This would also need to be changed if you change the Recommendation to
require namespace-validity as NMTOKEN attributes may contain colons
while ID attributes may not.

regards.
Received on Monday, 12 July 2004 00:14:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:14:51 UTC