OKF specification (v0.2)

Referencereferences/okf-specification

Confirmed by a person, 2026-10-13

Written 2026-10-13 by noelmcloughlin (a person). Last checked 2026-10-13 by noelmcloughlin (a person).

The full record

Checks

2026-09-09 by noelmcloughlin (a person)
2026-09-26 by noelmcloughlin (a person)
2026-10-06 by ktl-librarian (automation)
2026-10-13 by noelmcloughlin (a person)

Review by

2027-09-26

Sources

https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/main/SPEC.md

Pointed to by

ktl-librarian skill (references)
LOKF specification (related to)
OKF (defined by)
The curated context layer: one bundle, and a federation of bundles (references)
Trust label (references)

Graph

Open this concept in the knowledge graph

IRI

https://w3id.org/ktl/knowledge/references/okf-specification

Licence

CC BY 4.0

Files

Markdown JSON-LD Source on GitHub History on GitHub

Overview

Every LOKF bundle is also a valid OKF bundle. OKF supplies the substrate the skills depend on: one concept per file with path as concept ID, type as the only strictly required field, and permissive consumption - unknown types, unknown keys, and broken cross-links must never cause rejection.

Sections 5.1-5.5 define the trust vocabulary this repository’s whole thesis rests on: sources (provenance) and generated, verified (trust events), status and stale_after (lifecycle), and section 5.3’s trust tiers - derived from the actor strings, never stored. Section 7 fixes the actor convention (human:<id>, process:<id>, <producer>/<version>) that makes “confirmed by a person” a machine-checkable distinction.