Conal Tuohy wrote:

>IIUC it was a conscious design decision of the Cocoon developers to
>discourage the entire pattern where a processing pipeline is determined
>by the source content
>
They're just plain wrong :-}
It is essential for me to have both TEI and Docbook documents
supported on my web server, and distinguishing between them
by file name, or directory location, is simply unworkable. This
makes me inclined to entirely ditch Cocoon as a workable system,
to be honest - if I was not already thinking that due to the ridiculous
documentation....

>You can use XSLT to transform a TEI document into an xinclude statement
>with a new URI (part of which identifies what version of TEI it is),
>then you just perform the xinclude, dereferencing the URI and invoking
>the corresponding version-specific pipeline.
>  
>
gash......

>More Cocoon-friendly, if you can do it, is to keep the different
>versions in different folders, or to use distinct file extensions, or
>something
>
i can see that would work, but its not realistic.

>If you need to compose 2 pipelines for distinct versions of TEI into a
>single pipeline that presents both versions, you can use the
>ResourceExistsAction or the ResourceExistsSelector in the sitemap to
>determine what version files are available.  
>  
>
eh? I don't follow you there. what am I checking for in the way
of resources?


sebastian