Subject: Re: [xsl] Using not(...a nd ... ) to select nodes From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Thu, 10 Jul 2003 16:11:19 -0400 |
select="items/item[not(preceding-sibling::* [name=current()/name and type = current()/type and status = current()/status])]"
Cheers, Wendell
I'm trying to create a node set that only contains different nodes. The problem I'm running into is I seem to be losing nodes that I shouldn't.
I'm using the following to select the nodes:
<xsl:for-each select="items/item[not(name = preceding-sibling::*/name and type = preceding-sibling::*/type and status = preceding-sibling::*/status)]">
An example from the XML might be: truck,silverado,chevy,on truck,silverado,chevy,off truck,ranger,ford,on truck,silverado,chevy,on truck,silverado,chevy,off
>From that I want to see the first three in a node set. However, what I'm getting are the second and third ones.
Any suggestions would be much appreciated.
====================================================================== 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 ======================================================================
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Using not(...a nd ... ) to se, Barak | Thread | RE: [xsl] Using not(...a nd ... ) t, Barak |
RE: [xsl] Using not(...a nd ... ) t, cknell | Date | Re: [xsl] 'qname' is not a valid XS, Wendell Piez |
Month |