cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Quinn <>
Subject RE: [status & RT] design challenges
Date Mon, 08 Apr 2002 14:19:21 GMT
At 2:04 pm +0200 8/4/02, Carsten Ziegeler wrote:
>Jeremy Quinn wrote:
>> At 9:02 am +0200 8/4/02, Carsten Ziegeler wrote:
>> >Sylvain Wallez wrote:
>> >> <snip/>
>> >The Avalon Excalibur SourceResolver will replace all of our uri handler,
>> >source handler, source resolver stuff and clean up this area. There will
>> >only be one! The Avalon Excalibur SourceResolver.
>> Will it be possible (one day?) to allow XSLT to use Avalon Excalibur
>> SourceResolver to resolve urls in (for instance) document() functions?
>Yes, it will very soon. Currently the Cocoon source resolver is used
>for document() and this will be replaced.

Thanks, I see Sylvain asked almost the same question ....

>> Would this be desirable?
>Of course.
>I personally hope that other projects like FOP or Batik us the Avalon source
>resolver, too which would then solve the problems with image resolving etc.

Considering the success we have had recently, generating Schematron
Validation XSLTs dynamically, it would be interesting to be able to
<xsl:include/> StyleSheets generated via the sitemap, ie. via cocoon://

Though this may encourage a blurring of SoC.


regards Jeremy

   Jeremy Quinn                                           Karma Divers
                                                       webSpace Design
                                            HyperMedia Research Centre

   <>     		 <>
   <phone:+44.[0].20.7737.6831>             <>

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

View raw message