[XSL-LIST Mailing List Archive Home]
[Reply To This Message]
Re: XSLT, Web applications, and "native XML databases"
Subject: Re: XSLT, Web applications, and "native XML databases"|
From: ac <ac@xxxxxxxxxxxxx>
Date: Thu, 08 Jan 2009 09:14:22 -0500
I agree with you, but we may need more than just collection(), as we
also need something like result-document to write documents back to the
db. doc() could be useful also, if only not to have to modify
file-based stylesheets to work with db documents. It would be nice to
only set the url protocol, for example, to enable direct database access.
What do you think?
as an experiment, some time ago, I was able to integrate Juxy
(http://juxy.tigris.org/) with eXist to do just what you have outlined
Andrew ... the result being I could apply individual xslt templates,
etc ... I never followed it up because I find working with XQuery and
XSLT to be a good match ... also I think at the time I could not get
Juxy working with an xslt 2 processor.
cheers, Jim Fuller
On Thu, Jan 8, 2009 at 11:09 AM, Andrew Welch <andrew.j.welch@xxxxxxxxx> wrote:
Andrew Welch wrote:If you really want XSLT to work directly against the database
Once XSLT can work directly directly againstBit sweeping Andrew, but it always appeared as
the database, XQuery's days could be numbered.
a fairly natural extension to XSLT, to have
it operate on databases rather than files, to keep the dataheads
happy and answer the users who want to play
with dirty great datasets.
I'm surprised it's not on the agenda for the WG
you could use collection() to return the documents.
How about URIs (e.g. with protocol) directly referencing eXist collections
with i/o "as usual" for XSLT (e.g. doc(), document(), collection(),
To explain the difference between what is available now, and what we
mean by XSLT 2.0 working directly against the database, think of this
- You have 1000 xml files stored in the database, and each of them
have a <title>
- You want to get those titles and group, sort and number them using xslt 2.0
- Currently you either a) use xquery to get the title nodes, wrap them
in an arbitrary root element, then supply that document to the
transform (which needs to know about that new document) using the
database's xslt extension, or b) access all documents using say the
rest api and then extract the <title> from within the xslt... not
very feasible, and not taking advantage of the database.
- When xslt can work directly on the database, you would just do
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format