[Home] [By Thread] [By Date] [Recent Entries]
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
|

Cart



