OKF Specification (v0.2)

July 31, 2026 · View on GitHub

These pages restate the Open Knowledge Format v0.2 specification, one concept per spec section, cross-linked. OKF is a minimal, vendor-neutral format for representing knowledge as a directory of markdown files with YAML frontmatter — no schema registry, central authority, or required tooling. v0.2 adds optional provenance, trust, and lifecycle frontmatter and an Attested Computation concept type. The authoritative source is the OKF SPEC.md reference.

Normative keywords (MUST, SHOULD, MAY) are used in the RFC 2119 sense.

On this bundle: these pages document v0.2, but the bundle itself is still authored in v0.1 (the root index declares okf_version: "0.1"). See Changes from v0.1.

Front Matter of the Spec

  • Motivation - why standardize on established, diffable, portable formats.
  • Terminology - bundle, concept, frontmatter, body, link, source, actor, trust tier.

Structure

Concept Documents

  • Frontmatter - type is the only required key; recommended and optional families.
  • Body - conventional headings (# Schema, # Examples, # Computation), no required sections.

Provenance, Trust & Identity

Linking & Reserved Files

  • Cross-linking & Paths - markdown links as directed edges; path-valued fields; references/ (§6).
  • Index Files - directory listings enabling progressive disclosure (§8).
  • Log Files - date-grouped change history, newest first (§9).

Computation

Conformance & Evolution

  • Conformance - the minimal bar a bundle must clear (§11).
  • Versioning - <major>.<minor> and the okf_version declaration (§12).
  • Changes from v0.1 - two breaking changes with fallbacks; everything else additive (§13).