This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6990 - missing error case err:XQDY0091 in Constr-attr-id-2
Summary: missing error case err:XQDY0091 in Constr-attr-id-2
Status: RESOLVED DUPLICATE of bug 5275
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 1.0.2
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Andrew Eisenberg
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2009-06-02 15:42 UTC by Bogdan Butnaru
Modified: 2009-06-03 12:53 UTC (History)
1 user (show)

See Also:


Description Bogdan Butnaru 2009-06-02 15:42:39 UTC

Please consider the following test case: 

<test-case is-XPath2="false" name="Constr-attr-id-2"
  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="" 
    section-title="Attributes" section-pointer="id-attributes"/>

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

  <input-file role="principal-data"

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


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 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.)
Comment 1 Michael Kay 2009-06-02 16:07:13 UTC
In the CVS version of the test suite, the test does indeed have the error XQDY0091 as an expected outcome.

This appears to be a duplicate of bug #5275
Comment 2 Bogdan Butnaru 2009-06-03 12:53:07 UTC
(In reply to comment #1)
> This appears to be a duplicate of bug #5275

Yes, sorry. I searched for “Constr-attr-id-2” and I got no results, probably because the implicit settings search only for open bugs.

*** This bug has been marked as a duplicate of bug 5275 ***