- From: Innovimax SARL <innovimax@gmail.com>
- Date: Wed, 16 Aug 2006 16:48:09 +0200
- To: "Jeni Tennison" <jeni@jenitennison.com>
- Cc: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>
- Message-ID: <546c6c1c0608160748v14afc55fi8d2dae2f0a7b9441@mail.gmail.com>
I really prefer your suggestion Jeni, because it open the possibility to
document an input/output without conflicting with the here content
like that
<pipeline name="ex1">
...
<output name="result">
<documentation>This is the result of the pipeline ex1</documentation>
<pipe>
<mydoc xmlns="">...</mydoc>
</pipe>
</output>
</pipeline>
Regards
Mohamed
On 8/16/06, Jeni Tennison <jeni@jenitennison.com> wrote:
>
>
> I'd actually intended 'here' documents to be nested inside the <pipe>.
> In a <step>, they have to be, in order to indicate which port the 'here'
> document is associated with:
>
> <step kind="xslt" name="transform">
> <pipe to="source" from="validated!result" />
> <pipe to="stylesheet">
> <xsl:stylesheet ...>...</xsl:stylesheet>
> </pipe>
> </step>
>
> and I think it would be best to avoid having <pipe> work differently
> within <step>s from how it does within <input>/<output>. So I'd suggest
> we do 'here' documents for outputs with:
>
> <pipeline name="ex1">
> ...
> <output name="result">
> <pipe>
> <mydoc xmlns="">...</mydoc>
> </pipe>
> </output>
> </pipeline>
>
> (I'm all in favour of 'here' documents for outputs: I think it's
> essential for <choose>.)
>
> Cheers,
>
> Jeni
> --
> Jeni Tennison
> http://www.jenitennison.com
>
>
--
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 8 72 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €
Received on Wednesday, 16 August 2006 14:48:25 UTC