Skip to content

glossarist/concept-model

Repository files navigation

Glossarist Concept/Term Models

General

Glossarist Concept and Designation models are used in glossarist-supported sites for RDF and JSON-LD generation.

These models align with multiple ISO standards for terminology management:

  • ISO 10241-1 — Terminology entries in standardized terminology

  • ISO 704 — Terminology work: principles and methods (concept systems)

  • ISO 30042 / TBX — Terminology markup framework (data exchange)

  • ISO 12620 — Data category registry (term types, register, grammar)

  • ISO 25964 / SKOS — Thesaurus interoperability (hierarchical and mapping relationships)

  • ISO 639 — Language codes

  • ISO 15924 — Script codes

  • ISO 24229 — Conversion system codes

These models are meant to be fully compatible with the data in the IEC Electropedia.

Concept-Term interaction cycle

concept term cycle

Origin

The Concept models support ISO 10241-1 and ISO/IEC Directives 2, 16.6.

In particular, the following features are supported.

  • Multiple preferred terms

  • Single definition

  • Multiple notes

  • Multiple admitted terms

  • Multiple deprecated terms

  • Multiple examples

  • Single domain (per localized concept)

  • Multiple domains (concept-level ConceptReference collection)

  • Multiple tags (concept-level organizational labels, not rendered as domains)

  • Multiple sources

Paragraph/TextElement may contain a formula.

The Definition models support ISO 10241-1 and ISO/IEC Directives 2, 17.

The following features are supported:

  • Can be a symbol or abbreviation

  • A DefinitionCollection is represented as a single clause

Designation Types (7)

Designations form a MECE (Mutually Exclusive, Collectively Exhaustive) hierarchy:

| Type | Extends | Description | |------|---------|-------------| | expression | Base | A word or phrase used as a designation | | abbreviation | Expression | A shortened form (acronym, initialism, or truncation) | | symbol | Base | A non-letter symbol representing a concept | | letter_symbol | Symbol | A single letter used as a symbol | | graphical_symbol | Symbol | An iconic or graphical symbol | | prefix | Base | A prefix that attaches before a designation | | suffix | Base | A suffix that attaches after a designation |

All types inherit from Base: designation, normative_status, geographical_area, language (ISO 639), script (ISO 15924), system (ISO 24229), international, absent, pronunciation, sources, term_type, related, register.

Relationship Types (32)

Typed semantic links between concepts, spanning four standards:

| Category | Standard | Types | |----------|----------|-------| | Lifecycle | ISO 10241-1 | deprecates, supersedes, superseded_by | | Hierarchical | ISO 10241-1 / ISO 25964 | broader, narrower | | Generic hierarchy | ISO 25964 (BTG/NTG) | broader_generic, narrower_generic | | Partitive hierarchy | ISO 25964 (BTP/NTP) | broader_partitive, narrower_partitive | | Instantial hierarchy | ISO 25964 (BTI/NTI) | broader_instantial, narrower_instantial | | Equivalence | ISO 10241-1 / ISO 25964 / SKOS | equivalent, exact_match | | SKOS mapping | SKOS | close_match, broad_match, narrow_match, related_match | | Comparative | ISO 10241-1 | compare, contrast | | Associative | ISO 10241-1 / ISO 25964 | see, related_concept, related_concept_broader, related_concept_narrower | | Spatiotemporal | ISO 25964 / TBX | sequentially_related_concept, spatially_related_concept, temporally_related_concept | | Lexical | ISO 12620 / TBX | homograph, false_friend | | Designation-level | ISO 10241-1 | abbreviated_form_for, short_form_for |

Term Types (34)

ISO 12620 / TBX term_type classification for designations:

| Category | Types | |----------|-------| | Orthographic/structural | full_form, abbreviation, acronym, initialism, clipped_term, short_form, transliterated_form, transcribed_form, truncation, variant | | Symbolic/formulaic | symbol, formula, equation, logical_expression, mathematical_expression, reference_symbol, figure_symbol, graphic_symbol, letter_symbol, roman_numeral | | Usage/provenance | code, common_name, entry_term, internationalism, international_scientific_term, part_number, phrase, phraseological_unit, scientific_name, shortcut, sku, standard_text, synonym, synonymous_phrase |

Authoritative source

An authoritative source is the "source of truth" for a terminological entry or any of its parts. It is the bibliographic reference from which the content originates, represented in the model by the ConceptSource class.

Source type

Each ConceptSource carries a type attribute of type ConceptSourceType, which distinguishes between two kinds of source:

authoritative

The source is the definitive origin of the content. This is the primary reference that the entry is based on.

lineage

The source documents the historical derivation or provenance of the content, but is not itself the authoritative reference.

For example, a term may originate from ISO 19101 (authoritative) but also reference an earlier ITU definition from which the ISO definition was derived (lineage).

Source status

The status attribute of type ConceptSourceStatus describes the relationship between the entry content and the cited source:

identical

The content is identical to what appears in the source.

modified

The content has been modified from the source.

restyled

The content has been restyled (e.g. formatting changes) from the source.

context-added

Additional context has been added to the source content.

generalisation

The content is a generalisation of the source content.

specialisation

The content is a specialisation of the source content.

unspecified

The relationship to the source is unspecified.

The optional modification attribute on ConceptSource can provide a description of any change made relative to the cited source.

Multi-level source hierarchy

Sources can be attached at multiple levels of the model, allowing different parts of a terminological entry to have their own authoritative sources:

ManagedConcept.sources

Sources at the managed concept level, applicable to the concept as a whole rather than to any specific localisation.

Concept.sources

Sources at the localised concept level, applicable to a specific language version of the concept. This allows different language versions to cite different authoritative sources. For example, English terms sourced from one standard and French terms from another.

Designation.sources

Sources for individual terms (designations), when a particular term originates from a different source than the overall concept.

DetailedDefinition.sources

Sources for individual definitions, notes, or examples, allowing each to reference its own authoritative source independently of the enclosing concept’s sources.

NonVerbRep.sources

Sources for non-verbal representations (images, tables, formulas).

This hierarchy means that a concept may have multiple authoritative sources. A concept’s definition may come from one standard while a specific term for that concept comes from another, with each part independently referencing its own authoritative source. Multiple sources may also define the concept identically, in which case each is listed as an authoritative source with identical status.

The glossary as authoritative source

In some cases, the glossary itself is the authoritative source. For example, when a term and its definition originate within the glossary rather than being adopted from an external standard. In this case, the origin attribute of the ConceptSource references the glossary’s own bibliographic citation.

The TC 204 Geolexica site is an example of this: the entire glossary represents ISO 14812 terminology, so the authoritative source for every entry is the glossary itself.

Note
The ConceptSource model is shown in the ConceptSource UML diagram below.

UML Models

Concept

Concepts

ConceptSource

ConceptSource

Designation

Designations

ManagedConcept and ManagedConceptCollection

ManagedConcepts

About

Glossarist Concept model

Resources

Stars

Watchers

Forks

Packages

 
 
 

Contributors