W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > January 2012

Re: V.next: resource manager

From: Norman Walsh <ndw@nwalsh.com>
Date: Thu, 05 Jan 2012 11:57:46 -0500
To: public-xml-processing-model-wg@w3.org
Message-ID: <m2d3ayhyt1.fsf@nwalsh.com>
"Henry S. Thompson" <ht@inf.ed.ac.uk> writes:
> 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.

Does a nested scope inherit from its ancestor scopes, or explicitly
ignore them?

I expect that users need to be able to choose.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
Lead Engineer
MarkLogic Corporation
Phone: +1 413 624 6676
www.marklogic.com

Received on Thursday, 5 January 2012 17:00:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 5 January 2012 17:00:46 GMT