I am in exactly the same situation:
We are making a "gate-keeper" program that must validate all data against
a previously agreed upon schema.
If you come up with an idea, please let us know.
/Christoffer
> -----Original Message-----
> From: Alberto Massari [mailto:[EMAIL PROTECTED]]
> Sent: 26. juni 2001 10:58
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: 2 questions about parsing
>
>
> At 14.58 25/06/01 -0700, [EMAIL PROTECTED] wrote:
>
> >More details on second question...
> >
> >I will be provided with an XML file from another party. We
> will agree on
> >the DTD beforehand, of course. But they could send me a file which a
> >modified DTD and the XML data in the rest of the file could
> match that
> >modified DTD. So Xerces would parse and validate the file
> without any
> >problems. But my code to walk the doc tree and extract data
> would likely
> >break. So I would like to keep our agreed-upon DTD in a
> separate file.
> >Then apply that DTD to the file they provide me. Ideally, I
> would ignore
> >any DTD that they provided with their XML file.
>
> XML allows you to mix internal and external DTDs, like in
>
> <!DOCTYPE SYSTEM "Path_to_DTD_we_agreed_on" [ <!-- extra elements and
> modified definitions go here --!> ]>
>
> Unfortunately, in Xerces you could easily avoid loading the
> external DTD,
> but I don't think you can avoid loading the internal one (that, btw,
> overrides what is written in the external one)
>
> Alberto
>
>
> -------------------------------
> Alberto Massari
> eXcelon Corp.
> http://www.StylusStudio.com
>
>
> ---------------------------------------------------------------------
> 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]
