Skip to content

Authoritative Sources

ConceptSource UML

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. See the ConceptSource entity definition for the authoritative field list.

ConceptSource fields

FieldTypeCard.Description
typesourceType0..1authoritative or lineage
statussourceStatus0..1Relationship between entry content and source
originCitation0..1The bibliographic citation
modificationstring0..1Description of changes made relative to the source

Source type

Each ConceptSource carries a type attribute distinguishing between two kinds of source:

  • authoritative — The source is the definitive origin of the content.
  • 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 describes the relationship between the entry content and the cited source:

StatusDescription
identicalThe content is identical to what appears in the source
modifiedThe content has been modified from the source
restyledThe content has been restyled (e.g. formatting changes)
context-addedAdditional context has been added to the source content
generalisationThe content is a generalisation of the source content
specialisationThe content is a specialisation of the source content
unspecifiedThe relationship to the source is unspecified

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

Citation

A bibliographic citation with structured reference, locality, and optional link.

FieldTypeCard.Description
refCitationRef0..1Structured citation reference (source + id + optional version)
localityLocality0..1Location within the cited document
linkanyURI0..1URL to the cited document
originalstring0..1Original text from the source
custom_localityCustomLocality[]0..*Custom name-value locality pairs

Citation Reference

A structured reference to a source document.

FieldTypeCard.Description
sourcestring0..1The source document identifier
idstring0..1The specific identifier within the source
versionstring0..1Version of the source

Locality

A location within a cited document (section, clause, page, etc.).

FieldTypeCard.Description
typestring1..1Locality type (e.g. section, clause, page)
reference_fromstring0..1Start of the locality range
reference_tostring0..1End of the locality range

Custom Locality

A custom name-value locality pair within a citation.

FieldTypeCard.Description
namestring1..1The locality name
valuestring1..1The locality value

Multi-level source hierarchy

Sources can be attached at multiple levels of the model:

LevelScope
ManagedConcept.sourcesApplicable to the concept as a whole
LocalizedConcept.sourcesApplicable to a specific language version
Designation.sourcesSources for individual terms
DetailedDefinition.sourcesSources for individual definitions, notes, or examples
NonVerbRep.sourcesSources for non-verbal representations

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.

The glossary as authoritative source

In some cases, the glossary itself is the authoritative source — when a term and its definition originate within the glossary rather than being adopted from an external standard.

See the YAML Schema Reference for the complete JSON Schema definitions, the Entity Field Reference for all entity types, and the Standards compliance reference for ISO standard mappings.

An open source project of Ribose