Domain schema
glossary/domain-schemaChecked by automation only
still a draft
Written 2026-10-26 by ktl-librarian (automation). Last checked 2026-10-29 by ktl-librarian (automation).
A schema written in LinkML that extends LOKF's, for a domain whose concepts stop fitting LOKF's classes.
The full record
- Checks
- 2026-10-29 by
ktl-librarian(automation)
- 2026-10-29 by
- Sources
- Related to
- Pointed to by
- Curating a domain bundle (related to)
- LinkML (related to)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/ktl/knowledge/glossary/domain-schema- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Overview
Section titled “Overview”LOKF’s vocabulary is a short list of classes and typed relations, kept small so that bundles stay portable. Concepts typically stop fitting those classes in a deep or safety-critical domain, such as medicine, law, finance or safety engineering. The answer is then a domain schema written in LinkML that extends LOKF’s. The curator flags concepts that no longer fit, the team decides, and the librarian applies it.
The architecture page says that a domain that extends the schema has its own types checked rather than tolerated (when the built-in vocabulary stops fitting).
Since 0.44.0 one domain schema is released with the sidecar: domain.yaml, for a bundle that federates other bundles, as the curator’s domain-schemas.md says.
A domain schema that grows past a few classes is worth a project of its own, with lint, tests and a docs site. The linkml-sidecar skills install one beside the bundle, or around a schema the repository already holds, as the curator’s domain-schemas.md says since 0.55.1.