Structured Authoring
DITA — Structured Authoring & XML Publishing Standard
Overview
What is DITA?
DITA (Darwin Information Typing Architecture) is an XML data model for authoring and publishing. DITA is built around the idea of topics: discrete pieces of information that can be combined and recombined into different documents.
Key Features
- Topic-based authoring: content as individual topics, not monolithic documents
- Content reuse: topics reused across multiple publications
- Conditional publishing: different versions for different audiences
- Maps and bookmaps: define structure and organization
- Specialization: extend DITA to meet specific industry needs
Also written as: Darwin Information Typing Architecture · OASIS DITA
Who DITA Applies To
DITA is an open standard maintained by the OASIS consortium and is not tied to any industry or regulator. Nobody will require it of you contractually; it is chosen. That makes the evaluation different from a military or aviation specification — the question is not what compliance demands, but whether topic-based authoring and its reuse model fit the content you actually have.
Where DITA Programs Go Wrong
- Adopting topics without adopting an information model. Unmodelled topics are just short documents, and reuse never materialises.
- Specializing early. Specialization is powerful and raises the cost of every future toolchain upgrade; most teams need it later than they think and some never do.
- Reusing by copy because keys and content references were never set up, which reintroduces exactly the divergence DITA exists to prevent.
- Choosing DITA for an aerospace program that will later be contractually required to deliver S1000D, and discovering the conversion cost at that point.
How It Relates to Other Standards
- DocBook
- The other established open documentation vocabulary. DocBook is book-shaped and rich out of the box; DITA is topic-shaped and built for reuse and specialization.
- S1000D
- The comparison that matters in aerospace and defense. DITA is lighter to adopt but has no equivalent of the CSDB or of S1000D's applicability machinery.
- W3C / XML
- The underlying layer. DITA is an XML vocabulary, so the transformation and validation tooling is the W3C stack.
DITA Questions
What is DITA?
An XML architecture for authoring content as topics — discrete, self-contained pieces of information — which are then assembled into publications using maps. Its distinguishing features are reuse across publications, conditional processing for different audiences and outputs, and specialization, which lets an organization extend the vocabulary without leaving the standard.
DITA or S1000D?
If a contract specifies one, that is your answer. Where the choice is genuinely open, it usually turns on whether you need what S1000D adds — a managed source database, lifecycle handling, and applicability across configurations — or whether that machinery is overhead for content that does not vary by tail number. DITA is materially quicker to adopt; S1000D carries more of the hard problems for you.
Is DITA suitable for regulated content?
Yes, and it is used for it widely. What DITA does not give you is the aerospace and defense lifecycle model, so where a program needs configuration-driven applicability and a controlled source database, those have to be built around it rather than assumed.
Where to Get DITA
DITA is an open OASIS standard: the specification is free to read and use, and the open-source DITA Open Toolkit publishes from it.
Where DITA Applies
All standardsTechnical publications servicesTalk to us about DITA
Get In Touch
Let's Talk
Planning, building, or migrating DITA-compliant technical content? We can help.