- From: <bugzilla@jessica.w3.org>
- Date: Wed, 29 Oct 2014 12:28:32 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27189
Bug ID: 27189
Summary: [XSLT30] xsl:copy on-empty and document nodes
ambiguities
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
The spec says two things in 11.9.1.1:
(1) "If the selected item is not an element node, the attribute has no effect,
except that static errors must be reported and type errors may be reported."
(2) "If the result of the instruction in the absence of the on-empty attribute
would be an element or document node ...."
While I think it is possible to create a document node inside xsl:copy, it
would be a document-node as a child of a copied element node, which would be
ignored and it won't change the item type.
There are two ways to solve this ambiguity:
1) remove the reference to document nodes in quote (2)
2) allow document node creation and allow the on-empty type to be document-node
The second solution has the preference (see mail 0057.html below), but if we
allow that, we also need to make sure that the type of on-empty is the same as
the type of the selected item.
This bug is created as a result of WG email discussion, see
- https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Oct/0056.html (member
only)
- https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Oct/0057.html (member
only)
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 29 October 2014 12:28:34 UTC