W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2015

[Bug 28701] New: Use of NCName in KeySpecifier underspecified?

From: <bugzilla@jessica.w3.org>
Date: Tue, 26 May 2015 15:21:46 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28701-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 28701
           Summary: Use of NCName in KeySpecifier underspecified?
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3.1
          Assignee: jonathan.robie@gmail.com
          Reporter: pwalmsley@datypic.com
        QA Contact: public-qt-comments@w3.org

The meaning of using an NCName as a KeySpecifier feels underspecified to me.  

It says "If the KeySpecifier is not a wildcard ("*"), the semantics of the
UnaryLookup operator are as follows: Let KS denote the items in the sequence to
which the KeySpecifier evaluates."

If KeySpecifier is an NCName, for example ?foo, what are "the items in the
sequence to which the KeySpecifier evaluates"? 

It seems clear from the examples that that NCName foo would result in KS being
a single xs:string value ("foo"). But should the spec rely on examples to show
the intent?  Or maybe I'm missing something?

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 26 May 2015 15:21:47 UTC

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