Glossary
Every term the instances in this repository define or carry, as W3C SKOS. Terms link to the external concepts they match rather than copying them. 206 terms: 0 authored in 3 glossaries, one page per instance that owns them, and 0 extracted from knowledge-graph assets in 0 generated schemes, one page per asset type, plus the sources below.
| state | what it means | terms |
|---|---|---|
| authored | A person wrote or approved the definition. | 0 |
| candidate, extracted | Lifted from a knowledge-graph asset's own title and description, verbatim, and not curated. The definition is the asset's text, the source links to the asset, and an asset with no description gives a term with none. A person promotes one by authoring it. | 0 |
| could-not-extract | The source names a term the extractor could not read, and says why. | 5 |
Already somebody else’s concept?
Extracted candidates are minted from this repository’s own assets and are not, by themselves, checked against any vocabulary. check:term-mapping asks whether each already exists as a concept somebody is authoritative for — SKOS for what a term MEANS, FHIR for a clinical code’s operational semantics — and the two are separate questions with separate answers.
| target | mapped | unmapped | undetermined | why undetermined |
|---|---|---|---|---|
fhir | 4 | 202 | 0 | — |
skos | 0 | 206 | 0 | — |
Undetermined is never “no match”. A vocabulary that could not be reached has said nothing, and the column above keeps that apart from a checked miss. The counts are reported and not graded: an unmapped candidate may be a term this corpus is right to coin.
Pages
Each term is on exactly one page. Authored terms are on the page of the instance that owns their scheme (owner, 2026-10-15), and extracted candidates are split by asset type (owner, 2026-09-24), so that no page is fetched at the size of all of them.
| page | holds | terms | size |
|---|---|---|---|
| this page | counts and sources | — | 6 KB |
| dpi-h-ra | authored terms of dpi-h-ra | 206 | 339 KB |
| Skills | candidates, extracted | 0 | 2 KB |
| Tools | candidates, extracted | 0 | 2 KB |
| BPMN activities | candidates, extracted | 0 | 7 KB |
| DMN decisions | candidates, extracted | 0 | 2 KB |
| Schema fields | candidates, extracted | 0 | 15 KB |
Size: this page is 6 KB before compression, within its budget of 64 KB; each instance’s and each asset type’s page has a budget of 1.0 MB. There is no search index: the filter on each page runs over that page, and its A–Z bar jumps within it. The SKOS files in the sources are the machine-readable form.
Authored terms
- dpi-h-ra: 206 terms in Acronyms used in the DPI-H reference architecture, Glossary of the Reference Architecture and Guidance for DPI-H, Full-STAC: open Standards, Technologies, Architectures and Content
Sources
Authored
- Acronyms used in the DPI-H reference architecture (dpi-h-ra, 18 terms) · SKOS JSON-LD ·
glossary/dpi-h-ra-acronyms.glossary.json - Glossary of the Reference Architecture and Guidance for DPI-H (dpi-h-ra, 178 terms, 8 external members) · SKOS JSON-LD ·
glossary/dpi-h-ra.glossary.json - Full-STAC: open Standards, Technologies, Architectures and Content (dpi-h-ra, 10 terms) · SKOS JSON-LD ·
glossary/full-stac.glossary.json
Extracted from knowledge-graph assets
Generated by folio-assistant-core/scripts/glossary-extract.ts into folio-assistant-core/glossary/generated/<instance>/<type>.glossary.json, one scheme per asset type per instance, each term’s IRI in the namespace of the instance that holds the asset. BPMN lanes and roles are not extracted again: the 0 swimlane-role terms above already carry them, with every lane name as an alternative label.
No KG asset carried an extractable term.