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

Why isn't node-set built in?

Subject: Why isn't node-set built in?
From: "Paul W. Abrahams" <abrahams@xxxxxxxxxxx>
Date: Wed, 15 Dec 1999 13:46:02 -0500
t node
Phil Lanch wrote:

> Alternatively, use a named template to collect (nodes containing) the
> numbers you want to add up in a variable, and apply the sum() function
> to them. The tricky bit is that the variable contains a result-tree
> fragment, not a node list, and the sum() function must be given a
> node-list, so you need to convert the result-tree fragment to a
> node-list using a node-set() extension function. This is available in
> Saxon or XT (and it looks such a good idea that surely all good XSL
> processors will have it eventually).

That raises the question: since node-set so obviously fills a significant gap and is provided in two leading XSL processors as an
extension, why isn't it one of the Additional Functions listed in Sec. 12 of the XSL spec?   That would, among other effects,
standardize its definition and be a Good Thing.

Paul Abrahams



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


Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

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.
Email
First Name
Last Name
Company
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.