A note about a modification to a concept.
A controlled vocabulary in use for ten years will have been edited many times. Labels are corrected, concepts are split and merged, broader terms are rearranged. Users who return after a while want to know what moved and why. SKOS offers skos:changeNote for exactly that: a note about a modification to a concept.
One of seven SKOS notes
SKOS defines a general skos:note and six specialized sub-properties. Each serves a different reader:
| Property | Content | Main audience |
|---|---|---|
| skos:changeNote | a modification to the concept | maintainers, returning users |
| skos:definition | what the concept means | everyone |
| skos:editorialNote | administrative housekeeping | editors |
| skos:example | an example of use | indexers |
| skos:historyNote | past state, use or meaning | users of older records |
| skos:scopeNote | how the concept should be used | indexers |
Because all six are sub-properties of skos:note, a query for every note on a concept can use the general property, while an interface can show only the definition and scope note to the public and keep the rest for staff.
Change note or history note
The two are often confused. A skos:historyNote is about the concept’s past meaning in the world of indexing: how it was used, what it covered before a reorganization. A change note is about edits to the record itself. Consider a carrier vocabulary where the concept “Optical disk” had its spelling corrected to “Optical disc”. That is a change note. If the same concept had covered only CDs until 2015 and then widened to include DVDs and Blu-ray, that belongs in a history note, because an indexer reading old records needs it to interpret them.
skos:editorialNote is the third neighbor, meant for working comments (“check against the 2023 RDA update”) that should not be published at all.
Writing change notes that help
The SKOS reference leaves form open, so the useful conventions come from practice:
- Start with an ISO 8601 date. It sorts naturally and removes ambiguity between 05/02 and 02/05.
- Name what changed in terms the reader will recognize: labels as they appeared, concept identifiers as well as names.
- Say where an old label went. If a superseded preferred label became an skos:altLabel, mention it so searchers know the term still works.
- One change per note. A concept with four notes is easier to read than one long paragraph.
Notes can carry a language tag like any other literal. Multilingual vocabularies sometimes write change notes in a single working language only, which is a reasonable shortcut as long as it is consistent.
Structured change notes
SKOS places no range on documentation properties. The example shows the second form the SKOS Primer describes: a note as a resource with rdf:value for the text and Dublin Core properties for its author and date. That turns a list of notes into something a script can sort or filter, at the price of a slightly more complex graph. Projects that publish vocabularies through a management tool often generate this form automatically.
In the plain-literal form, the date and the author tend to be written into the text itself, as in the first note of the example. That is readable but hard to query. A team that starts with literals and later needs reports, for example every label change made in one year, will have to parse its own notes, so the choice is worth making early, before several hundred notes exist.
Neither form replaces proper version history. A change note says what a person thought worth recording; the full diff of triples between releases lives in the publishing system, and a dated release with its own version identifier is what external users cite when they need to reproduce an earlier state.
Example in RDF
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
<https://example.org/vocab/carriers/c0107> a skos:Concept ;
skos:prefLabel "Optical disc"@en ;
skos:changeNote "2024-05-02: preferred label changed from 'Optical disk' to 'Optical disc'; old form kept as altLabel."@en ;
skos:changeNote [
rdf:value "Broader concept changed from c0090 to c0102."@en ;
dcterms:creator <https://example.org/staff/jsmith> ;
dcterms:date "2025-01-14"
] .
Questions about skos:changeNote
What is skos:changeNote?
It is a SKOS documentation property for a note about a modification to a concept: a changed label, a moved broader term, a revised definition. It is a sub-property of skos:note and is used to keep a readable record of edits.
What is the difference between skos:changeNote and skos:historyNote?
A changeNote records fine-grained edits to the concept, usually for maintainers. A historyNote describes the past state, use or meaning of the concept for users. 'Label corrected on 2024-05-02' is a change note; 'used for audio and video discs before 2015' is a history note.
Can a concept have multiple change notes?
Yes. skos:changeNote is repeatable, and a concept that has been edited several times often carries one note per change. Starting each note with a date keeps the sequence readable, and sorting by that date gives a simple timeline of the concept.
Can a skos:changeNote be a resource instead of a string?
Yes. SKOS documentation properties have no range restriction. A note can be a literal, or a resource with rdf:value plus metadata such as dcterms:creator and dcterms:date, which allows structured change logs.
Is a change note a substitute for version control?
No. It is a human-readable summary attached to the concept. Full version history (who changed which triple when) belongs in the vocabulary management system or a versioned repository; the change note tells readers what matters.