[Bug 17601] [XQ31] Importing XSLT function libraries

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

--- Comment #3 from Jonathan Robie <jonathan.robie@gmail.com> ---
Minutes from today's meeting:

John suggests using packaging to define the semantics of importing
XSLT function libraries.

Jonathan suggests defining a function that specifies the stylesheet
(as a node or a URI), the instance to be transformed (as a node or a
URI), and a map with the XSLT 2.0 parameters.  Perhaps this is the
minimum required to declare victory?

Decided:

MUST: be able to invoke stylesheet with params in XQuery 3.1

SHOULD: XQuery 3.1 should have built-in support for calling functions in XSLT
3.0

MUST: recommend to the XSLT WG that XSLT 3.0 must define a way to
invoke functions

MUST: An XQuery top-level expression that invokes an XSLT
transformation MUST be able to access the (primary) result document of
that transformation and MAY be able to access any other documents
created by that transformation

MAY: be able to invoking xslt 2.0 functions from XQuery 3.1 using
semantics defined in XSLT 3.0 packaging

MUST: allow either a URI or a node to identify either a stylesheet or
content to be transformed

Action A-###-###: Mary to update her proposal based on the following
requirements (fold into the action item, except the XSLT 3.0
requirement)

Action A-###-###: Jim to forward the XSLT requirement to the XSLT WG.

Loren notes how Exist does this:

http://exist-db.org/exist/apps/fundocs/view.html?uri=http://exist-db.org/xquery/transform&location=java:org.exist.xquery.functions.transform.TransformModule

Josh may propose something along these lines:

declare %ora-xslt:binding(“file:/path/to/my.xslt”)  function
local:my-xslt-transform($input as document-node()) as document-node() external;

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 11 November 2013 10:06:36 UTC