SKOS, the Simple Knowledge Organization System, is a W3C standard for expressing taxonomies, thesauri and controlled vocabularies in a machine-readable form. It gives you a small, deliberately limited set of terms. You can say that one concept is broader than another, that two labels mean the same thing, and that a concept in your vocabulary matches one in somebody else's.
The point of the limit is portability. SKOS does not try to express everything an ontology can. It expresses the structure of a vocabulary well enough that any system can read it without agreeing to your modelling philosophy first.
Five things, and each one solves a problem a spreadsheet creates.
| SKOS gives you | The problem it solves |
|---|---|
| Stable identifiers | A concept keeps its identity when its label changes, so renaming does not orphan everything pointing at it |
| Preferred and alternative labels | One concept, many names. Internal jargon and reader language resolve to the same thing |
| Broader and narrower | Hierarchy expressed as data, including more than one parent where the domain needs it |
| Mapping relations | Your term lines up with an external scheme without either side adopting the other |
| Notes and provenance | Scope notes, definitions and editorial history travel with the concept |
The mapping relations are the underrated ones. Every organization eventually has to line a vocabulary up against an industry scheme, a marketplace taxonomy or a regulator's list. In a spreadsheet that mapping becomes something nobody can maintain. In SKOS it becomes something a system can resolve.
Four signals, and the absence of all four is the clearest reason to stay in a spreadsheet a while longer.
Where SKOS stops is where real modelling starts. It has no way to say that every order must have exactly one billing account, or that a cardiologist is necessarily a clinician. Those are constraint and inference questions, and they belong to SHACL and OWL respectively. Ontology vs taxonomy vs knowledge graph covers where the line sits.
They do different jobs and most serious deployments run both.
An ontology says what kinds of thing exist and how they relate: a Customer has Orders, an Order has exactly one billing Account. SKOS says what the agreed terms are and how they nest: this subject sits under that one, and these two labels mean the same thing.
In practice the vocabulary usually arrives first, because agreeing a list of terms is the cheapest thing an organization can do together. The ontology comes later, when somebody needs the relationships to be enforceable. Running the two side by side is a real operating question and taxonomy and ontology management covers it.
One practical note: SKOS concepts and ontology classes are different things and conflating them causes trouble later. A SKOS concept is a term in an agreed vocabulary. An ontology class is a set of things in the world. "Respiratory condition" as a subject heading and "RespiratoryCondition" as a class look similar and behave differently under a reasoner.
Four limits worth knowing before you commit.
The last one catches people. Expressing a taxonomy in SKOS makes it portable and does nothing to make it good. Validation is a separate step and it needs its own tooling.
Three extensions come up often enough to be worth a direct answer.
The failure pattern across all three is reaching for an extension before the base vocabulary is agreed. SKOS-XL on a vocabulary nobody has approved records the provenance of a decision that was never made.
Smaller than you expect, and in one direction only to start with. The instinct is to convert everything at once, which turns a week of work into a quarter and surfaces every unresolved disagreement simultaneously.
Take one vocabulary that several systems already argue about. Give every concept an identifier and a preferred label. Add alternative labels for the names other teams use, which is usually where the argument was. Add broader relationships only where the hierarchy is already agreed, and leave the contested parts flat until somebody decides them.
That produces something useful within days and makes the undecided parts visible instead of papering over them with a structure nobody agreed. How to build a taxonomy covers the fuller method.
SKOS is the portable form of a controlled vocabulary. It is small on purpose, it handles the things that actually break when a vocabulary moves between systems, and it stops short of constraints and inference by design.
TopQuadrant builds on open W3C standards, and our own authorship claim is in RDF and SHACL. SKOS we implement, and we leave the authorship claim to the people who hold it. The practical argument for it here is narrow and worth stating plainly: a vocabulary expressed in SKOS can leave the platform it was built in, with its relationships and its editorial history intact. One that cannot has made your next platform decision for you. Taxonomy management covers the discipline around it.