[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fwd: partial draft TC charter, and request for help with today's minutes
OASIS Darwin Information Typing Architecture (DITA) TC TC Name Darwin Information Typing Architecture (DITA) Technical Committee Statement of Purpose Business Benefits The work of this committee will benefit any organization that creates a significant amount of content, especially if that content applies to multiple products or multiple goals (such as technical documentation, marketing literature, online knowledge bases, etc.), and/or is usable on mutiple devices. information architects who define and execute a content architecture policy for such organizations. Content creators who create that content. vendors/implementers of editors, formatting engines and other tools for editing and publishing that content. vendors/implementers of content management systems for managing/publishing that content. stylesheet designers who design the 'look and feel' of that content. Scope Deliverables The TC creates the following types of deliverables: 1. Specifications ? these comprise an architecture document with a) formal definitions of a set of information types, b) formal definitions of the rules for extending, constraining, and modifying that set by creating new structural and domain specializations through specialization and generalization, and c) descriptions of methods for integrating all such information types into document types. Supporting technical work consisting of grammar files, both Relax NG (normative) and DTD versions, for the structural and domain specializations associated with the information types defined in the architecture document. usage and reference information to support the DITA elements and their standardized specializations defined in the architecture document. The TC produces a 'base' specification for a base set of information types; it may in addition produce one or more 'profiles/profile specifications' (?not sure what the actual term is?) based on the base specification for additional commonly-used information types that are not necessary for all types of content. Use of information types defined in a profile requires availability of the information types defined in the base specification 2. Committee Notes ? these contain explanatory information about the DITA architecture that is not pertinent to the specification. ??? 3. Migration information ? this is intended to help users of the specification move from one release to a newer release when the new release contains significant changes. (or will we put this in a CN?) IPR Mode RF on Limited Terms (this is the mode OASIS has listed for us) Audience Writers of other specifications that could benefit from DITA's 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 Language English Optional References ???
Attachment:
charter-draft.pdf
Description: Adobe PDF document
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]