Glossary Updates16 new terms added to the glossaries · 12 November 2026, 21:23 CET
AI TechDocKnowledge
  • English (US)
  • English (UK)
  • Deutsch
All context cards

Role card

Content developer: the functional role

Who writes and maintains the content a DITA and iiRDS digital twin is built from?

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.

By knowledge.aitechdoc.world

Reviewed

Review log and changes

The short answer

The content developer is the functional role that writes and maintains the DITA topics, maps and iiRDS metadata from which the content twin of a knowledge graph is built. Michael Iantosca’s white paper names content developers among the people AI systems serve; in an adaptive architecture they are also the ones who see first when content, not vocabulary, is missing. They work within the governed vocabulary and propose changes to it; they don’t change it on their own.

For: Technical writers and everyone who writes product content

Key points

  • Writes typed topics and declares their applicability and iiRDS metadata.
  • Links safety messages to the safety requirements they come from.
  • Reports gaps and says whether content or vocabulary is missing.

Functional role

Content developer

The role in one sentence

The function that writes and maintains the DITA topics, maps and iiRDS metadata from which the content twin of a knowledge graph is built.

Responsibilities

  • Write typed topics as self-contained units of one information type.
  • Declare product applicability and iiRDS metadata within the governed vocabulary.
  • Link safety messages to the safety requirements they come from.
  • Report questions the content can’t answer and say whether content or vocabulary is missing.
  • Update topics and metadata against approved changes.

Decides

  • What a topic says and how it is structured.
  • Metadata values within the governed vocabulary.

Does not decide

  • The vocabulary itself: new terms are proposed, not added.
  • Safety requirements, which come from the risk assessment.
  • Whether a reported gap becomes a model change.

Receives

  • Product information from engineering.
  • The approved vocabulary and its changes.
  • Gaps reported by readers, users and agents.

Hands over

  • Topics, maps and their metadata.
  • Gap reports with the content view.

Typically held by

Reader roles of the pathway map that usually take on this function.

Technical writers
The main holders of the function.
Technical marketers
When they write product content close to marketing.

On the map

The context

What the role does

Every node of the content twin starts as a DITA topic someone wrote and classified. The content developer writes those topics as self-contained units, declares which products, variants and audiences they apply to and classifies them with iiRDS information types, so the graph can connect them to the product world and deliver them by situation.

In an adaptive architecture

When agents and readers keep asking what the content can’t answer, the content developer is the first to tell two cases apart: the answer is missing because nobody wrote it, or because the vocabulary has no way to express it. The first is a content task; the second becomes evidence for a candidate change. Content is updated only against approved changes.

Questions readers ask next

Is this the same as a technical writer?
Mostly, but not always. Technical writers usually hold this function; product managers, engineers or marketers who write product content hold it too while they do.
Can a content developer add a new metadata value?
Within the governed vocabulary, yes. A value that the vocabulary doesn’t know is proposed as a candidate change, not added on the spot.

Sources

  1. From knowledge graphs to adaptive semantics: evolving DITA and iiRDS digital twins for AI (white paper) — Michael Iantosca, 25 September 2026
  2. 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.