The DOM's architecture deliberately does not require continuous checking, since it is usually _MASSIVE_ overkill -- most applications check the data before they add it to the DOM, and it can be checked at serialization time. DOM Level 3 plans to add the option to more intensively check a subtree on demand.
That isn't to say a DOM _can't_ continuously check itself. But that's something of a special-purpose requirement, and probably doesn't belong in a general-purpose implementation like the one in Xerces. ______________________________________ Joe Kesselman / IBM Research --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
