8564 2009-12-28 16:41:33 +0000 [XQuery] orphaned error XQDY0096 2010-03-21 17:43:44 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 1.0 Proposed Edited Recommendation PC Windows XP RESOLVED FIXED P2 normal --- 1 andrew.eisenberg jonathan.robie public-qt-comments oldest_to_newest 30282 0 andrew.eisenberg 2009-12-28 16:41:33 +0000 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. 31658 1 jonathan.robie 2010-02-09 13:42:49 +0000 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. 32104 2 andrew.eisenberg 2010-02-15 20:35:27 +0000 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. 32200 3 jonathan.robie 2010-02-16 18:58:31 +0000 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). 33741 4 jonathan.robie 2010-03-21 17:43:44 +0000 (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.