>I have advice for using the DOM (in any implementation) for
>XML editing applications:
>
> Don't
Arguably offtopic for this mailing list, but I have to respond to this
one...
The DOM _IS_ well-suited for many applications. And you did say that your
problems were with DOM Level 1; DOM Level 2 has been a Recommendation for
quite some time now, and may have addressed some of your concerns.
Yes, there are things the DOM APIs don't yet do. DTD support was held off
due to a desire to provide a single API for both DTDs and Schemas and is
only now being designed (as part of DOM Level 3). If you happen to need to
do something the DOM doesn't support, then yes, you do have to step outside
and use custom APIs or another approach.
The DOM is still evolving, as is SAX and as is everything else in the XML
space. And DOM is not the right answer for all applications, though it _is_
the right answer for some. Make the decision based on what your actual
needs are, and use the tool that best fits the problem and the way you want
to approach it.
For related comments, see http://www.w3.org/DOM/faq.html#SAXandDOM
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]