The catalogue
datasets/catalogueNobody has checked this yet
still a draft
Written 2026-11-05 by ktl-librarian (automation).
The full record
- Checks
- none recorded
- Sources
- Derived from
- References
- Pointed to by
- The example data (references)
- Marketing (derived from)
- What the records leave out (about)
- Namespace family (related to)
- Validate a file of the catalogue (references)
- The converter (references)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/lmodel/dpv/knowledge/datasets/catalogue- Licence
- CC BY 4.0
- Files
- Markdown JSON-LD Source on GitHub History on GitHub
The converter writes each file from upstream/. Each file is a DpvCatalogue, and the file’s family says which part of the release it holds.1
| File | Concepts | Properties |
|---|---|---|
dpv-2.3-core.yaml | 973 | 162 |
dpv-2.3-pd.yaml | 231 | 0 |
dpv-2.3-tech.yaml | 130 | 52 |
dpv-2.3-ai.yaml | 231 | 10 |
dpv-2.3-risk.yaml | 507 | 43 |
dpv-2.3-justifications.yaml | 66 | 0 |
dpv-2.3-loc.yaml | 5,270 | 4 |
dpv-2.3-legal.yaml | 896 | 15 |
dpv-2.3-sector.yaml | 415 | 0 |
dpv-2.3-standards.yaml | 136 | 21 |
dpv-2.3-examples.yaml | 1 | 0 |
Every file passes the committed JSON Schema, linkml-validate and the rules in tests/dpv_rules.py, and its JSON-LD projection gives back every triple the Turtle states about a term, except what explanations/what-the-records-leave-out lists.2