W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2010

[Bug 9070] Invoking XQuery from XSLT

From: <bugzilla@jessica.w3.org>
Date: Wed, 12 May 2010 13:30:39 +0000
To: public-qt-comments@w3.org
Message-Id: <E1OCC1H-0000r7-NN@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9070





--- Comment #2 from Michael Kay <mike@saxonica.com>  2010-05-12 13:30:39 ---
The XSL WG has just published its FPWD of XSLT 2.1, and all work on
enhancements was put on hold until that was done.

The direction I'm most inclined to pursue is (2): perhaps a new declaration of
the form <xsl:import-library language="xquery" href="location-uri"/> which
imports the functions and global variables from the specified XQuery library
module, with lower import precedence than the importing module. There are
obviously details to be sorted out (such as whether it makes sense to specify a
module URI as well as or instead of a location URI) but it shouldn't be too
difficult. It would have to be an optional feature.

Doing (3) has all sorts of complications because XQuery is not XML. There are
other XML-based languages that would like to embed XQuery, for example XForms,
and if a suitable (XML-based but human-readable) representation of XQuery were
defined, then we could consider using it embedded in XSLT.

We've now got dynamic XPath evaluation in XSLT 2.1, and my feeling is that
meets enough of the requirement to make dynamic XQuery evaluation unnecessary
for the time being.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 12 May 2010 13:30:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:42 UTC