From 657571537792946deb23986e7afa4d4c2d09ae79 Mon Sep 17 00:00:00 2001 From: manumishra12 Date: Sat, 11 Jul 2026 14:25:49 -0700 Subject: [PATCH] okf: align timestamp as recommended and note staleness use (SPEC 4.1) Section 4.1 lists timestamp under Recommended, but the frontmatter example comment still labelled it Optional. Aligns the comment and adds a sentence explaining that consumers rely on timestamp to detect stale knowledge, so producers SHOULD set it whenever a concept is created or updated. Addresses #97. --- okf/SPEC.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/okf/SPEC.md b/okf/SPEC.md index 55d0a46c..c9e4e337 100644 --- a/okf/SPEC.md +++ b/okf/SPEC.md @@ -128,7 +128,7 @@ title: description: resource: tags: [, , …] # Optional -timestamp: # Optional last-modified time +timestamp: # Recommended last-modified time # … other producer-defined key/value pairs --- ``` @@ -155,7 +155,9 @@ timestamp: # Optional last-modified time concept describes. Absent for concepts that describe abstract ideas rather than physical resources. - `tags` — A YAML list of short strings for cross-cutting categorization. -- `timestamp` — ISO 8601 datetime of last meaningful change. +- `timestamp` — ISO 8601 datetime of last meaningful change. Because + consumers rely on it to detect stale knowledge, producers SHOULD set it + whenever a concept is created or updated. **Extensions:** Producers MAY include any additional keys. Consumers SHOULD preserve unknown keys when round-tripping and SHOULD NOT reject