dpv
Theme
Text size
GitHub Menu

Why terms are records

Explanation explanations/terms-as-records

Nobody has checked this yet

still a draft

Written 2026-11-05 by ktl-librarian (automation).

The full record
Checks
none recorded
Sources
About
Related to
Pointed to by
Graph
Open this concept in the knowledge graph
IRI
https://w3id.org/lmodel/dpv/knowledge/explanations/terms-as-records
Licence
CC BY 4.0
Files
Markdown JSON-LD Source on GitHub History on GitHub

DPV states dpv:Marketing a rdfs:Class, skos:Concept, dpv:Purpose. A LinkML class cannot also be a value, so a schema with one class per term could not hold hasPurpose: dpv:Marketing.1

So the concepts that terms are instances of are classes, and every term is a record. A term and its kind’s class can be the same thing seen two ways: dpv:Purpose is a record, and DpvPurpose is the class a host names as a concept’s type.1

So project/owl/ describes this schema, and upstream/2.3/ is DPV’s ontology.2

The schema it replaced held 973 classes with no slots of their own, and enforced only id.3


  1. docs/about.md, Terms are records ↩︎ ↩︎

  2. README.md, What it models ↩︎

  3. CHANGELOG.md, Changed ↩︎