•

ES 2501

First edition

Date: 2025-05-01

ES

Terminology management — Principles and methods




Foreword

The Enosema Foundation (“ES”) is the premier non-profit standardization organization for terminology standardization and terminology related processes such as management. It facilitates the education, standardization, research, promotion, definition, and usage of terminology resources and management practices globally.

ES works with international partners and experts across the globe, reflecting the international nature of its mission. More information about ES is available on the official website (https://www.enosema.org).

The procedures used to develop this document and those intended for its further maintenance are described in the ES Directives.

In particular, the different approval criteria needed for the different types of ES documents should be noted. This document was drafted in accordance with the editorial rules of the ES Directives.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ES shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be provided in the Introduction.

Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.

This document was prepared by Technical Committee Terminology.


Introduction

Terminology, the collection of terms and their definitions within a specific domain, forms the foundation of effective communication in specialized fields. Terminology management refers to the systematic handling of terminology, including the creation, collection, recording, processing, and dissemination of terminological information across organizations and domains.

In our increasingly globalized and specialized world, the consistent use of terminology has become essential for clear communication, accurate knowledge transfer, and effective content management. Poorly managed terminology leads to misunderstandings, inconsistencies in documentation, increased translation costs, and potential safety and compliance issues in regulated industries.

Several international standards provide the foundation for terminology work, including ISO 704 (Terminology work — Principles and methods), which establishes the basic principles and methods for terminology work; ISO 30042 (Management of terminology resources — TermBase eXchange (TBX)), which specifies a framework for representing terminological data; and ISO 10241-1 and ISO 10241-2, which provide guidelines for terminological entries in standards and the adoption of standardized terminological entries.

Despite the existence of these standards, organizations often struggle with implementing effective terminology management practices due to a lack of practical guidance, organizational commitment, and understanding of the principles and methods involved. Inconsistent terminology usage continues to be a significant challenge across industries, leading to confusion, inefficiencies, and increased costs.

This document addresses this gap by providing comprehensive guidelines for terminology management based on established international standards and best practices. It outlines the core principles, consistency approaches, requirements, and presentation rules necessary for effective terminology management.

The guidelines presented in this document are designed to help organizations:

  • Establish consistent terminology across all content and communications

  • Implement efficient terminology management processes

  • Build and maintain terminology resources that meet international standards

  • Improve the clarity and quality of content

  • Reduce translation and localization costs

  • Facilitate knowledge transfer and communication across boundaries

By following these guidelines, organizations can improve the clarity and consistency of their communications, enhance their content quality, reduce costs, and better serve their global audiences.

This standard builds upon the significant contributions of terminology experts worldwide and the foundational work established in ISO standards. The Enosema Foundation recognizes the critical importance of terminology management in today’s knowledge-based economy and is committed to advancing terminology standardization and related processes.

Terminology management — Principles and methods

1  Scope

This document specifies principles, methods, and best practices for terminology management across organizations and domains. It provides a standardized approach to the creation, collection, storage, processing, and dissemination of terminology resources.

The guidelines specified in this document apply to all terminology management activities, regardless of the subject field, industry, or organization size. The standardized approaches enhance terminology consistency, improve communication clarity, and ensure compliance with international terminology standards.

This document provides practical guidance for implementing effective terminology management processes based on established international standards, including ISO 704, ISO 30042, ISO 10241-1, and ISO 10241-2, with examples illustrating the application of these principles in various contexts.

This document is intended for:

  • Terminology managers and terminologists responsible for developing and maintaining terminology resources

  • Content creators, technical writers, and documentation specialists who need to apply consistent terminology

  • Translators and localizers who work with specialized terminology across languages

  • Standards developers who need to ensure terminological consistency in their documents

  • Subject matter experts contributing to terminology resources

  • Managers and decision-makers responsible for content quality and strategy

The guidelines specified here complement the principles and methods described in ISO 704, the data exchange formats defined in ISO 30042, and the rules for terminological entries established in ISO 10241-1 and ISO 10241-2.

2  Normative references

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

ISO 704:2022, Terminology work — Principles and methods

ISO 10241-1:2011, Terminological entries in standards — Part 1: General requirements and examples of presentation

ISO 10241-2:2012, Terminological entries in standards — Part 2: Adoption of standardized terminological entries

ISO 30042:2019, Management of terminology resources — TermBase eXchange (TBX)

3  Terms and definitions

For the purposes of this document, the following terms and definitions apply.

ISO and IEC maintain terminology databases for use in standardization at the following addresses:

terminology

set of designations belonging to one special language

[SOURCE: ISO 704:2022]

term

verbal designation of a general concept in a specific subject field

[SOURCE: ISO 704:2022]

terminology management

management of terminology resources through the systematic collection, description, processing, and presentation of concepts and their designations

[SOURCE: ISO 30042:2019]

terminology database

database containing terminology data

[SOURCE: ISO 30042:2019]

concept

unit of knowledge created by a unique combination of characteristics

[SOURCE: ISO 704:2022]

terminological data

data related to concepts or their designations

[SOURCE: ISO 30042:2019]

designation

representation of a concept by a sign which denotes it

Note 1 to entry: In terminology work, three types of designations are distinguished: symbols, appellations and terms.

[SOURCE: ISO 704:2022]

definition

representation of a concept by a descriptive statement which serves to differentiate it from related concepts

[SOURCE: ISO 704:2022]

3.9

terminological entry

part of a terminological data collection which contains the terminological data related to one concept

[SOURCE: ISO 10241-1:2011]

subject field

field of special knowledge

[SOURCE: ISO 704:2022]

concept harmonization

activity leading to the establishment of a correspondence between two or more closely related or overlapping concepts in order to eliminate or reduce minor differences between them

[SOURCE: ISO 704:2022]

concept system

set of concepts structured according to the relations among them

[SOURCE: ISO 704:2022]

term extraction

process of identifying and collecting term candidates from a corpus by manual, automatic, or semi-automatic means

terminology workflow

series of coordinated terminology activities

terminology resource

structured collection of terminological data

4  Principles of terminology management

4.1  General

Effective terminology management is founded on a set of core principles derived from international standards and best practices. These principles ensure that terminology work is systematic, consistent, and of high quality, serving the needs of all stakeholders.

The principles outlined in this section build upon the fundamental principles of terminology work established in ISO 704:2022 and provide a comprehensive framework for terminology management activities across organizations and domains.

4.2  Concept-based approach

Terminology management shall be based on concepts rather than terms. A concept is a unit of knowledge created by a unique combination of characteristics.

This principle dictates that:

  1. Concepts should be clearly defined before terms are assigned

  2. Each concept should be placed within its appropriate concept system

  3. Relationships between concepts should be explicitly documented

  4. One concept should correspond to one terminological entry

EXAMPLE  Instead of creating separate entries for similar terms such as “backup,” “back-up,” and “back up,” a concept-based approach would create a single entry for the concept, documenting these terms as synonyms or variants.

4.3  Clarity and precision

Definitions and terms shall be clear, precise, and unambiguous within their subject field.

This principle requires:

  1. Definitions that clearly distinguish a concept from related concepts

  2. Terms that accurately represent the concept they designate

  3. Avoidance of ambiguity and vagueness in both definitions and terms

  4. Appropriate use of defining characteristics based on the concept type

EXAMPLE  Poor definition: “database — a collection of data” Better definition: “database — structured collection of data that is stored on a computer system and can be accessed, managed, and updated in various ways”

4.4  Subject field orientation

Terminology shall be developed and managed within the context of its subject field.

This principle emphasizes:

  1. Organizing terminology within clearly defined subject fields

  2. Understanding and respecting the conceptual structures of each field

  3. Using field-specific classification systems where appropriate

  4. Involving subject matter experts in terminology development

4.5  Documentation of sources

All terminological data shall be properly documented with reliable sources.

This principle requires:

  1. Citing authoritative sources for definitions, contexts, and other data

  2. Documenting the origin and evolution of terms

  3. Maintaining bibliographic information for all external sources

  4. Indicating the reliability and relevance of sources

4.6  Systematic management

Terminology shall be managed systematically following established processes and workflows.

This principle involves:

  1. Establishing clear procedures for terminology collection, creation, validation, and dissemination

  2. Implementing appropriate technology solutions for terminology storage and retrieval

  3. Defining roles and responsibilities for terminology management tasks

  4. Regular review and updating of terminology resources

4.7  Appropriate level of granularity

The level of detail in terminological entries shall be appropriate for the intended use and users.

This principle means:

  1. Determining the appropriate amount of information to include in entries based on user needs

  2. Balancing comprehensiveness with usability

  3. Providing sufficient context for proper understanding and application

  4. Adapting the level of technical specificity to the target audience

4.8  Stakeholder involvement

Terminology management shall involve relevant stakeholders throughout the process.

This principle emphasizes:

  1. Identifying and engaging key stakeholders (subject experts, translators, content creators, etc.)

  2. Establishing collaborative processes for terminology development and review

  3. Considering the needs and perspectives of different user groups

  4. Creating feedback mechanisms for continuous improvement

4.9  Quality assurance

Terminology management shall include quality assurance measures at all stages.

This principle requires:

  1. Establishing clear quality criteria for terminological data

  2. Implementing validation and approval processes

  3. Regular review and updating of terminology resources

  4. Monitoring the application of terminology in content

4.10  Harmonization

Terminology shall be harmonized within and across subject fields when appropriate.

This principle involves:

  1. Identifying and resolving inconsistencies in terminology use

  2. Aligning terminology across related domains and disciplines

  3. Reconciling differences in term usage across departments, companies, or regions

  4. Balancing standardization with domain-specific needs

5  Terminology consistency

5.1  General

Terminology consistency refers to the uniform and coherent use of terminology across all content within an organization or specific domain. Consistency in terminology is essential for effective communication, clear documentation, efficient translation, and improved user experience.

This section outlines approaches and strategies for achieving and maintaining terminology consistency, in accordance with the principles described in ISO 704 and the requirements for terminological entries in ISO 10241-1.

5.2  Importance of terminology consistency

5.2.1  Improved communication clarity

Consistent terminology reduces ambiguity and confusion in communication. When the same concept is consistently represented by the same term, readers can focus on understanding the information rather than deciphering terminology.

5.2.2  Enhanced content quality

Content with consistent terminology appears more professional and authoritative. Inconsistent terminology can undermine reader confidence and diminish the perceived quality of the content.

5.2.3  Reduced translation costs and improved translation quality

Consistent source terminology significantly improves translation efficiency and quality. When terms are used consistently, translation memory systems can achieve higher match rates, reducing costs and increasing consistency across languages.

5.2.4  Improved searchability and information retrieval

Consistent terminology makes it easier to find and retrieve information in documentation, knowledge bases, and other content repositories. Users can search for specific terms with confidence that all relevant information will be found.

5.2.5  Legal and safety compliance

In regulated industries, consistent terminology is often a requirement for compliance. Inconsistent terminology in safety-critical documentation can lead to misunderstandings with potentially serious consequences.

5.3  Strategies for achieving terminology consistency

5.3.1  Establishing a single source of truth

Organizations shall establish an authoritative terminology resource that serves as the single source of truth for approved terminology. This resource may take the form of:

  • A terminology database (termbase) following the TBX standard (ISO 30042:2019)

  • A terminology management system

  • A controlled vocabulary or glossary

All content creators and translators should have access to this resource and be required to use it as the authoritative reference.

5.3.2  Implementing terminology workflows

Organizations shall establish formal workflows for terminology management, including:

  1. Term identification and extraction

  2. Term research and definition

  3. Term approval and validation

  4. Term dissemination and implementation

  5. Term maintenance and updating

EXAMPLE  An effective terminology workflow:

  • Content authors flag potential new terms during content creation

  • Terminologists research the terms and propose definitions

  • Subject matter experts validate the terms and definitions

  • The approved terms are added to the terminology database

  • Content authors are notified of new approved terms

  • Translation teams are informed of terminology updates

5.3.3  Integration with content creation processes

Terminology consistency shall be integrated into the content creation process through:

  1. Terminology validation during content authoring

  2. Terminology checks in content review processes

  3. Automated terminology verification tools

  4. Style guides with clear terminology guidelines

5.3.4  Regular terminology audits

Organizations shall conduct regular terminology audits to:

  1. Identify inconsistencies in terminology usage

  2. Detect unauthorized terms or definitions

  3. Evaluate compliance with terminology guidelines

  4. Prioritize areas for terminology improvement

5.4  Measuring terminology consistency

5.4.1  Quantitative measures

Terminology consistency can be measured quantitatively through:

  • Term compliance rate: percentage of terminology usage that complies with approved terminology

  • Term coverage: percentage of concepts in a domain that have approved terms

  • Term usage frequency: how often approved terms are used correctly compared to unapproved variants

5.4.2  Qualitative assessment

Qualitative assessment of terminology consistency may include:

  • User feedback on terminology clarity and consistency

  • Subject matter expert evaluation of terminology appropriateness

  • Translator assessment of terminology translatability

  • Content reviewer reports on terminology issues

5.5  Maintaining terminology consistency over time

5.5.1  Continuous improvement processes

Terminology consistency requires ongoing attention through:

  1. Regular review and updating of terminology resources

  2. Soliciting and incorporating user feedback

  3. Monitoring term usage patterns

  4. Adapting to evolving subject field knowledge

5.5.2  Change management for terminology

When terminology changes are necessary, organizations shall implement change management processes that include:

  1. Documentation of the rationale for terminology changes

  2. Communication of changes to all stakeholders

  3. Version control of terminology resources

  4. Guidance on transitioning to new terminology

  5. Update of existing content to reflect terminology changes

5.5.3  Training and awareness

Organizations shall provide appropriate training and awareness programs to promote terminology consistency, including:

  1. Introductory training on terminology principles and practices

  2. Regular updates on terminology changes and additions

  3. Guidance on using terminology tools and resources

  4. Recognition of good terminology practices

6  Terminology requirements

6.1  General

Terminology requirements define the technical and procedural specifications for establishing and maintaining effective terminology resources. These requirements ensure that terminology resources meet quality standards, serve their intended purpose, and comply with relevant international standards.

The requirements outlined in this section are derived from established standards, including ISO 30042 for terminology data exchange and ISO 10241-1 for terminological entries in standards.

6.2  Data structure requirements

6.2.1  Terminological entry structure

Terminological entries shall include the following core components in accordance with ISO 10241-1:2011:

  • Entry identifier

  • Subject field

  • Definition

  • Term(s)

  • Source information

Additional components may include:

  • Grammatical information

  • Context examples

  • Notes

  • Multimedia representations

  • Cross-references to related concepts

  • Administrative information

EXAMPLE  Sample terminological entry structure:

Entry ID: TM-0023 Subject field: Terminology management Term: terminology database Definition: database containing terminology data Source: ISO 30042:2019 Grammatical information: noun, singular Context: “The terminology database should be regularly maintained to ensure its relevance and accuracy.” Related concepts: terminology resource, termbase

6.2.2  Concept orientation

Terminology resources shall be concept-oriented, meaning that:

  1. Each entry represents one concept

  2. All terms designating the same concept are included in the same entry

  3. Relationships between concepts are explicitly documented

  4. Each entry is assigned to at least one subject field

6.2.3  Data categories

Terminology resources shall use a consistent set of data categories for terminological information in accordance with ISO 30042:2019.

Data categories should be:

  1. Clearly defined

  2. Consistently applied

  3. Compatible with international standards

  4. Appropriate for the intended use

  5. Documented in a data category registry

6.2.4  Metadata

Terminology resources shall include appropriate metadata to facilitate management and use, including:

  • Resource identification information

  • Creation and modification dates

  • Version information

  • Responsibility information

  • Usage rights and permissions

  • Processing history

6.3  Functional requirements

6.3.1  Search and retrieval

Terminology resources shall provide effective search and retrieval capabilities, including:

  1. Multiple search criteria (term, definition, subject field, etc.)

  2. Flexible matching options (exact, fuzzy, wildcard, etc.)

  3. Filtering by various attributes

  4. Sorting options for search results

  5. Search history and saved searches

6.3.2  Data import and export

Terminology resources shall support data exchange through:

  1. Import from common terminology formats

  2. Export to standard exchange formats, particularly TBX (ISO 30042:2019)

  3. Batch processing of multiple entries

  4. Selective import and export by criteria

  5. Data conversion utilities

6.3.3  User management

Terminology management systems shall include user management functions:

  1. Role-based access control

  2. Customizable user permissions

  3. Authentication mechanisms

  4. User activity tracking

  5. Collaborative features

6.3.4  Workflow support

Terminology management systems shall support established workflows:

  1. Task assignment and tracking

  2. Status tracking for terminology entries

  3. Approval processes

  4. Notification mechanisms

  5. Integration with content creation systems

6.4  Quality requirements

6.4.1  Data validation

Terminology resources shall implement validation mechanisms to ensure data quality:

  1. Format validation for specific data categories

  2. Mandatory field checking

  3. Consistency checking across entries

  4. Duplicate detection

  5. Reference integrity checking

6.4.2  Revision control

Terminology resources shall maintain revision history:

  1. Change tracking at the entry level

  2. Version comparison

  3. Rollback capabilities

  4. User attribution for changes

  5. Timestamp information

6.4.3  Compliance checking

Terminology resources shall support compliance with terminology policies:

  1. Automated term verification in content

  2. Consistency checking against approved terminology

  3. Reporting on terminology usage

  4. Identification of deprecated terms

  5. Detection of unapproved synonyms

6.5  Documentation requirements

6.5.1  User documentation

Terminology resources shall be accompanied by comprehensive user documentation:

  1. User guides for different user roles

  2. Tutorial materials

  3. FAQ documents

  4. Best practice guidelines

  5. Quick reference materials

6.5.2  Administrative documentation

Terminology resources shall include administrative documentation:

  1. System architecture and design specifications

  2. Data models and schemas

  3. Configuration parameters

  4. Backup and recovery procedures

  5. Integration specifications

6.5.3  Process documentation

Terminology management processes shall be documented:

  1. Terminology workflows and procedures

  2. Decision-making processes

  3. Quality assurance protocols

  4. Change management procedures

  5. Implementation guidelines

6.6  Integration requirements

6.6.1  Authoring system integration

Terminology resources shall integrate with content authoring systems:

  1. Real-time terminology verification

  2. Term suggestion capabilities

  3. Context-sensitive terminology lookup

  4. Direct access to terminology resources from within authoring tools

  5. Automated terminology extraction from draft content

6.6.2  Translation system integration

Terminology resources shall integrate with translation tools:

  1. Compatibility with translation memory systems

  2. Support for multilingual terminology management

  3. Term recognition in translation interfaces

  4. Terminology consistency checking during translation

  5. Terminology extraction from aligned bilingual content

6.6.3  Content management integration

Terminology resources shall integrate with content management systems:

  1. Shared authentication mechanisms

  2. Synchronized metadata

  3. Terminology status aligned with content lifecycle

  4. Terminology reporting within content management analytics

  5. Automated terminology updates across content repositories

7  Terminology presentation rules and requirements

7.1  General

Terminology presentation rules establish standardized formats for displaying terminological data in various contexts, ensuring clarity, consistency, and usability. Proper presentation enhances the accessibility and effectiveness of terminology resources for all users.

The presentation rules outlined in this section are based on the guidelines provided in ISO 10241-1:2011 for terminological entries and ISO 10241-2:2012 for adopted terminological entries.

7.2  Terminological entry presentation

7.2.1  General layout

The layout of terminological entries shall follow these general principles:

  1. Each entry shall be visually distinct and clearly separated from other entries

  2. Core components shall be presented in a consistent sequence

  3. Typographical devices shall be used consistently to distinguish different data categories

  4. The layout shall facilitate quick identification of key information

EXAMPLE  Example of a well-structured terminological entry:

terminology database

database containing terminology data

NOTE  Terminology databases may contain additional information such as definitions, context examples, notes, and multimedia representations.

7.2.2  Term representation

Terms shall be presented according to these rules:

  1. The preferred term shall be highlighted or presented first

  2. Synonyms shall be clearly marked and distinguished from the preferred term

  3. Deprecated terms shall be marked as such with appropriate labels

  4. Term status shall be indicated using consistent markers

  5. Terms shall be presented in their basic form unless otherwise required

EXAMPLE  Preferred term: terminology database Synonym: termbase Deprecated: term bank [DEPRECATED]

7.2.3  Definition presentation

Definitions shall be presented according to these rules:

  1. Definitions shall be clearly distinguished from other entry elements

  2. Definitions shall be presented as a single coherent unit

  3. The first word of a definition shall not repeat the term being defined

  4. Definitions shall follow a consistent grammatical pattern based on the concept type

  5. Cross-references in definitions shall be clearly marked

7.2.4  Subject field indication

Subject field information shall be presented:

  1. In a consistent location within the entry

  2. Using standardized subject field designations

  3. With appropriate hierarchical indication when necessary

  4. In a way that clearly associates it with the concept rather than with individual terms

7.2.5  Source references

Sources of terminological information shall be presented:

  1. Using a consistent citation format

  2. With clear indication of which element the source applies to (term, definition, etc.)

  3. With sufficient information to locate the original source

  4. Using standard abbreviations when appropriate

  5. With date information to indicate currency

7.3  Presentation in specialized contexts

7.3.1  Presentation in standards

Terminological entries in standards shall follow the specific rules established in ISO 10241-1:2011 and ISO 10241-2:2012, including:

  1. Placement in a dedicated “Terms and definitions” section

  2. Sequential or systematic ordering

  3. Consistent entry structure

  4. Proper cross-referencing to other standards

  5. Clear indication of adopted terms

EXAMPLE  Example of a terminological entry in a standard document:

terminology management

management of terminology resources through the systematic collection, description, processing, and presentation of concepts and their designations

*[SOURCE: ISO 704:2009]*

Figure 1

7.3.2  Digital presentation

Terminology presented in digital formats shall follow these additional requirements:

  1. Hyperlinks for cross-references and sources

  2. Appropriate use of metadata for improved searchability

  3. Consistent layout across different viewing devices

  4. Clear indication of expandable/collapsible content

  5. Accessible formatting for screen readers and other assistive technologies

7.3.3  Multilingual presentation

Multilingual terminology shall be presented according to these rules:

  1. Consistent indication of language for each element

  2. Clear visual distinction between languages

  3. Alignment of corresponding elements across languages

  4. Appropriate handling of script and directionality differences

  5. Indication of term equivalence status (full equivalent, partial equivalent, etc.)

EXAMPLE  Example of a multilingual entry:

terminology database (en) database containing terminology data

base de données terminologique (fr) base de données contenant des données terminologiques

Terminologiedatenbank (de) Datenbank mit terminologischen Daten

7.4  Typographical and formatting conventions

7.4.1  Typographic distinctions

Different data categories shall be distinguished using consistent typographic conventions:

  1. Terms may be presented in bold

  2. Definitions may be presented in regular type

  3. Sources may be presented in italic or smaller type

  4. Notes may be presented in smaller type or indented

  5. Cross-references may be presented in a distinctive font or color

7.4.2  Symbols and markers

Special symbols and markers shall be used consistently:

  1. Symbols indicating term status (preferred, admitted, deprecated)

  2. Markers for grammatical information

  3. Indicators for usage restrictions

  4. Symbols for cross-referencing

  5. Markers for context and examples

7.4.3  Abbreviations and labels

Abbreviations and labels used in terminological entries shall be:

  1. Standardized across the terminology resource

  2. Explained in a key or legend

  3. Used consistently

  4. Intuitive where possible

  5. Compliant with relevant domain conventions

7.5  Presentation requirements for specific data categories

7.5.1  Grammatical information

Grammatical information shall be presented:

  1. In a consistent format and position

  2. Using standard abbreviations

  3. With clear distinction between different grammatical attributes

  4. In accordance with the linguistic conventions of each language

7.5.2  Context examples

Context examples shall be presented:

  1. Clearly distinguished from definitions

  2. In a consistent format (e.g., italics, quotation marks)

  3. With the term highlighted or emphasized within the context

  4. With source attribution when applicable

  5. In sufficient quantity to illustrate typical usage

7.5.3  Notes and supplementary information

Notes and supplementary information shall be presented:

  1. Clearly distinguished from the definition

  2. In a consistent location

  3. Numbered if multiple notes exist

  4. With clear indication of their purpose

  5. In a hierarchical structure if appropriate

7.5.4  Concept relations

Concept relations shall be presented:

  1. Using standardized relationship indicators

  2. With clear distinction between different relation types

  3. With consistent formatting for all related concepts

  4. With appropriate directional indicators for hierarchical relations

  5. With cross-references to the related concepts


Bibliography

[1]  ISO 860:2007, Terminology work — Harmonization of concepts and terms

[2]  ISO 1087:2019, Terminology work and terminology science — Vocabulary

[3]  ISO 12615:2004, Bibliographic references and source identifiers for terminology work

[4]  ISO 12616:20021, Translation-oriented terminography

[5]  ISO 12620:20192, Management of terminology resources — Data category specifications

[6]  ISO 16642:2017, Computer applications in terminology — Terminological markup framework

[7]  ISO 22128:2008, Terminology products and services — Overview and guidance

[8]  ISO 23185:2009, Assessment and benchmarking of terminological resources — General concepts, principles and requirements

[9]  ISO 26162-1:2019, Management of terminology resources — Terminology databases — Part 1: Design

[10]  ISO 26162-2:2019, Management of terminology resources — Terminology databases — Part 2: Software

[11]  Arntz, R., Picht, H., & Schmitz, K. 2014. Einführung in die Terminologiearbeit. Hildesheim: Olms.

[12]  Cabré, M.T. 1999. Terminology: Theory, Methods, and Applications. Amsterdam/Philadelphia: John Benjamins.

[13]  Sager, J.C. 1990. A Practical Course in Terminology Processing. Amsterdam/Philadelphia: John Benjamins.

[14]  Temmerman, R. 2000. Towards New Ways of Terminology Description: The Sociocognitive Approach. Amsterdam/Philadelphia: John Benjamins.

[15]  Wright, S.E. and G. Budin. 1997. Handbook of Terminology Management. Amsterdam/Philadelphia: John Benjamins.