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 28896 - [xp3.1] EQName definition
Summary: [xp3.1] EQName definition
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.1 (show other bugs)
Version: Last Call drafts
Hardware: SGI All
: 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-07-05 20:01 UTC by Michael Kay
Modified: 2015-07-14 18:48 UTC (History)
1 user (show)

See Also:


Attachments

Description Michael Kay 2015-07-05 20:01:26 UTC
In section 2 Basics, third bullet under production [118], we read:

In this case the local name and namespace URI are as written, and the prefix is absent. This way of writing a QName is context-free, which makes it particularly suitable for use in queries|expressions that are generated by software. This form is a .

The last sentence is unfinished.

Also, this paragraph fails to explain that if there is nothing between the curly braces, e.g. Q{}local, then the namespace URI is absent.

Also, I suspect that "queries|expressions" should be "queries" in XQuery and "expressions" in XPath.

Just above production [112] appears "In the XQuery|XPath grammar" which is probably the same problem.
Comment 1 Josh Spiegel 2015-07-14 15:40:04 UTC
Fixed.