From: Evan Lenz (elenz@xyzfind.com)
Date: Tue Dec 04 2001 - 17:36:46 CET
Leigh Dodds wrote:
> As a means to further discussion about the goals/aims of Transquery
> is it worth discussing the need for a standardised input for a
> collection of documents?
I think it's important to note that if the answer to this question is NO,
then TransQuery doesn't have a reason to exist. That may help put
perspective on the actual scope that TransQuery intends to address.
> In other words:
>
> Why use a separate top-level parameter, rather than providing
> the document collection as input directly?
The question here is what you mean by "input directly". The only "direct"
input that XSLT processors receive is the source tree, which is a single
document. That's what "/" refers to. If a future version of XSLT provides a
different built-in way of accessing a statically unknown collection of
documents, then great. But that would be outside of TransQuery's scope,
which is particular to XSLT 1.0. Instead, TransQuery makes use of an
existing XSLT 1.0 construct that's very flexible--top-level parameters. This
is meant to be the simplest way of providing an interoperable way of
accessing an input document collection without extending or deviating from
XSLT 1.0.
Evan Lenz
This archive was generated by hypermail 2.1.4 : Fri Feb 22 2002 - 11:35:58 CET