A note for an editor, translator or maintainer of the vocabulary.
Every vocabulary under active maintenance accumulates small questions. Is this translation right? Should these two concepts merge? Which source did that definition come from? SKOS has a dedicated place for such remarks: skos:editorialNote, a note for an editor, translator or maintainer of the vocabulary. The audience is in the definition, and it is the vocabulary team, not the people who use the concepts for indexing.
Where it sits among SKOS notes
skos:editorialNote is one of six specialized sub-properties of skos:note, and it is the only one written mainly for insiders. A rough split:
- For users and indexers:
skos:definition,skos:scopeNote,skos:example,skos:historyNote. - For maintainers:
skos:editorialNote, and often skos:changeNote.
That split is a convention, not a rule enforced by SKOS. It is still the most practical way to decide which notes a public browser shows.
What belongs in an editorial note
Typical content falls into a few kinds:
- Open questions: “Is ‘Historias orales’ the established term in the target community?”
- Pending decisions: merge candidates, proposed splits, labels under review.
- Sources: where a definition or label was taken from, when that is not meant for display.
- Translator remarks: why a term was rendered a certain way, or that no exact equivalent exists.
What does not belong: the definition itself (use skos:definition), indexing instructions (use skos:scopeNote), and a record of completed changes, which is a change note. Notes that explain an old meaning to users of legacy records are history notes.
Publishing and privacy
SKOS vocabularies are usually exported as complete RDF files, and editorial notes travel with them unless someone removes them. That is fine for notes like “source: ISO 25964-1 glossary”. It is less fine for “check with Maria, she disagrees”, which names a person and exposes internal debate.
The cleanest approach is a filter in the release pipeline: a SPARQL CONSTRUCT that copies everything except skos:editorialNote into the public file, or a configuration option in the vocabulary editor if it offers one. Some teams publish editorial notes deliberately, as a sign of an open process, and write them with that in mind. Either way works if it is decided once and not left to each editor.
A middle path is to keep editorial notes in a separate named graph or file that is loaded only into the editing environment. The published concepts stay clean, the notes stay attached to the same concept URIs for the team, and nothing depends on a filter being remembered at release time.
Keeping notes current
Editorial notes go stale quickly. A question resolved two years ago but still attached to the concept misleads the next editor into thinking it is open. A useful habit is to date each note and review all editorial notes before a release; anything resolved is either deleted or, if the resolution changed the concept, converted into a change note.
Language tags apply as for any literal. In a multilingual vocabulary where labels exist in six languages, editorial notes in the team’s working language only are normal. For broad descriptive text about the vocabulary as a whole, as opposed to single concepts, dcterms:description on the concept scheme is the usual place, and the full list of SKOS notes is on the SKOS Core vocabulary page.
Example in RDF
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:skos="http://www.w3.org/2004/02/skos/core#">
<skos:Concept rdf:about="https://example.org/vocab/genres/g0214">
<skos:prefLabel xml:lang="en">Oral histories</skos:prefLabel>
<skos:prefLabel xml:lang="es">Historias orales</skos:prefLabel>
<skos:editorialNote xml:lang="en">Spanish label pending review by the translation group; current form taken from the 2022 project glossary.</skos:editorialNote>
<skos:editorialNote xml:lang="en">Candidate for merge with g0219 (Interviews); decision at next editorial meeting.</skos:editorialNote>
</skos:Concept>
</rdf:RDF>
Questions about skos:editorialNote
What is skos:editorialNote for?
It holds notes meant for the people who edit, translate or maintain a vocabulary: open questions, sources to check, reminders about pending decisions. It is a sub-property of skos:note and is not intended as guidance for end users.
Should editorial notes be published?
SKOS does not forbid it, and many vocabularies publish them because the full RDF export includes every triple. If notes contain internal discussion or names, filter skos:editorialNote out of the public release.
How is an editorial note different from a scope note?
A skos:scopeNote tells indexers how to apply the concept, and it is meant to be read by them. A skos:editorialNote is housekeeping for the vocabulary team. 'Use for recorded interviews about lived experience' is scope; 'check this against AAT' is editorial.
Should I delete editorial notes once resolved?
Usually yes. An editorial note describes work in progress. Once the question is settled, the note can be removed, and if the resolution changed the concept, a skos:changeNote records what changed.
Can editorial notes be in a different language from the labels?
Yes. Editorial notes are working notes, so many multilingual vocabularies write them in the team's working language only. Tag each note with its language so tools can filter or display it correctly.