>Scott, what do you think about making this an abstract class instead of
>an interface?
How about an interface plus an abstract base class that can be used as a
starting point by implementations?
Example: DTM is an interface, DTMDefaultBase is an abstract base class,
iteration is layered on top of that (still abstract), and finally the
concrete SAX2DTM and DOM2DTM classes are derived from those.
The advantage is that if someone wants to use an entirely different
internal architecture, they can implement the interface directly.
