This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: preceding sibling test
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: preceding sibling test
- From: Kay Michael <Michael dot Kay at icl dot com>
- Date: Tue, 15 Feb 2000 09:34:11 -0000
- Reply-To: xsl-list at mulberrytech dot com
Sorry, typo. For previous read preceding. My usual mistake is to type
"prior" - result of years working with Codasyl databases in my youth. When
you're on your 20th language you start mixing them up.
Mike Kay
> -----Original Message-----
> From: Sargeant, Richard (GEIS) [mailto:Richard.Sargeant@geis.ge.com]
> Sent: 14 February 2000 11:57
> To: 'xsl-list@mulberrytech.com'
> Subject: RE: preceding sibling test
>
>
> Hi Michael,
>
> > I suspect what you meant to write was something like
> >
> > <xsl:template match="PB_ITEM">
> > <xsl:apply-templates
> select="USER[not(.=previous::sibling::USER[1])]"/>
>
> I tried your suggestion but it doesn't work! I'm using
> Oracle's parser
> and it aborts with "Axis 'previous' not found". I have also
> checked the
> XPATH specs (16 Nov 1999) and there is no mention of
> previous::sibling. Am I
> looking at the wrong specs ?
>
> For your information, all I'm doing is processing the results of a
> database query and each time the 'USER" changes I need to
> print some header
> information.
>
> regards
> Richard Sargeant
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list