RE: transform optimization for a schema-constrained do

The Tamino XML database (from Software AG) uses schema knowledge to optimize
queries against a database (the queries are currently written in a language
that's somewhere between XPath and XQuery). But this is a rather different
scenario, because the database can do a lot of work at document loading time
to set up metadata that's useful at query time. An XSLT processor generally
has only raw XML as its input, so there's a real risk that optimisation time
will exceed transformation time - especially if it means reading and
analysing a schema.

Another problem is that you can't bind a stylesheet to a particular schema
at the time it is compiled - though I guess one could get around that.

In short, I don't think anyone is doing this in an XSLT processor today. I
might be wrong, of course.

Mike Kay

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of
> Huebel, David
> Sent: 25 July 2001 16:57
> To: 'xsl-list@xxxxxxxxxxxxxxxxxxxxxx'
> Subject:  transform optimization for a schema-constrained domain
>
>
> Hello,
>
> Are there any XSLT processors that can use a schema for the
> input domain to
> improve performance?  For example, I'm currently using Saxon
> and would love
> to say
>
> Templates templates =
>     transformerFactory.newTemplates(transformSource, inputSchema);
>
> so that Saxon would use its knowledge of the input domain to
> create a faster
> implementation of the transform.
>
> Has this been implemented anywhere, and does anyone have any
> comments on its
> usefulness?
>
> David
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list