[
Lists Home |
Date Index |
Thread Index
]
Liam Quin wrote:
> On Thu, Dec 02, 2004 at 03:10:06PM -0500, Michael Champion wrote:
> [...]
>
>>So, I guess one could say that XQuery is at least implicitly targeting
>>the situations where you have multiple collections of XML or
>>XMLizeable information that need to be related, and allows you to
>>relate them dynamically by value rather than by a priori links.
>
>
<snip/>
>
> Strictly speaking it could also have been done in XSLT, but there's a
> danger that the XSLT implementation would have had to examine my
> entire database (e.g. if I used apply-templates) and a lower chance
> that it would have made use of an index... in other words, even
> if the languages are very similar in coverage, the focus of
> implementations is likely to be very different.
Why do you think an xsl:apply-templates would need to examine your
entire db (even if it could)? Your uri resolver could grab what you need
to return to the transformation.
Heck, you could form some XQuery string in XSLT 1.0, send it to a uri
resolver (through document()), which then does the xquery, then returns
the result back to the transformation so you can apply-templates.
best,
-Rob
>
> Liam
>
|
