29226 2015-10-22 10:41:06 +0000 [xt30] Empty enclosed expressions 2015-11-05 21:25:10 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Last Call drafts PC All CLOSED FIXED P2 normal --- 1 mike mike abel.braaksma public-qt-comments oldest_to_newest 123840 0 mike 2015-10-22 10:41:06 +0000 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. 123859 1 abel.braaksma 2015-10-22 19:24:53 +0000 I assume you mean to allow this for dynamic AVT's, static AVT's and TVT's? I think it is a good thing. If I want to temporarily disable an expression, I have to wrap it now into smiley comments and add a "()" (empty sequence) expression to it, which is annoying (but by no means unsurpassable). 123861 2 abel.braaksma 2015-10-22 19:29:12 +0000 > 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) We may need to be explicit about whitespace; "nothing" is too broad (or narrow). For XPath whitespace is clearly defined, but we now say "optional XPath expression", so we must be clear about what it is when it is not an XPath expression. 124009 3 mike 2015-10-30 12:31:54 +0000 The changes were accepted, and have been applied to the spec (in a way that answers the questions raised in comments on this bug). The bug remains open to allow the WG to review and approve the changes. 124107 4 mike 2015-11-05 18:43:41 +0000 The change was approved.