Fwd: BOUNCE xsl-list@lists.mulberrytech.com: Non-me

Date: Tue, 8 May 2001 04:31:44 -0400 (EDT)
From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
To: xsl-list-approval@xxxxxxxxxxxxxxxxxxxxxx
Subject: BOUNCE xsl-list@xxxxxxxxxxxxxxxxxxxxxx: Non-member submission from ["Jeni Tennison" <jeni@xxxxxxxxxxxxxxxxxxxx>]
X-Loop-Detect: 1

>From jeni@xxxxxxxxxxxxxxxxxxxx Tue May 8 04:31:34 2001
Received: from www.2ndmail.com (2ndmail.com [209.75.7.64])
by biglist.com (8.8.8/8.8.5/BL-2) with SMTP id EAA12306
for <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>; Tue, 8 May 2001 04:31:34 -0400 (EDT)
Date: Tue, 8 May 2001 04:31:34 -0400 (EDT)
Message-Id: <200105080831.EAA12306@xxxxxxxxxxx>
Received: (qmail 70351 invoked from network); 8 May 2001 08:32:51 -0000
Received: from localhost (HELO 2ndmail.com) (127.0.0.1)
by localhost with SMTP; 8 May 2001 08:32:51 -0000
From: "Jeni Tennison" <jeni@xxxxxxxxxxxxxxxxxxxx>
To: "Ryan Worley" <rworley@xxxxxxxxxxx>
Cc: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Importance: Normal
X-Mailer: VisualMail 3.05 ( http://www.mintersoft.com/visualmail )
Subject: Re: XML --> HTML | PDF | XXX
Mime-Version: 1.0
Content-type: text/plain; charset="iso-8859-1"

Hi Ryan,

> What method are you guys using to transform one XML document into
> multiple types of output documents based on incoming variables? I
> saw two options in the Cocoon FAQ, via XSP and XSLT, neither of
> which I thought where very elegant. Are there other options for
> accomplishing this? Also, I read that a future XSLT spec is going to
> address this issue, does anyone have specific knowledge about what
> will be proposed?

The XSLT 1.1 WD addresses this by (a) adding an xsl:document element
to redirect output and (b) making many of its attributes and the
attributes on xsl:output into attribute value templates, so that they
can be set dynamically using variables.  I guess it's fairly likely
that XSLT 2.0 will incorporate these changes.

The xsl:document element has been added to EXSLT
(http://www.exslt.org) as exsl:document (at the moment), given that
XSLT 1.1 so we can hopefully try it out in the shorter term, and there
are also processor-specific extension elements that do the same kind
of thing.

So for example, you could do:

<xsl:template name="output">
  <xsl:param name="file" />
  <xsl:param name="method" select="'xml'" />
  <xsl:param name="content" />
  <exsl:document href="{$file}" method="{$method}">
     <xsl:copy-of select="$content" />
     <xsl:fallback>
        <xsl:message terminate="yes">
           Unable to create output file.
        </xsl:message>
     </xsl:fallback>
  </exsl:document>
</xsl:template>

I hope that helps,

Jeni

(this is a temporary address due to mailing problems - please use mail@xxxxxxxxxxxxxxxx)

Jeni Tennison
http://www.jenitennison.com

======================================================

The most personalized email addresses available!
at: http://www.2ndmail.com
Say goodbye to that boring email address.

======================================================