In XSLT 2.0, an <xsl:output> specification may be named, and
<xsl:result-document> has a format attribute to reference a named
<xsl:output> declaration. You can select an output format dynamically,
but it is not possible to calculate the values of the individual
serialization parameters dynamically.

Michael Kay


> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx 
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Bob Foster
> Sent: 06 October 2003 18:26
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: XSLT 2.0 dynamically parameterized output? Was: Re: 
>  Trying to use Docbook transforms with Saxon7
> 
> 
> Jirka Kosek wrote:
> > Recommended version of Saxon for DocBook XSL stylesheets is Saxon 
> > 6.5.x.
> > DocBook stylesheets are written in XSLT 1.0 with lots of EXSLT and 
> > vendor dependant extensions. These extensions are not 
> always available 
> > in Saxon7 as similar functionality is provided by XSLT 2.0.
> 
> Yes, I know and I had no trouble running the stylesheet in 
> Saxon 6.5.2. 
> But this doesn't help me get it running in Saxon 7.
> 
> The Doctype chunker.xsl stylesheet is using saxon:output, 
> exsl:document, 
> etc. for their ability to dynamically specify the output 
> parameters with 
> attribute value templates.
> 
> There seem to be two main differences between these extension 
> instructions and xsl:output/xsl:result-document provided by XSLT 2.0:
> 
> 1. xsl:output may only appear at the top level.
> 2. (Serious problem) none of xsl:output's attributes are specified in 
> the syntax summary as allowing attribute value templates.
> 
> So what does one use in 2.0 when it is desired to dynamically 
> calculate 
> values of, e.g., doctype-system, media-type, etc.?
> 
> Bob Foster
> http://www.xmlbuddy.com/
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


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