- From: Alessandro Vernet <avernet@orbeon.com>
- Date: Wed, 24 May 2006 17:37:59 -0700
- To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>
On 5/24/06, Jeni Tennison <jeni@jenitennison.com> wrote:
> I think that, in order to keep our options open for using a directed
> syntax in the future, and to enable users to easily create their own
> directed syntax that they can easily translate into our generic syntax,
> the names of parameters and inputs/outputs should share a symbol space.
Jeni,
In my mind, separate namespaces are the main reasons why we have
parameters in addition to inputs. Say XSLT is invoked with:
<p:step name="xslt">
<p:with-input name="document" select="..."/>
<p:with-input name="stylesheet" select="..."/>
<p:with-output name="result" label="..."/>
</p:step>
Now I happen to have a stylesheet that takes a parameter named
"document". How can I pass a value for this parameter if I can't add a
<p:with-param name="document" select="..."/>?
In my mind inputs and parameters are both "inputs" to the step. Yes,
for now we will restrict inputs to sequences of documents and
parameters to strings, but I like to think that both will use XDM in
the future.
So it is really up to the component to define the semantic of "input"
and "parameter". For the XSLT component it would go as follows: there
are exactly two inputs "document" and "stylesheet", and 0 to n
parameters that are passed as parameters to the stylesheet.
Alex
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/
Received on Thursday, 25 May 2006 00:38:06 UTC