Hello!

Please consider the following test case: 

<test-case is-XPath2="false" name="Constr-attr-id-2"
  FilePath="Expressions/Construct/DirectConElem/DirectConElemAttr/"
  scenario="standard" Creator="Andreas Behm">

  <description>Enclosed expression in attribute content - xml:id attribute 
    value must be further normalized.</description>

  <spec-citation spec="XQuery" section-number="3.7.1.1" 
    section-title="Attributes" section-pointer="id-attributes"/>

  <query name="Constr-attr-id-2" date="2005-03-05"/>

  <input-file role="principal-data"
    variable="input-context">emptydoc</input-file>

  <output-file role="principal" compare="XML">Constr-attr-id-2.xml</output-file>

</test-case>

The query is “<elem xml:id="    a{'b    c


d','        '}"/>” (note that some of the whitespace might be transformed by the browser).

The expected result is “<elem xml:id="ab c d"/>”. There are no expected errors, although a file named “Constr-attr-id-2.log” in the same directory contains the (non-existent) error code “err:XQST0083
”; this file is not referenced anywhere in the catalog.

However, the cited section reads “If an error is encountered during xml:id processing, an implementation MAY raise a dynamic error [err:XQDY0091].” If my reading of http://www.w3.org/TR/xml-id/#processing is correct, one such error may be raised in the value of the attribute is not a valid NCName.

The value of the attribute in the given query is "ab c d", which is not a NCName because it contains spaces.

Thus, unless I'm missing something, a conforming implementation is allowed to raise err:XQDY0091 for this test-case, and “<ts:expected-error>XQDY0091</ts:expected-error>” should be added to the test case.

(By the way, err:XQDY0091 is not mentioned anywhere else in the test catalog.)