RE: [xsl] Using not(...a nd ... ) to select nodes

[Wendell Piez <wapiez@xxxxxxxxxxxxxxxx>]

Lars,

Now I'm putting 2 + 2 together and seeing that you're showing why the code 
I offered yesterday doesn't work. :->

Which leaves me wondering whether an XPath-based solution is even possible 
(in XPath 1.0). Unfortunately, I will have to ponder that while I work on 
other things.... :-(

Cheers,
Wendell

At 05:47 PM 7/10/2003, you wrote:
> In order for your code to work, current() in the select expression
> of a for-each loop must refer to the <item> node currently being
> tested for whether it gets selected, right?
> If so, is this the way xsl:for-each / xpath work?
> I realize that INSIDE the for-each, current() refers to the node
> currently being processed, but is that also true in the select
> expression of the for-each? Or does current() there refer to
> the context node outside the for-each?
>
> > Chris,
> >
> > Try
> >
> > select="items/item[not(preceding-sibling::*
> >    [name=current()/name and
> >     type = current()/type and
> >    status = current()/status])]"


======================================================================
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
======================================================================


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