This is because they(the fxsl stylesheets) depend on a node-set()
function which is an extension function under xslt 1.0
Exslt has a node-set() function in the exsl namespace so that one could
be processor independent, at least if processors used support exsl.
The native xalan node-set() function is named nodeset() if I remember
correctly (I keep saying that cause it's a hell of a long time since I
used xalan), which means that it is not name-compatible with others.
Most processors have node-set() so that if what one needs to do is just
use node-sets one can have the following
ns:node-set($mynode)
and then bind the ns prefix to whichever node-set implementation one
wants.
Fxsl could have used fallbacks etc., I suppose, to make it all processor
independent, not sure why this wasn't done other than not wasting
processing power.
-----Original Message-----
From: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
[mailto:owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com] On Behalf Of
Robert P. J.
Day
Sent: Friday, March 21, 2003 12:37 PM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: [xsl] A list of useful functions that aren't in the core of
xsl.
On Fri, 21 Mar 2003, bryan wrote:
http://fxsl.sourceforge.net/
http://www.exslt.org/
these are complimentary. Fxsl implements functions in xslt, exslt
defines a list of functions and implementation guidelines so that one
can have extention functions not otherwise in the core. Saxon and if I
remember correctly Xalan both implement the exslt core functions.
having just looked at the FXSL sourceforge site, i'm intrigued by
the fact that there are three different .zip files; for MS, Saxon
and Xalan, respectively.
i'm just about to take a look at FXSL, but is there some reason
that functions written in XSLT would need to be processor
dependent? curious.
rday
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list