This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29800 - [FO31] fn:load-xquery-module, fn:transform
Summary: [FO31] fn:load-xquery-module, fn:transform
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2016-08-30 13:16 UTC by Tim Mills
Modified: 2016-12-16 19:55 UTC (History)
0 users

See Also:


Description Tim Mills 2016-08-30 13:16:27 UTC
These functions are classified as "context-independent", however the text states of the stylesheet-location option that "If the value is a relative reference, it is resolved against the static base URI of the fn:transform function call." i.e. it depends on the static context.

I'd guess (although it isn't stated) that in a call to fn:load-xquery-module, a relative $module-uri would be resolved against the static base URI of the function call, making fn:load-xquery-module similarly context-dependent.

Also, if the fn:transform/fn:load-xquery-module function is unsupported by the host language or explicitly disabled by the user, is err:FOXT0001/err:FOQM0006. the appropriate error to raise?
Comment 1 Michael Kay 2016-09-06 16:26:21 UTC

1. We agree.

2. Module URIs are namespace URIs therefore relative URIs are deprecated and not resolved.

3. Yes.

We need test cases for processors that don't support the function except by throwing an error.
Comment 2 Michael Kay 2016-09-06 19:42:50 UTC
I have labelled this functions as context-dependent, and I have expanded the descriptions of error cases to include these.

(Note that FOXT0004 should be used when the fn:transform function has been disabled)
Comment 3 Tim Mills 2016-09-07 12:40:26 UTC
I have added tests.