Technical documentation models

Structured authoring

Also known as: Structured writing · Structured content authoring · XML authoring

Structured authoring is a model of technical documentation in which content is written according to a formally defined structure, usually expressed as a schema or document type definition, and validated against it. Content is separated from its presentation; formatting is applied at publishing time. Structured authoring enables consistent content, automated publishing to several output formats and reuse at the level of elements.

By knowledge.aitechdoc.world · Last reviewed October 1, 2026

Definition

In structured authoring, each document or topic follows a content model that defines which elements may occur, in what order and how often. The structure is enforced by authoring tools and by validation. Presentation is defined separately in stylesheets or transformation pipelines that produce HTML, PDF and other formats from the same source.

Historical development

Generalized markup was developed at IBM from 1969 as GML. It led to the Standard Generalized Markup Language (SGML), published as ISO 8879:1986, which became the basis of documentation systems in defense, aerospace and publishing. DocBook originated in 1991 for software documentation. XML, a W3C Recommendation since 1998, simplified SGML and made structured content processable by widely available tools. Domain specifications followed, among them S1000D for technical publications in aerospace and defense and DITA for topic-based documentation.

Components

Content model. The rules defining elements, attributes and their permitted combinations, expressed as a DTD, XML Schema, RELAX NG or comparable grammar.
Validation. Checking content against the model, optionally extended by rule-based checks such as Schematron.
Authoring tools. Editors that guide writers through the structure.
Transformation. Pipelines that convert structured source into output formats.
Content management. Systems that store, version and reuse structured units, such as component content management systems.

Function and purpose

Structured authoring makes content consistent across writers and products, allows automated multichannel publishing, supports reuse of elements and topics, and gives other systems reliable access to content. The structure also supports translation by separating text from layout.

Applications

The model is used for product and machinery documentation, aircraft and defense maintenance data, regulatory submissions, software documentation and reference works. Lightweight structured formats such as Markdown with front matter apply some of its principles with less formal enforcement.

Limitations

Introducing structured authoring requires information modeling, tool investment and training. Content models that are too rigid hinder writers; models that are too loose lose the benefits of structure. Structure alone does not ensure that content is correct, relevant or understandable.

Relation to other models

Structured authoring is the technical foundation on which topic-based, task-based and semantic documentation are commonly implemented. It can enforce the patterns that EPPO and minimalism describe, for example by requiring a context element or a result after each step.

Conclusion

Structured authoring turns documentation into data with a defined structure. It provides the mechanisms on which the other documentation models depend for consistency and automation.

Cite this article

knowledge.aitechdoc.world. “Structured authoring.” Encyclopedia, AI TechDoc Blog. Last reviewed October 1, 2026. https://knowledge.aitechdoc.world/encyclopedia/technical-documentation-models/structured-authoring

Glossary terms

Structured authoring

In technical communication, structured authoring is a way of writing in which content is created as discrete information units that follow a formally defined content model — a schema, document type definition, or specification — rather than as free-form pages shaped by a word processor. Meaning is marked up explicitly (a warning is tagged as a warning, a step as a step), while typography, pagination, and layout are applied later by a publishing process. Because the markup is validated against the model, the same source can be checked automatically, reused across deliverables, and rendered to print, HTML, or machine-readable formats. Structured authoring is one of the six documentation models described in the encyclopedia subject area Technical documentation models and is usually combined with the others rather than used alone.

Schema (data)

In information architecture, a schema is a formal definition of data structure, types, fields, constraints and allowed values. Data or documents can be checked against it automatically.

Schema validation

In data processing, schema validation is the automated check of a data document, such as XML, JSON or a configuration file, against a schema that defines its permitted structure, data types, values and required elements.

DITA (Darwin Information Typing Architecture)

DITA (Darwin Information Typing Architecture) is an OASIS XML standard for creating, managing and publishing topic-based content. Content is authored as typed topics, organized and reused through maps, and extended through specialization. DITA 1.3 is the version approved by OASIS in December 2015.

DITA specialization

In DITA, specialization is the mechanism for defining new element types and attributes as extensions of existing ones. A specialized element is based on an existing element, declares its ancestry in the @class attribute and can always be processed, or generalized, as its ancestor.

DITA content reference (conref)

In DITA, a content reference (conref) is a reuse mechanism in which an element, through the @conref attribute, pulls in the content of another element of the same type from another topic or map. When the document is processed, the referencing element is replaced by the referenced element.