8537 2009-12-22 21:47:17 +0000 [XQuery] computed attribute constructor issue raise by XQTS Bug #8480 2010-02-17 19:48:21 +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 30232 0 andrew.eisenberg 2009-12-22 21:47:17 +0000 Bug #8480 is concerned with a new test case written to cover erratum XQ.E19 and an older test case that is almost identical that returns a different error. The new query is: <result>{attribute {"xmlns:error"} {}}</result> In 3.7.3.2 Computed Attribute Constructors we say: If the keyword attribute is followed by a name expression, the name expression is processed as follows: 1) . . . 3) ... If conversion of the atomized name expression to an expanded QName is not successful, a dynamic error is raised [err:XQDY0074]. A static error is raised [err:XQST0044] if the node-name of the constructed attribute node has any of the following properties: * Its namespace prefix is xmlns. * ... The text introduced by XQ.E19 seems to have two problems: - it is raising a static error after the attribute node is constructed - the construction of the attribute fails, because xmlns is not defined in our statically known namespaces, and so the new text will never be considered 32201 1 jonathan.robie 2010-02-16 19:05:32 +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). That will fix the static / dynamic error problem. 32202 2 andrew.eisenberg 2010-02-16 19:10:25 +0000 After WG discussion I now believe that the second problem I reported does not exist. The following query should return a dynamic error (we say XQST0044 now): <result>{attribute {fn:QName("foo", "xmlns:error")} {}}</result>