Darwin Information Typing Architecture

The Darwin Information Typing Architecture (DITA) specification defines a set of document types for authoring and organizing topic-oriented information, as well as a set of mechanisms for combining, extending, and constraining document types. It is an open standard that is defined and maintained by the OASIS DITA Technical Committee.

The name derives from the following components:
 * Darwin: it uses the principles of specialization and inheritance, which is in some ways analogous to the naturalist Charles Darwin's concept of evolutionary adaptation,
 * Information Typing: which means each topic has a defined primary objective (procedure, glossary entry, troubleshooting information) and structure,
 * Architecture: DITA is an extensible set of structures.

Content reuse
Topics are the foundation for content reuse, and can be reused across multiple publications. Fragments of content within topics can be reused through the use of content references (conref or conkeyref), a transclusion mechanism.

Information typing
The latest version of DITA (DITA 1.3) includes five specialized topic types: Task, Concept, Reference, Glossary Entry, and Troubleshooting. Each of these five topic types is a specialization of a generic Topic type, which contains a title element, a prolog element for metadata, and a body element. The body element contains paragraph, table, and list elements, similar to HTML.


 * A Task topic is intended for a procedure that describes how to accomplish a task. It lists a series of steps that users follow to produce an intended outcome. The steps are contained in a taskbody element, which is a specialization of the generic body element. The steps element is a specialization of an ordered list element.
 * Concept information is more objective, containing definitions, rules, and guidelines.
 * A Reference topic is for topics that describe command syntax, programming instructions, and other reference material, and usually contains detailed, factual material.
 * A Glossary Entry topic is used for defining a single sense of a given term. In addition to identifying the term and providing a definition, this topic type might also have basic terminology information, along with any acronyms or acronym expansions that may apply to the term.
 * The Troubleshooting topic describes a condition that the reader may want to correct, followed by one or more descriptions of its cause and suggested remedies.

Maps
A DITA map is a container for topics used to transform a collection of content into a publication. It gives the topics sequence and structure. A map can include relationship tables (reltables) that define hyperlinks between topics. Maps can be nested: they can reference topics or other maps, and can contain a variety of content types and metadata.

Metadata
DITA includes extensive metadata elements and attributes, both at topic level and within elements. Conditional text allows filtering or styling content based on attributes for audience, platform, product, and other properties. The conditional processing profile (.ditaval file) is used to identify which values are to be used for conditional processing.

Specialization
DITA allows adding new elements and attributes through specialization of base DITA elements and attributes. Through specialization, DITA can accommodate new topic types, element types, and attributes as needed for specific industries or companies. Specializations of DITA for specific industries, such as the semiconductor industry, are standardized through OASIS technical committees or subcommittees. Many organizations using DITA also develop their own specializations.

The extensibility of DITA permits organizations to specialize DITA by defining specific information structures and still use standard tools to work with them. The ability to define company-specific information architectures enables companies to use DITA to enrich content with metadata that is meaningful to them, and to enforce company-specific rules on document structure.

Topic orientation
DITA content is created as topics, each an individual XML file. Typically, each topic covers a specific subject with a singular purpose, for example, a conceptual topic that provides an overview, or a procedural topic that explains how to accomplish a task. Content should be structured to resemble the file structure in which it is contained.

Creating content in DITA
DITA map and topic documents are XML files. As with HTML, any images, video files, or other files that must appear in the output are inserted via reference. Any XML editor or even text editor can be used to write DITA content, depending on the level of support required while authoring. Aids to authoring featured in specialized editors include WYSIWYG preview rendering, validation, and integration with a DITA processor, like DITA-OT or ditac.

Publishing content written in DITA
DITA is designed as an end-to-end architecture. In addition to indicating what elements, attributes, and rules are part of the DITA language, the DITA specification includes rules for publishing DITA content in HTML, online Help, print, Content Delivery Platform and other formats.

For example, the DITA specification indicates that if the conref  attribute of element A contains a path to element B, the contents of element B will display in the location of element A. DITA-compliant publishing solutions, known as DITA processors, must handle the conref attribute according to the specified behaviour. Rules also exist for processing other rich features such as conditional text, index markers, and topic-to-topic links. Applications that transform DITA content into other formats, and meet the DITA specification's requirements for interpreting DITA markup, are known as DITA processors.

Localization
DITA provides support for translation via the localisation attribute group. Element attributes can be set to indicate whether the content of the element should be translated. The language of the element content can be specified, as can the writing direction, the index filtering and some terms that are injected when publishing to the final format. A DITA project can be converted to an XLIFF file and back into its original maps and topics, using the DITA-XLIFF Roundtrip Tool for DITA-OT and computer-assisted translation (CAT) tools, like Swordfish Translation Editor or Fluenta DITA Translation Manager, a tool designed to implement the translation workflow suggested by the article "Using XLIFF to Translate DITA Projects" published by the DITA Adoption TC at OASIS.

History
The DITA standard is maintained by OASIS. The latest (current) version is 1.3, approved December 2015. An errata document for DITA 1.3 was approved in June 2018.
 * March 2001 Introduction by IBM of the core DTD and XML Schema grammar files and introductory material
 * April 2004 OASIS DITA Technical Committee formed
 * February 2005 IBM contributes the original DITA Open Toolkit project to SourceForge; though regularly confused with the DITA standard, DITA-OT is not affiliated with the OASIS DITA Technical Committee
 * June 2005 DITA v1.0 approved as an OASIS standard
 * August 2007 DITA V1.1 is approved by OASIS; major features include:
 * Bookmap specialization
 * Formal definition of DITAVAL syntax for content filtering
 * December 2010 DITA V1.2 is approved by OASIS; major features include:
 * Indirect linking with keys
 * New content reuse features
 * Enhanced glossary support, including acronyms
 * New industry specializations (Training, Machinery)
 * New support for controlled values / taxonomies (Subject Scheme specialization)
 * 17 December 2015, DITA V1.3 is approved by OASIS; major features include:
 * Specification now delivered in three packages: Base, Technical content, and All Inclusive (with Learning and Training)
 * New troubleshooting topic type
 * Ability to use scoped keys
 * New domains to support MathML, equations, and SVG
 * Adds Relax NG XML syntax as the normative grammar for DITA
 * 25 October 2016, DITA V1.3 Errata 01 is approved by OASIS
 * 19 June 2018, DITA V1.3 Errata 02 is approved by OASIS

.ditaval file sample (for conditionalizing text)
Example of conditionalized text: