Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO 26162-1:2019 — Terminology Databases — Part 1: Design
Management of Terminology Resources — Terminology Databases — Design
1. Fundamentals of Terminology Database Design
ISO 26162-1:2019 is the first part of the ISO 26162 series, providing comprehensive guidelines for the design of terminology databases. As organizations increasingly manage multilingual terminology assets for technical documentation, software localization, and enterprise knowledge management, a well-structured database design becomes critical for operational efficiency. The standard establishes the conceptual framework and data model requirements for terminology management systems, with emphasis on the concept-oriented approach where each terminological entry represents a single concept rather than a single term. This approach fundamentally differs from traditional dictionary-style databases and provides superior support for multilingual terminology work across diverse technical domains.
The standard follows a modular data model separating conceptual, linguistic, and administrative levels a design pattern that maximizes flexibility and reusability across different subject domains and languages. This layered approach allows independent management of each information level while maintaining conceptual integrity.
The core design principle is that multiple terms including synonyms, abbreviations, spelling variants, and translated equivalents can be associated with the same concept identifier across languages. This enables translators to navigate directly to equivalent terms in any supported language, technical writers to maintain consistent terminology across documentation sets, and knowledge managers to build rich concept networks. The concept-oriented approach also supports advanced features such as automatic term recognition, translation memory integration, and terminology extraction from document corpora, all of which depend on clean concept-level data organization.
| Data Level | Description | Key Elements |
|---|---|---|
| Concept level | Core entry identifier forming the foundation of the database | Concept ID, definition, domain classification, concept relations |
| Language level | Language-specific information for each concept across all supported languages | Term, grammatical information, usage notes, context examples |
| Term level | Variant details for different usage scenarios and registers | Spelling variants, abbreviations, synonyms, term type classification |
| Administrative level | Metadata management ensuring quality and governance | Creation date, last modified, approval status, responsible person |
2. Core Data Categories and Modeling
The standard specifies a comprehensive set of data categories aligned with ISO 12620 and the TBX (TermBase eXchange) format defined in ISO 30042. Each category is carefully defined with its purpose, permitted values, and usage constraints, ensuring consistent application across different implementations and organizations. The data categories support the full terminology lifecycle from initial term creation through maintenance and eventual retirement, providing a complete framework for professional terminology management that scales from small project-specific term lists to enterprise-wide terminology assets containing hundreds of thousands of entries.
A well-designed terminology database implementing ISO 26162-1 principles can reduce translation costs by up to 30% through improved term consistency, eliminate ambiguity in technical documentation, streamline regulatory compliance in multilingual environments, and accelerate content localization cycles by providing translators with immediate access to approved terminology.
Key categories include subject field classification using standard taxonomies, definition types (descriptive, prescriptive, and operational with specific structural requirements), grammatical information (part of speech, gender, number, and inflectional paradigms for morphologically rich languages), usage labels (recommended, admitted, deprecated, obsolete, and superseded), geographical usage restrictions for regional language variants, and cross-references establishing relationships between related concepts. The standard particularly emphasizes documenting terminological relationships generic-specific hierarchies, part-whole decompositions, and associative thematic connections as these enable intelligent concept navigation and semantic query expansion.
3. Implementation Strategies for Engineering Teams
Successful implementation requires careful upfront planning before any software selection begins. Engineering teams should conduct a domain concept inventory, map subject field classifications to existing organizational taxonomies, define quality metrics and acceptance criteria, and establish governance procedures with clear roles and responsibilities. The standard recommends a role-based access control model where terminologists, domain experts, translators, and reviewers have clearly defined permissions aligned with their responsibilities, ensuring that terminology quality is maintained throughout the content lifecycle.
A common and costly pitfall in terminology database implementation is treating the system as a simple glossary or dictionary tool. ISO 26162-1 mandates a concept-oriented approach where definitions and metadata are attached to concepts rather than individual terms. Organizations that ignore this principle inevitably encounter data redundancy, conceptual inconsistency, and significant rework costs that can multiply project budgets.
Quality assurance is embedded through status indicators (preferred, permitted, deprecated), mandatory review cycles with documented procedures, comprehensive version management with audit trails, and automated validation rules checking for completeness, consistency, and compliance with data category specifications. The standard recommends establishing a terminology governance board with representatives from technical writing, translation, engineering, and legal departments to oversee the entire terminology lifecycle from creation through retirement, ensuring alignment with organizational goals and regulatory requirements.
Organizations that skip the systematic design phase and directly implement terminology software nearly always face substantial data migration and restructuring costs later. Decisions about data categories, concept relation types, multilingual mapping strategies, and quality metrics made during the design phase have long-lasting consequences for data quality, usability, and interoperability with downstream systems such as content management platforms and machine translation engines.
4. Frequently Asked Questions
Q1: What distinguishes a concept-oriented database from a term-oriented database in practical application?
In concept-oriented databases, each entry represents one concept with all associated terms across all supported languages linked through a shared concept identifier, ensuring conceptual integrity across languages. Term-oriented databases treat each term as an independent entry, making cross-lingual management significantly more complex and error-prone for multilingual applications.
In concept-oriented databases, each entry represents one concept with all associated terms across all supported languages linked through a shared concept identifier, ensuring conceptual integrity across languages. Term-oriented databases treat each term as an independent entry, making cross-lingual management significantly more complex and error-prone for multilingual applications.
Q2: How does ISO 26162-1 relate to the TBX interchange format?
TBX (TermBase eXchange, defined in ISO 30042) is the XML-based interchange format for terminology data. ISO 26162-1 establishes the conceptual design principles and specifies required data categories, while TBX provides the machine-readable syntax for exchanging data between different terminology management systems.
TBX (TermBase eXchange, defined in ISO 30042) is the XML-based interchange format for terminology data. ISO 26162-1 establishes the conceptual design principles and specifies required data categories, while TBX provides the machine-readable syntax for exchanging data between different terminology management systems.
Q3: What are the minimum data categories required for a compliant terminology database?
At minimum: unique concept identifier, term in at least one language, definition or explanation, part of speech classification, subject field assignment, and administrative status indicator. Professional applications should additionally include usage labels, geographical restrictions, and comprehensive cross-references.
At minimum: unique concept identifier, term in at least one language, definition or explanation, part of speech classification, subject field assignment, and administrative status indicator. Professional applications should additionally include usage labels, geographical restrictions, and comprehensive cross-references.
Q4: How frequently should a terminology database undergo formal review?
The standard recommends continuous maintenance combined with formal documented reviews at intervals not exceeding 12 months. Terminology supporting safety-critical or regulatory domains may require quarterly reviews, with each entry carrying a review date and next scheduled review date for compliance tracking across the entire terminology lifecycle.
The standard recommends continuous maintenance combined with formal documented reviews at intervals not exceeding 12 months. Terminology supporting safety-critical or regulatory domains may require quarterly reviews, with each entry carrying a review date and next scheduled review date for compliance tracking across the entire terminology lifecycle.
