Re: A valid pipeline?

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

To briefly summarize an IRC conversation I just had with Norm -- in my
view this pipe succeeds iff some-imaginary-dns-name.tld serves
something in response to a GET for
http://some-imaginary-dns-name.tld/document.

The output of the XSLT2 step falls on the floor.

We discussed and rejected the idea of treating pipelines as document
management systems, allowing internal access to documents by name.  I
still don't want to go there.

However, the functionality Norm wants has general applicability, for
computing the input to existing mechanisms which take their 'inputs'
- From URIs, which include not only xinclude but also xsl:import and
xsl:include and possibly others.

Alternative suggestion:  give 'p:group' an input, call it 'cache', and
specify that any documents presented at that port must function as a
local cache for any http GET issued by any step inside the group's
subpipeline.

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)

iD8DBQFF/s/XkjnJixAXWBoRApB/AJ4zxkLPk0GGDX5DMQgwO1r+SZOWAACePlW7
rnNeKb74U3u3ZTWSeSaTlP0=
=xd3K
-----END PGP SIGNATURE-----

Received on Monday, 19 March 2007 18:01:14 UTC