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">
<map:generate...>
<map:transform...>
<!-- no serializer, this is a "source only" pipeline -->
</map: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"/>
</map:pipeline>
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
"pipeline":
<map:pipe type="transformer">
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
