-
Notifications
You must be signed in to change notification settings - Fork 5
Working Group Timeline
Standard development usually takes much more time than usual software projects because we need to listen to the participants and make consensus-based decisions. The need of building consensus also demands flexibility in the timeline.
The first part of our work is development of specifications, and reach to the public draft stage. The year 2023 should be dedicated to development of the standard. After which we need to have a fairly long period in which we will encourage the implementations, which include validator, production tools and reading tools. The implementation period is very important because it provides the real-life test of the standard and helps in refining the standard.
The initial plan is as follows. We will keep on adjusting the plan and refining it further as we discover new facts.
- Finalize Minimum Viable Product (MVP) for the eBraille specification.
- Work on use cases to ensure that they cover all MVP requirements.
- Start evaluating if all the MVP requirements can be covered by existing HTML/XHTML 5 and CSS specifications.
- Start identification of the metadata required for the format.
- Figure out the approach for providing text information for tactile graphics. (we should decide whether all the information should be embedded in tactile graphic file or should the text information should be the part of content document and only graphics part should go in tactile graphics file)
- Figure out what is missing from HTML/XHTML 5 and CSS specifications with respect to MVP.
- Formulate the approach for addressing the gap.
- Evaluate which of the metadata requirements can be met by existing metadata standards.
- Figure out the approach for extending the metadata for meeting the requirements.
- Identify at least two existing tactile graphic formats to be used with this content specifications.
- Continue work on metadata.
- Continue work on content document specifications for meeting the requirements of MVP.
- Figure out the approach for managing multiple content documents.
- Commence work on packaging specifications.
- Commence debate of using HTML vs XHTML.
- Content document specifications based on XHTML/HTML and CSS should meet the requirements of MVP.
- Continue discussions on the packaging specifications, styling, and tagging needs.
- Make decision for using either HTML or XHTML.
- Packaging specifications are ready for MVP.
- Metadata for MVP is ready.
- Release the first public working draft.
- Release drafts of the styling and tagging documents
- Commence review of specifications
- Continue work on implementations and improving the public working draft.
- Continue work on implementations and improving the public working draft.
- Commence implementation of at least two authoring/production tools.
- Commence implementation of at least two reading solutions.
- Commence implementation of validator.
- Commence implementation of exemplars.
- Release the finalized specifications version 1.0.
- Release validator
- Release exemplars