A note about the past state/use/meaning of a concept.
Vocabularies change their meaning slowly and quietly. A concept called “Disk images” may have meant floppy disks only for a decade before someone widened it. Every record indexed before that point still carries the concept, and anyone searching it today needs to know the term once meant less. skos:historyNote exists for this: a note about the past state, use or meaning of a concept.
A note for readers of old records
The property’s main value is interpretive. A searcher retrieving records with a given concept sees results from many years of indexing. If the concept’s scope changed, those results are inconsistent, and the history note is where the vocabulary explains the inconsistency.
Library subject heading systems have long used this kind of note. In printed authority files, a history note might say that a heading was established in a certain year and that earlier material sits under a former heading. When such files are published as SKOS (as LCSH is at id.loc.gov), notes of that kind map naturally onto skos:historyNote.
What a useful history note contains
The best history notes answer three questions for the reader:
| Question | Example content |
|---|---|
| When did the meaning change? | “Until 2018 …” |
| What did it cover before? | ”… floppy disk images only.” |
| Where was the rest indexed? | “Optical disc images were under c0388.” |
The third answer is the one most often missing, and it is the most useful. Written once by the person who made the change, it saves every later searcher from reconstructing the old indexing practice by trial and error. Without it, a reader knows the old records are incomplete but cannot find the missing ones.
Dates should be specific enough to act on, ideally a year or a release. “Formerly” or “in earlier versions” leaves the reader guessing which records are affected. If the vocabulary has numbered releases, citing the release number is better still, because indexing records often store the vocabulary version they were made with.
History, change and editorial notes compared
The three SKOS notes about a concept’s evolution divide the work:
- historyNote explains the past meaning to users. Public.
- changeNote logs specific modifications to the record. Often public, sometimes internal.
- editorialNote holds open questions and housekeeping. Usually internal.
A single reorganization can produce all three. The editorial note records the proposal under discussion. Once it is adopted, a change note logs the edit, and a history note explains what that means for older records. The editorial note is then deleted.
When labels are involved, a history note often mentions a former preferred label that has become an skos:altLabel. That keeps old search terms working and tells users why the familiar term now leads to a differently named concept, which otherwise looks like a search error.
Deprecated concepts
SKOS has no formal deprecation mechanism, though vocabularies commonly add owl:deprecated true and a link to a replacement concept, for example with dcterms:isReplacedBy. A history note completes the picture in human language: when the concept was retired, why, and where its content went. Concepts that are retired without any of this leave dangling identifiers in every system that indexed with them, and the first person to resolve one has no way to tell whether it was removed by mistake or by design.
Removing a concept URI entirely is the worse option. Keeping it resolvable, with a history note and a pointer, is a small ongoing cost against a recurring problem for every collection that used it.
Example in RDF
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
<https://example.org/vocab/formats/c0412> a skos:Concept ;
skos:prefLabel "Disk images"@en ;
skos:altLabel "Floppy disk images"@en ;
skos:historyNote "Until 2018 this concept covered images of floppy disks only. Images of optical and hard disks were indexed under c0388 (Digital media, other). Records indexed before 2018 may therefore use c0388 for optical disc images."@en .
Questions about skos:historyNote
What is skos:historyNote?
It is a SKOS documentation property for a note about the past state, use or meaning of a concept. It helps people reading older indexed records understand what a concept covered at the time, especially after the concept was redefined, split or merged.
Who is the audience for a history note?
Mainly searchers and indexers working with records created under earlier versions of the vocabulary. The note explains why a search may return, or miss, older material, which makes it public-facing in most vocabularies.
How is historyNote different from changeNote?
skos:changeNote logs a modification to the concept record, often in maintenance terms. skos:historyNote interprets the concept's past for its users. A change from 'disk' to 'disc' in a label is a change; a widened scope that affects old records is history.
Is skos:historyNote a sub-property of skos:note?
Yes. Like changeNote, definition, editorialNote, example and scopeNote, historyNote is a sub-property of skos:note. A query for skos:note with sub-property reasoning returns history notes alongside the others. An interface can still filter by the specific property to show history notes in their own section.
Do deprecated concepts need a history note?
It is good practice. When a concept is retired, a history note saying when, why and which concept replaced it lets anyone resolving an old identifier understand the record. Many vocabularies pair it with a link to the replacement concept.