Re: URIs as inputs and outputs

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeni Tennison writes:

> The crux is that instead of passing *documents* between steps, we pass
> *URIs*. The pipeline processor acts as a resource manager/entity
> resolver. Whenever a component wants to read a document, it requests
> it, using the URI, from the pipeline processor. Whenever a component
> wants to write a document, it registers it with a particular URI with
> the pipeline processor (and that URI can be supplied to the component
> when the step is defined).

We discussed something like this at the f2f - I've been thinking about
it off and on.  It simplifies some things, in particular computed
'static' resources.  That is, on the pure dataflow model, you need
e.g. two XSLT components, one with one input and a static resource
stylesheet, and one with two inputs.  On the
processor-as-resource-manager approach, you only need one.

One obvious glitch is document sequences. . .

ht
- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFENNVlkjnJixAXWBoRAp+mAJ9fP82EyEUaqIsrzl6EcHZdHpEirgCggtLD
HKHA80s/3aL89a1r7ZXAOiI=
=69z1
-----END PGP SIGNATURE-----

Received on Thursday, 6 April 2006 08:46:37 UTC