Re: component questions

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

Alex Milowski writes:

> I didn't expect this component to be this hard to understand which
> obviously means that I need to expand the description.

Yes, thanks, I finally get it.

> I have a document A that uses xinclude to include documents B and C.
>
> Currently, the XInclude step would use the base URI of A to formulate
> the absolute URI of B and C from the the xi:include element's href
> attribute.  Let's call these uris URIB and URIC.  The regular xinclude
> step would just read from URIB and URIC to perform the include.
>
> This new component wouldn't read from URIB and URIC and instead
> look at the sequence of documents provided on the 'documents'
> port.  If it finds a document whose base URI is 'URIB' or 'URIC',
> it will use them for the xinclude.  Otherwise, it will "fail" however
> the xinclude spec says.
>
> In general, this step includes from the sequence and only considers
> "known" document to be those in the sequence provided on the
> 'documents' input port.  All other URI values are "not found".

So, another way to put it is that it uses a very restricted 'cache' to
fetch the included documents from, namely the documents presented to
the 'documents' port.

Thanks for your patience,

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+sixkjnJixAXWBoRAl7UAJ9lWYns97zisBDOUrS+CS9Djy96MACdG44g
XYBzSYGY+8nNsalucSicPew=
=ccyV
-----END PGP SIGNATURE-----

Received on Friday, 16 March 2007 16:41:28 UTC