SAX 2.0.3 Bug Database

It would be useful to begin immediately working on SAX 2.0.3 since 
there are a lot of leftover niggling little issues we should fix, 
ranging from trivial things like the proper capitalization of 
"namespace" to major issues such as whether or not parsers are 
required to call endDocument() after a fatal error. Sadly there are 
also now some broken parts we can't fix because 2.0.2 has locked them 
in, like the Locator2 interface. :-(

Toward this end, it would be very helpful if we could start using the 
Bug database at sourceforge to track these things. For myself, I know 
I can't really keep track of what I have and have not reported, much 
less what others have. If we continue in the current informal post to 
the mailing list fashion (especially with list archives down) then 
when we do open up work on SAX 2.0.3, I just know I'm going to 
resubmit at least three things that have already been rejected, and 
forget about at least three others.

I suggest beginning by pruning the existing bugs and RFEs. Looking at 
it now, there are only two unresolved bugs and one and perhaps both 
of them should simply be closed with no further action. I haven't 
read all the RFEs, but some of them can likewise simply be closed. 
Others we may want to consider for SAX 2.0.3.
-- 

   Elliotte Rusty Harold
   [email protected]
   Effective XML (Addison-Wesley, 2003)
   http://www.cafeconleche.org/books/effectivexml
   http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE. 
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
List: sax-devel, [email protected]
See:  http://www.saxproject.org/
https://lists.sourceforge.net/lists/listinfo/sax-devel