Re: resource manager

More on p:uri-scope -- the idea is that there is an implicit
p:uri-scope around the entire top-level pipeline, and that every
p:uri-scope acts as a scope for an *available documents* collection,
mapping from URIs to documents, which is initially empty.  Any URI
resolution action works with respect to its nearest (lexically)
surrounding uri-scope, and either uses what it finds there, or does a
'fetch' and caches the result there.

I _think_ that the 'to' URIs in a map-uri or map-public are actually
in the _surrounding_ scope, not the newly created one. . .

       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail:
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

Received on Thursday, 5 January 2012 16:38:39 UTC