- From: Michael Kay <mike@saxonica.com>
- Date: Mon, 20 Mar 2006 15:59:49 -0000
- To: "'Elliotte Harold'" <elharo@metalab.unc.edu>, <public-xml-id@w3.org>
- Cc: "'xom-interest'" <xom-interest@lists.ibiblio.org>, "'Wolfgang Hoschek'" <whoschek@lbl.gov>
> Section 4 of xml:id states: > > An xml:id processor must assure that the following > constraints hold for > all xml:id attributes: > > * The normalized value of the attribute is an NCName > according to > the Namespaces in XML Recommendation which has the same > version as the > document in which this attribute occurs (NCName for XML 1.0, > or NCName > for XML 1.1). > And it then says: An xml:id error occurs for any xml:id attribute that does not satisfy the constraints. Having earlier said: [Definition: An xml:id error is a non-fatal error that occurs when an xml:id processor finds that a document has violated the constraints of this specification.] Section 6 further says: A violation of the constraints in this specification results in an xml:id error. Such errors are not fatal, but should be reported by the xml:id processor. In the interest of interoperability, it is strongly recommended that xml:id errors not be silently ignored. So: it's clear as mud. The processor must "assure that" (assure whom?) the value is an NCName, and it mustn't fail if it isn't. Michael Kay
Received on Monday, 20 March 2006 16:00:09 UTC