XOM API for Processing XML with Java

[jcowan AT reutershealth.com]

Elliotte Rusty Harold scripsit:

> I don't see an obvious use case for this right now.Since adding it in 
> the future would not be backwards incompatible with existing code, 
> I'm going to hold off on this until it becomes obvious that it's 
> necessary. 

I accept this.  The use case is similar to that of DocFragment in DOM;
it allows you to keep a sequence of Nodes without the implementation
or conceptual baggage of either Document or Element.  Currently, Nodes
shows its read-only ancestry, but exposes mutator methods insert, append,
and remove without the most basic mutator.  I proposed put for symmetry
with get, but I agree that replace is less confusing.

-- 
One Word to write them all,             John Cowan <jcowan AT reutershealth.com>
  One Access to find them,              http://www.reutershealth.com
One Excel to count them all,            http://www.ccil.org/~cowan
  And thus to Windows bind them.                --Mike Champion