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 29673 - [XSLT30] small typos in the section on classifying expressions
Summary: [XSLT30] small typos in the section on classifying expressions
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Member-only Editors Drafts
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-27 19:57 UTC by Abel Braaksma
Modified: 2016-10-06 18:42 UTC (History)
0 users

See Also:

Attachments

Description Abel Braaksma 2016-05-27 19:57:35 UTC 
In section 19.8.8 Classifying Expressions, bottom of the list, there are a few entries with references to the production rule that start with a comma (,).

MapConstructor [,69]
Lookup (Postfix [,49] and Unary [,53])
ArrowExpr [,29]
SquareArrayConstructor [,74]
CurlyArrayConstructor [,75]

I think the comma is superfluous, unless it was intended to signify these productions only appear in XP31.
Comment 1 Abel Braaksma 2016-05-27 20:20:34 UTC 
Note, the same happens in 19.1 Determining the Static Type of a Construct (bottom of the table).
Comment 2 Michael Kay 2016-06-02 20:14:00 UTC 
The notation used was chosen deliberately to highlight the absence of a production rule in XPath 3.0
Comment 3 Michael Kay 2016-06-09 16:31:20 UTC 
Decided it would probably be best to use an ndash or mdash.

Note also a small typo above the table: For “also given for new constructs introduced by XPath 3.1..” read “also given for new constructs introduced by XPath 3.1.” - doubled full stop.
Comment 4 Michael Kay 2016-06-09 22:27:29 UTC 
Replaced the notation [,91] by [-,91] where the "-" is an en dash.

No change log entry.