OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] SAX/Java Proposed Changes

[ Lists Home | Date Index | Thread Index ]

At 9:11 AM -0500 3/5/04, David Megginson wrote:

>* 2004-0005: endDocument
>- note that a parser might not invoke endDocument after reporting a
>   fatal error (this produces the fewest incompatibilities)

I'm a little uncomfortable with this "fix". I think always calling 
endDocument is the right thing to do, and it should be required in 
the spec. I don't think this would increase incompatibility in any 
significant way. It would simply encourage vendors of non-conformant 
parsers to bring their parsers into compliance, thereby increasing 
compatibility. This would allow users to depend on this behavior for 
the first time.

I don't think a parser suddenly changing from not calling endDocument 
to  calling endDocument is likely to cause major problems. Fixing 
this in the direction you propose would simply bake in the existing 
incompatibility. One way or the other, this should be nailed down. 
Either parser all parsers should call endDocument after a 
well-formedness error or none should. Letting it go either way is the 
real problem.

   Elliotte Rusty Harold
   Effective XML (Addison-Wesley, 2003)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS