This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28701 - Use of NCName in KeySpecifier underspecified?
Summary: Use of NCName in KeySpecifier underspecified?
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: SGI Windows NT
: P2 minor
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-26 15:21 UTC by Priscilla Walmsley
Modified: 2015-07-04 18:36 UTC (History)
2 users (show)

See Also:

Attachments

Description Priscilla Walmsley 2015-05-26 15:21:46 UTC 
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?
Comment 1 Andrew Coleman 2015-06-12 11:15:03 UTC 
At the teleconference on 2015-06-09, the Working Group agreed to make this fix (editorial).