- From: <bugzilla@jessica.w3.org>
- Date: Thu, 22 Oct 2015 10:41:06 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29226
Bug ID: 29226
Summary: [xt30] Empty enclosed expressions
Product: XPath / XQuery / XSLT
Version: Last Call drafts
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: XSLT 3.0
Assignee: mike@saxonica.com
Reporter: mike@saxonica.com
QA Contact: public-qt-comments@w3.org
Target Milestone: ---
XQuery has adopted a proposal to allow empty enclosed expressions, e.g.
<a b="some { (:absent:) } content"/>
Should we do the same?
We don't define value templates using a grammar, so the change required would
be in 5.6:
Change:
A variable part consists of an XPath expression enclosed in curly brackets
({}).
to
A variable part consists of an optional XPath expression enclosed in curly
brackets ({}).
Change:
It is a static error if the string contained between matching curly brackets in
a value template does not match the XPath production ExprXP30
to
It is a static error if the string contained between matching curly brackets in
a value template does not match the XPath production ExprXP30? (that is, an
expression or nothing)
Change:
The expansion of a variable part is obtained by evaluating the enclosed XPath
expression and converting the resulting value to a string
to
The expansion of a variable part is obtained as follows:
* If the variable part contains an expression, [current text]
* Otherwise, the result is a zero-length string.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 22 October 2015 10:41:10 UTC