RE: Re: The Perils of Sudden Type-Safety in XPath 2.0

> I would think that if you set your 
> version to 1.0, it would support only 1.0 elements, and not 
> provide the other functionality available in 2.0 specs. It 
> seems to me a better solution would be another kind of 
> switch, like, XPath = "1.0" and XPath = "2.0" within the 
> stylesheet element.

That's one viewpoint, and the XSL WG hasn't yet made a decision on this.

However, if you want to write a stylesheet that can run under both 1.0
and 2.0 processors, then it has to be a legal XSLT 1.0 stylesheet, and a
stylesheet that contained the attribute XPath="1.0" would not be.

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx 


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