The OASIS DITA Technical Committee charter <ul><li>“ The purpose of the OASIS DITA Technical Committee (TC) is to define and maintain the Darwin Information Typing Architecture (DITA) and to promote the use of the architecture for creating standard information types and domain-specific markup vocabularies. ”
Governments, academics, interested parties </li></ul><li>Audience (from the charter): </li><ul><li>Writers of other specifications that could benefit from DITAs specialization model or other aspects of its architecture;
Vendors offering XML authoring or development products;
XML architects and developers who design and write XML applications;
Information developers and information architects </li></ul></ul>
Current Scope <ul><li>Subcommittees: </li><ul><li>DITA Translation Subcommittee
DITA Learning and Training Content Specialization Subcommittee
DITA Machine Industry Specialization Subcommittee
DITA Semiconductor Information Design Subcommittee
DITA for Enterprise Business Documents Subcommittee
Conferences and Workshops </li></ul><li>Defining behaviors for implementers (for example, the DITA Open Toolkit reference implementation)
Demonstrating interoperability with other standards </li></ul>
The DITA Roadmap <ul><li>OASIS DITA 1.0 (approved May 2005):
DITA 1.0 is the formalization of the DITA DTDs and Schemas contributed by IBM to OASIS in 2004.
The goal of development through the 1.x series of releases is to add function while maintaining backwards compatibility with previous 1.x releases. The DITA TC has collected and prioritized a number of requirements based on known shortcomings, user requests, and relationship with other standards and industry trends.
Starting with DITA 1.1, backwards-compatible updates will be released peridically.
Backwards-compatible bug fixes will be released from time to time as Candidate Releases keyed to just-previous approved standards. The last such release was DITA 1.0.1 in the fall of 2005. </li></ul>
Roadmap, continued <ul><li>OASIS DITA 1.1 (approved August, 2007):
Two major themes: </li><ul><li>Book deliverables </li><ul><li>Converged metadata within the bookmap
Booklist function for generating collections of content