[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

External Literal Result Elements?

Subject: External Literal Result Elements?
From: "Don Park" <donpark@xxxxxxxxx>
Date: Sat, 1 May 1999 14:12:46 -0700
result elements
Are there anyways, other than the ones I listed below, to use external
literal result elements?  I have several reasons for this:

1. In the maintenance phase, literal result elements will change far more
frequently than other parts of XSL files.

2. There could be multiple literal result elements depending on the context
(i.e. target browser type).

3. Architecturally, I dislike mixing 'process' with'data'.

The methods I came up with are:

1. Store literal result elements as external parsed entities and insert
appropriate entity references in the XSL file.

2. Use DOM-based XSL processors and drop in literal result element nodes.

3. Use external script.

Are there any other ways?


Don Park

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

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.