The following shows the status of schema development, and proposes 2
checkpoints to roll the support out in.
Comments welcome...

If anyone wants to volunteer for particular development items or open
issues, that would be great...

Thx,
Lisa.

(See attached file: schemastatus.html)
Title: Xerces-2 Schema support: Status/Open Issues

Xerces-2 Schema support: Status/Open Issues

We propose that the remaining schema design/development work be separated into 2 parts

  1. Schema alpha including: support for the majority of XML Schema as provided in Xerces-1. Missing features: UPA and Particle Derivation checking.
  2. Schema beta including: full XML Schema support and some enhancements (grammar caching, redesigned validator, better content model support, etc.)

We may be able to target an alpha in the mid-late October timeframe (depending on how much volunteer help there is). The date for a beta is still TBD, and depends on some design work that still needs to be done/completed.

The following lists development line items and open issues for the 2 proposed checkpoints.

XML Schema alpha - no UPA or particle derivation checking

Misc. work

Line item Volunteer Status
Package reorganization Neil Graham
Build changes Neil Graham

Schema Traversal and Constraint checking

Line item Volunteer Status
XSDHandler Neil Graham In progress.
Base traverser classes Elena Litani Code complete. Testing to be done.
Simpletype traversal Elena Litani Code complete. Testing to be done.
Group traversal Rahul Srivastava Code complete. Testing to be done.
complexType traversal Lisa Martin In progress
Element traversal Sandy Gao Code complete. Testing to be done.
Identity constraint traversal Neil Graham Code complete. Testing to be done.
Notation traversal Rahul Srivastava Code complete. Testing to be done.
Attribute traversal Sandy Gao Code complete. Testing to be done.
attributeGroup traversal TBD Initial skeleton submitted by Rahul S. Needs to be completed
Wildcard traversal TBD Initial skeleton submitted by Rahul S. Needs to be completed
Particle tree construction Elena Litani Code complete. Testing to be done

Validation

The goal for the alpha is to implement a (potentially tactical) schemaValidator, similar to what is in Xerces-1.

Line item Volunteer Status
SchemaValidator Sandy Gao In progress. Partial implementation already in place for testing.
Content Model Builder Elena Litani In progress.
Simple Content Model Elena Litani Code complete. Testing to be done
DFA Content Model Neil Graham New
All Content Model TBD New

XML Schema beta

The second checkpoint would contain:

  • full XML Schema support, including particle derivation checking and UPA checking
  • redesigned validator (potentially)
  • improved content models
    • do a better job for Schema mixed models
    • try to support content models for various ranges of minOccurs/maxOccurs
  • improved message facilities
    • detect errors giving schema document location info
    • message cleanup
  • improved simpleType design (should this be moved into the alpha?)
  • some support for accessing PSVI?

Open Issues that need further work/investigation (and volunteers to lead)

  1. Schema validation re-design
    • Needs to take DOM revalidation into account
  2. Finalize grammar resolution/caching design
  3. Finalize new simpleType design
  4. PSVI API- what should we provide, how should XNI change?
  5. How can we change our error reporting facilities to improve schema messages as described above?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to