|
Subject: Re: dl/dt/dd matching From: ht@xxxxxxxxxxxxxxx (Henry S. Thompson) Date: 16 Jan 1999 11:06:05 +0000 |
"Pawson, David" <DPawson@xxxxxxxxxxx> writes:
> James wrote:
>
> A variation on your suggestion can handle this:
>
> - next-element() returns the next element sibling;
>
> - next-element(MatchExpr) returns the next element sibling if it matches
> MatchExpr (otherwise nothing)
>
>
> DP:
> Naming, suggested improvement.
> If it deals with siblings, say so.
> next-sibling-element()
> and
> next-sibling-element(MatchExpr)
I'd like to explore combining this with the scanning operation
discussed (perhaps only on the WG list) some time back, so that one
could specify a path for next-element/previous-element to search
along, with siblings merely being the default. The most obvious
alternatives are (inverse) pre-order, and elders-only.
ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@xxxxxxxxxxxxxxx
URL: http://www.ltg.ed.ac.uk/~ht/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| RE: dl/dt/dd matching, Pawson, David | Thread | Re: dl/dt/dd matching, Oisin McGuinness |
| Re: Feature Request - Node Set Proc, James Clark | Date | Invoking XSL from XSL (was: Feature, Boris Moore |
| Month |