[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Re: . in for

Subject: RE: Re: . in for
From: "Michael Kay" <michael.h.kay@xxxxxxxxxxxx>
Date: Sun, 6 Jan 2002 19:38:59 -0000
mike paints
> The picture that Mike paints here is of an XSLT that is basically a
> language for defining functions, defining sort keys, defining decimal
> formats, defining variables and so on. XPath becomes the main driving
> force of the transformation, with XSLT simply backing it up.

I'd characterize it differently. XSLT declarations are used for defining
things as you describe; XPath expressions are used for computing information
based on the contents of the source tree(s); XSLT instructions are used for
creating nodes in the result tree, with the contents of those nodes being
computed using XPath expressions. If we get the design right, I don't think
it should ever be necessary to use an XSLT instruction unless you are trying
to write something to the result tree.

I take your point about the limitations of named sort keys. To solve that I
think we would have to allow named sort keys to be declared locally within a
template, so that the sort expression could refer to variables.

Mike Kay

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

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.