[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XSLT, Web applications, and "native XML databases"

Subject: Re: XSLT, Web applications, and "native XML databases"
From: "James Fuller" <james.fuller.2007@xxxxxxxxx>
Date: Thu, 8 Jan 2009 11:35:14 +0100
Re:  XSLT
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:
>>>>>>
>>>>>> Once XSLT can work directly directly against
>>>>>> the database, XQuery's days could be numbered.
>>>>>
>>>>> Bit sweeping Andrew, but it always appeared as
>>>>> 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
>>>>
>>>> If you really want XSLT to work directly against the database
>>>> you could use collection() to return the documents.
>>>
>>> false.
>>
>> How about URIs (e.g. with protocol) directly referencing eXist collections
>> with i/o "as usual" for XSLT (e.g. doc(), document(), collection(),
>> result-document()) ?
>>
>
> 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
> example:
>
> - 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
> <xsl:for-each-group select="collection(...)//title">
>
>
>
>
>
>
> --
> Andrew Welch
> http://andrewjwelch.com
> Kernow: http://kernowforsaxon.sf.net/

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.