W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2012

[Bug 19658] New: XQST0070 and EQNames (probably editorial)

From: <bugzilla@jessica.w3.org>
Date: Mon, 22 Oct 2012 18:16:42 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-19658-523@http.www.w3.org/Bugs/Public/>

          Priority: P2
             Group: XSLXQuery_WG
            Bug ID: 19658
          Assignee: jonathan.robie@gmail.com
           Summary: XQST0070 and EQNames (probably editorial)
        QA Contact: public-qt-comments@w3.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: josh.spiegel@oracle.com
          Hardware: PC
            Status: NEW
           Version: Proposed Recommendation
         Component: XQuery 3.0
           Product: XPath / XQuery / XSLT

In meeting 453, there was this decision:
DECISION: Prohibit the xmlns namespace in EQNames.  Raise the error 
XQST0070 in this case.

The change log for the specification has this entry:
"Prohibited the xmlns namespace in EQNames. Resolves Bug 10869."

Problem 1: In section Node Tests, the following sentence has a typo:
  "It is a static error [err:XQST0070] if the for an EQName is

Problem 2: Based on the log and the recorded decision, it seems like the intent
is that this namespace should not be used in any EQName.  I don't see how
XQST0070 is prescribed in some cases.  For example, should the following query
raise XQST0070?

declare variable $Q{http://www.w3.org/2000/xmlns/}foo := 1;

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 22 October 2012 18:16:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:50 UTC