This is basically directed at Shon I suspect...

If I were to for-each over an event document (say a modify or add event)
with the XPATH of .//@attr-name

and the same attribute was in there a couple of times. (You may recall
my question from last week if there was a way to add multiple values via
an add-dest-attr style token into a single <modify-attr> node with many
values, instead of many <modify-attr> nodes with single values.

Here was my example there:
<modify-attr attr-name="pager">
<value>123-123-1234</value>
<value>231-231-2314</value>
<value>321-321-3214</value>
</modify-attr>

You get this:
<modify-attr attr-name="pager">
<value>123-123-1234</value>
</modify-attr>
<modify-attr attr-name="pager">
<value>231-231-2314</value>
</modify-attr>
<modify-attr attr-name="pager">
<value>321-321-3214</value>
</modify-attr>


Would I get a loop iteration for each attribute that has an attr-name
XML attr?

That is, the first example is clearly a single iteration. But in the
second, would I get one or three?

If 3 which I suspect is what happens, is there any clever way to make it
just do it once? I guess if I treat current-node as a nodeset, would I
get the nodeset of all the pager attrs at once? (Does the engine
actually provide current-node as a string, or as a nodeset?)