[saxon] Warning: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor

[Andrew Welch]

I'm currently getting in standard out:

"Warning: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor"

...and yet I'm sure all the stylesheets state version="2.0" - is there
any other reason Saxon might think I'm using v1.0 stylesheets?

thanks
andrew

[Michael Kay]

This warning should only be output if the xsl:stylesheet element of the
principal stylesheet module specifies version="1.0". If you're convinced
that's not the case, could I see it please?

Michael Kay
Saxonica Limited

-----Original Message-----
Andrew Welch
Sent: 06 January 2005 16:03
Subject: [saxon] Warning: Running an XSLT 1.0 stylesheet with
an XSLT 2.0 processor
"Warning: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor"
...and yet I'm sure all the stylesheets state version="2.0" - is there
any other reason Saxon might think I'm using v1.0 stylesheets?
thanks
andrew
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
saxon-help mailing list
https://lists.sourceforge.net/lists/listinfo/saxon-help

[Andrew Welch]

Post by Michael Kay
This warning should only be output if the xsl:stylesheet
element of the principal stylesheet module specifies
version="1.0". If you're convinced that's not the case, could
I see it please?

Yes, sorry about the short (and premature) email but it was so strange
as there were only so many stylesheets to check. As it turns out there
was a hard-coded indentity transform within the app that hadn't been
updated. Sorry for the noise.

andrew

[Michael Kay]

Post by Andrew Welch

Post by Michael Kay
This warning should only be output if the xsl:stylesheet
element of the principal stylesheet module specifies
version="1.0". If you're convinced that's not the case, could
I see it please?

Yes, sorry about the short (and premature) email but it was so strange
as there were only so many stylesheets to check. As it turns
out there
was a hard-coded indentity transform within the app that hadn't been
updated. Sorry for the noise.

As it happens, I'm not particularly happy about outputting this warning: I
think it's likely to cause unnecessary anxiety about the level of
compatibility. There are now very few cases indeed where a 2.0 processor in
1.0 mode produces different results from a 1.0 processor. But the spec says
I have to output the warning, so I do. It perhaps has the unintended benefit
of encouraging people to move faster to running in pure 2.0 mode.

Michael Kay
http://www.saxonica.com/