Hi there, I just realized that some mail I attempted to post re: future work for xerces 1 earlier this week bounced back - sigh.
In any case, I would like to see us put together a rollout for remaining schema support, among other things (this will probably need to be done across a few xerces releases, but I guess that depends on who volunteers to do what). I posted mail last week about the items which are remaining to be done, or are incomplete - here is the list again: - redefine - whiteSpace facet - simple value normalization - Abstract (currently ignored) - Block and final (currently ignored) - NOTATION - Annotation (currently ignored) - handling of default and fixed attributes for element decls (these are currently ignored) - Date/time - Identity constraints (experimental subset currently implemented) - Structures Chapter 5 constraint checking - rework of "all" model group (currently has limitations) I believe a subset of these features should be included in 1.3.1 (and again, I think we ought to try to define the rollout for *all* of this support). I don't mind helping out with this release planning. Unless anyone objects, I suggest we include the following schema items in 1.3.1 (as a minimum): - redefine (which Neil volunteered to work on already - see his posting from a couple of weeks ago ) - whiteSpace facet and simple value normalization (I believe Elena has begun work in this area already) - abstract (which I'll volunteer to work on next) If there are other schema features that people think are high priority, pls let us know... (and if anyone would like to help out with any of this, that would be great...) Since Edwin has done work on JAXP 1.1 already, I assume that will be included in xerces 1.3.1. Are there other features folks would like to see added? Thx, Lisa. "Ted Leung" <[EMAIL PROTECTED]> on 02/08/2001 03:24:29 PM Please respond to [EMAIL PROTECTED] To: <[email protected]> cc: Subject: Call for Xerces 1.3.1 Release Plan Now that Bugzilla is set up and 1.3 is out, I think it's a good idea to start working on a release plan for 1.3.1. Is there a known list of things that need to be done for 1.3.1? At the moment I have enough time to coordinate getting the plan together. I don't know if I have sufficient time to be the release coordinater -- I would like to try to get us moving in a way that allows more people to participate. I've taken the liberty of creating a nearly blank document in CVS: RELEASE-PLAN-1.3.1 Once we get a discussion started, we can start to pile content into the file. Ted
