>I'm sure one of the IBM developers said that XML4C internally uses the >SAX interface to build a tree for final DOM exposure.
Can't vouch for XML4C, but that's not entirely true for XML4J. First, SAX1 didn't have everything that a DOM needed. Second, the default "Deferred DOM" implementation requires a lower-level connection to the parser than SAX can provide. There are tools that will generate DOM from SAX and vice versa. I've been told that some of the impedence mismatches are fixed by SAX2; I don't know if that's a complete solution. The DOM still has a few behaviors which are "specified as magic", such as the behavior of default attribues, so full DOM support still requires that the parser or other builder have some DOM-implementation-specific glue code. Adding DTD support in Level 3 should fix those. ______________________________________ Joe Kesselman / IBM Research
