cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bertrand Delacretaz <>
Subject Re: [RT] Using pipeline as sitemap components (long)
Date Tue, 26 Nov 2002 14:23:17 GMT
On Tuesday 26 November 2002 14:55, Christian Haul wrote:
>. ..what about e.g.
> <map:pipeline type="transformer" name="super_skin">
>   <!-- ... -->
> </map:pipeline>

For someone like me who doesn't know a lot about sitemap and pipeline 
internals, this looks very logical and understandable. 

Logical extensions of this for other types of incomplete pipelines could 
then be:

  <map:pipeline type="source" name="xmlized-google">
    <!-- no serializer, this is a "source only" pipeline -->

(but source is not a good name, already used)

  <map:pipeline type="sink" name="fo2rtf">
    <!-- no generator, this is a "sink only" pipeline -->
    <map:transform src="fix-fo-for-jfor.xsl"/>
    <map:serialize type="rtf"/>

Not sure if this is already covered by other mechanisms though, but it looks 
logical for defining partial pipelines. 

Alternatively they could just be called "pipe" which IRL is a part of a 

  <map:pipe type="transformer">


To unsubscribe, e-mail:
For additional commands, email:

View raw message