Home
DITA authoring concepts
Moving from style-based authoring to a structured authoring methodology such as DITA requires a radically different approach to writing.
Introduction to DITA
DITA is an XML standard, an architectural approach, and a writing methodology, developed by technical communicators for technical communicators.
Topic-based authoring
Content in DITA is authored in topics, rather than in larger documents or publications. A DITA topic must make sense in its own right. A topic is authored as a unit, not as part of a larger document.

Introduction
Information types and topics
Topics are the building blocks of modular documents, and organising topics by semantic information types is one of the architectural features of DITA.
DITA map files
Syntax and mark-up
Language and punctuation
Graphics and figures
Cross-referencing
Cross-references are a means of binding individual topics into a coherent and navigable document.
Content re-use
Metadata, conditional processing, and indexing
The DITA documentation process
DITA authoring concepts
Moving from style-based authoring to a structured authoring methodology such as DITA requires a radically different approach to writing.
- Introduction to DITA
  DITA is an XML standard, an architectural approach, and a writing methodology, developed by technical communicators for technical communicators.
  - History of DITA
    DITA was originally developed within the technical publications department at IBM, but was donated to OASIS in 2004. It is now maintained by the OASIS DITA Technical Committee.
  - The A in DITA
    DITA provides a standardised architectural framework for creating and maintaining content.
  - OASIS and the DITA Technical Committee
    OASIS is a not-for-profit standards body, and membership is open to all. To participate in the ongoing development of the DITA standard, you must join OASIS.
  - DITA features
    DITA incorporates features designed to improve the quality and efficiency of documentation.
  - Information typing
    Information typing is a methodology which underpins DITA. Information is structured by topics with content models appropriate to the nature of the content. The three base DITA information types are concept, task and reference.
  - Topic-based authoring
    Content in DITA is authored in topics, rather than in larger documents or publications. A DITA topic must make sense in its own right. A topic is authored as a unit, not as part of a larger document.
  - Modularity
    DITA enables modular document development. Not only can topics be re-used, but any group of topics or elements can be treated as a modular document component.
  - Minimalism
    Particularly for procedural documentation, DITA topics should be written following the minimalism approach. Information should be arranged in succinct, action-oriented topics that help readers to understand quickly what they need to know.
  - Structured authoring
    Structured authoring can mean many things, but in the context of this document, structured authoring means a standardised, methodological approach to content creation incorporating systematic labelling, modular, topic-based architecture, constrained writing environments, and the separation of content and form.
  - The separation of content and form
    Fundamental to structured authoring is the concept of the separation of content from presentation and delivery. The way a piece of text looks during authoring is irrelevant. The formatting and presentation are post-authoring considerations, and activities possibly not performed by a technical writer.
  - Where DITA fits...
    DITA is technically defined as an XML application, and is therefore built on XML language standards. XML itself is based on other character representation rules. DITA can also be used in conjunction with related standards and technologies.
  - Inheritance
    Inheritance is a key technical feature of DITA, as it is inheritance that enables specialisation of information types.
  - Conditions, filtering, variants and ditaval
    Many confusing terms are used to describe different parts of the conditional publishing process. Understanding the terms is key to understanding the concepts.
  - Techniques to learn
    Authors moving from style-based authoring to structured authoring in a DITA environment will need to build chunking, labelling and linking skills, and to understand the technique of separation of content and form.
- Distinction between format and style, and data and metadata
  In DITA, format has a different meaning to style. Likewise, the meanings of data and metadata are very different. These distinctions in meaning are important to understanding the broader concept of the separation of content and form.
- Specialisation
  Specialisation allows you to construct your own types of documents without losing the benefits of working within a DITA framework; in particular, you can maintain interchangeability.
- Generalisation
  When information in a specialised information type needs to be converted into the information type from which it was specialised, the process is known as generalisation.
- Constraints
  The constraints mechanism in DITA allows the use of elements and attributes in an information type to be restricted without needing to create a full specialisation. Constraints aim to simplify the authoring process by reducing the complexity of an information type.

Topic-based authoring

Content in DITA is authored in topics, rather than in larger documents or publications. A DITA topic must make sense in its own right. A topic is authored as a unit, not as part of a larger document.

DITA has a topic-based architecture, requiring a topic-based approach to document authoring. The term topic can be thought of as being short for topical information unit, or a topical unit of discourse.

A topic-based architecture opens up the opportunity for large scale content re-use. Topics are assembled from a single pool or repository into different deliverable documents. Topics can be used in different publications, provided the topic makes sense when read in different contexts.

A special DITA file called a map or ditamap is used to specify topics to be included in a deliverable document. The ditamap doesn't store much content; it mainly comprises of pointers to the topics that contain the content.

Not only does a topic-based architecture allow information to be re-used, it also makes translation and localisation more efficient because the same information never has to be translated more than once.