12649 2011-05-12 13:09:45 +0000 [XQuery30] Namespace constructors: ordering of rules (editorial) 2013-06-19 08:21:02 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3.0 Working drafts PC Windows NT CLOSED FIXED P2 minor --- 1 mike jonathan.robie jim.melton public-qt-comments oldest_to_newest 48487 0 mike 2011-05-12 13:09:45 +0000 Section 3.8.3.7 clause 2 reads: 2. If the result of atomization is a single atomic value of type xs:NCName, xs:string, or xs:untypedAtomic, it is used as the prefix property of the newly constructed namespace node; if it can not be cast to xs:NCName, dynamic error is raised [err:XQDY0074]. If the result is the empty sequence or an empty string, the prefix property of the newly constructed namespace node is empty. For any other result, a type error is raised [err:XPTY0004]. The rules here are in the wrong order; if the name is "" we raise an error (because it's not an invalid NCName) before encountering the rule that says "" is allowed. Furthermore, namespace nodes do not have a "prefix property". I suggest: 2. If the result of atomization is an empty sequence or a single atomic value of type xs:string or xs:untypedAtomic, then the following rules are applied in order: 2a. If the result is castable to xs:NCName, then it is used as the local name of the newly constructed namespace node. (The local name of a namespace node represents the prefix part of the namespace binding.) 2b. If the result is the empty sequence or a zero-length xs:string or xs:untypedAtomic value, the new namespace node has no name (such a namespace node represents a binding for the default namespace). 2c. Otherwise, a dynamic error is raised [err:XQDY0074]. 3. If the result of atomization is not an empty sequence or a single atomic value of type xs:string or xs:untypedAtomic, a type error is raised [err:XPTY0004]. 56620 1 jonathan.robie 2011-09-10 20:28:50 +0000 I agree. Changes made as requested.