| <?xml-stylesheet type="text/xsl" href="../../../../development/milestone_plans/stylesheets/milestone-bulletList.xsl"?> |
| |
| <plan xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
| xsi:noNamespaceSchemaLocation="../../../../development/milestone_plans/milestonePlan.xsd"> |
| <component name="xml" subproject="wst"> |
| <description> |
| Milestone planning for XML Core, UI, and Tools |
| </description> |
| <milestone name="M4"> |
| <title>M4 Plan</title> |
| <category name="Design for Platform Use"> |
| <item priority="high" status="in-progress"> |
| <description> |
| Document Designs, API, JUnit tests, and |
| Performance Tests |
| </description> |
| <detail> |
| Describe not only "standard" DOM APIs we |
| support, but also, the extensions to that API, |
| include Adapters and ReadOnly APIs. |
| </detail> |
| </item> |
| <item priority="medium" status="in-progress"> |
| <description> |
| continue refactoring to improve separation of |
| components |
| </description> |
| </item> |
| </category> |
| <category name="Eclipse base parity"> |
| <item priority="medium" status="in-progress"> |
| <description> |
| Unified Validation marker/annotation model. |
| </description> |
| <detail> |
| Need to finish work started in M3, namely use |
| grey icons, and integrate as extension |
| participant. |
| </detail> |
| </item> |
| </category> |
| <category name="XML Catalog"> |
| <item priority="high" status="in-progress"> |
| <description>Provide API for XML Catalog entry contributions via extension point</description> |
| <developer name="ebelisar@ca.ibm.com" /> |
| <step start="4" pds="2"></step> |
| </item> |
| <item priority="medium" status="in-progress"> |
| <description>Investigate API requirements for XML Catalog model</description> |
| <developer name="ebelisar@ca.ibm.com" /> |
| <detail>We're not sure how much of the XML Catalog model needs to be exposed as API. We need to investigate. It's not likely that any model API will be exposed in WTP 1.0.</detail> |
| <step start="4" pds="3"></step> |
| </item> |
| <item priority="low"> |
| <description>Support OASIS standard XML Catalog format</description> |
| <developer name="ebelisar@ca.ibm.com" /> |
| <step start="5" pds="5">Implement new serializer and de-serializer</step> |
| <step start="6" pds="5">Add JUnit tests for XML Catalog resolution</step> |
| </item> |
| </category> |
| <category name="Misc. Items"> |
| <item priority="medium" status="in-progress"> |
| <description> |
| implement (minimal) DOM Core 3 |
| </description> |
| <detail> |
| Some intend to use our code with JDK 1.5. While |
| we don't claim to support full compliance with |
| 1.5 (or with DOM Core 3 APIs), this is an area |
| than may cause -verify errors even if 1.5 runs a |
| 1.4 library. |
| </detail> |
| </item> |
| <item priority="medium" status="in-progress"> |
| <description> |
| implement DOM Core 3 Validation API |
| </description> |
| <detail> |
| Four DOM API's will be the public side of our |
| validate content APIs. (Current, complex content |
| model classes/methods will be 'internal'). |
| </detail> |
| </item> |
| <item priority="medium" status="in-progress"> |
| <description>Graphical Table View</description> |
| </item> |
| <item priority="medium" status="in-progress"> |
| <description> |
| Example Cheat-Sheet XML Editor |
| </description> |
| </item> |
| </category> |
| </milestone> |
| <milestone name="M5"> |
| <title>M5 Plan (initial Rough Draft)</title> |
| <category name="Design for Platform Use"> |
| <item priority="medium" status="new" |
| helpWanted="true"> |
| <description>Improve JUnit Coverage</description> |
| <detail> |
| Seems there must be thousands of (public) XML |
| Parsing examples we should test and make sure we |
| parse the same way as other parsers, such as |
| Xerces, when well formed. |
| </detail> |
| </item> |
| <item priority="low" status="investigate"> |
| <description> |
| add (non-standard) DOM Operation API. |
| </description> |
| <detail> |
| Its purpose is to optimize notifications, undo |
| "units", and also handle such things as |
| auto-formatting for all clients. |
| </detail> |
| </item> |
| <item priority="low" status="investigate"> |
| <description> |
| investigate DOM Event model |
| </description> |
| </item> |
| <item priority="low" status="investigate"> |
| <description> |
| investigate Content Assist Participant extension point |
| </description> |
| </item> |
| </category> |
| <category name="Eclipse base parity"> |
| <item priority="low" status="investigate" |
| helpWanted="true"> |
| <description> |
| Improve formatting options |
| </description> |
| <detail> |
| The Eclipse Java Formatter has approximately 129 |
| formatting options. I'm not sure we can beat |
| that record, but we should at least investigate |
| the possiblity. :) |
| </detail> |
| </item> |
| </category> |
| </milestone> |
| </component> |
| </plan> |