W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2015

[Bug 28888] [xslt 3.0] xsl:on-empty with xsl:value-of

From: <bugzilla@jessica.w3.org>
Date: Thu, 09 Jul 2015 23:49:01 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28888-523-pjQxrOl1JC@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28888

--- Comment #3 from Michael Kay <mike@saxonica.com> ---
I propose the following changes:

(a) if an xsl:on-empty instruction appears in a sequence constructor then (i)
it must be the only xsl:on-empty instruction in the sequence constructor, and
(ii) it must not be followed by any other instructions, with the exception of
xsl:fallback. (It may however be followed by non-instructions such as xsl:catch
if the context permits).

(b) an xsl:on-empty instruction is evaluated if and only if there is no
preceding instruction in the sequence constructor whose evaluation produces a
substantive result. For this purpose a result is substantive if it is not any
of the following:

b(i) an empty sequence
b(ii) a text node whose string value is zero length
b(iii) a document node having no children

[Note: the significance of these choices is that these values have no effect in
the common case where the sequence constructor is used for constructing the
content of nodes: see *Constructing complex content* and *Constructing simple
content*.]

(c) xsl:on-non-empty can continue to appear anywhere, and repeatedly. The rules
change to:

an xsl:on-non-empty instruction is evaluated if and only if there is an
instruction in the sequence constructor, other than an xsl:on-empty or
xsl:on-non-empty instruction, whose evaluation produces a substantive result
[defined as above].

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 9 July 2015 23:49:04 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 9 July 2015 23:49:04 UTC