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

Re: p:pipeline

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Thu, 20 Jul 2006 10:21:14 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <87ejwg4asl.fsf@nwalsh.com>
/ Alessandro Vernet <avernet@orbeon.com> was heard to say:
| On 7/19/06, Norman Walsh <Norman.Walsh@sun.com> wrote:
|> A pipeline looks like this:
|>
|>   pipeline := ($name?, input*, output*, {body}+)
|
| If a name is present on the pipeline, how would it be used? To call
| the pipeline from another pipeline? This could be done by URI instead.
| How are pipeline discovered? Is this dependent on the implementation?

I had something like this in mind:

  <p:pipeline>
    ...

    <p:pipeline name="somecommonsteps">
      ...
    </p:pipeline>

    <p:choose>
      <p:when>
        <p:step kind="somecommonsteps">
         ...
        </p:step>
        <p:step kind="postproc"/>
      </p:when>
      <p:otherwise>
        <p:step kind="somecommonsteps">
         ...
        </p:step>
      </p:otherwise>
    </p:choose>

| As a proxy, we can look at XSLT, which allows stylesheets to
| import/include other stylesheets, without introducing the concept of
| named stylesheet.

True. But requiring all pipelines to be in external files strikes me
as analagous to requiring all xsl:templates to be in separate files.

                                        Be seeing you,
                                          norm

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

Received on Thursday, 20 July 2006 14:21:29 GMT

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