|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: literal result elements vs. <xsl:element>
Abie,
At 12:21 PM 10/1/2003, you wrote: can someone please explain what the difference is between using literal result elements and using <xsl:element>, and what pros and cons exist? Stay tuned, someone will say.... I have been using <xsl:element>, b/c it had seemed the more correct somehow, but from what I'm reading on literal result elements, they should work just as well, and they even offer the advantage of being able categorically to use attribute value templates. (-and they're in the book, so that means they're legitimate.;) ). They're legitimate as can be. I mainly use literal result elements because they're easier to type and to read and debug (since they look like fragments of the target). However I know an esteemed XML uber-guru who uses xsl:element so that he can use the tagging support in his preferred coding environment (Emacs) with validation and tag completion. There are a number of things you can do with xsl:element that aren't possible with literal result elements, whose advantage is mainly conciseness and ease of use. Also there's the "literal result element as stylesheet" feature (check the spec), which isn't actually used all that much in my experience: it's syntax sugar for a "pull" stylesheet. Cheers, Wendell
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|

Cart








