Saxon already allows the second of these two:

http://www.saxonica.com/documentation/extensions/instructions/import-query.h
tml

The only real difficulty with the first (calling XSLT from XQuery) is
working out how things like import precedence should fit into the picture.

There's no difference in the data models and type systems used by XSLT and
XQuery, so there's no reason why they shouldn't interoperate at this kind of
level.

Michael Kay
http://www.saxonica.com/
 

> -----Original Message-----
> From: Robert Koberg [mailto:[email protected]] 
> Sent: 11 July 2008 13:41
> To: xml-dev
> Subject:  xquery and xsl
> 
> Hi,
> 
> What are the impediments to using the same internal tree for 
> both XQuery and XSL? Do the respective processors require 
> different types of trees?
> 
> Wouldn't it be lovely if you could do:
> 
> import module namespace 
> xsl="http://www.w3.org/1999/XSL/Transform" at "view.xsl";
> 
> and then use:
> 
> xsl:apply-templates(nodes [, "some-mode", ((param1=x), (param2=y))])
> 
> Similary in XSL:
> 
> <xsl:import href="controller.xq"/>
> 
> and call out to XQuery functions.
> 
> Will the two ever be able to couple or are their interfacing 
> parts incompatible?
> 
> best,
> -Rob
> 
> 
> 
> ______________________________________________________________
> _________
> 
> XML-DEV is a publicly archived, unmoderated list hosted by 
> OASIS to support XML implementation and development. To 
> minimize spam in the archives, you must subscribe before posting.
> 
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: [email protected]
> subscribe: [email protected] List archive: 
> http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>