You never need a [1] when using the "parent" axis because there is only
ever one parent node. The "ancestor" axis includes the parent node, its
parent node and so on, all that way to and including the root node.
Keep in mind that the axis determines which "direction" you're looking in
the tree from the context node. The default axis is "child", so "code[1]"
will select the first child of the context node, which would be a "code"
element, in your FOSI excerpt. If I'm reading your requirement right,
you're in one of potential several sibling "code" elements and want to get
the content of the first such element.
My first inclination would be to use the "preceding-sibling" axis, with an
XPath of "preceding-sibling::code[last()]", but that wouldn't work if
you're already in the first element, so you may want to use "../code[1]",
instead. For the former, keep in mind that cardinal positions are relative
to document order except for any "backward-looking" axis, so for
"preceding-sibling", the "last()" is actually the first one, in document
order.
-Brandon 🙂
On Sat, Jun 22, 2013 at 2:56 PM, Caroline Leccese <
caroline@thecodesource.net> wrote:
> Thanks, guys. So I don't to qualify with [1] such as parent::tagA[1],
> because I just want the one parent node directly above tagB.
>
>
>
> Also, how would I access the first occurring eic from the all context via
> XPATH?
>
> This didn't work:
>
>
>
> <e-i-c gi="code" occur="all">
> ...
> <att>
>
> <specval attname="code[1]" attloc="#xpath" attval="1"/">
> <charsubset>...</charsubset>
> </att>
> </e-i-c>
>
