OASIS logo

DITA Version 1.1

Specification Overview

OASIS Standard

1 August 2007

This Version:

http://docs.oasis-open.org/dita/v1.1/OS/overview/overview.html

Previous Version:

http://docs.oasis-open.org/dita/v1.1/CS01/overview/overview.html

Latest Version:

http://docs.oasis-open.org/dita/v1.1/overview/overview.html

Technical Committee:

OASIS Darwin Information Typing Architecture (DITA) TC

Chair(s):

Don Day

Editor(s):

Michael Priestley, Robert D. Anderson, and JoAnn Hackos

Related Work:

This overview page replaces or supercedes:

OASIS DITA Version 1.0

This specification is related to:

OASIS DITA Version 1.1 Architectural Specification Committee Specification 01 (http://docs.oasis-open.org/dita/v1.1/CS01/archspec/archspec.html)

OASIS DITA Version 1.1 Language Specification Committee Specification 01 (http://docs.oasis-open.org/dita/v1.1/CS01/langspec/ditaref-type.html)

OASIS DITA Version 1.1 DTDs Committee Specification 01 (http://docs.oasis-open.org/dita/v1.1/CS01/dtd/ditadtd.zip)

OASIS DITA Version 1.1 Schemas Committee Specification 01 (http://docs.oasis-open.org/dita/v1.1/CS01/schema/ditaschema.zip)

Declared XML Namespace(s):

[none]

Abstract:

The Darwin Information Typing Architecture (DITA) Version 1.1 comprises the following individual components: an architectural specification, a language specification, a set of DTDs and an equivalent set of Schemas.

Status:

This document was last revised or approved by the 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.

Notices

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 Introduction

1.1 Architectural specification

1.2 Language specification

1.3 DTDs and Schemas

1.4 Terminology

1.5 Normative References

1. Introduction

Version 1.1 of the Darwin Information Typing Architecture (DITA) is made up of four distinct units: an architectural specification, a language specification, and the DTD and Schema implementations of the language.

1.1 Architectural specification

The architectural specification defines many of the core concepts behind DITA. It is divided into the following sections:

While the specification does contain some introductory information, it is not intended as an introduction to DITA nor as a users guide. The intended audience of this specification consists of implementers of the DITA standard, including tool developers and specializers.

1.2 Language specification

The language specification defines each element that is part of the core DITA specification. It includes all elements from the core DITA map and topic specifications, as well as all OASIS approved specializations (both topic and domain specializations). Beginning with version 1.1 it also includes each element in the DITAVAL format, which may be used when processing or displaying DITA content.

The specification provides the following information for each element:

Many elements in the language specification also include usage examples. In general, processing implications are not listed unless they are useful in describing the purpose of the element.

1.3 DTDs and Schemas

The DITA specification includes DTD and Schema implementations of all OASIS DITA components. They each include the following document types:

The architectural specification includes overviews of each document type, as well as suggestions on when to use each one.

Although the DTDs are considered normative, the DTDs and Schemas are functionally equivalent.

1.4 Terminology

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” are to be interpreted as described in [RFC2119].

1.5 Normative References

[RFC2119]

S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.