Can anyone speculate about other areas where this behavior could
cause pain?  Most importantly, can anyone imagine stylesheets
that do *not* use node-set() extensions and do *not* expect the
RTF to be a node-set, but are tripped up by the fact that
MSXML assumes it is?  I want to make sure I give this a complete
treatment in the FAQ..

Thanks,
Joshua

> -----Original Message-----
> From: Kay Michael [mailto:Michael.Kay@xxxxxxx]
> Sent: Wednesday, August 02, 2000 10:56 AM
> To: 'xsl-list@xxxxxxxxxxxxxxxx'
> Subject: RE: node-set() function in MSXML?
> 
> 
> > I tried your stylesheet with Saxon and with MSXML3, and it 
> > worked for both.
> > However, I still don't entirely trust it.  Is it really safe 
> > to assume that
> > the processor will not choke on the attempt to access an RTF 
> > as a node-set
> > because it won't come across that code at run-time?  
> > Especially if we're
> > talking about compiling stylesheets--that's where I'd have my 
> > doubts about
> > this stylesheet's portability. 
> 
> The stylesheet is portable among a finite set of known XSLT 
> processors.
> Which is better than not being portable at all.
> 
> Mike 
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


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