6275 2008-12-04 15:11:05 +0000 [XQuery 1.1] Computed Namespace Constructors 2013-06-19 07:43:17 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3.0 Working drafts PC Windows NT CLOSED FIXED P2 normal --- 1 mike jonathan.robie public-qt-comments oldest_to_newest 22679 0 mike 2008-12-04 15:11:05 +0000 This relates to the public WD dates 3 December 2008. Section 3.7.3.7 Computed Namespace Constructors 1. A trivial typo: "creates a new namespacee node," 2. The current text says: ...the prefix expression is evaluated as follows: Atomization is applied to the result of the name expression. 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. 2a: missing "is" where shown 2b: "xs:NCName or xs:string" is redundant. If it's an xs:NCName then it will also be an xs:string. 2c: there needs to be a rule that it must be valid as an NCName. I would suggest: ...the prefix expression is evaluated as follows: Atomization is applied to the result of the name expression. If the result of atomization is a single atomic value of type xs:string or xs:untypedAtomic, it is cast to type xs:NCName (which may raise an error FORG0001) and the result is used as the prefix property of the newly constructed namespace node. 3. Section 3.7.4: It seems to me that error XQTY0102 should be XQDY0102. It's a dynamic error not a type error. 4. The newly-introduced error codes (XQ**0096 onwards), unlike all the older error codes, have no link to the term "static error", "dynamic error", or "type error" in their descriptions. Some of them include the term, but unlinked; others do not include the term at all.