3308 2006-06-01 21:14:56 +0000 Which error to raise for attributes with the same node-name in a direct element constructor? 2006-06-06 16:59:42 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 1.0 Candidate Recommendation PC Windows XP CLOSED WONTFIX P2 normal --- 1 ying.lu chamberl public-qt-comments oldest_to_newest 9923 0 ying.lu 2006-06-01 21:14:56 +0000 For the following query, <elem attr="val1" attr="val2" attr2="val3"/> it can raise error XQST0040, according to XQuery specification section 3.7.1.1, "If the attributes in a direct element constructor do not have distinct expanded QNames as their respective node-name properties, a static error is raised [err:XQST0040]." It can also raise error XQDY0025, based on section 3.7.1.3 bullet 5.d, "attributes consist of all the attributes specified in the start tag as described in 3.7.1.1 Attributes, together with all the attribute nodes in the content sequence, in implementation-dependent order. If two or more of these attributes have the same node-name, a dynamic error is raised [err:XQDY0025]." Should both error codes be allowed for the sample query? Please clarify. Thanks, Ying 9929 1 mike 2006-06-04 22:28:21 +0000 If a query contains a static error then the evaluation phase will never take place and therefore a dynamic error will never be raised. I think there's a clear distinction here between the static error that occurs when the attribute names are known statically, and the dynamic error that occurs when they are computed. Michael Kay (personal response) 9936 2 ying.lu 2006-06-05 18:37:22 +0000 If that is the intention, please clarify in the specification, as the section 3.7.1.3 bullet 5.d says, "attributes consist of all the attributes specified in the start tag as described in 3.7.1.1 Attributes...." An implementation can choose to check the attribute name during the evaluation phase, therefore raise the dynamic error instead of the static error. Both are allowed in the current specification. Thanks, Ying 9949 3 mike 2006-06-06 16:59:25 +0000 The Working Group discussed this on 2006-06-06 and decided that no change to the specification is needed. In a direct element constructor, the presence of two conflicting attributes is a static error, which means that it can and must be detected statically (which means it must be reported, using error code XQST0040, even if it occurs in code that is never executed). In a computed element constructor, it's not possible in general to detect the error statically. It's therefore defined as a dynamic error, and it's only mandatory to report the error if the code is actually executed. But note that section 2.3.1 says that dynamic errors "may" be detected during the static phase: in this case this means that if you use a computed element constructor and the compiler can work out in advance that the attribute names will conflict, it is allowed to report the error XQDY0025 statically. I am closing this as "Won't fix". If you feel there are issues that we haven't addressed here, please feel free to reopen the bug. Michael Kay for the XQuery Working Group