
Reference articles
Encyclopedia
The encyclopedia of AI TechDoc Knowledge collects reference articles written in a formal, neutral style. Each article defines its subject, traces its historical development, describes its components and functions and compares it with related concepts. Articles are grouped into subject areas; every subject area explains how its topics relate to one another and where they interoperate. Terms used in the articles link to the glossaries, and short context cards answer the questions the articles raise.
How to use the encyclopediaSubject areas
Software development kits
4 articles · 6 context cards · Last reviewed September 29, 2026
A software development kit (SDK) is a packaged set of tools, libraries, documentation and samples that enables the development of software for a particular target. The term is used across subject areas that otherwise have little in common. This subsection distinguishes four types — developer SDKs, publishing SDKs, platform SDKs and hardware SDKs — describes each in a separate article and examines the points at which they interoperate.
Overview and comparison- Developer SDKsDeveloper SDKs wrap a platform’s APIs in language libraries, authentication, serialization and error handling. Definition, history, components and uses.
- Publishing SDKsPublishing SDKs parse, validate, transform and render structured content such as DITA or XML into many output formats. Definition, history and components.
- Platform SDKsPlatform SDKs define how third-party apps, plug-ins and integrations extend a platform: extension points, manifests, sandboxes and permissions.
- Hardware SDKsHardware SDKs expose devices, sensors and processors to software through drivers, low-level libraries, toolchains and debug tools. Definition and uses.
Technical documentation models
6 articles · 4 context cards · Last reviewed October 1, 2026
A technical documentation model is a set of principles for dividing, organizing and expressing technical content. Several models shape current practice. This subsection distinguishes six — topic-based documentation, task-based documentation, Every Page is Page One, semantic documentation, minimalism and structured authoring — describes each in a separate article and examines how they combine in a documentation system.
Overview and comparison- Topic-based documentationTopic-based documentation writes content as self-contained units on one subject and assembles them into deliverables. Definition, history, types and limits.
- Task-based documentationTask-based documentation organizes content around what users do, derived from task analysis. Definition, history, components, uses and limits.
- Every Page is Page OneEvery Page is Page One (EPPO), described by Mark Baker, treats each page as the reader’s entry point. Seven characteristics, origin, uses and limits.
- Semantic documentationSemantic documentation represents the meaning of content in machine-readable markup and metadata. Definition, history, components, uses and limits.
- MinimalismMinimalism, described by John M. Carroll, designs documentation for action: real tasks, error recovery and little text. Principles, history and limits.
- Structured authoringStructured authoring writes content to a schema and separates it from formatting. Definition, history from SGML to DITA, components, uses and limits.
Cognitive psychology in technical communication
6 articles · 8 context cards · Last reviewed October 5, 2026
Cognitive psychology studies how people perceive, remember, understand, decide and act. Technical communication draws on its findings to design information that readers can find, understand and use. This subsection describes six areas along the reader’s processing chain — perception and attention, memory, reading comprehension, cognitive load, judgment and human error, and information seeking — and keeps the research findings apart from the documentation practices derived from them.
Overview and comparison- Perception and attentionPerception and attention: selective attention, Gestalt grouping, inattentional blindness and signal detection, and what they mean for layout and warnings.
- Memory and instructionsMemory and instructions: working memory, chunking, schemas and prospective memory, why "seven plus or minus two" is no rule for steps, and what follows.
- Reading comprehensionReading comprehension: construction-integration, situation models, dual coding and mental models, and how they inform concept information and plain language.
- Cognitive loadCognitive load: Sweller’s theory, split attention, expertise reversal and Mayer’s multimedia principles, with their evidence and limits for documentation.
- Judgment and human errorJudgment and human error: heuristics, satisficing, situation awareness, SRK levels and error types, and how they shape troubleshooting and recovery.
- Information seekingInformation seeking: information foraging, scent, the paradox of the active user and scanning, and how they shape navigation, headings and entry points.
Concepts, frames and cascades
7 articles · 5 context cards · Last reviewed October 13, 2026
How do minds represent concepts, and how do word meanings combine? This subject area presents the main answers discussed in cognitive science, linguistics and philosophy — frames, cascades, conceptual spaces, prototypes, decomposition and atomism, formal and cognitive semantics — and the experiments that test them. It rests on the open-access volume Concepts, Frames and Cascades in Semantics, Cognition and Ontology (Springer, 2021) and relates its ideas to ontologies, knowledge graphs and structured documentation.
Overview and comparison- FramesFrames: concepts as recursive attribute–value structures (Barsalou), their formal definition, uses in semantics and their relation to ontologies.
- Cascades and level-generationCascades: Goldman’s level-generation read as multilevel categorization, c-constitution, cascades as relations between frames, and their uses.
- Conceptual spacesConceptual spaces: concepts as regions in spaces of quality dimensions (Gärdenfors), convexity as naturalness, similarity as distance.
- Prototypes and typicalityPrototypes and typicality: graded membership, the modification effect, typical members as extremes, and frame-based category learning.
- Decomposition and atomismDecomposition vs. atomism: whether word meanings have structure, the analytic–synthetic problem, and frame-based decomposition.
- Formal and cognitive semanticsFormal vs. cognitive semantics: truth conditions and compositionality, the extensional turn, and bridges such as TTR record types.
- Cognitive structures in experimentExperimental tests of cognitive structures: reversal learning, social reinforcement in rats, action verbs and motor activity, and representational explanation.
Medical-device documentation
7 articles · 12 context cards · Last reviewed November 10, 2026
Medical-device documentation comprises the records with which manufacturers of medical devices and in vitro diagnostic devices demonstrate safety, performance and clinical benefit and keep that demonstration current. This subsection treats it as an evidence system and describes seven of its domains — the technical file, design controls and design history, risk management to labeling, clinical and performance evidence, software and AI lifecycle documentation, the comparison of EU and FDA documentation, and post-market evidence — and examines how their relationships form one chain of evidence.
Overview and comparison- Technical documentation as an evidence systemThe technical file of a medical device as an evidence system: MDR and IVDR Annexes II and III, consistency as evidence, and what structure can provide.
- Design controls and design historyDesign controls and their records: DHF, DMR and DHR as practice terms after the FDA QMSR, and the medical device and design files of ISO 13485.
- Risk management to labelingFrom hazard to IFU warning: ISO 14971:2019 risk control priority, information for safety, IEC 62366-1 and the traceability of warnings in labeling.
- Clinical and performance evidenceClinical evaluation, PMCF and IVDR performance evaluation as evidence, the clinical benefit, and why claims are controlled statements that need evidence.
- Software and AI lifecycle documentationIEC 62304, SOUP, SaMD and AI-enabled device software functions; PCCPs, the AI Act and one technical file for AI medical devices.
- EU and FDA documentation comparedEU technical documentation and notified bodies vs. FDA 510(k), De Novo and PMA; QMSR vs. ISO 13485, PCCP vs. EU change rules, EUDAMED vs. GUDID.
- Post-market evidencePost-market surveillance, PSUR, PMCF, vigilance, trend reporting and CAPA, FDA medical device reporting, and how post-market signals update the documentation.
About the encyclopedia
Encyclopedia articles are written in a formal, neutral register and follow a fixed sequence of sections: definition, historical development, components, function and purpose, applications, comparison with related concepts and conclusion. The glossaries define the individual terms; the context cards answer single questions in a few sentences. Naming a product, standard or technique in an article does not imply that any system conforms to it.