My first reaction was why is this a premium feature (it is until 3.0
reaches the cheap seats).
My subsequent reaction is surprise the content models ever differed in
the first place.
On Thu, Mar 27, 2014 at 7:20 AM, Michael Kay <mike(_at_)saxonica(_dot_)com>
wrote:
On 27 Mar 2014, at 01:40, Ihe Onwuka <ihe(_dot_)onwuka(_at_)gmail(_dot_)com>
wrote:
The select clause on xsl:copy requires XSLT 3.0 - it didn't matter in
my case as I was only copying an attribute and got the same effect
with copy-of.
The content models for the respective commands are otherwise
symmetrical. Why the sudden departure?
Do you mean, why was the select attribute added to xsl:copy in XSLT 3.0?
You can find the rationale here:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=6848
Michael Kay
Saxonica
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--