Re: Getting variable yet most immediate parentNode

...Like a charm.

On 9/28/07, Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> wrote:
> At 11:26 AM 9/28/2007, you wrote:
> >I think we've gone awry. .//answer's doesn't make sense because, as
> >Wendell pointed out, I want to go up the tree if there is no child
> ><answers />. I tried his syntax, however I'm not sure how to make it
> >choose a child answer's node before it goes looking for the closest
> >ancestral answer node (without using those pesky case statements).
>
> Try ancestor-or-self::*[answers][1]/answers.
>
> This is the kind of thing where a little bit of formal instruction or
> exposure can really help. :-)
>
> Cheers,
> Wendell
>
>
> ======================================================================
> 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
> ======================================================================