[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Hi Abie,
At 03:34 PM 9/9/2003, you wrote:
I bet long-term, you'd regret the "efficiency" of saving a step, especially considering how simple the XML-rewriting transform you're describing would be stand-alone, vs. the complexity of implementing a garden-variety transform this way. (Imagine: in every template you're writing out faux "XML" instead of using literal result elements or <xsl:element> ... thereby taking on the burden of ensuring well-formedness everywhere, not to mention handling character-escaping. Unh.) Also, if you want such a module once, chances are fair you'll want it again ... why reimplement every time?
Not if you do it right. On the ground, of course, the answer depends on how you're running the transforms to begin with. (And since XSLT is an openly specified "standard", you have the option of looking at alternatives if your current setup isn't up to the job.)
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Re: [xsl] formatting xml output: inserting newlines between generated attributes
Subject: Re: [xsl] formatting xml output: inserting newlines between generated attributes From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Tue, 09 Sep 2003 16:11:03 -0400 |
Hi Abie,
At 03:34 PM 9/9/2003, you wrote:
It does make more sense to do it in the way you're suggesting. I appreciate the modularization advantages. We actually do already have a 2 step transform, and my hesitation to have yet another stage is only in terms of efficiency. 2 steps is ostensibly faster than 3.
I bet long-term, you'd regret the "efficiency" of saving a step, especially considering how simple the XML-rewriting transform you're describing would be stand-alone, vs. the complexity of implementing a garden-variety transform this way. (Imagine: in every template you're writing out faux "XML" instead of using literal result elements or <xsl:element> ... thereby taking on the burden of ensuring well-formedness everywhere, not to mention handling character-escaping. Unh.) Also, if you want such a module once, chances are fair you'll want it again ... why reimplement every time?
Is there a lot of overhead in invoking the transform process multiple times? say I wanted to do it 10, 20 or 60 times?
Not if you do it right. On the ground, of course, the answer depends on how you're running the transforms to begin with. (And since XSLT is an openly specified "standard", you have the option of looking at alternatives if your current setup isn't up to the job.)
Cheers, Wendell
====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] formatting xml output: in, Abie Hamaoui | Thread | Re: [xsl] formatting xml output: in, Abie Hamaoui |
Re: [xsl] fo:block-container questi, Abhijit Junnare | Date | Re: [xsl] fo:block-container questi, G. Ken Holman |
Month |