A specification here is referenced, not held: the edition is named and the terms this repository actually acts on are materialised into the graph, but the document itself stays at the authority. That split is the owner’s: “dont need to materalize, but should reference specific version being used”, and “some schema that is operational should be in KG”.
So each record answers three questions — which edition, what here depends on it, and which of its terms this repository branches on.
The specifications
| specification | authority | edition | how it is used |
|---|---|---|---|
DCMI Metadata Termsdcmi-terms |
DCMI | 2020-01-20 | reads — this repository parses documents written in it |
HL7 FHIRhl7-fhir |
HL7 | unpinned | reads — this repository parses documents written in it |
Handle System Overview (RFC 3650), with its namespace (RFC 3651) and protocol (RFC 3652)ietf-handle-system |
IETF | 2003-11 | conforms — this repository’s artefacts are valid against it |
Business Process Model and Notation (BPMN)omg-bpmn-2.0 |
OMG | 2.0 | conforms — this repository’s artefacts are valid against it |
Diagram Definition (DD)omg-dd-1.0 |
OMG | 1.0 | conforms — this repository’s artefacts are valid against it |
Decision Model and Notation (DMN)omg-dmn-1.3 |
OMG | 1.3 | conforms — this repository’s artefacts are valid against it |
ArchiMate® Model Exchange File Formatopengroup-archimate-3.0 |
other | 3.0 | reads — this repository parses documents written in it |
The Bibliographic Ontology (BIBO)purl-bibo |
other | unpinned | conforms — this repository’s artefacts are valid against it |
Schema.orgschema-org |
other | unpinned | conforms — this repository’s artefacts are valid against it |
SPAR Ontologies: DoCO, DEO and CiTOspar-doco-deo-cito |
other | unpinned | conforms — this repository’s artefacts are valid against it |
SPAR Ontologies: FaBiO, the FRBR-aligned Bibliographic Ontologyspar-fabio |
other | unpinned | conforms — this repository’s artefacts are valid against it |
SPDX License Listspdx-license-list |
other | 3.29.0 | reads — this repository parses documents written in it |
Metadata Vocabulary for Tabular Dataw3c-csvw |
W3C | 2015-12-17 | conforms — this repository’s artefacts are valid against it |
Hydra Core Vocabularyw3c-hydra |
W3C | unpinned | conforms — this repository’s artefacts are valid against it |
RDF 1.1 N-Quads: A line-based syntax for RDF datasetsw3c-n-quads |
W3C | 2014-02-25 | conforms — this repository’s artefacts are valid against it |
ODRL Information Model 2.2w3c-odrl |
W3C | 2018-02-15 | conforms — this repository’s artefacts are valid against it |
OWL 2 Web Ontology Language Document Overview (Second Edition)w3c-owl2 |
W3C | 2012-12-11 | conforms — this repository’s artefacts are valid against it |
The PROV-JSONLD Serialization: A JSON-LD Representation for the PROV Data Modelw3c-prov-jsonld |
W3C | 2024-08-25 | conforms — this repository’s artefacts are valid against it |
PROV-O: The PROV Ontologyw3c-prov-o |
W3C | 2013-04-30 | conforms — this repository’s artefacts are valid against it |
RDF Calendar — an application of the Resource Description Framework to iCalendar Dataw3c-rdf-calendar |
W3C | 2005-09-29 | conforms — this repository’s artefacts are valid against it |
RDF 1.1 Concepts and Abstract Syntaxw3c-rdf |
W3C | 2014-02-25 | conforms — this repository’s artefacts are valid against it |
RDF Schema 1.1w3c-rdfs |
W3C | 2014-02-25 | conforms — this repository’s artefacts are valid against it |
SKOS Simple Knowledge Organization System Referencew3c-skos |
W3C | 2009-08-18 | conforms — this repository’s artefacts are valid against it |
SPARQL 1.1 Query Languagew3c-sparql-1.1-query |
W3C | 2013-03-21 | conforms — this repository’s artefacts are valid against it |
Web Annotation Vocabularyw3c-web-annotation |
W3C | 2017-02-23 | conforms — this repository’s artefacts are valid against it |
XML Schema Definition Language (XSD) 1.1 Part 2: Datatypesw3c-xsd11-datatypes |
W3C | 2012-04-05 | conforms — this repository’s artefacts are valid against it |
W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structuresw3c-xsd11-structures |
W3C | 2012-04-05 | conforms — this repository’s artefacts are valid against it |
WHO SMART Guidelines base IGwho-smart-base |
other | v1.0.0 | reads — this repository parses documents written in it |
Who declares each specification
A user declares the specification it depends on; the record names no user.
That is data-modelling step 8 — the dependent holds the pointer — and it is
why this list cannot drift from the code: a file that stops declaring stops
being listed. Four forms are read: a @conformsTo tag, a conformsTo:
front-matter list, an xmlns binding, and a graph typology whose typing module
declares the spec (bean u63y).
Every declaration names a record on this page.
1 record(s) nothing declares. A version bump would move nothing that says so:
Namespaces the corpus uses against the ones it declares
Read from diagram files (BPMN and DMN), metadata records, and JSON-LD contexts — 33 namespace IRI(s) are in use across the corpus. Derived rather than listed, so an artefact that adopts a new vocabulary shows up here instead of going unnoticed.
Every namespace the corpus declares is covered by a record above.
2 declared and not in use. Not a defect on its own: a record may cover a namespace only some artefacts carry. It is here because a registry nobody prunes is one that stops describing the repository.
http://www.w3.org/ns/formats/N-Quadshttps://www.omg.org/spec/DMN/20191111/DMNDI/
Each specification
DCMI Metadata Terms
dcmi-terms — DCMI, edition 2020-01-20 — reads, meaning this repository parses documents written in it.
Namespaces.
http://purl.org/dc/elements/1.1/http://purl.org/dc/terms/http://purl.org/dc/dcam/
Note. reads, not conforms: these records describe external metadata (DSpace), so a DCMI revision is a compatibility question rather than a migration. The transcription came first, which was the defect: dublin-core.ts was written from one captured IRIS record and carries the prefix string dc with no namespace URI and no edition, recording what one deployment spells rather than what the standard defines. A transcription with no cited edition cannot distinguish a missing field from one absent in that edition.
The operative terms below are derived from the catalogue records, so they are what IRIS actually sends (DSpace also mints dcterms, local and other prefixes this repository has not met). A term absent here is undeclared, not unsupported.
What depends on it.
| user | declared by |
|---|---|
cat-harness-tools/scripts/kg-export.ts |
@conformsTo tag |
cat-harness-tools/scripts/ns-export.ts |
@conformsTo tag |
cat-harness-tools/scripts/todo-graph.ts |
@conformsTo tag |
folio-assistant-core/schemas/dublin-core-render.ts |
@conformsTo tag |
folio-assistant-core/schemas/dublin-core.ts |
@conformsTo tag |
folio-assistant-core/schemas/reference.ts |
@conformsTo tag |
folio-assistant-core/skills/library/catalogue/oxigraph-catalogue-search.md |
conformsTo: front matter |
folio-dublin-core/v1 nodes |
through the module that types it (folio-assistant-core/schemas/dublin-core.ts) |
Operative terms (22). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
| term | what it means here |
|---|---|
dc.contributor.author |
Primary author or creator of the catalogue record or ingested document. |
dc.coverage.spatial |
Spatial or geographic coverage of the publication or resource. |
dc.date.accessioned |
Timestamp when the digital repository accessioned the resource. |
dc.date.available |
Date when the resource became publicly available in the catalogue. |
dc.date.created |
Creation date of the original document or intellectual work. |
dc.date.issued |
Formal publication or issue date asserted by the publisher. |
dc.description |
General descriptive summary or annotation of the resource. |
dc.description.abstract |
Abstract summarizing the contents and findings of the publication. |
dc.description.tableofcontents |
Table of contents or section outline of the document. |
dc.identifier.govdoc |
Government or agency publication document number. |
dc.identifier.isbn |
International Standard Book Number (ISBN) for the published work. |
dc.identifier.uri |
Canonical persistent URI (e.g. Handle or DOI) identifying the resource. |
dc.language |
Language designation of the catalogue record resource. |
dc.language.iso |
ISO language code representing the language of the resource content. |
dc.publisher |
Organization or publisher responsible for distributing the resource. |
dc.subject.mesh |
Medical Subject Headings (MeSH) descriptor assigned to the health topic. |
dc.subject.meshqualifier |
MeSH qualifier sub-heading refining the subject topic. |
dc.subject.other |
Additional topical classification or keyword descriptor. |
dc.title |
Formal title of the catalogue publication or document. |
dc.title.release |
Release or edition title qualifying the primary title. |
dc.type |
Resource publication type or document genre classification. |
who.relation.languageVersion |
Language edition relationship linking multilingual publications. |
HL7 FHIR
hl7-fhir — HL7, edition unpinned — reads, meaning this repository parses documents written in it.
Namespaces.
http://hl7.org/fhir/
Note. No FHIR version is declared anywhere in this repository (measured 2026-09-23), and the namespace is version-independent. reads: the platform parses FHIR artefacts other instances ingest; it does not claim its own documents are FHIR resources.
What depends on it.
| user | declared by |
|---|---|
cat-harness/schemas/jsonld.ts |
@conformsTo tag |
cat-harness/schemas/vocab-mapping-fhir.ts |
@conformsTo tag |
cat-harness/schemas/vocab-mapping.ts |
@conformsTo tag |
vocab-mapping graph |
through the module that types it (cat-harness/schemas/vocab-mapping.ts) |
Operative terms (1). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
All terms below are derived from the corpus; operational semantics are pending individual per-term descriptions.
| term | what it means here |
|---|---|
fhir:ValueSet |
(pending description) |
Handle System Overview (RFC 3650), with its namespace (RFC 3651) and protocol (RFC 3652)
ietf-handle-system — IETF, edition 2003-11 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
https://hdl.handle.net/
Note. The persistent identifiers DSpace mints (<prefix>/<suffix>, e.g. WHO IRIS’s 10665/332098), written as IRIs through the global HTTP resolver https://hdl.handle.net/. Emitted by schemas/prov-jsonld.ts for PROV prov:used: owner decision 2026-10-01 (option A) links a catalogue item at its Handle, the identifier that outlives the publishing host, rather than at the host’s own item URL. folio-assistant-core’s catalogue schema (HandleSchema, handleIri) applies the same rule to catalogue records. The RFCs are Informational and define the identifier system; the hdl.handle.net proxy is the resolver its operators run, not a namespace in the vocabulary sense.
What depends on it.
| user | declared by |
|---|---|
cat-harness/schemas/prov-jsonld.ts |
@conformsTo tag |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
Business Process Model and Notation (BPMN)
omg-bpmn-2.0 — OMG, edition 2.0 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.omg.org/spec/BPMN/20100524/MODELhttp://www.omg.org/spec/BPMN/20100524/MODEL#http://www.omg.org/spec/BPMN/20100524/DI
Note. The 20100524 in every namespace is BPMN 2.0’s release date and is how the edition is identified in an instance document — the diagrams have carried it since the first one was drawn, and until 2026-09-20 nothing in this repository said which specification that was. conforms rather than reads: these are our instance documents, so a version bump is a migration of the corpus rather than a compatibility question.
No XSD is held and none is fetched — referenced, per the owner’s “dont need to materalize, but should reference specific version being used”. That means nothing validates a diagram structurally against OMG’s schema; check:workflows and kg:audit check the things this repository cares about (lanes bind declared roles, activities name skills) and are not a substitute for it.
The MODEL# form is the RDF spelling of the same namespace: OMG publishes no RDF vocabulary for BPMN, so a graph that states a sequence flow’s sourceRef/targetRef or a node’s incoming/outgoing (kg-export, and bootstrap-tools’ export-graph.ts) names BPMN’s own attribute by appending # to its XML namespace — the model’s name for the relation, rather than a second one minted here (owner, 2026-09-30, bean xsqm).
What depends on it.
| user | declared by |
|---|---|
bootstrap-tools/processes/*.bpmn (1) |
xmlns binding |
bootstrap/processes/*.bpmn (5) |
xmlns binding |
cat-harness-tools/scripts/kg-export.ts |
@conformsTo tag |
cat-harness-tools/scripts/render-bpmn.ts |
@conformsTo tag |
cat-harness-tools/src/workflow/process-model.ts |
@conformsTo tag |
cat-harness/processes/content/*.bpmn (3) |
xmlns binding |
cat-harness/processes/kg/*.bpmn (10) |
xmlns binding |
cat-harness/processes/library/*.bpmn (10) |
xmlns binding |
cat-harness/processes/process/*.bpmn (13) |
xmlns binding |
cat-harness/processes/sdlc/*.bpmn (27) |
xmlns binding |
cat-harness/processes/ui/*.bpmn (4) |
xmlns binding |
folio-assistant-core/processes/conduct/*.bpmn (1) |
xmlns binding |
folio-assistant-core/processes/content/*.bpmn (7) |
xmlns binding |
folio-assistant-core/processes/library/*.bpmn (6) |
xmlns binding |
folio-assistant-core/processes/ui/*.bpmn (3) |
xmlns binding |
processes/process/*.bpmn (7) |
xmlns binding |
Operative terms (23). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
Terms marked pending description are derived from the corpus and await detailed operational description.
| term | what it means here |
|---|---|
bpmn:callActivity |
Reusable sub-process invocation referencing another diagram by QName. |
bpmn:collaboration |
Collaboration diagram container binding participants and message flows. |
bpmn:definitions |
Root element of a BPMN diagram carrying namespaces and targetNamespace. |
bpmn:documentation |
Authored prose description attached to a process, lane, or activity. |
bpmn:endEvent |
Terminal node marking completion of a process execution path. |
bpmn:exclusiveGateway |
Conditional XOR decision branching or converging control flow. |
bpmn:extensionElements |
Extension container holding role bindings, skills, and preconditions. |
bpmn:flowNodeRef |
Reference connecting a process activity or gateway into a specific lane. |
bpmn:import |
(pending description) |
bpmn:incoming |
Incoming sequence flow connection entering an activity or gateway. |
bpmn:lane |
Process swimlane establishing the role persona responsible for activities. |
bpmn:laneSet |
Container partitioning a process into one or more participant swimlanes. |
bpmn:outgoing |
Outgoing sequence flow connection leaving an activity or gateway. |
bpmn:parallelGateway |
Concurrent AND fork or join synchronization of parallel execution paths. |
bpmn:participant |
Swimlane participant representing a collaboration role or system boundary. |
bpmn:process |
Top-level executable workflow definition containing activity flow nodes. |
bpmn:resource |
(pending description) |
bpmn:sequenceFlow |
Directed transition connecting source and target flow nodes. |
bpmn:serviceTask |
Automated system task invoked during workflow execution. |
bpmn:startEvent |
Entry node initiating execution of a workflow process. |
bpmn:task |
Base unit of atomic work within a business process flow. |
bpmn:timerEventDefinition |
Timer schedule trigger defining timeouts or delayed transitions. |
bpmn:userTask |
Interactive step requiring explicit human or agent persona execution. |
Diagram Definition (DD)
omg-dd-1.0 — OMG, edition 1.0 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.omg.org/spec/DD/20100524/DChttp://www.omg.org/spec/DD/20100524/DI
Note. Separate from BPMN even though the release date matches: DD is its own OMG specification and BPMN’s DI namespace builds on it. Recording them as one would make a DD bump invisible. DD/.../DC is Diagram Common — NOT Dublin Core, which is dcmi-terms in this registry and shares nothing with it but a two-letter prefix. That collision is exactly why a namespace URI is the identity here and a prefix is not.
What depends on it.
| user | declared by |
|---|---|
bootstrap-tools/processes/*.bpmn (1) |
xmlns binding |
bootstrap/processes/*.bpmn (5) |
xmlns binding |
cat-harness-tools/scripts/render-bpmn.ts |
@conformsTo tag |
cat-harness/processes/content/*.bpmn (3) |
xmlns binding |
cat-harness/processes/kg/*.bpmn (10) |
xmlns binding |
cat-harness/processes/library/*.bpmn (10) |
xmlns binding |
cat-harness/processes/process/*.bpmn (13) |
xmlns binding |
cat-harness/processes/sdlc/*.bpmn (27) |
xmlns binding |
cat-harness/processes/ui/*.bpmn (4) |
xmlns binding |
folio-assistant-core/processes/conduct/*.bpmn (1) |
xmlns binding |
folio-assistant-core/processes/content/*.bpmn (7) |
xmlns binding |
folio-assistant-core/processes/library/*.bpmn (6) |
xmlns binding |
folio-assistant-core/processes/ui/*.bpmn (3) |
xmlns binding |
processes/process/*.bpmn (7) |
xmlns binding |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
Decision Model and Notation (DMN)
omg-dmn-1.3 — OMG, edition 1.3 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
https://www.omg.org/spec/DMN/20191111/MODEL/https://www.omg.org/spec/DMN/20191111/DMNDI/
Note. The decision tables under processes/decisions/ that BPMN gateways compute from. Added 2026-09-27 when the knowledge graph began linking each process graph to the standards its files declare; until then the DMN namespaces went unregistered because namespacesInUse read only the top of processes/.
What depends on it.
| user | declared by |
|---|---|
cat-harness/processes/kg/decisions/*.dmn (4) |
xmlns binding |
cat-harness/processes/process/decisions/*.dmn (1) |
xmlns binding |
cat-harness/processes/sdlc/decisions/*.dmn (5) |
xmlns binding |
folio-assistant-core/processes/conduct/decisions/*.dmn (2) |
xmlns binding |
folio-assistant-core/processes/content/decisions/*.dmn (2) |
xmlns binding |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
ArchiMate® Model Exchange File Format
opengroup-archimate-3.0 — other, edition 3.0 — reads, meaning this repository parses documents written in it.
Namespaces.
http://www.opengroup.org/xsd/archimate/3.0/
Note. The Open Group’s ArchiMate vocabulary, the archimate: prefix of the JSON-LD the archimate subgraph’s page generator writes (gen-archimate-pages.ts, in cat-harness-tools since 70lx) for every model, view, element and relationship it gives a page. Authority other: The Open Group is not in SPEC_AUTHORITIES. Added 2026-10-10 when external-schemas:check found the namespace in use and unregistered, a day after the subgraph landed.
What depends on it.
| user | declared by |
|---|---|
cat-harness-tools/archimate/scripts/gen-archimate-pages.ts |
@conformsTo tag |
cat-harness/archimate/schemas/archimate.ts |
@conformsTo tag |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
The Bibliographic Ontology (BIBO)
purl-bibo — other, edition unpinned — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://purl.org/ontology/bibo/
What depends on it.
| user | declared by |
|---|---|
folio-assistant-core/schemas/reference.ts |
@conformsTo tag |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
Schema.org
schema-org — other, edition unpinned — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
https://schema.org/
Note. No release is pinned: schema.org publishes continuously under one namespace. Used for one property in kg-export. Recorded 2026-09-23 (bean 2j09).
What depends on it.
| user | declared by |
|---|---|
cat-harness-tools/scripts/kg-export.ts |
@conformsTo tag |
cat-harness-tools/scripts/todo-graph.ts |
@conformsTo tag |
Operative terms (4). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
All terms below are derived from the corpus; operational semantics are pending individual per-term descriptions.
| term | what it means here |
|---|---|
schema:WebPage |
(pending description) |
schema:codeRepository |
(pending description) |
schema:softwareVersion |
(pending description) |
schema:text |
(pending description) |
SPAR Ontologies: DoCO, DEO and CiTO
spar-doco-deo-cito — other, edition unpinned — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://purl.org/spar/doco/http://purl.org/spar/deo/http://purl.org/spar/cito/
Note. No edition is pinned: each namespace is a purl.org redirect to the ontology’s current release. Recorded 2026-09-23 (bean 2j09) so the dependency is named; pinning an edition is a later decision.
What depends on it.
| user | declared by |
|---|---|
cat-harness/schemas/jsonld.ts |
@conformsTo tag |
Operative terms (7). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
All terms below are derived from the corpus; operational semantics are pending individual per-term descriptions.
| term | what it means here |
|---|---|
cito:cites |
(pending description) |
deo:Conclusion |
(pending description) |
deo:Introduction |
(pending description) |
doco:Figure |
(pending description) |
doco:Formula |
(pending description) |
doco:Section |
(pending description) |
doco:Table |
(pending description) |
SPAR Ontologies: FaBiO, the FRBR-aligned Bibliographic Ontology
spar-fabio — other, edition unpinned — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://purl.org/spar/fabio/
What depends on it.
| user | declared by |
|---|---|
folio-assistant-core/schemas/reference.ts |
@conformsTo tag |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
SPDX License List
spdx-license-list — other, edition 3.29.0 — reads, meaning this repository parses documents written in it.
Namespaces.
https://spdx.org/licenses/
Note. The identifiers a licence.json id (and an intake.json licence) may use, as an SPDX licence expression: a listed licence or exception id, or a LicenseRef-. Adopted for VALIDATION ONLY on the owner’s ruling 2026-10-03 (bean sd5v): ‘go ahead with licence-id validation, that’s it for now’ — no SPDX documents are produced. The ids are snapshotted beside this record in spdx-license-list.terminology.json; move this pin, fetch github.com/spdx/license-list-data at tag v
What depends on it.
| user | declared by |
|---|---|
cat-harness/schemas/spdx-license-expression.ts |
@conformsTo tag |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
Metadata Vocabulary for Tabular Data
w3c-csvw — W3C, edition 2015-12-17 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/ns/csvw#
What depends on it.
| user | declared by |
|---|---|
cat-harness/schemas/jsonld.ts |
@conformsTo tag |
Operative terms (1). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
All terms below are derived from the corpus; operational semantics are pending individual per-term descriptions.
| term | what it means here |
|---|---|
csvw:TableGroup |
(pending description) |
Hydra Core Vocabulary
w3c-hydra — W3C, edition unpinned — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/ns/hydra/core#
What depends on it.
| user | declared by |
|---|---|
cat-harness-tools/openapi/scripts/gen-openapi-pages.ts |
@conformsTo tag |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
RDF 1.1 N-Quads: A line-based syntax for RDF datasets
w3c-n-quads — W3C, edition 2014-02-25 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/ns/formats/N-Quads
What depends on it.
| user | declared by |
|---|---|
cat-harness/schemas/nquads-distribution.ts |
@conformsTo tag |
cat-harness/skills/kg/graph-management/named-query-execution.md |
conformsTo: front matter |
cat-harness/skills/kg/graph-management/nquads-distribution.md |
conformsTo: front matter |
Operative terms (2). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
| term | what it means here |
|---|---|
nquads:dataset |
line-based serialization of RDF datasets with named graph support |
nquads:statement |
four-element quad: subject, predicate, object, graphLabel |
ODRL Information Model 2.2
w3c-odrl — W3C, edition 2018-02-15 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/ns/odrl/2/
Note. Added when the bean 2j09 JSON-LD scan found ODRL bound in cat-harness/policies/folio-defaults.jsonld (#1181) with no record. conforms: that file is an ODRL policy document, by the rule the owner approved 2026-09-23 for namespaces this instance’s documents are written in.
What depends on it.
| user | declared by |
|---|---|
cat-harness/schemas/odrl.ts |
@conformsTo tag |
policies graph |
through the module that types it (cat-harness/schemas/odrl.ts) |
Operative terms (14). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
All terms below are derived from the corpus; operational semantics are pending individual per-term descriptions.
| term | what it means here |
|---|---|
odrl:annotate |
(pending description) |
odrl:derive |
(pending description) |
odrl:display |
(pending description) |
odrl:eq |
(pending description) |
odrl:execute |
(pending description) |
odrl:invalid |
(pending description) |
odrl:isAnyOf |
(pending description) |
odrl:isNoneOf |
(pending description) |
odrl:modify |
(pending description) |
odrl:neq |
(pending description) |
odrl:perm |
(pending description) |
odrl:prohibit |
(pending description) |
odrl:translate |
(pending description) |
odrl:use |
(pending description) |
OWL 2 Web Ontology Language Document Overview (Second Edition)
w3c-owl2 — W3C, edition 2012-12-11 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/2002/07/owl#
What depends on it.
| user | declared by |
|---|---|
cat-harness-tools/scripts/code-lists.ts |
@conformsTo tag |
cat-harness-tools/scripts/glossary-export.ts |
@conformsTo tag |
cat-harness-tools/scripts/ns-export.ts |
@conformsTo tag |
Operative terms (3). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
All terms below are derived from the corpus; operational semantics are pending individual per-term descriptions.
| term | what it means here |
|---|---|
owl:Ontology |
(pending description) |
owl:deprecated |
(pending description) |
owl:sameAs |
(pending description) |
The PROV-JSONLD Serialization: A JSON-LD Representation for the PROV Data Model
w3c-prov-jsonld — W3C, edition 2024-08-25 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
https://openprovenance.org/ns/provext#
Note. A W3C Member Submission (King’s College London; editors Luc Moreau, Dong Huynh) — acknowledged by W3C, NOT endorsed. Adopted by owner decision 2026-10-01 (beans jcet, 9y9j) because W3C publishes no JSON-LD context for PROV-O; PROV itself stays pinned by w3c-prov-o. The text is held at library/w3c-2024-prov-jsonld and its context.jsonld beside it, pinned by sha256 in schemas/prov-jsonld.ts and served offline; provext# is the Submission’s own extension namespace, which that context binds.
What depends on it.
| user | declared by |
|---|---|
cat-harness/schemas/prov-jsonld.ts |
@conformsTo tag |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
PROV-O: The PROV Ontology
w3c-prov-o — W3C, edition 2013-04-30 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/ns/prov#
What depends on it.
| user | declared by |
|---|---|
bootstrap-tools/scripts/export-graph.ts |
@conformsTo tag |
cat-harness-tools/scripts/kg-export.ts |
@conformsTo tag |
cat-harness/schemas/jsonld.ts |
@conformsTo tag |
Operative terms (3). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
All terms below are derived from the corpus; operational semantics are pending individual per-term descriptions.
| term | what it means here |
|---|---|
prov:Entity |
(pending description) |
prov:alternateOf |
(pending description) |
prov:wasDerivedFrom |
(pending description) |
RDF Calendar — an application of the Resource Description Framework to iCalendar Data
w3c-rdf-calendar — W3C, edition 2005-09-29 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/2002/12/cal/ical#
What depends on it.
| user | declared by |
|---|---|
cat-harness-tools/scripts/todo-graph.ts |
@conformsTo tag |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
RDF 1.1 Concepts and Abstract Syntax
w3c-rdf — W3C, edition 2014-02-25 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/1999/02/22-rdf-syntax-ns#
What depends on it.
| user | declared by |
|---|---|
cat-harness-tools/scripts/code-lists.ts |
@conformsTo tag |
cat-harness-tools/scripts/ns-export.ts |
@conformsTo tag |
folio-assistant-core/schemas/dublin-core-render.ts |
@conformsTo tag |
folio-assistant-core/skills/library/catalogue/oxigraph-catalogue-search.md |
conformsTo: front matter |
Operative terms (2). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
All terms below are derived from the corpus; operational semantics are pending individual per-term descriptions.
| term | what it means here |
|---|---|
rdf:JSON |
(pending description) |
rdf:Property |
(pending description) |
RDF Schema 1.1
w3c-rdfs — W3C, edition 2014-02-25 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/2000/01/rdf-schema#
What depends on it.
| user | declared by |
|---|---|
cat-harness-tools/scripts/glossary-export.ts |
@conformsTo tag |
cat-harness-tools/scripts/kg-export.ts |
@conformsTo tag |
cat-harness-tools/scripts/ns-export.ts |
@conformsTo tag |
Operative terms (5). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
All terms below are derived from the corpus; operational semantics are pending individual per-term descriptions.
| term | what it means here |
|---|---|
rdfs:Class |
(pending description) |
rdfs:comment |
(pending description) |
rdfs:isDefinedBy |
(pending description) |
rdfs:label |
(pending description) |
rdfs:seeAlso |
(pending description) |
SKOS Simple Knowledge Organization System Reference
w3c-skos — W3C, edition 2009-08-18 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/2004/02/skos/core#
What depends on it.
| user | declared by |
|---|---|
cat-harness-tools/scripts/glossary-export.ts |
@conformsTo tag |
cat-harness-tools/scripts/ns-export.ts |
@conformsTo tag |
cat-harness/schemas/jsonld.ts |
@conformsTo tag |
cat-harness/schemas/vocab-mapping.ts |
@conformsTo tag |
cat-harness/schemas/vocabulary.ts |
@conformsTo tag |
vocab-mapping graph |
through the module that types it (cat-harness/schemas/vocab-mapping.ts) |
Operative terms (22). The terms this repository acts on — derived by the tooling from the corpus, never hand-listed, and deliberately a subset of the edition rather than a transcription of it.
Terms marked pending description are derived from the corpus and await detailed operational description.
| term | what it means here |
|---|---|
skos:Collection |
A glossary’s members (folio-glossary/v1): external concepts this folio lists without copying them, emitted by the content core’s schemas/glossary.ts#toSkos. |
skos:Concept |
A MEANING, and the authoritative object for one. Minted per declared ROLE, never per lane name — 85 lane names resolve to 36 roles, so a concept per name would mint 85 terms for 36 meanings. |
skos:ConceptScheme |
The glossary document IS the scheme; there is no separate …#scheme IRI, because that would name a set that already has a name and would not dereference (blv9). |
skos:OrderedCollection |
(pending description) |
skos:altLabel |
The other names one concept is drawn under. build-pipeline is labelled ten ways across the corpus; nine are altLabels, which is what makes “Reviewer / SME” findable as “Reviewer” rather than a rival entry. |
skos:broadMatch |
Declared as one of the four mapping predicates vocabulary-authority names, and NOT YET emitted by anything: check:term-mapping resolves label equality, which cannot establish that one concept is broader than another. Recorded as available rather than used, so a reader does not infer from its presence that a hierarchy has been computed. |
skos:broader |
A glossary term’s broader: a local term id or an external IRI, emitted as a link (folio-glossary/v1). |
skos:changeNote |
Retirement. A term whose defining role is gone is deprecated and dated in the ledger, never deleted — a derived document has no memory, so the ledger is what makes “reported and never deleted” implementable. |
skos:closeMatch |
A candidate matched through a concept’s altLabel rather than its prefLabel — the right idea under another name. It is the concept-but-not-exact case, and the asymmetry is the whole reason check:term-mapping records the two states as a pair rather than one boolean. |
skos:definition |
What the term MEANS, taken from the role’s authored description — one author, one place to fix. Absent by design on a lane whose performer varies, which is honest rather than indistinguishable from a lane nobody bound. |
skos:exactMatch |
A candidate glossary term matched to a concept by its prefLabel — the exact half of check:term-mapping’s pair. Also what an authored term carries to an external vocabulary (policy to ODRL’s), which is how a match against a local concept reports the external IRI behind it rather than only an in-repo id. |
skos:hiddenLabel |
a role’s former names (formerNames in roles.json), emitted by glossary-export: findable by a reader holding an old name, never offered as current |
skos:inScheme |
Binds a concept to its instance’s glossary document. Each concept’s inScheme names that document’s own published URL, so a preview that publishes the graph without the glossary serves a 404ing scheme IRI — which check:invocation-parity refuses. |
skos:member |
The external concept IRIs of a glossary’s members Collection. |
skos:memberList |
(pending description) |
skos:narrowMatch |
The SKOS rendering of FHIR R5’s source-is-broader-than-target in a vocabulary mapping table (SKOS_MATCH_FOR, schemas/vocab-mapping.ts, bean k74z): A skos:narrowMatch B says B is narrower. |
skos:notation |
The CODE. TermGloss’s prefixed name (cat:FshGutsNode) already WAS this, which is why the “coded glossary” requirement was satisfied by data that existed rather than by new authoring. |
skos:note |
The status of a glossary term that is not authored (candidate, or could-not-extract with its reason), so a SKOS-only reader can tell it is not a curated definition (bean lqo9). |
skos:prefLabel |
The one name a concept is published under. AUTHORITATIVE for a concept’s name — where a node is both a resource and a concept, dcterms:title is the derived copy and this is the source. |
skos:related |
A glossary term’s related: a local term id or an external IRI. |
skos:relatedMatch |
The fourth mapping predicate, and like broadMatch not yet emitted. Relatedness is a judgement no label comparison can reach, so it waits for an adjudication step (bean 2i5f) rather than being approximated. |
skos:scopeNote |
What a lane is accountable for IN ONE PROCESS. Carried on the LaneUsage node, never the concept: of 26 lane names appearing in more than one diagram, 26 of 26 document themselves differently per occurrence, so ten unattributed notes on one concept would read as ten contradictions. Stored verbatim, because the note is a .pot msgid. |
SPARQL 1.1 Query Language
w3c-sparql-1.1-query — W3C, edition 2013-03-21 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
Note. The query language the IRIS replica’s Oxigraph pipeline (skill iris-oxigraph) runs over the catalogue’s N-Quads: faceted rollups and combined queries, in the browser (WebAssembly) and on the CLI. A language, not an RDF vocabulary, so it claims no namespace; the IRIs its queries match are the vocabularies’ own (dcterms, skos, …), recorded under those.
What depends on it. Nothing here declares it.
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
Web Annotation Vocabulary
w3c-web-annotation — W3C, edition 2017-02-23 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/ns/oa#
What depends on it.
| user | declared by |
|---|---|
cat-harness/schemas/jsonld.ts |
@conformsTo tag |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes
w3c-xsd11-datatypes — W3C, edition 2012-04-05 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/2001/XMLSchema#
What depends on it.
| user | declared by |
|---|---|
cat-harness-tools/scripts/kg-export.ts |
@conformsTo tag |
cat-harness/schemas/jsonld.ts |
@conformsTo tag |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures
w3c-xsd11-structures — W3C, edition 2012-04-05 — conforms, meaning this repository’s artefacts are valid against it.
Namespaces.
http://www.w3.org/2001/XMLSchema-instance
Note. Added for bean 7eak. The Dublin Core XML rendering (folio-assistant-core/schemas/dublin-core-render.ts) puts xsi:type="dcterms:<Scheme>" on an element to name its encoding scheme. That is how DCMI’s Guidelines for implementing Dublin Core in XML (2003-04-02) carry W3CDTF, URI, RFC4646 and MESH. The xsi namespace is defined in Part 1 (Structures) §2.7, not in Part 2 (Datatypes), which w3c-xsd11-datatypes already pins. So this is a separate record and not an extra namespace on that one.
What depends on it.
| user | declared by |
|---|---|
folio-assistant-core/schemas/dublin-core-render.ts |
@conformsTo tag |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.
WHO SMART Guidelines base IG
who-smart-base — other, edition v1.0.0 — reads, meaning this repository parses documents written in it.
Namespaces.
http://smart.who.int/base/StructureDefinition/
Note. Tracks the canonical smart-base’s sushi-config.yaml declares (http://smart.who.int/base); its logical models publish under StructureDefinition/. reads: the platform references those models; it does not publish them. PINNED 2026-09-30 to v1.0.0 (sushi-config version: 1.0.0, releaseLabel: release — a published release, not a ci-build), on the owner’s ruling that check:term-mapping’s fhir half asserts a published IG AT A VERSION. Its terminology is snapshotted beside this record in who-smart-base.terminology.json; move the pin and re-run scripts/pin-smart-base-terminology.ts to update both together.
What depends on it.
| user | declared by |
|---|---|
cat-harness/schemas/jsonld.ts |
@conformsTo tag |
No operative terms. This repository conforms to the specification without branching on any of its terms, so none is materialised into the graph. That is a determined zero, not an unfilled field.