dpv
Theme
Text size
GitHub Menu

How kinds and slots get their names

Explanation explanations/kinds-and-slots

Nobody has checked this yet

still a draft

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

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

A slot keeps the local name of the DPV property it renders, so a record’s keys are DPV’s: hasPurpose, prefLabel. Where two namespaces define one name, the core keeps it and the other takes its namespace first: hasRiskLevel and eu_aiact_hasRiskLevel.1

A kind’s class takes the namespace the same way: DpvRiskLevel and DpvEuAiactRiskLevel. Each slot and each class keeps its own IRI.2

German stays in keys of its own, prefLabel_de and definition_de, because only the German health data law states it.3


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

  2. tests/test_coverage.py, test_a_shared_local_name_keeps_each_iri ↩︎

  3. tests/test_catalogue.py, test_german_stays_in_its_own_keys ↩︎