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 8564 - [XQuery] orphaned error XQDY0096
Summary: [XQuery] orphaned error XQDY0096
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 1.0 (show other bugs)
Version: Proposed Edited Recommendation
Hardware: PC Windows XP
: P2 normal
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: 2009-12-28 16:41 UTC by Andrew Eisenberg
Modified: 2010-03-21 17:43 UTC (History)
0 users

See Also:


Attachments

Description Andrew Eisenberg 2009-12-28 16:41:33 UTC
XQDY0096 is defined in F Error Conditions as:

err:XQDY0096

    It is a dynamic error the node-name of a node constructed by
    a computed element constructor has any of the following properties:

        * Its namespace prefix is xmlns.
        * Its namespace URI is http://www.w3.org/2000/xmlns/.
        * Its namespace prefix is xml and its namespace URI is not
          http://www.w3.org/XML/1998/namespace.
        * Its namespace prefix is other than xml and its namespace URI is
          http://www.w3.org/XML/1998/namespace.

It is not referenced in the body of the specification. It was added by erratum XQ.E19.
Comment 1 Jonathan Robie 2010-02-09 13:42:49 UTC
This error does not occur in the curent draft of XQuery 1.1. Because it is never used in 2ed, it does not change the normative language.

If we decide to edit the text of the 2ed, it's easily removed.
Comment 2 Andrew Eisenberg 2010-02-15 20:35:27 UTC
XQ.E19 defines error XQDY0096 in its item 6. Item 2 inserts, "A dynamic error is raised [ERROR 0096 NOT FOUND] ..." Perhaps item 2 was not correctly applied to the specification.
Comment 3 Jonathan Robie 2010-02-16 18:58:31 UTC
Erratum XQ.E19 does not accurately reflect the resolution of Bug 4463. 

I need to fix this in both the erratum and in the XQuery specification (2ed and 1.1).
Comment 4 Jonathan Robie 2010-03-21 17:43:44 UTC
(In reply to comment #3)
> Erratum XQ.E19 does not accurately reflect the resolution of Bug 4463. 
> 
> I need to fix this in both the erratum and in the XQuery specification (2ed and
> 1.1).


False alarm - XQ.E19 and Bug 4463 do correspond, except that 0044 has been made static. and the order is different.

XQ.E19 says how this should be fixed - I will close this when I have made those changes.