- From: James Fuller <jim@webcomposite.com>
- Date: Thu, 9 Feb 2012 12:34:13 +0100
- To: Norman Walsh <ndw@nwalsh.com>
- Cc: public-xml-processing-model-wg@w3.org
On Thu, Feb 9, 2012 at 11:15 AM, Norman Walsh <ndw@nwalsh.com> wrote: > Suppose we said that parameters were named collections of key/value pairs. > The XProc context includes by default two such named collections: > > p:global - initialized by some implementation-defined mechanism to contain > all the parameters passed to the pipeline by the user. > > p:none - initialized to be empty > > Implementations may provide a mechanism to create other named collections. > > We update p:parameters so that it adds/replaces keys to the collection it names. > > We remove parameter input ports in favor of a parameters option that takes > a list of named collections. If no parameters option is specified, p:global > is assumed. > > If we add types to options, we can make "parameters" a special type. I was thinking along the same lines … but to make an offering to the gods of reuse perhaps we could just call it 'map' then params become less exceptional ? Or am I missing something ? J
Received on Thursday, 9 February 2012 11:34:41 UTC