It's been a long time since we actually had a release of the
Xerces2 codebase. The previous one was last year. Since then,
the codebase has changed a lot, improved, and we've added a
lot of very useful features like parser configurations.
Therefore, I think it's time we had a beta release of the
Xerces2 code. Assuming that everyone's in agreement, here's
what needs to be done for that to happen:
[1] Code Changes
There is some open code work to be done that I would like
to go into the beta release. However, it's not critical
because there's nothing stopping us from following up with
another beta shortly afterwards. What I'm talking about
specifically is the following:
1) Removing dependence on SAX (andyc)
2) Implementing scanner interface changes (twleung)
Is there any other outstanding code items that should be
considered complete before spinning a beta? Schema
support would be nice but is out of the question due to
the amazing amount of difficult work it would take to
port the Xerces 1.x Schema code into the new framework.
[2] Documentation
Perhaps the most important thing (and I probably should
have made it point [1]) is documentation. The current
docs are either incorrect (e.g. samples), or very
incomplete. We need to add a lot of content regarding
XNI. A lot of which could probably be hobbled together
from the various posts and presentations I've made.
I'll be starting to work on this a little bit as I find
time but could definitely use a lot of help in this
regard.
[3] Build and Test
We need to make sure that the build works and passes as
many tests as possible. I think we're already fully
passing the OASIS well-formedness tests but I am not
sure about DTD validation.
* * *
So, what does everyone think? and who's going to help
me pull this off in the near future?
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
