This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In 2. basics we find "XQuery does not support the namespace axis and does not represent namespace bindings in the form of nodes." I think this needs rewording. It definitely appears that the XQuery specification _does_ use namespace nodes to represent namespace bindings, despite not supporting the namespace axis. For example: "By itself, a computed namespace constructor has no effect on in-scope namespaces, but if an element constructor's content sequence contains a namespace node, the namespace binding it represents is added to the elements in-scope namespaces." This change might be as simple as omitting "and does not represent namespace bindings in the form of nodes." I'd also argue that "However, where other specifications such as [XSLT and XQuery Serialization 3.0] refer to namespace nodes, these nodes may be synthesized from the in-scope namespaces of an element node by interpreting each namespace binding as a namespace node." is questionable.
I propose the following modification: XQuery does not support the namespace axis and does not represent the namespace bindings of an element in the form of nodes.