W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2013

[Bug 20830] New: [XQ30]

From: <bugzilla@jessica.w3.org>
Date: Wed, 30 Jan 2013 22:12:41 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20830-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 20830
           Summary: [XQ30]
    Classification: Unclassified
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3.0
          Assignee: jonathan.robie@gmail.com
          Reporter: tim@cbcl.co.uk
        QA Contact: public-qt-comments@w3.org

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.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 30 January 2013 22:12:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:41 UTC