This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The test is attribute xmlns:localName {"content"} Error code XQDY0044 seems more appropriate than XPST0081: err:XQDY0044 It is a dynamic error if the node-name property of the node constructed by a computed attribute constructor is in the namespace http://www.w3.org/2000/xmlns/ (corresponding to namespace prefix xmlns), or is in no namespace and has local name xmlns. Similarly K2-ComputeConAttr-38
So prefix xmlns, bound to "http://www.w3.org/2000/xmlns/", is a binding that is by default available? http://www.w3.org/2000/xmlns/ are "fn, xml, xs, xsi, local", so to me it seems one can never get that far as to saying it's in the namespace http://www.w3.org/2000/xmlns/.
Closed because I think Frank is probably right. The spec is a little curious in treating "attribute xmlns:abc {$uri}" as a static error XPST0081 while treating "attribute xmlns {$uri}" as a dynamic error XQDY0044, but that does seem to be the intended reading. Technically, however, one could argue for XQDY0044 for this one on the grounds that the "statically known namespaces" can be augmented by the implementation, and that includes the option of augmenting it with the binding xmlns=http://www.w3.org/2000/xmlns/ Michael Kay