Fodder for the @name proposal

Consider this pipeline that I'm crafting for the new parallelism
section:

<p:pipeline xmlns:p="http://www.w3.org/ns/xproc">

  <p:xslt name="generate-stylesheet">
    <p:input port="source" href="someURI"/>
    <p:input port="stylesheet" href="someOtherURI"/>
  </p:xslt>

  <p:store href="gen-style.xsl"/>

  <p:xslt>
    <p:input port="source">
      <p:pipe step=??? port="source"/>



I find now that I want to refer to the pipeline input. I can't put
a name up there, so I have to invent a namespace and a type:

<p:pipeline xmlns:p="http://www.w3.org/ns/xproc"
            xmlns:px="http://example.org/doesntmatter"
            type="px:mypipe">

  <p:xslt name="generate-stylesheet">
    <p:input port="source" href="someURI"/>
    <p:input port="stylesheet" href="someOtherURI"/>
  </p:xslt>

  <p:store href="gen-style.xsl"/>

  <p:xslt>
    <p:input port="source">
      <p:pipe step="mypipe" port="source"/>

Ugh.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | The firmest line that can be drawn upon
http://nwalsh.com/            | the smoothest paper is still jagged
                              | edges if seen through a microscope.
                              | This does not matter until important
                              | deductions are made on the supposition
                              | that there are no jagged edges.--Samuel
                              | Butler (II)