Altova Mailing List Archives

Re: [xml-dev] Namespaces conformance tests

From: james anderson <james.anderson@----.-->
To: xml-dev@-----.---.---
Date: 3/2/2003 7:28:00 PM
Karl Waclawek wrote:
> ...
> I read this as meaning that such prefixes are not illegal per se.
> But I am confused about how to treat declarations.
> "xml" may, but does not need to be declared.
> "xmlns must not be declared.
> But what about the other prefixes with leading characters "xml"?
> I would tend to think they should be treated like "xml", that is,
> declaration optional, but must be to the correct namespace.
> If no mapping to a namespace defined yet (in specifications), then
> do not reject, but feel free to issue a warning.

the only exceptions made to the requirement that a prefix must be be bound are those concerning the prefixes xml and xmlns. the phrase "processors must not
treat [all other prefixes beginning with the three-letter sequence x, m, l] as fatal errors" permits the appearance of such prefixes as the ncname of a
prefixedattname and as a prefix in a qname. there is nothing in the passage which parallels the assertion which is made with respect to the xml prefix, this is,
that "[i]t may, but need not, be declared," which would mean that the exceptions do not govern the appearance of such an unbound prefix. which mean the the
normal constraints would apply to them.



These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.