Re: Error handling in XML

 > I suggest that we add language to section 5, "conformance", which says:
>  "An XML processor which encounters a violation of the constraints
>   of well-formedness must not thereafter pass any information about
>   text or markup to the application.  It must pass to the application
>   a notification of the first such violation encountered.  It MAY
>   thereafter, at user option, pass to the application information
>   about well-formedness violations encountered after the first."
> [or in English: you gotta tell the app about the first syntax botch you hit;
>  you're allowed to send the app more error messages, but you're not allowed
>  to send anything but error messages after you've detected an error]

I disagree that XML processor stops passing any text information about text or markup
to the application after first violation.  There may be lot of applications that may require
data after that.

The solution can be that after the first violation is encountered, notify application and then
DON'T send any data until the </endtag> of the <tag> in which violation occured.  Start
sending the data again after </endtag>

For example:

        [ 1. some other correct tags / informations ]

            [2. >>> violation occured in this tag.]

       [ 3. some more information ]

1 and 3 information is sent but information 2 is sent only if required by the application.
(by default the information 2 can be skipped.)

Satwinder Singh Mangat
Novell Inc.