W3C home > Mailing lists > Public > xsl-editors@w3.org > July to September 2000

Re: XSL Transformations Requirements - output destinations

From: Steve Muench <smuench@us.oracle.com>
Date: Wed, 13 Sep 2000 13:58:46 -0700
Message-ID: <000901c01dc5$68b24410$72164498@us.oracle.com>
To: <David_Marston@lotus.com>
Cc: <xsl-editors@w3.org>
David,

Do you mean that it would be desireable to
control the output of where messages go via <xsl:message> ?

______________________________________________________________
Steve Muench, Lead XML Evangelist & Consulting Product Manager
BC4J & XSQL Servlet Development Teams, Oracle Rep to XSL WG
Author "Building Oracle XML Applications", O'Reilly
http://www.oreilly.com/catalog/orxmlapp/

----- Original Message ----- 
From: <David_Marston@lotus.com>
To: <xsl-editors@w3.org>
Sent: Wednesday, September 13, 2000 1:56 PM
Subject: XSL Transformations Requirements - output destinations


| In part 4 of the Version 1.1 requirements document for XSLT, the following
| requirements are listed:
| 
| It MUST be possible to specify the destination URI (e.g. file name) of each
| output document
| It MUST be possible to assign the name of the destination URI dynamically
| It MUST be possible to control serialization of each output document using
| the same facilities as <xsl:output>
| 
| I would suggest that the implementation of the above requirements be
| designed in such a way that they can be applied to xsl:message as well. The
| third one is especially noteworthy, as it has an impact on the treatment of
| xsl:element and similar instructions inside the message.
| 
| Further, I think that the requirements document should make an explicit
| acknowledgement that the requirements above, or at least the third one,
| apply to xsl:message or could apply in a later version.
| .................David Marston
| 
| 
Received on Wednesday, 13 September 2000 17:04:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:50 GMT