Okay, now's the time to look at what needs to be done for Xerces2. This posting will document what I think needs to be done but consider it fluid. In other words, don't hesitate to add to the list. And it goes without saying that I would like to get some volunteers to help on the various parts. So feel free to jump right in! THINGS TO BE DONE The following is a brief list of things to be done. A full list will be kept in the "TODO" file in the "xerces_j_2" branch. In addition, I'll be keeping a list of open issues in the file "ISSUES". * Schema Validation One of the most important features needed in Xerces2 is to be able to perform Schema validation. While we've had some discussions recently about redesigning the validation engine, I think that it's more important to get Schema validation working first and *then* worry about the "right" way of doing things. My proprosal is to do a complete port of the existing validation engine of Xerces 1.x into the Xerces2 codebase. This will require a serious amount of work but is pretty straightforward. For this work, I've tagged the starting point in the Xerces 1.x codebase called "valport_x1". In addition, I've created a branch in the Xerces2 code called "valport_x2". If you want to help in the porting effort, please checkout the valport_x2 branch and start from there. I'll be posting more details about the porting effort in a separate thread. * Documentation A *lot* of documentation needs to be written. The samples document needs to be redone to reflect the changes to the samples; XNI documentation needs to be done (right now it's just a collection of HTML documents and presentations); etc. There's a BIG open issue of whether we stick with the Stylebook tool for generating our documentation or if we convert to straight HTML for simplicity. What does every- one think? * What Else? Obviously there is more to do. If you want to add something to the list, just reply to this thread and I'll update the TODO and ISSUES files. -- Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
