This is the mail archive of the xsl-list@mulberrytech.com mailing list .

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: xt:node-set usage (was Re: Future XSLT expansion.)

To: xsl-list at mulberrytech dot com
Subject: Re: xt:node-set usage (was Re: Future XSLT expansion.)
From: David Carlisle <davidc at nag dot co dot uk>
Date: Sun, 19 Mar 2000 21:41:24 GMT
References: <3.0.6.32.20000319111302.00862730@postoffice.worldnet.att.net> <008901bf91c7$324a1ae0$0200a8c0@ne.mediaone.net>
Reply-To: xsl-list at mulberrytech dot com


> Because of this I can only use core XSLT functions that are required
> to be in all XSLT implementations.

although in this case xt saxon xalan msxml all offer this functionality
(MS not quite legally) and it is possible within a conforming stylesheet
to ask if the function is available. So it is probably hard to find an
XSL system where you can not coerce a result tree to a node set, and 
you can still do it while writing a valid xslt stylesheet.

David
 


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

References:
- xt:node-set usage (was Re: Future XSLT expansion.)
  - From: Tom Myers
- Re: xt:node-set usage (was Re: Future XSLT expansion.)
  - From: Jon Smirl

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]