RE: Cascading. ( Re: Recursive Template Application )

> what a browser is meant to do: picks up the transformations from the
> originating document via the <?xml-stylesheet?> processing
> instructions. I'm sorry if I confused things by using your
> "cat" command. I should have said its more like:
> 
> "process some.xml"
> 
> Where the process command picks out the stylesheets to use.

Even so, I am a little bit puzzled.  For an XML file to be truly generic and capable of multiple, independent conversions, the conversion should not be specified in the document itself but somewhere else.  This is exactly the same problem that Cocoon version 1 suffers from...

A problem is that there is too little information embedded in the filename and the MIME-type for any processing pathway to be inferred, as such.    Would it be possible to make an extension mechanism allowing a document to provide keywords to its content, and then say: apply A, B and C to the document to get the desired result?

-- 
  Thorjbørn


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list