This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Evaluating a node-set with select (MSXSL vs. Saxon)
- From: David Carlisle <davidc at nag dot co dot uk>
- To: xsl-list at lists dot mulberrytech dot com
- Cc: wapiez at mulberrytech dot com, xsl-list at lists dot mulberrytech dot com
- Date: Fri, 19 Apr 2002 09:03:27 +0100
- Subject: Re: [xsl] Evaluating a node-set with select (MSXSL vs. Saxon)
- References: <4F99A6F46351D511B6EB00508BAC7F0BA5BED2@fcgmail3.fcg.com>
- Reply-to: xsl-list at lists dot mulberrytech dot com
> Ouch! Does this mean that I have to stop using Saxon as my "conformance
> checker?" :-)
No, just update your saxon.
Saxon 6 implements the (now defunct) XSLT 1.1 draft which did allow
silent conversion of rtf variables to node sets.
However since the 1.1 draft was frozen the later versions of 6.5.x
force you to put version="1.1" on your xsl:stylesheet element to get
this behaviour, and go back to complaining about this use if you use
version="1.0".
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list