| Date: | Friday, 6 October 2000 |
|---|---|
| Depends: | M1 |
| Task: | More documentation
Parser initialization and the validation system needs to be documented. Driver: Jeff Rodriguez Contributors: Arnaud Le Hors - Contact task driver to contribute. |
| Task: | Re-organize package structure to separate core interfaces
and classes from implementation
Driver: Andy Clark Contributors: Arnaud Le Hors - Contact task driver to contribute. |
| Task: | Improve entity manager and scanner
Must support external entities, including the DTD entity and pre-defined general entities (e.g. &). Driver: Andy Clark Contributors: Contributors wanted! Contact task driver to contribute. |
| Task: | Improve document scanner
Handle trailing miscellaneous section; premature end of file; use the error reporter; etc. Driver: Eric Ye Contributors: Contributors wanted! Contact task driver to contribute. |
| Task: | Parsing of DOCTYPE line and DTD markup declarations
Driver: Arnaud Le Hors Contributors: Contributors wanted! Contact task driver to contribute. |
| Task: | Storing basic DTD grammar information
Driver: Jeff Rodriguez Contributors: Contributors wanted! Contact task driver to contribute. |
| Depends: | M2 |
|---|---|
| Task: | Ever more documentation
Document parser configurations and how new components and configurations would be written and connected. Driver: Andy Clark Contributors: Contributors wanted! Contact task driver to contribute. |
| Task: | Datatype validators
Only those datatype validators needed for DTD grammars need to be added. All DTD datatypes should work: CDATA, ENTITY, ENTITIES, ID, IDREF, IDREFS, NMTOKEN, NMTOKENS, and NOTATION. Driver: Jeff Rodriguez Contributors: Contributors wanted! Contact task driver to contribute. |
| Task: | Content model validators
This affects the following classes: SimpleContentModel, MixedContentModel, DFAContentModel. Driver: Eric Ye Contributors: Contributors wanted! Contact task driver to contribute. |
| Depends: | M3 |
|---|---|
| Task: | DOM implementation
Write the DOMParser to populate the DOM tree. Decide what should be done with the "deferred" DOM implementation. Driver: Arnaud Le Hors Contributors: Contributors wanted! Contact task driver to contribute. |
| Task: | Schema structures updated to current spec (22 Sep 2000)
Can this be done without using the DOM? Driver: Eric Ye Contributors: Contributors wanted! Contact task driver to contribute. |
| Task: | Schema datatypes updated to current spec (22 Sep 2000)
Driver: Jeff Rodriguez Contributors: Contributors wanted! Contact task driver to contribute. |
| Date: | Friday, 29 Sep 2000 |
|---|---|
| Task: | Document design based on Xerces community feedback
Driver: Andy Clark Contributors: Contributors wanted! Contact task driver to contribute. |
| Task: | Support classes
This affects the following classes: XMLString, XMLStringBuffer, XMLChar, EncodingMap, SymbolTable, QName. Driver: Eric Ye Contributors: Contributors wanted! Contact task driver to contribute. |
| Task: | Basic entity managment
This affects the following classes: XMLEntityManager, XMLEntityScanner. Driver: Jeff Rodriguez Contributors: Contributors wanted! Contact task driver to contribute. |
| Task: | Basic error handling
This affects the following interfaces & classes: XMLErrorReporter, some MessageFormatter. Driver: Eric Ye Contributors: Contributors wanted! Contact task driver to contribute. |
| Task: | Parsing of elements and attributes using internal
interface
This affects the following classes: XMLAttributes, XMLDocumentScanner. Driver: Andy Clark Contributors: Contributors wanted! Contact task driver to contribute. |
| Task: | Implement a SAX2 parser from internal callbacks
This affects the following classes: XMLParser, XMLDocumentParser, SAXParser. Driver: Arnaud Le Hors Contributors: Contributors wanted! Contact task driver to contribute. |