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 21575 - [XP3.0] Operator precedence table
Summary: [XP3.0] Operator precedence table
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC All
: P2 normal
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: 2013-04-03 21:59 UTC by Michael Kay
Modified: 2014-12-12 23:59 UTC (History)
0 users

See Also:

Attachments

Description Michael Kay 2013-04-03 21:59:12 UTC 
Section A.4 says: "The grammar in A.1 EBNF normatively defines built-in precedence among the operators of XQuery. "

For XQuery read XPath.

Furthermore, the new string concatenation operator is missing from the table.
Comment 1 Jonathan Robie 2013-04-16 15:37:26 UTC 
This is editorial. I will fix this.
Comment 2 Michael Kay 2014-09-16 18:50:49 UTC 
Reopening. This problem is still present in the published XPath 3.0 specification, and is also present in the current XPath 3.1 draft.
Comment 3 Jonathan Robie 2014-09-30 21:01:29 UTC 
I have fixed the XML so that this reads XPath in the XPath spec, XQuery in the XQuery spec.

But the table seems to contain the operator in XQuery/XPath 3.0 and XQuery/XPath 3.1.  What am I missing?

http://www.w3.org/TR/xquery-30/#id-precedence-order
http://www.w3.org/TR/xpath-30/#id-precedence-order
http://www.w3.org/TR/xquery-31/#id-precedence-order
http://www.w3.org/TR/xpath-31/#id-precedence-order

In all cases, it occurs in row #6.
Comment 4 Michael Kay 2014-09-30 21:55:52 UTC 
I guess I didn't see it because (a) it's not a very prominent symbol, and (b) I was looking in the wrong place.