The records SMART Base (smart-base) holds in smart-base/external-schemas, read at this build’s pins. The platform’s own registry, and the namespaces the whole corpus uses compared against it, are on the full page.

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.

1specifications
0operative terms in graph
0declared uses
57declarations naming no record

The specifications

specificationauthorityeditionhow it is used
WHO SMART Guidelines knowledge graph (ontology)
who-smart-kg
other66a9b1393fd7f315eb4eb0dab001db5e3eb0c5efcites — it is referenced, and nothing here is validated against 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).

57 declaration(s) name a specification no record has.

usernames
bootstrap-tools/scripts/export-graph.tsw3c-prov-o
cat-harness-tools/archimate/scripts/gen-archimate-pages.tsopengroup-archimate-3.0
cat-harness-tools/openapi/scripts/gen-openapi-pages.tsw3c-hydra
cat-harness-tools/scripts/code-lists.tsw3c-owl2
cat-harness-tools/scripts/code-lists.tsw3c-rdf
cat-harness-tools/scripts/glossary-export.tsw3c-owl2
cat-harness-tools/scripts/glossary-export.tsw3c-rdfs
cat-harness-tools/scripts/glossary-export.tsw3c-skos
cat-harness-tools/scripts/kg-export.tsdcmi-terms
cat-harness-tools/scripts/kg-export.tsomg-bpmn-2.0
cat-harness-tools/scripts/kg-export.tsschema-org
cat-harness-tools/scripts/kg-export.tsw3c-prov-o
cat-harness-tools/scripts/kg-export.tsw3c-rdfs
cat-harness-tools/scripts/kg-export.tsw3c-xsd11-datatypes
cat-harness-tools/scripts/ns-export.tsdcmi-terms
cat-harness-tools/scripts/ns-export.tsw3c-owl2
cat-harness-tools/scripts/ns-export.tsw3c-rdf
cat-harness-tools/scripts/ns-export.tsw3c-rdfs
cat-harness-tools/scripts/ns-export.tsw3c-skos
cat-harness-tools/scripts/render-bpmn.tsomg-bpmn-2.0
cat-harness-tools/scripts/render-bpmn.tsomg-dd-1.0
cat-harness-tools/scripts/todo-graph.tsw3c-rdf-calendar
cat-harness-tools/scripts/todo-graph.tsschema-org
cat-harness-tools/scripts/todo-graph.tsdcmi-terms
cat-harness-tools/src/workflow/process-model.tsomg-bpmn-2.0
cat-harness/archimate/schemas/archimate.tsopengroup-archimate-3.0
cat-harness/schemas/jsonld.tshl7-fhir
cat-harness/schemas/jsonld.tsspar-doco-deo-cito
cat-harness/schemas/jsonld.tsw3c-csvw
cat-harness/schemas/jsonld.tsw3c-web-annotation
cat-harness/schemas/jsonld.tswho-smart-base
cat-harness/schemas/jsonld.tsw3c-prov-o
cat-harness/schemas/jsonld.tsw3c-skos
cat-harness/schemas/jsonld.tsw3c-xsd11-datatypes
cat-harness/schemas/nquads-distribution.tsw3c-n-quads
cat-harness/schemas/odrl.tsw3c-odrl
cat-harness/schemas/prov-jsonld.tsw3c-prov-jsonld
cat-harness/schemas/prov-jsonld.tsietf-handle-system
cat-harness/schemas/spdx-license-expression.tsspdx-license-list
cat-harness/schemas/vocab-mapping-fhir.tshl7-fhir
cat-harness/schemas/vocab-mapping.tshl7-fhir
cat-harness/schemas/vocab-mapping.tsw3c-skos
cat-harness/schemas/vocabulary.tsw3c-skos
cat-harness/skills/kg/graph-management/named-query-execution.mdw3c-n-quads
cat-harness/skills/kg/graph-management/nquads-distribution.mdw3c-n-quads
folio-assistant-core/schemas/dublin-core-render.tsdcmi-terms
folio-assistant-core/schemas/dublin-core-render.tsw3c-rdf
folio-assistant-core/schemas/dublin-core-render.tsw3c-xsd11-structures
folio-assistant-core/schemas/dublin-core.tsdcmi-terms
folio-assistant-core/schemas/reference.tsdcmi-terms
folio-assistant-core/schemas/reference.tspurl-bibo
folio-assistant-core/schemas/reference.tsspar-fabio
folio-assistant-core/skills/library/catalogue/oxigraph-catalogue-search.mddcmi-terms
folio-assistant-core/skills/library/catalogue/oxigraph-catalogue-search.mdw3c-rdf
who-iris/skills/iris-dspace.mddcmi-terms
who-iris/skills/iris-oxigraph.mdw3c-sparql-1.1-query
who-iris/skills/iris-oxigraph.mdw3c-n-quads

1 record(s) nothing declares. A version bump would move nothing that says so:

Each specification

WHO SMART Guidelines knowledge graph (ontology)

who-smart-kg — other, edition 66a9b1393fd7f315eb4eb0dab001db5e3eb0c5ef — cites, meaning it is referenced, and nothing here is validated against it.

Namespaces.

  • http://smart.who.int/kg/

Note. litlfred/smart-kg, a fork of WorldHealthOrganization/smart-kg, PINNED 2026-10-02 to the commit ‘Merge pull request #1 from WorldHealthOrganization/l1-graph’. It is a T-Box only: a type graph over the SMART Guidelines layers (L1 recommendations, evidence and PICO; L2 DAK components; BPMN and DMN interiors; an L3 FHIR index), with no instance data. REFERENCED, never copied (owner 2026-09-23, bean wg7r: ‘that is its own repo already’). cites: smart-base’s document kinds name the smart-kg classes a section instantiates (modelledBy); the class ids at this commit are snapshotted beside this record in who-smart-kg.terms.json by smart-base/scripts/pin-smart-kg.ts, so that check runs offline. Move to conforms when smart-base produces smart-kg instance documents (bean 8pzh). Bean pebe.

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.


folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev