This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Re: _why_ do people use xsl:element and xsl:attribute so much
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: [xsl] Re: _why_ do people use xsl:element and xsl:attribute so much
- From: David Carlisle <davidc at nag dot co dot uk>
- Date: Wed, 5 Sep 2001 23:30:43 +0100
- References: <200109051910.f85JAJQ60739@skew.org>
- Reply-To: xsl-list at lists dot mulberrytech dot com
It seems to me that
teaching people about literal result elements as "text that is
copied through" rather than as "shorthand for instructions to
create nodes --
I agree completely, if we describe it as passing text we can't blame
people if they want to just output an unmatched start tag.
But I think that it _is_ natural to say that a template body can be
viewed as a fragment of the output tree, and that the most natural way
to express a tree structure in XML is to use the standard XML
representation of that tree, thus
<a href="...">...</a>
for an a element with an href attribute. (where actually one uses
xslt/xpath rather than ... to fill out the blanks.
On the other hand the comments from a tool author on the utility of the
more regular xsl:element constructs sounded reasonable, tool generated
sheets, and setting breakpoints etc does seem to have different
requirements/flavour than hand authoring.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list