(Sorry to everyone for letting this through twice - it often happens when someone posts, gets bounced because they are not subscribed, then subscribes and posts again).
I would really like to get rid of this warning completely rather than working out how to let users suppress it. The spec says (3.6) "the processor SHOULD output a warning advising the user of possible incompatibilities, unless the user has requested otherwise. "
I'm inclined to disobey this SHOULD when the XSLT compilation is invoked from an API. (I can regard the act of invoking the API as a "request to do otherwise", if that's what the API is specified to do...) Instead it would seem to be more useful to provide an interrogative so the user can determine what the version attribute on the stylesheet was, and decide themselves whether they want to take action on this.
Michael Kay

From: saxon-help-bounces@lists.sourceforge.net [mailto:saxon-help-bounces@lists.sourceforge.net] On Behalf Of Nimoh, Kofi (Harvey Nash)
Sent: 28 November 2007 11:02
To: saxon-help@lists.sourceforge.net
Subject: [saxon] Suppressing the XSLT 1.0 stylesheet with an XSLT 2.0processor (SAXON.NET)


Anyone know how to suppress the warning emitted when I try to run an XSLT1.0 stylesheet with SAXON.NET?  I have found some stuff whilst searching on the web to do with the command line -novw flag and/or using the list  of "FeatureKeys" suported with the "TransformerFactory" class.  I am using the cross-compiled .NET version of SAXON though and the API is different, and I can't  use the "-novw" flag because I need to set this in code?

And no, I don’t want to set version="2.0"!