W3C home > Mailing lists > Public > public-xml-id@w3.org > March 2006

Non NCName IDs

From: Elliotte Harold <elharo@metalab.unc.edu>
Date: Mon, 20 Mar 2006 10:45:58 -0500
Message-ID: <441ECE36.1050401@metalab.unc.edu>
To: public-xml-id@w3.org
CC: Wolfgang Hoschek <whoschek@lbl.gov>, xom-interest <xom-interest@lists.ibiblio.org>

Wolfgang Hoschek pointed out an inconsistency in how XOM tests xml:id 
values which I've now traced to an apparent discrepancy between the 
current xml:id test suite and the xml:id spec, and I was hoping somebody 
could explain this to me.

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).

However the very first test case normal_001 uses a non-NCName and 
apparently expects this test to pass:

<para xml:id=" te  st ">MATCH</para>

In the catalog this is listed as

<test-case category="normalize" id="normal_001">
<creator>Norman Walsh</creator>
<purpose>Check ID normalization</purpose>
<spec-citation place="4" type="section" version="1.0" spec="xml:id"/>
	<scenario operation="standard">
<id>te st</id>
<result>xml:id on para is an ID (te st)</result>
<notes>XSLT cannot perform this test.</notes>

However a probably older version of the catalog I find laying around on 
my hard drive lists this as an error condition. i.e. the value of the 
operation attribute of the scenario element is error, not standard.

Can anyone shed some light on this? What is supposed to happen here? Is 
the test suite wrong or the spec? Or are they consistent in a way I'm 
not seeing?

Elliotte Rusty Harold  elharo@metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
Received on Monday, 20 March 2006 15:46:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:53:50 UTC