• To: XML Developers List <xml-dev@l...>
• Subject: Re: JSR 206 and SAX
• From: David Megginson <dmeggin@a...>
• Date: Wed, 18 Feb 2004 21:07:16 -0500
• In-reply-to: <87znbgt3nb.fsf@n...>
• References: <87znbgt3nb.fsf@n...>
• User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040122 Debian/1.6-1

Norman Walsh wrote:

> In fact, I have had remarkable difficulty eliciting any response from
> the readers of the sax-devel list or David Megginson or David
> Brownell, the only individuals with committer status on the SAX
> project.

It looks like Dave Brownell is no longer actively maintaining SAX.  I did 
exchange initial e-mails with Norm, but have not followed up further, partly 
because of pressing committments and partly because I'm not sure if I still 
have my old SourceForge password.  I can take over as a caretaker maintainer 
for SAX again for a while, but I'm afraid that my response times might not 
be brilliantly fast right now because I have a lot going on.

I sympathize with the fact that the JSR 206 deadline is pressing, but let's 
shift the focus to SAX itself, since many of us (including me) have never 
looked at Sun's Java XML APIs.  Perhaps Norm could post a short list of 
changes that he believes are necessary for SAX2 to support XML 1.1 and 
Namespaces 1.1 properly.  We can discuss them for a few days, and then 
consider some code and documentation changes for SAX itself.


All the best,


David

• Follow-Ups:
  • Re: JSR 206 and SAX
    • From: Norman Walsh <ndw@n...>

• References:
  • JSR 206 and SAX
    • From: Norman Walsh <ndw@n...>

• Prev by Date: Re: JSR 206 and SAX
• Next by Date: RE: <selector xpath="."/> doesn't work
• Previous by thread: Re: JSR 206 and SAX
• Next by thread: Re: JSR 206 and SAX
• Index(es):
  • Date
  • Thread