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

RE: V.next: empty parameters

From: <vojtech.toman@emc.com>
Date: Thu, 9 Feb 2012 05:38:29 -0500
To: <public-xml-processing-model-wg@w3.org>
Message-ID: <3799D0FD120AD940B731A37E36DAF3FE341A809371@MX20A.corp.emc.com>
> Well. Consider this pipeline:
>   <p:pipeline>
>     <p:xslt>
>       <p:input port="stylesheet"><p:document href="doc.xsl"/></p:input>
>     </p:xslt>
>   </p:pipeline>
> The primary parameter input port isn't empty by default because if it
> was, then you couldn't pass parameters to that p:xslt step.

That is not what I meant. I was wondering why we made it an error if the step has an unbound primary parameter input port and the owner pipeline does not have a primary parameter input port.


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

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