Contracts & knowledge · W3C vocabulary model
SKOS
Represent concepts, preferred terms, alternative labels, and their relationships consistently.
What it helps you do
Keep terminology organized without pretending every vocabulary relationship is a strict logical definition.
Starting knowledge: Understand identifiers and basic vocabulary relationships; RDF is helpful for implementation.
- Give a concept a stable identifier.
- Distinguish preferred labels from alternative labels.
- Use broader, narrower, and related links according to their intended meanings.
The problem it came from
W3C published the SKOS Recommendation in 2009, alongside a primer for representing knowledge-organization systems on the web.
SKOS builds on RDF to represent concept schemes such as thesauri and taxonomies. It distinguishes the concept from the words used to label it.
Work through an example
Concept: example:Tutorial
Preferred label: tutorial (English)
Alternative label: guided learning exercise (English)
Broader concept: learning resource
Related concept: how-to guide
Scope note: a learning-oriented guided experience, not any page with steps.- The concept has an identity beyond its current label.
- Related does not mean equivalent.
- The scope note reduces ambiguous tagging decisions.
Where it helps. Where it stops.
Use it when
- An organization uses different labels for the same concept.
- A topic catalog needs a maintained taxonomy or mappings across vocabularies.
Potential benefits
- Stable concept identities support label changes and multilingual vocabularies.
- Explicit relationships reduce accidental synonym and hierarchy confusion.
Limits and common mistakes
- A broader concept is not automatically an object-oriented superclass.
- A taxonomy does not verify the factual truth of documents tagged with its concepts.
The prompt below asks for this structure. It does not guarantee accuracy, complete coverage, better learning, or conformance to a standard. Treat those outcomes as separate checks.
Practise the judgment
Try a choice, inspect a boundary, then explain a case yourself. Hints and answers are available whenever you need them.
A team renames “participant” to “attendee” without changing the concept. What can remain stable?
Hint
A name is not the same as the concept.
Explained answer
Best answer for this case: The concept identifier
The identity can persist while labels change or alternatives remain searchable.
Does a broader link necessarily mean software inheritance?
Hint
Check what the relation actually asserts.
Explained answer
Best answer for this case: No; SKOS conceptual hierarchy is not automatically class inheritance
Knowledge-organization relations should not be silently converted into stronger implementation semantics.
Explain why tutorial and how-to guide should not automatically be alternative labels for one concept.
Hint
Could substituting one label change the reader’s expectation?
Explained answer & self-review rubric
They can serve different reader needs: learning a skill versus applying existing skill to a task. Model their relationship and scope rather than merging them merely because both contain steps.
- Use meaning rather than similar appearance
- State the distinction
- Choose an appropriate relation
Take it into your own work
Manual template
Use this structure yourself, with a colleague, or in your preferred writing tool.
# Vocabulary concept
Stable identifier:
Preferred label and language:
Alternative labels:
Definition / scope note:
Broader / narrower concepts:
Related concepts:
Mapping to other schemes:
Source and owner:
Review the result
- Are concepts separated from labels?
- Does a synonym really mean the same thing in this scope?
- Are broader and related links being confused?
Use this approach with your own AI tool
Help me apply SKOS to the material below.
Reader and existing knowledge: [describe]
Task and desired outcome: [describe]
Use these principles: Give a concept a stable identifier.; Distinguish preferred labels from alternative labels.; Use broader, narrower, and related links according to their intended meanings..
Preserve source facts, identifiers, quantities, conditions, exceptions, and uncertainty.
Separate supplied facts from assumptions. Ask for missing information instead of inventing it.
Explain your representation choices and provide a review checklist. Do not claim formal compliance or correctness from formatting alone.
Material: [paste only information you are permitted to share]Go to the source
History and the underlying approach are grounded in these references. Examples, prompts, and practice cases here are original educational adaptations. Edition-specific details should be checked against the referenced publication.
Last editorial review: 2026-10-24. An overview is not certification, and this guide is not a reproduction of a standard.