XOM API for Processing XML with Java

["Bradley S. Huffman" <hip AT a.cs.okstate.edu>]

Elliotte Rusty Harold writes:

> At 6:50 AM -0400 9/20/02, John Cowan wrote:
> 
> 
> >This is just what I was saying (but I still prefer Container to TreeNode
> >or BranchNode).
> 
> 
> I am thinking about this. It does have a nice simplicity. I like the 
> idea of navigation methods in Node and mutation methods in 
> BranchNode/Container. That pretty clearly explains what goes where 
> and why.

At home I have a experimental version of JDOM where I have a Parent and
a Content interface.  Content is basically XOM Node with previous and next
siblings, and Parent has the mutation methods along with firstChild/lastChild.
It works quite well and is clear and easy to understand, so I can recommend 
it. 

> Name-wise, how does "ParentNode" strike you?

I like the word "parent" over "branch" or "container", to me it invokes a
easily recognizable mental picture of the structure. Even non-coders can
picture a parent with a parent with a parent, and that a parent can have
zero or more children.

Brad