[xquery-talk] [Announce] XQilla version 1.1.0 released

Andrew Welch andrew.j.welch at gmail.com
Tue Sep 4 15:03:08 PDT 2007

On 9/4/07, David Carlisle <davidc at nag.co.uk> wrote:
> > The point I was trying to make was that XQuery + XML DB should be able
> > to select nodes far faster than XSLT + REST API, so the ideal
> > combination is XSLT + XQuery extension function.
> why does it have to be an extension function? XQuey and XSLT difer
> mainly in surface syntax so if the XQuery engine can be hooked up to a
> DB rather than an in memory tree, it's surely not impossible for the
> Xpath that's embedded in XSLT to access a database in teh same way is
> it?

I was thinking about that (perhaps implementing Saxon's NodeInfo to
work on the XQuery data model) but I don't think its needed... (and I
may be talking nonsense there)

All that's needed is a high level way to select from the db - thats
it.  Whether it's through passing an XQuery to an extension function
that returns each tuple as an item in a sequence, or using a REST
interface that returns each tuple as element in a document, once you
have that then the rest of the processing can be done using standard

> > I was wondering though if XQuery is even needed - if there was an XSLT
> > extension function that took three arguments:
> >
> > xmldb($db-uri, $collection, $xpath)
> why not just
> collection('some-uri-representing-the-db')/the/xpath/query/you/want)

You need to specify the collection in the db, unless you can wedge it
into the uri somehow.

But either way, I reckon passing an XQuery to the XQuery engine is the
way to go.  It seems like it should be straightforward to do...

Andrew Welch
Kernow: http://kernowforsaxon.sf.net/

More information about the talk mailing list