[
Lists Home |
Date Index |
Thread Index
]
Yeah, I've seen inconsistencies in behavior between different parsers in
this regard.
> -----Original Message-----
> From: David Brownell [mailto:david-b@pacbell.net]
> Sent: Friday, January 25, 2002 10:37 AM
> To: Heikki Toivonen; xml-dev@lists.xml.org
> Subject: Re: [xml-dev] Non-validating parser, non-existing DTD,
> undefined entity and error reporting
>
>
> SAX parsers will report some kind of fatal exception,
> likely an IOException, unless you have one (say, AElfred2)
> that supports disabling the external-parameter-entities
> feature (setting the flag value to "false").
>
> If the processor isn't handling external PEs then the XML
> spec says you'll get a report that it skipped those entities.
> And maybe a validity error, but that bit in the spec is
> excessively short of crystalline clarity ... :)
>
> - Dave
>
>
> ----- Original Message -----
> From: "Heikki Toivonen" <heikki@netscape.com>
> To: <xml-dev@lists.xml.org>
> Sent: Friday, January 25, 2002 10:21 AM
> Subject: [xml-dev] Non-validating parser, non-existing DTD,
> undefined entity and error reporting
>
>
> > What should a non-validating XML parser report in the below cases:
> >
> > 1)
> >
> > <?xml version="1.0" standalone="yes"?>
> > <!DOCTYPE test SYSTEM "notexist.dtd">
> > <test>a&foo;b</test>
> >
> >
> > 2)
> >
> > <?xml version="1.0" standalone="no"?>
> > <!DOCTYPE test SYSTEM "notexist.dtd">
> > <test>a&foo;b</test>
> >
> >
> > Should it report that the notexist.dtd could not be loaded, or that
> > entity foo is undefined, or totally ignore any errors?
> >
> > --
> > Heikki Toivonen
|
