Re: resource manager

"Henry S. Thompson" <> 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,

Norman Walsh
Lead Engineer
MarkLogic Corporation
Phone: +1 413 624 6676

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