Re: Sub-pipelines

/ 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.