LOKF Specification
references/lokf-specificationChecked by automation only
Written 2026-09-13 by ktl-librarian (automation). Last checked 2026-09-13 by ktl-librarian (automation).
The full record
- Checks
- 2026-09-13 by
ktl-librarian(automation)
- 2026-09-13 by
- Sources
- Derived from
- Pointed to by
- LOKF (defined by)
- LOKF Toolkit (related to)
- Validator Engine (about)
- Why KTL Registrar (about)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/ktl/registrar/knowledge/references/lokf-specification- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Overview
Section titled “Overview”LOKF is a semantic profile of OKF. It keeps the same directory-of-Markdown convention, and adds a bundle-root semantic header, a controlled type vocabulary (15 classes, Role included), typed RDF-backed relationships, and rules for building ids and IRIs. src/validator.ts implements Golden Rules 2-5 of this specification.
Golden Rule 6 (trust, provenance and lifecycle) is OKF v0.2’s own. The plugin checks the shape of those fields: a well-formed { by, at } event, a known status, a dated stale_after, and a resource on every source. It never checks their credibility, which is the sibling KTL Curator’s surface (docs/for-the-curious.md, “What LOKF adds over plain OKF”).
Corrected 2026-09-13: this concept had said Rule 6 was left to a separately installed OKF validator, the design abandoned on 2026-09-12.