- From: <bugzilla@jessica.w3.org>
- Date: Sun, 12 Oct 2014 14:05:51 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27026 Bug ID: 27026 Summary: [XSLT30] EBNF incompatibility between XP31 MapConstructor and XSLT30 MapExpr Product: XPath / XQuery / XSLT Version: Last Call drafts Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: XSLT 3.0 Assignee: mike@saxonica.com Reporter: abel.braaksma@xs4all.nl QA Contact: public-qt-comments@w3.org In XP31 the MapConstructor is defined as: MapConstructor ::= "map" "{" (MapConstructorEntry ("," MapConstructorEntry)*)? "}" MapConstructorEntry ::= MapKeyExpr ":" MapValueExpr In XSLT30 the MapExpr is defined as: MapExpr ::= "map{" (KeyExpr ":" ValueExpr ("," KeyExpr ":" ValueExpr )*)? "}" Functionally, these are equal. However, the XP31 production allows a space between the keyword "map" and the opening curly (the production is not marked ws-explicit), whereas XSLT30 does not allow such space. I propose to allow that space in XSLT30 as well: MapExpr ::= "map" "{" (KeyExpr ":" ValueExpr ("," KeyExpr ":" ValueExpr )*)? "}" -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 12 October 2014 14:05:52 UTC