[Bug 27189] [XSLT30] xsl:copy on-empty and document nodes ambiguities

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27189

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Michael Kay <mike@saxonica.com> ---
The WG agreed to make changes as defined in message

https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Nov/0027.html
(member-only link)

The effect of the changes is, in summary:

(1) Drop the existing on-empty attribute from the instructions on which it
appears

(2) Introduce a new instruction xsl:on-empty which is evaluated only if the
result of the containing sequence constructor would otherwise be an empty
sequence

(3) Introduce a new instruction xsl:on-non-empty which is evaluated only if the
result of the containing sequence constructor would otherwise be a non-empty
sequence

(4) Introduce a new instruction xsl:conditional-content whose effect is to
filter the results of evaluating its contained sequence constructor, by
removing any items with "empty content". For document and element nodes this is
defined to mean "no child nodes", for other items it is defined to mean
string(.) = "".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 18 December 2014 21:27:11 UTC