[Bug 17601] New: Importing XSLT function libraries

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 17601] New: Importing XSLT function libraries

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

           Summary: Importing XSLT function libraries
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3.1 Requirements and Use Cases
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]
         QAContact: [hidden email]


XQuery should have the ability to import and use functions from XSLT. It should
possibly also be able to use other things declared in the stylesheet, like
global variables/parameters, modes, etc.

This was part of an unmet requirement of XQuery 3.0:

http://www.w3.org/TR/xquery-30-requirements/#invocation-of-external-functionality

--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 17601] [XQ31ReqUC] Importing XSLT function libraries

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

--- Comment #1 from Jonathan Robie <[hidden email]> ---
We discussed this in meeting #523 and decided that this should be a "may".

<quote>
Q2.9.16 Bugzilla Bug 17601, [XQ31ReqUC] Importing XSLT function
libraries
See http://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

include in requirements document as a MAY
</quote>

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

Reply | Threaded
Open this post in threaded view
|

[Bug 17601] [XQ31] Importing XSLT function libraries

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

Jim Melton <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|XQuery 3.1 Requirements and |XQuery 3.1
                   |Use Cases                   |
            Summary|[XQ31ReqUC] Importing XSLT  |[XQ31] Importing XSLT
                   |function libraries          |function libraries

--- Comment #2 from Jim Melton <[hidden email]> ---
This bug has been redirected to the XQuery 3.1 document, as it has been
accepted as a requirement (a MAY requirement).

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

Reply | Threaded
Open this post in threaded view
|

[Bug 17601] [XQ31] Importing XSLT function libraries

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

--- Comment #3 from Jonathan Robie <[hidden email]> ---
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.
Reply | Threaded
Open this post in threaded view
|

[Bug 17601] [XQ31] Importing XSLT function libraries

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

Christian Gruen <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #4 from Christian Gruen <[hidden email]> ---
Thanks for the dicscussion. This is how it’s done in BaseX:
http://docs.basex.org/wiki/XSLT_Module

--
You are receiving this mail because:
You are the QA Contact for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug 17601] [XQ31] Importing XSLT function libraries

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

Adam Retter <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #5 from Adam Retter <[hidden email]> ---
I would comment that I am sure we have discussed this in great detail in the
past at the last Prague F2F (and perhaps even the one before that). The only
thing I will add, is that if I remember correctly (and I may well not), we put
this on hold until 'maps' was to be done. The reason being that many wanted to
pass parameters to the Transformation, and to be able to provide document nodes
etc, we needed a data structure that would not loose that identity information.

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

Reply | Threaded
Open this post in threaded view
|

[Bug 17601] [XQ31] Importing XSLT function libraries

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

Mary Holstege <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #6 from Mary Holstege <[hidden email]> ---
And, here is how MarkLogic does it: http://docs.marklogic.com/xdmp:xslt-eval
and http://docs.marklogic.com/xdmp:xslt-invoke

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

Reply | Threaded
Open this post in threaded view
|

[Bug 17601] [XQ31] Importing XSLT function libraries

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

--- Comment #7 from John Snelson <[hidden email]> ---
(In reply to Adam Retter from comment #5)
> I would comment that I am sure we have discussed this in great detail in the
> past at the last Prague F2F (and perhaps even the one before that). The only
> thing I will add, is that if I remember correctly (and I may well not), we
> put this on hold until 'maps' was to be done. The reason being that many
> wanted to pass parameters to the Transformation, and to be able to provide
> document nodes etc, we needed a data structure that would not loose that
> identity information.

The difference here is that we are considering this in the context of XQuery
3.1 where we have maps to be able to solve this.

Speaking for myself, I have a tiny brain with little recollection, and would
value any input you have on what the requirements or details for such an API
would look like. In particular, are you hoping to simply "eval" an XSLT
stylesheet, or do you also have aspirations to be able to import XSLT function
libraries etc.

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

Reply | Threaded
Open this post in threaded view
|

[Bug 17601] [XQ31] Importing XSLT function libraries

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

O'Neil Delpratt <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #8 from O'Neil Delpratt <[hidden email]> ---
Created attachment 1497
  --> https://www.w3.org/Bugs/Public/attachment.cgi?id=1497&action=edit
Importing XSLT in XQuery

proposal attached

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

Reply | Threaded
Open this post in threaded view
|

[Bug 17601] [XQ31] Importing XSLT function libraries

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

Michael Kay <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #9 from Michael Kay <[hidden email]> ---
A specification for the fn:transform() function has been added to the spec and
accepted as status quo by the working group, while requesting members to review
it carefully.

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

Reply | Threaded
Open this post in threaded view
|

[Bug 17601] [XQ31] Importing XSLT function libraries

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17601

Michael Kay <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #10 from Michael Kay <[hidden email]> ---
Note that although the proposed function does not import XSLT functions into
the static context as originally suggested, it does make XSLT functions
callable from XQuery and this has been deemed to satisfy the requirement.
Closing accordingly.

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