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

Re: Sub-pipelines

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Wed, 15 Mar 2006 15:18:40 -0500
To: public-xml-processing-model-wg@w3.org
Message-ID: <87irqf1mxr.fsf@nwalsh.com>
/ Rui Lopes <rlopes@di.fc.ul.pt> was heard to say:
| I would like to add that a pipeline should be called not just by name,
| but through hrefs, allowing the execution of external pipelines as
| services, e.g.:
>
| <p:call-pipeline href="my-other-pipeline.xml#expandandvalidate">
|    ...
| </p:call-pipline>

Yes, I think we want to allow external pipelines, but do you think
that these two pipelines mean exactly the same thing?

  <p:pipeline>
    <xi:include href="my-other-pipeline.xml"
                xpointer="element(expandandvalidate)"/>
    <p:call-pipeline name="expandandvalidate"/>
  </p:pipeline>

  <p:pipeline>
    <p:call-pipeline name="my-other-pipeline.xml#expandandvalidate"/>
  </p:pipeline>

I'm not sure. I had sort of imagined a "pipeline processor component"
for executing external pipelines. That would make them semantically
completely disconnected processes. OTOH, if we agree that a
sub-pipeline can't refer to "global" variables, I'm not sure there's
any way to distinguish between these two cases.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

Received on Wednesday, 15 March 2006 20:18:51 GMT

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