RE: [xsl] iterate through nodes and determine output by node type

Subject: RE: [xsl] iterate through nodes and determine output by node type
From: "Scott Trenda" <Scott.Trenda@xxxxxxxx>
Date: Tue, 2 Oct 2007 10:42:26 -0500
(XSLT 1.1 argument aside here...)
According to Michael Kay's XSLT 2nd Edition Programmer's Reference:

"In the draft XSLT 1.1 specification, the result tree fragment is no
longer a separate data type, but is merged into the node-set data type.
A tree is manipulated in the form of a node-set containing one node, the
root of the tree."

So it looks like you're home free to slice and dice your variable

~ Scott

-----Original Message-----
From: Wendell Piez [mailto:wapiez@xxxxxxxxxxxxxxxx]
Sent: Tuesday, October 02, 2007 9:03 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] iterate through nodes and determine output by node


At 01:46 AM 10/2/2007, you wrote:
>About my original advice, I really don't know if XSLT 1.1 has
>dropped the tedious RTF, but if they did, you can use the pipeline
>technique I presented tp make your overall matching process easier.
>Otherwise, just as with 1.0, you'll have to resort to node-set
>extension functions (which can get heavy).

IIRC, XSLT 1.1 included a node-set() function, so you still had to
call a function explicitly, it's just that it wasn't an extension

Of course, since 1.1 was never approved, node-set() never became an
XSLT function. Formally speaking, XSLT 1.1 isn't any sort of
"standard". It's safer to regard it as a set of extensions, which
overlap in functionality with proprietary and other non-proprietary
extensions (EXSLT) and which may or may not happen to have been
implemented in any given XSLT engine.


Wendell Piez                            mailto:wapiez@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.      
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

Current Thread