Saxon

XSLT Version information is pretty widely scattered. Here's the result of a survey:

On StyleElement, version, and the getEffectiveVersion() method, return the value of the [xsl:]version attribute on the nearest ancestor element that has such an attribute.

On StylesheetPackage, version and getVersion() are the value of the version attribute on the root xsl:package or xsl:stylesheet element.

On CompilerInfo, xsltVersion and getXsltVersion() give the requested processor version: 0.0 meaning no specific version requested, or 2.0 or 3.0. If no specific version was requested, then the value is set to the actual value of the version attribute on the root element of the stylesheet as soon as it is read. (This seems a dubious thing to do: can't a CompilerInfo object be reused for multiple compilations?)

On Compilation, stylesheetVersion and getStylesheetVersion give the actual value of the version attribute on the root element of the stylesheet. As far as I can see, this is set when processing the root element of any stylesheet module, which seems wrong, because an included/imported module is processed using the same Compilation object as its includer/importer.

On StyleNodeFactory, processorVersion and getProcessorVersion give the same as CompilerInfo.getXsltVersion(), provided that the StyleNodeFactory was obtained from the Compilation object. (In other cases, it generally returns null).

On StyleElement, the method isXslt30Processor (which is what we are calling on this path) calls StyleElement.getProcessorVersion(), which constructs a new StyleNodeFactory from the Compilation object, and returns the value of getProcessorVersion() on this StyleNodeFactory; this therefore gives the result of getXsltVersion() on the CompilerInfo.

I am now satisfied with the patch and am committing it on the 9.6 and 9.7 branches.

Bug fix patch applied to the Saxon 9.6.0.3 maintenance release