Re: Variables and parameters

Norman Walsh wrote:
> / Rui Lopes <rlopes@di.fc.ul.pt> was heard to say:
> | I've got something bugging my head on p:for-each. How to handle naming
> | the outputs from pipelines which have for-each on them? Things such as
> 
> For a pipeline that returns a sequence of documents, I expect the base
> URI of each document to provide its "name". If my XSLT (2.0) process
> produces a principle result document and three additional result
> documents with the href values 'chap1.xml', 'chap2.xml', and
> 'manifest', I expect the output from the XSLT 2.0 step to be a
> sequence of four documents (in no particular order). Each document
> will "know" it's own base URI and I expect we'll have components that
> can make selections based on that URI.

If I understood you correctly, then there will be no explicit reference 
in the pipeline to each of those document names. E.g.

<p:pipeline name="mypipe">

   <p:input name="book" />
   <p:output name="manifest" />
   <p:output name="chapter" />

   <p:step name="xslt">
     <p:input name="document" ref="$book" />
     <p:input name="stylesheet" href="chunker.xsl" />
     <p:output name="result" ref="$manifest" />
     <p:output ref="$chunk" />
   </p:step>

   <p:for-each select="$chunk">
     <p:input name="document" label="one-chunk" />
     <p:output name="result" label="fancy-chapter" ref="chapter" />

     <p:step name="xslt">
       <p:input name="document" ref="$one-chunk" />
       <p:input name="stylesheet" href="fancy-chap.xsl" />
       <p:output name="result" ref="$fancy-chapter" />
     <p:/step>
   <p/for-each>

</p:pipeline>


That would be ok for me, as I intend to use XProc in document flow 
basis. However, if used in backwards chaining environments, such as a 
web server, it may pose some kind of difficulty. If I access a pipeline 
service with my user agent I would to point to 
http://example.com/mypipe/chapter1.xhtml. As the pipeline has no 
reference for it, it would fail delivering the request.

Other solution may be http://example.com/mypipe/chapter?number=1, where 
the "number" points to the desired document in the sequence. Maybe it's 
an issue for environment/implementation, but it must be thought.


Cheers,
Rui