Yes, this is correct behaviour. Backwards compatibility mode affects the
result of certain 1.0 constructs (for example, it causes xsl:value-of to
ignore all but the first selected item) but it does not affect the way a
2.0 processor handles 2.0 constructs.
Michael Kay
Saxonica
On 10/09/2012 10:54, Ihe Onwuka wrote:
I have just encountered code that uses the copy-namespace attribute on
a stylesheet that is being processed with an XSLT 2.0 processor but
has the xsl:stylesheet version attribute set to 1.0.
It runs without complaint (although with data that does not exercise
that precise piece of code), is this correct behaviour when running in
backward compatibility mode.
ihe
--~------------------------------------------------------------------
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>
--~--