DITA Version 1.1
1 August 2007
http://docs.oasis-open.org/dita/v1.1/OS/archspec/archspec.zip (DITA source; see archspec.ditamap)
http://docs.oasis-open.org/dita/v1.1/CS01/archspec/archspec.zip (DITA source; see archspec.ditamap)
http://docs.oasis-open.org/dita/v1.1/archspec/archspec.zip (DITA source; see archspec.ditamap)
OASIS Darwin Information Typing Architecture (DITA) TC
Michael Priestley and JoAnn Hackos
This specification replaces or supercedes:
This specification is related to:
Declared XML Namespace(s):[none]
The Darwin Information Typing Architecture (DITA) 1.1 specification defines both a) a set of document types for authoring and organizing topic-oriented information; and b) a set of mechanisms for combining and extending document types using a process called specialization.
This document was last revised or approved by the OASIS Darwin Information Typing Architecture (DITA) TC on the above date. The level of approval is also listed above. Check the "Latest Version" or "Latest Approved Version" location noted above for possible later revisions of this document.
Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/dita/ipr.php.
The non-normative errata page for this specification is located at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita.
Copyright © OASIS® 1993-2007. All Rights Reserved.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.
The name "OASIS" is a trademark of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.
Table of Contents
1.0 About the DITA 1.1 Specification
2.0 An introduction to DITA
2.1 Definitions and background concepts
2.1.1 Basic concepts
2.2 Naming conventions and file extensions
2.3 DTD organization
2.4 XML Schema organization
3.0 DITA markup
3.1 DITA topics
3.1.1 What are topics?
3.1.2 Why topics?
3.1.3 Information typing
3.1.4 Transitional text
3.1.5 Generic topics
188.8.131.52 Topic structure
184.108.40.206 Topic content
220.127.116.11 Topic modules
3.1.10 Topic domains
3.2 DITA maps
3.2.1 What are maps?
3.2.2 Why DITA maps?
3.2.3 Common DITA map attributes and metadata
3.2.4 DITA map structure
3.2.5 DITA map modules
3.2.6 Inheritance of attributes and metadata in maps
3.2.8 Map domains
18.104.22.168 The xNAL domain
3.3 Metadata elements and common attributes
3.3.1 Common metadata elements
22.214.171.124 Publication metadata elements
126.96.36.199 Management metadata elements
188.8.131.52 Metadata qualification elements
3.3.2 Common attributes
184.108.40.206 Identifier and content referencing attributes
220.127.116.11 Metadata attributes
18.104.22.168 Miscellaneous Attributes
22.214.171.124 Architectural attributes
3.3.3 Topic properties in topics and maps
126.96.36.199 Metadata inheritance between maps and topics
4.0 DITA processing
4.1 IDs and references
4.2 Navigation behaviors
4.3 Content inclusion (conref)
4.4 Conditional processing (profiling)
4.6.1 The xml:lang attribute
4.6.2 The dir attribute
4.6.3 All elements with translation properties
5.0 DITA specialization
5.1 What is specialization?
5.2 Why specialization?
5.3 Structural versus domain specialization
5.4 Specializing foreign or unknown content
5.5 Data extensibility
5.6 Limits of specialization
5.7 Specialization in content
5.7.1 Why specialization in content?
5.7.2 Specialization of attributes
5.7.3 The class attribute
5.7.4 Class attribute syntax
5.7.5 The domains attribute
5.7.6 Specialization validity
188.8.131.52 Attribute generalization
184.108.40.206 Foreign generalization
5.8 Specialization in design
5.8.1 Why specialization in design?
5.8.2 Modularization and integration of design
5.8.4 Modularization in DTDs
5.8.5 Modularization in schemas
5.9 Specialization in processing
5.9.1 Using the class attribute
5.9.2 Processing specialized attributes
5.9.3 Processing foreign content
5.9.4 Modularization and integration of processing
5.9.6 Modularization in CSS
5.9.7 Modularization in XSLT