From 83f42388eca845095d49fff9ff2f9a567e7a9764 Mon Sep 17 00:00:00 2001 From: manumishra12 Date: Sat, 11 Jul 2026 14:30:02 -0700 Subject: [PATCH] okf: allow okf_version on standalone concept files (SPEC 11) Section 11 only allowed okf_version in a bundle-root index.md. Issue #57 asks how a single document distributed outside a bundle identifies itself as OKF. Clarifies that a standalone concept file MAY declare okf_version in its own frontmatter and be treated as a one-concept bundle, with the bundle-root declaration taking precedence once the file is placed in a bundle. Additive and backward-compatible (per SPEC 11). Addresses #57. --- okf/SPEC.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/okf/SPEC.md b/okf/SPEC.md index 55d0a46..c9ece1a 100644 --- a/okf/SPEC.md +++ b/okf/SPEC.md @@ -395,6 +395,13 @@ only place frontmatter is permitted in an `index.md`). Consumers that do not understand the declared version SHOULD attempt best-effort consumption rather than refusing the bundle. +A single concept document distributed on its own — outside any bundle — MAY +likewise declare `okf_version` in its own frontmatter. This lets a standalone +file identify itself as OKF content without a surrounding bundle or a root +`index.md`; consumers SHOULD treat such a file as a one-concept bundle. When +the file is later placed inside a bundle that declares its own version at the +root, the bundle-root declaration takes precedence. + --- ## Appendix A — Minimal example bundle