- From: <bugzilla@jessica.w3.org>
- Date: Sun, 05 Jul 2015 20:01:26 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28896
Bug ID: 28896
Summary: [xp3.1] EQName definition
Product: XPath / XQuery / XSLT
Version: Last Call drafts
Hardware: PC
OS: All
Status: NEW
Severity: minor
Priority: P2
Component: XPath 3.1
Assignee: jonathan.robie@gmail.com
Reporter: mike@saxonica.com
QA Contact: public-qt-comments@w3.org
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 5 July 2015 20:01:29 UTC