Joe Kesselman wrote:

> Personally, I still think the p.lepin's solution is overcomplicated;

I have yet to fully comprehend it :-)

> Both are reusable. Which one is more reusable -- or teaches you more
> about reuse -- is debatable.

I tend to go with the p.lepin solution. Your solution demands that I 
hard-code the names of the nodes "levelone" and "child".
p.lepins only need the "sort"-attribute to be hardcoded.

After I understand p.lepins solution better, I hope to find out if it will 
work with a more deeper nested XML lilke

<levelone>
<child ID="1" 
sort="5"><names><name>Paul</name><name>Anka</name></names></child>
<child ID="2" sort="1"><name>Adam</name></child>
<child ID="3" sort="2"><name>Will</name></child>
</levelone>

> One of the nice things about asking on a
> newsgroup is that you may get multiple solutions, as here, in which
> case you can pick the one that matches your own needs... or, if you
> don't yet know your needs, you'll at least be exposed to the fact
> that multiple valid answers exist.
>
> Have fun.

Thanks. To both of you. For guiding me from wet feet, to knee-deep :-)

/jim