Role card
Ontology steward: the functional role
Who keeps the governed semantic core of a DITA and iiRDS knowledge architecture stable while the model evolves?
A role card explains a functional role: what has to be done, not a job title. One person can hold several of them, and one can be spread over several people.
The short answer
The ontology steward is the functional role that keeps the governed ontologies controlled, stable and versioned and turns approved changes into the official model. In Michael Iantosca’s white paper this is the ontology engineering that adaptive semantics adds a feedback mechanism to; it doesn’t replace it. It is a function, not a job title: in many teams an information architect and a documentation systems developer share it.
For: Information architects, documentation systems developers and technical project managers
Key points
- Keeps DITA, iiRDS extensions, product, safety and regulatory ontologies controlled, stable and versioned.
- Checks candidate changes for consistency with the model before they are evaluated.
- Models approved changes, but doesn’t decide which changes are approved.
Functional role
Ontology steward
The role in one sentence
The function that keeps the governed ontologies — DITA, iiRDS extensions, product, safety and regulatory models — controlled, stable and versioned, and turns approved changes into the official model.
Responsibilities
- Maintain the classes, relationships and rules of the governed ontologies.
- Check candidate changes for consistency with the existing model before evaluation.
- Model approved changes and release them as new versions of the core.
- Keep the semantic contract documented for every consuming system.
- Keep local extensions in line with the standards they extend.
Decides
- How an approved change is modelled: name, definition, constraints.
- Version numbers and release notes of the semantic core.
- Consistency and validation rules of the model.
Does not decide
- Whether a candidate becomes part of the enterprise model.
- The content of safety requirements or regulatory obligations.
- What a topic says.
Receives
- Approved changes from governance.
- Candidate changes with their evidence, for the consistency check.
- Updates of the standards the model builds on (DITA, iiRDS).
Hands over
- Versioned releases of the ontologies.
- Documentation of the semantic contract.
- Consistency assessments of candidates.
Typically held by
Reader roles of the pathway map that usually take on this function.
- Documentation systems developers
- Often model and release the ontologies.
- Technical writers
- Information architects among them contribute the content and metadata model.
- Technical project managers
- Plan the releases and the dependencies of downstream systems.
On the map
- The ontology as semantic contract· From knowledge graphs to adaptive semantics: the pathway map
Keeps the contract defined and documented.
- Candidate change (typed edit)· From knowledge graphs to adaptive semantics: the pathway map
Checks candidates for consistency with the model.
- Only approved changes reach the enterprise model· From knowledge graphs to adaptive semantics: the pathway map
Turns approved changes into the official model.
- Versioned semantic core· From knowledge graphs to adaptive semantics: the pathway map
Assigns and publishes the versions.
The context
What the role does
The steward maintains the ontology that works as the semantic contract between authoring, delivery, engineering and AI: the classes, relationships and rules every system relies on. When the adaptive layer proposes a candidate change, the steward checks whether it fits the existing model — names, definitions, constraints — and, once governance approves it, turns it into a new versioned release of the core.
Why it is a function, not a job
The paper doesn’t name a job title. Someone has to do this work in every architecture, whether that is an information architect, a taxonomist or a documentation systems developer. Naming the function makes it visible where nobody is assigned to it.
Questions readers ask next
- Does the ontology steward approve changes?
- No. The steward models and releases approved changes; the decision belongs to the semantic governance approver. One person can hold both functions, but the two decisions stay apart.
- Does the steward own the iiRDS standard?
- No. The iiRDS core is curated by its consortium; the steward maintains local extensions and keeps them in line with the standard.
Sources
- From knowledge graphs to adaptive semantics: evolving DITA and iiRDS digital twins for AI (white paper) — Michael Iantosca, 25 September 2026
- EvoOntology vs. iiRDS: understanding two divergent ontology paradigms — AI TechDoc Press (Saina Veigel), 23 September 2026
Review log and changes
Every context card is checked against its sources before it is published, and again whenever it changes; the date under the byline is the last review. Corrections (something was wrong) and additions (something was missing) are logged below with date and time (Berlin time). Typos, formatting and link fixes are not listed.
Reviewed
No corrections or additions since publication.