Skip to content
Vocabulary · Vocabularies and ontologies

The SKOS ontology and vocabulary: SKOS Core classes and properties

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

A common data model for sharing and linking knowledge organization systems via the Web.

Libraries, museums, archives and software companies all maintain lists of terms: subject headings, genre lists, product taxonomies, format vocabularies. SKOS gives them one data model to publish those lists on the web. Its name is the Simple Knowledge Organization System, and it became a W3C Recommendation on 18 August 2009. The namespace, http://www.w3.org/2004/02/skos/core#, still carries the date of the earlier SKOS Core work, which is why the vocabulary is often called SKOS Core even today.

Concepts and schemes

The central class is skos:Concept: a unit of thought, identified by a URI and given labels. Concepts belong to a skos:ConceptScheme through skos:inScheme, and the top of a hierarchy is marked with skos:hasTopConcept on the scheme and skos:topConceptOf on the concept.

skos:Collection and skos:OrderedCollection group concepts under a label without making the group a concept in its own right. Thesaurus builders use them for “node labels” such as “by material” or “by size”, which organize a display without being terms anyone would index with.

skos:notation holds a code that identifies a concept within a scheme, such as a class number in a classification. It is typically a typed literal, so codes from different schemes can be kept apart. A Dewey number and a Library of Congress class number can look alike as strings, and the datatype is what tells them apart.

Labels and notes

SKOS separates labels into three roles: skos:prefLabel (one per language), skos:altLabel for synonyms and variants, and skos:hiddenLabel for search-only forms. The three are pairwise disjoint on any one concept.

Documentation comes in seven note properties: skos:note and six sub-properties.

Note Purpose
definition what the concept means
scopeNote how to apply it
example an instance of use
historyNote past state, use or meaning
changeNote a modification to the concept
editorialNote housekeeping for maintainers

changeNote, editorialNote and historyNote are covered on their own pages. None of the note properties has a range restriction, so a note can be a plain literal or a resource carrying its own metadata.

Semantic relations and mappings

Inside a scheme, concepts are connected by skos:broader, skos:narrower and skos:related. Broader and narrower are inverses; related is symmetric. The transitive versions, skos:broaderTransitive and skos:narrowerTransitive, exist mainly for queries that follow a chain; data publishers normally assert only the direct relations.

Between schemes, SKOS uses mapping properties: skos:exactMatch, skos:closeMatch, skos:broadMatch, skos:narrowMatch and skos:relatedMatch. Of these, only exactMatch is transitive, a design choice that keeps loose mappings from chaining into nonsense across three or four vocabularies. A local genre list mapped to Library of Congress terms is a typical use. Mapping statements are usually published with the local vocabulary, not the external one, because only the local team can judge how close each match is.

SKOS in practice

Large vocabularies published in SKOS include the Library of Congress Subject Headings at id.loc.gov (LCSH), the EU’s EuroVoc, the FAO’s AGROVOC and the Getty vocabularies. Dublin Core properties are widely used alongside SKOS for scheme-level metadata: creator, publisher, license, modified date.

SKOS is deliberately lightweight. Treating skos:broader as rdfs:subClassOf is a common modeling error; broader in SKOS can mean whole and part, class and instance, or genus and species, and SKOS does not distinguish them. Vocabularies that need those distinctions either use the ISO 25964 extension vocabulary or model the domain in OWL with SKOS labels on top. People and organizations in the same data set are usually described with the FOAF vocabulary, not as SKOS concepts.

Example in RDF

@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix ex:   <https://example.org/vocab/carriers/> .

ex:scheme a skos:ConceptScheme ;
    skos:prefLabel "Carrier types"@en ;
    skos:hasTopConcept ex:c0100 .

ex:c0100 a skos:Concept ;
    skos:prefLabel "Discs"@en ;
    skos:topConceptOf ex:scheme ;
    skos:narrower ex:c0107 .

ex:c0107 a skos:Concept ;
    skos:inScheme ex:scheme ;
    skos:prefLabel "Optical disc"@en ;
    skos:altLabel "Optical disk"@en ;
    skos:notation "OD" ;
    skos:scopeNote "Use for CD, DVD and Blu-ray carriers."@en ;
    skos:exactMatch <https://example.net/terms/optical-disc> .

Questions about SKOS Core

What is SKOS?

SKOS, the Simple Knowledge Organization System, is a W3C Recommendation published in August 2009 for representing thesauri, classification schemes, subject heading lists and taxonomies as RDF. Its namespace is http://www.w3.org/2004/02/skos/core#.

Is SKOS an ontology?

SKOS is defined as an OWL Full ontology, but it is meant for vocabularies where concepts are linked by looser relations such as broader and narrower. It describes terms and their organization, not formal class definitions about the world.

What are the main SKOS classes?

skos:Concept for individual concepts, skos:ConceptScheme for a whole vocabulary, and skos:Collection and skos:OrderedCollection for labeled groups of concepts that do not form part of the broader/narrower hierarchy. Most vocabularies need only Concept and ConceptScheme; collections are added when a display needs grouping.

What is the difference between SKOS and SKOS-XL?

Core SKOS labels are plain literals. SKOS-XL, published alongside it, makes labels into resources of class skosxl:Label, so each label can carry its own metadata such as dates, sources or relations to other labels.

Why does the namespace say 2004 when SKOS was published in 2009?

The namespace was established during the earlier SKOS Core work, which started in the SWAD-Europe project and produced drafts from 2004 onward. W3C kept that namespace for the 2009 Recommendation so that existing data stayed valid.

More from Vocabularies and ontologies

All 3 in this group