RE: [xsl] Converting attributes to elements and preserving the hierarchy

[Wendell Piez <wapiez@xxxxxxxxxxxxxxxx>]

Also,

*Anything* you can do with a for-each, you can do with a template (with a 
mode if necessary).

I wonder whether the reverse is the case. (Can anyone suggest something 
that can't be done with a for-each, but can be done with templates? I can 
think of things much harder to do with for-each, but impossible?)

In anything but the simplest cases, templates are far more flexible, easier 
to extend and maintain. In particular, if you need to preserve the order 
and hierarchy of your data (see the Subject line), for-each will make 
things harder.

Cheers,
Wendell

At 04:58 AM 12/19/01, Mike wrote:
> For beginners: always use template rules, until you understand them well
> enough to know their strengths and weaknesses.
>
> For advanced users: use xsl:for-each only when you are absolutely confident
> that the structure of the source documents handled by your stylesheet is not
> going to change.


======================================================================
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