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

RE: A parameters alternative

From: <vojtech.toman@emc.com>
Date: Thu, 9 Feb 2012 08:08:37 -0500
To: <public-xml-processing-model-wg@w3.org>
Message-ID: <3799D0FD120AD940B731A37E36DAF3FE341A8093D6@MX20A.corp.emc.com>
> I was thinking that the parameters option would take a list:
>   <p:xslt parameters="p:global my:computed other:whatever">...

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.?

(I originally thought you meant that the step would see three named collections (A, B, and C) - but that is probably too weird to make any sense at all.)

To declare a step with two parameter "ports", would you do something like this:

  <p:param name="xquery-params"/>
  <p:param name="xslt-params"/>


Or, if we treat parameter "ports" as options with a special type:

  <p:option name="xquery-params" type="parameter"/>
  <p:option name="xslt-params" type="parameter"/>

Or we could get rid of the word parameter altogether and simply call the type "collection" or "map".


Vojtech Toman
Consultant Software Engineer
EMC | Information Intelligence Group
Received on Thursday, 9 February 2012 13:10:20 UTC

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