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

Overriding pipelines

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Tue, 20 Mar 2007 14:06:37 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <877itb7psi.fsf@nwalsh.com>
This is not legal:

  <p:pipeline-library>

   <p:pipeline name="foo">
     <p:input port="source/">
     <p:output port="result"/>
     ...
   </p:pipeline>

   <p:pipeline name="foo">
     <p:input port="source/">
     <p:input port="otherstuff/">
     <p:output port="result"/>
     ...
   </p:pipeline>

 </p:pipeline-library>

 But is this?

  <p:pipeline-library>

   <p:import href="somelib.xml"/>

   <p:pipeline name="foo">
     <p:input port="source/">
     <p:input port="otherstuff/">
     <p:output port="result"/>
     ...
   </p:pipeline>

 </p:pipeline-library>

 Where somelib.xml contains:

  <p:pipeline-library>

   <p:pipeline name="foo">
     <p:input port="source/">
     <p:output port="result"/>
     ...
   </p:pipeline>

 </p:pipeline-library>



                                        Be seeing you,
                                          norm

-- 
Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.

Received on Tuesday, 20 March 2007 18:06:47 GMT

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