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 13964 - Recap of XQST0022 in appendix F should have changed in second edition
Summary: Recap of XQST0022 in appendix F should have changed in second edition
Status: RESOLVED DUPLICATE of bug 11986
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 1.0 (show other bugs)
Version: 2nd Edition Recommendation
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-29 21:05 UTC by Michael Dyck
Modified: 2011-08-29 21:14 UTC (History)
0 users

See Also:


Attachments

Description Michael Dyck 2011-08-29 21:05:15 UTC
In the first edition of XQuery 1.0, section 3.7.1.2
[Namespace Declaration Attributes] said:
    The value of a namespace declaration attribute must be a
    URILiteral; otherwise a static error is raised [err:XQST0022].

In response to Bug 5083, erratum XQ.E13 changed this to:
    The value of the namespace declaration attribute
    (a DirAttributeValue) is processed as follows.
    If the DirAttributeValue contains an EnclosedExpr,
    a static error is raised [err:XQST0022].
and that's how it appears in 3.7.1.2 in XQuery 1.0 second edition.

All that is fine.

However, in Appendix F [Error Conditions], the recap of XQST0022
still reflects the definition from the first edition:
    It is a static error if a namespace declaration attribute
    contains an EnclosedExpr.

XQ.E13 should have changed it to (something like):
    It is a static error if the DirAttributeValue of a
    namespace declaration attribute contains an EnclosedExpr.

(Note that XQuery 3.0 already has more-or-less this change, since
the 2011-07-17 WD.)
Comment 1 Michael Dyck 2011-08-29 21:14:07 UTC
Whoops, this is a duplicate of Bug 11986.
Comment 2 Michael Dyck 2011-08-29 21:14:43 UTC

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