I haven't been keeping up, but I think that there used to be 'extra-standard' APIs on the DOM parser to handle this. They may have been removed though since I last looked, or maybe I'm just hallucinating and they were never provided on the DOM parser. They clearly were always available in the underlying scanner so they could have been exposed through any wrapping parser.
------------------------------------- Dean Roddey The Charmed Quark Controller [EMAIL PROTECTED] www.charmedquark.com -----Original Message----- From: Leitner, Sarah M. [Contractor] [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 11:25 AM To: '[EMAIL PROTECTED]' Subject: DTD for my DOM program So are you saying I can't do this for DOM? If so, how do I validate my code using a DTD? Sarah >>>>> "Erik" == Erik Rydgren <[EMAIL PROTECTED]> writes: Erik> The entity resolver is a functionality actually stolen from Erik> SAX to DOM and if I'm not mistaken it is proposed as a DOM Erik> standard as well. It is not DOM standard yet, but it has Erik> been a part of Xerces DOM for a long time. it is in the proposed 3.0 draft. But it depends upon DOMInputSource, which isn't fully implemented in Xerces yet (in fact, it's useless as far as I can see). -- Colin Paul Adams Preston Lancashire --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
