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

Re: Parameter input ports

From: Alessandro Vernet <avernet@orbeon.com>
Date: Wed, 16 Apr 2008 11:35:30 -0700
Message-ID: <4828ceec0804161135y2a0a97f5t55d0fb97b13b9490@mail.gmail.com>
To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>

On Wed, Apr 16, 2008 at 7:11 AM, Norman Walsh <ndw@nwalsh.com> wrote:
>  Yes. I think I could live with that, but what happens in the following
>  case:
>
>  <p:declare-step name="main" type="...">
>   <p:input port='source'/>
>   <p:input port='style'/>
>   <p:output port='result'/>
>
>   <p:xslt>
>     <p:input port='stylesheet'>
>       <p:pipe step="main" port="style"/>
>     </p:input>
>   </p:xslt>
>  </p:declare-step>
>
>  The p:xslt step has an unbound parameter input port. Is that an error,
>  or do we bind it to an empty document?

For consistency with document input ports, I would think this is an
error. Doesn't this look like a case of "pipeline containing a step
whose specified inputs, outputs, and options do not match the
signature for steps of that type" (static error err:XS0010)?

Alex
-- 
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Received on Wednesday, 16 April 2008 18:48:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 16 April 2008 18:48:40 GMT