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

Re: multiple subpipelines : how to count the number of outputs ?

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 10 Aug 2007 11:50:18 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <87r6mb9yo5.fsf@nwalsh.com>
I think, after the decisions we made yesterday, that this will work too:

<p:pipeline>
 <p:option name="operation"/>
 <p:choose>
   <p:when test="$operation = 'parameters'">
     <p:output port="result" primary="yes">
       <p:pipe step="params" port="result"/>
     </p:output>
     <p:parameters name="params"/>
   </p:when>
   <p:when test="$operation = 'xslt'">
     <p:xslt name="xslt">
       <p:input port="stylesheet"/>
         <p:document href="stylesheet.xsl"/>
       </p:input>
     </p:xslt>
   </p:when>
   <p:when test="$operation = 'xslfo'">
     <p:output port="result" primary="yes">
       <p:pipe step="fo" port="result"/>
     </p:output>
     <p:xsl-formatter uri="result.pdf" name="fo"/>
   </p:when>
   <p:otherwise>
     <p:output port="result" primary="yes"/>
       <p:inline>
         <nop/>
       </p:inline>
     </p:output>
     <p:error code="404" />
   </p:otherwise>
 </p:choose>
</p:pipeline>

That is, the XSLT step gets a defaulted primary output port named
'result' so you only need to fiddle with the outputs on the steps
where you don't have primary outputs.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Everything should be made as simple as
http://nwalsh.com/            | possible, but no simpler.

Received on Friday, 10 August 2007 15:50:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:54 GMT