OKF log.md file can have a frontmatter ?

[straumat]

From what I understood in 0.1 & 0.2 specs, log.md files should not have frontmatter ?

But the log.md provided in the the acme_retail provided example has one:

---
type: Log
title: Acme Retail bundle history
---

[scaccogatto]

Ran into the same thing from the implementer side, with a reproduction.

Our validator (okf-skills, mine, disclosure) warns on acme_retail/log.md itself: "§9 log.md should contain no frontmatter". So at least two readers have taken §9 to imply §8's rule, and the spec's own reference bundle disagrees with both of them. Worth adding that acme_retail is the only one of the four reference bundles that ships a log.md at all, so the examples do not settle the convention either way.

Why it is not cosmetic: §11 makes reserved files a conformance criterion, "follows the structure in §8 and §9". And a consumer that inventories concepts by scanning frontmatter for type (§4.1) picks up a log carrying type: Log as a concept of that type, which is the outcome §3.1 exists to prevent when it says reserved names must not be used for concept documents.

It is also already propagating. Basic Memory's public OKF v0.2 compatibility draft emits logs "with or without optional type: Log frontmatter", which reads like the reference bundle being taken as the convention: https://app.basicmemory.com/s/5bntnlG7DexytBlLSTyWZ

I have no stake in which way this goes, and my validator may well be the one over-reaching, since §9 never says what §8 says. What would settle it is one sentence in §9 mirroring §8's, and acme_retail agreeing with it.

[Sayantan181222]

I've submitted a fix in PR #401. Added one sentence to §9 mirroring §8's
existing rule, and removed the frontmatter from the acme_retail reference
bundle so spec and example agree.