fn:transform(): source-node and global context item
See also bug #4768.
I think that Saxon/J, and test case fn-transform-82e, are misinterpreting the spec.
fn:transform() requests an XSLT 2.0 processor, and if no XSLT 2.0 processor is available, but an XSLT 3.0 processor is available, then the function executes with an XSLT 3.0 processor. This is the situation with Saxon 10, which no longer offers XSLT 2.0 processing as an option.
The question then is whether the "global-context-item" option to fn:transform() should be ignored. The wording in the spec is:
For invocation of an XSLT 2.0 processor (see [XSL Transformations (XSLT) Version 2.0]), the supplied options must include all of the following (if anything else is present, it is ignored):
followed by another section:
For invocation of an XSLT 3.0 processor...
Which of these two sections applies? I think it is the one relevant to the processor version that is actually invoked, not the one that is requested. With this interpretation, the
global-context-item option in fn-transform-82e should not be ignored.
#1 Updated by Michael Kay about 1 year ago
- Category set to XSLT conformance
- Status changed from New to Resolved
- Priority changed from Low to Normal
- Applies to branch 10, trunk added
- Fix Committed on Branch 10, trunk added
I raised a test bug at
and have modified the test case accordingly.
Changed TransformFn (case "global-context-item" on line 682) so it always takes account of the option if present, rather than ignoring it if a 2.0 processor was requested.
Please register to edit this issue