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

[Bug 29141] [XSLT30] fn:snapshot and fn:copy-of talk about node (singular), where the signature allows nodes

From: <bugzilla@jessica.w3.org>
Date: Wed, 23 Sep 2015 20:58:29 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29141-523-KS4cQbjpHT@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29141

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
Yes, the change to make these functions work on sequences of nodes was clearly
only implemented partially.

John Lumley also points out that we ought to be clear in the case where the
same node is present more than once in the input sequence whether the output
sequence will also contain the same node more than once, or whether each gets a
different copy, or whether this is implementation-dependent. In keeping with
the use of new-each-time="maybe", I think it should be
implementation-dependent. 

More complex scenarios are also possible, where the input sequence to copy() or
snapshot() contains a node N and also one or more of its ancestor or descendant
nodes. We could either allow the result to contain overlapping copies in this
case, or we could insist that in the result of copy-of, each node is parentless
and siblingless, and in the result of snapshot, each node is siblingless (which
would imply multiple copies).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 23 September 2015 20:58:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 23 September 2015 20:58:34 UTC