External Literal 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?

Best,

Don Park
Docuverse



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