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

RE: A parameters alternative

From: <vojtech.toman@emc.com>
Date: Fri, 10 Feb 2012 10:44:24 -0500
To: <public-xml-processing-model-wg@w3.org>
Message-ID: <3799D0FD120AD940B731A37E36DAF3FE341A80963E@MX20A.corp.emc.com>
> > Oh, I think I misunderstood your initial email. So using
> parameters="A
> > B C" means that the union of all parameters in A, B, and C will be
> > passed to the step? If so, how do you then access the parameters
> > inside the step? Using the name "parameters" or using "p:global",
> > "my:computed" etc.?
> Do we need that? If you want to access them in a step, you can use
> options. I'm imagining that parameters retain their magic bindings in
> XSLT, XQuery, etc.

Suppose I want to write a pipeline that takes a collection of parameters and iterates over them. Would I do something like this?

  <p:option name="params" type="p:parameters"/>  

    <p:with-param sets="params"/>


Vojtech Toman
Consultant Software Engineer
EMC | Information Intelligence Group
Received on Friday, 10 February 2012 15:45:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:50 UTC