Skip to content
Property · SKOS

SKOS altLabel: how alternative labels work, with examples

Published Formatory editorial team
http://www.w3.org/2004/02/skos/core#altLabel

An alternative lexical label for a resource.

Acronyms, abbreviations, spelling variants, and irregular plural/singular forms may be included among the alternative labels for a concept. Mis-spelled terms are normally included as hidden labels (see skos:hiddenLabel).

Users search with the words they know, and those are seldom the words a vocabulary editor picked as preferred. Someone looking for “PDF” should find the concept labeled “Portable Document Format”. In SKOS, the property that makes this work is skos:altLabel: an alternative lexical label for a resource. The official usage note lists what belongs there: acronyms, abbreviations, spelling variants, and irregular plural or singular forms.

The three SKOS labeling properties

SKOS gives every concept up to three kinds of label, and their division of labor is the heart of the model:

Property Per language Shown to users Typical content
skos:prefLabel at most one yes the authorized term
skos:altLabel any number usually, as “see also” or “used for” synonyms, acronyms, variants
skos:hiddenLabel any number no misspellings, obsolete forms for search

The three are pairwise disjoint: the same literal (text plus language tag) cannot be both preferred and alternative, or alternative and hidden, on one concept. A validator such as Skosify or qSKOS reports a clash when it happens, naming the concept and the offending literal. All three are sub-properties of rdfs:label.

What makes a good alternative label

Alternative labels should be things a user might actually type or expect to see. For a format vocabulary that includes the acronym, the vendor-prefixed name, and older names of the same format, such as “Tagged Image File Format” next to “TIFF”. For a subject vocabulary like LCSH, the “Used For” references from the authority record become altLabels when the headings are published in SKOS, which is how id.loc.gov models them.

Three cautions keep the list useful:

  • An alternative label should mean the same thing as the preferred label. A broader or narrower term belongs in skos:broader or skos:narrower, not here.
  • Language tags matter. “PDF” may be an altLabel in English and French alike, with one statement each, because a literal with a different tag is a different label.
  • Ambiguous acronyms can be legitimate altLabels on several concepts. SKOS allows that; the interface then has to show enough context to let users choose.

altLabel in thesaurus conversion

Most SKOS vocabularies started life as a thesaurus built to ISO 25964 or its predecessors. The mapping is direct: a preferred term becomes the prefLabel, each non-preferred term (the “UF” entries) becomes an altLabel. What does not survive is any distinction among non-preferred terms, for instance between a true synonym and a spelling variant. SKOS-XL, the extension vocabulary, turns labels into resources so they can carry their own metadata, and projects that need to record why a label was added or retired often move to it.

The disjointness rule also catches a common conversion bug. Some thesaurus exports list the preferred term among its own non-preferred terms; a naive mapping then writes the same string as both prefLabel and altLabel, and the result fails validation. Filtering the preferred form out of the alternative list during conversion is a one-line fix.

Changes to labels are part of a concept’s history. Recording them in a skos:changeNote or skos:historyNote lets users understand why a familiar term moved from preferred to alternative.

Common mistakes

Placing misspellings in altLabel is the most visible error, since they then appear in public interfaces as accepted forms; hiddenLabel exists for that. Adding the preferred label again as an altLabel violates the disjointness rule. And leaving the language tag off some labels but not others means an untagged “PDF” and an English-tagged “PDF” count as two different literals, which defeats duplicate checks.

Example in RDF

@prefix skos: <http://www.w3.org/2004/02/skos/core#> .

<https://example.org/vocab/formats/c0031> a skos:Concept ;
    skos:prefLabel "Portable Document Format"@en ;
    skos:altLabel  "PDF"@en , "Adobe PDF"@en ;
    skos:hiddenLabel "Portable Documnet Format"@en ;
    skos:prefLabel "Format de document portable"@fr ;
    skos:altLabel  "PDF"@fr .

Questions about skos:altLabel

What is skos:altLabel?

It is the SKOS property for an alternative lexical label of a concept: a synonym, acronym, abbreviation, variant spelling or other form that users might search for. A concept can have any number of alternative labels in each language.

What is the difference between skos:prefLabel and skos:altLabel?

skos:prefLabel is the single preferred label per language, the one shown by default. skos:altLabel holds the other accepted forms. A concept has at most one prefLabel per language tag, but many altLabels.

Can the same text be both a prefLabel and an altLabel?

Not on the same concept. SKOS declares prefLabel, altLabel and hiddenLabel pairwise disjoint, so one string with one language tag can occupy only one of the three roles for a given concept.

Where should misspellings go?

In skos:hiddenLabel. Hidden labels are indexed for search but not displayed, so a user typing a common misspelling still finds the concept, without the misspelling appearing in the interface as an accepted form.

Is skos:altLabel a sub-property of rdfs:label?

Yes. prefLabel, altLabel and hiddenLabel are all sub-properties of rdfs:label in SKOS. Generic RDF tools that read rdfs:label will therefore see alternative labels too, which is why some interfaces show them unexpectedly.

More from SKOS

All 4 in this group