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


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: ANN: SAX 2.0 extension proposals.

[ Lists Home | Date Index | Thread Index ]
  • From: Stefan Haustein <haustein@kimo.cs.uni-dortmund.de>
  • To: David Megginson <david@megginson.com>
  • Date: Tue, 22 Feb 2000 11:54:05 +0100

David Megginson wrote:
> Miles Sabin <msabin@cromwellmedia.co.uk> writes:
> > Better to put that in the SAX core, I'd say.
> For the SAX core, I'm leaning towards a rewrite of the SAX1
> ParserFactory into XMLReaderFactory, only with methods that throw
> SAXException (as David B. suggested).  It will look like this:



isn't it possible to include at least the provider 
file core of Miles proposal in SAX2? I could live 
with a solution that includes instantiation, but
the global variable approach (shudder) alone 
will surely become inapropiate when more
and more libraries for different purposes
depend on xml parsers (with different 
features). With Miles approach, the libraries 
could just search an appropiate parser on their 
own, whereas with the system property approach 
the application would need to take
care about handling the "right" parser
over to the library. Thus, using
XML components would become
more complicated than neccessary.

I agree that Miles' proposal could be
put into a separate (sax independent) package, 
in principle, but without putting it into SAX2 
core, parser vendors would not be forced to
supply the parser vendor file, so it would be 

Best regards


Stefan Haustein
University of Dortmund
Computer Science VIII

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/threads.html


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

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