On Wed, 2002-03-27 at 13:02, [EMAIL PROTECTED] wrote: > Hi folks, > > Sandy asked me to forward this along. > > ******************* > > Hi all, > > Guess it's time to collect things that we want to see in the next release > of Xerces-2. Here is a list of development items that we think are > important. > > - Full PSVI support > > This has been asked for again and again on the mailing list. We need to > either define or adopt a schema component API, then implement it. Then the > schema components will be exposed via PSVI items. This also includes > read-only support of DOM L3 Abstract Schema. > > - Performance > > There has been no specific effort to improve the parser's performance. (But > Xerces-2 still performs pretty well. :-)) Details about performance > concerns of Xerces-2 that we're aware of will follow in a separate note. > > Some performance data has been posted to the list. If anyone has more > concerns or more comparison data between Xerces-2 and other XML parsers, > you are welcome to post it; this will help us make improvements.
I think this needs to be an ongoing item. I have a copy of OptimizeIt and am willing to use it if we can agree on what areas we want to improve. There's an article on Sun's web site that shows some concerns http://developer.java.sun.com/developer/technicalArticles/xml/JavaTechandXML_part2 > - Grammar caching > > We are finishing up the grammar caching functionality for XML Schema (which > you'll see soon). The remaining work is how to cache DTD grammars. > > - DOM L3 > > DOM L3 is only partially implemented in Xerces-2. Implementing every piece > of DOM L3 doesn't seem reasonable/feasible in the near future, but we may > at least want to implement the DOM Core part (which includes DOM validation > -- validate a DOM tree against some Abstract Schema). Another interesting > part is DOM AS, which is related to PSVI support (as mentioned above). > > - SAX > > As indicated in one of the bug reports, Xerces-2 doesn't currently use the > latest SAX code. We need to investigate whether/how to upgrade to it. I think there's a bigger issue here as well. On the PMC phone call this week, we discussed the issue of xml-commons in relation to JAXP, DOM and SAX. I'd like to see us use as much of commons as we can -- we can get commit privs if we need them. I'm willing to help on this. Last item, there is a new JSR for Pull-Parsing: http://www.jcp.org/jsr/detail/173.jsp Since the XNI pull api is one of the references, I think that someone from Xerces should be involved -- anyone interested? > > Does any one have more items to add to this list? And is there any > volunteer who wants to help out on any of the development items? > > Cheers, > Sandy Gao > Software Developer, IBM Canada > (1-905) 413-3255 > [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
