[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Can an XSLT 3.0 stylesheet access the complete se
On 14.01.2020 10:25, Martin Honnen martin.honnen@xxxxxx wrote:
Am 13.01.2020 um 13:27 schrieb Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx: b& As you observed, with XProc 3.0, when using p:xslt in XSLT-3.0 mode, a transformation that is invoked without an initial template is supposed to process each document of the input sequence individually. The default collection is undefined. Yes, the version attribute is the premier way to enforce a certain behavior. Without it, the XProc processor will determine a version for you. Most likely it will look at the top-level stylesheetbs version attribute.
If the XProc processor uses Saxon 9.8+, it has the liberty to bail out if XSLT 2 is explicitly requested, claiming that the XSLT processor at hand does not support XSLT 2. This would be a stupid thing to do though because, as is stated in the Saxon documentation: bXSLT 3.0 has a very high level of backwards compatibility with XSLT 2.0, so all existing stylesheets should continue to run. The only significant difference when you process a 2.0 stylesheet with a 3.0 processor is that you will no longer get errors if you use constructs that are permitted in 3.0 but not in 2.0.b So the XProc processor will probably declare that it will use Saxon for XSLT 2 processing, with the specified bahavior for XSLT 2 operation: All source port documents go into the default collection all of the time; process only the first document in sequence in the absence of the template-name option. It will refer to the Saxonica documentation with respect to the few possible restrictions when running an XSLT 2 stylesheet with Saxon 9.8+.
Yes. Keep in mind though that the XProc processor is not required to use any version of Saxon at all. In practice, the next version of XML Calabash will be closely intertwined with Saxon 9.9 while I think Morgana XProc III will still offer Saxon support as an add-on (with no other viable options for a readily available XSLT 2 or 3 processor AFAIK).
Ibd expect that an XProc processor that bundles Saxon 9.9 might get away with stating that it does indeed provide XSLT 2 support: By using the XSLT 3 processor with the specific provisions of https://spec.xproc.org/master/head/steps/#c.xslt.11 But I will raise an issue that we will discuss in the next editorial meeting (Jan 23). Others might be inclined to say that an XProc processor that bundles Saxon 9.9 may not claim that it provides XSLT 2 support at all. If this is the standpoint, an XProc processor may still offer a configuration option to bypass this rather pedantic check. Gerrit
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|