properties /meets specification
specification scheme
also called who wrote it
Who issues the specification a `meets_specification` claim cites — an industry body, a regulator, or the machine's own manufacturer. It is STORED because it cannot be derived, and the derivation was attempted and failed: run a reader over real printed designations and 'API SN/CF', 'ACEA A3/B4', 'ILSAC GF-5' and 'FMVSS 116 DOT 4' parse, while 'DEXRON III', 'Type WS', 'JWS 3309', 'NS-3', '229.1', 'B71 2295', 'RN 0700/0710', 'MS-12991', 'WSS-M97B44-D' and 'DQC CB-14' name no issuer anywhere in the string — the function fails on more inputs than it succeeds on. A fact that is sometimes encoded and sometimes not cannot be read; it must be stored. IT IS NOT A DATASHEET LAYOUT collapsed into a token and must never be defended as one: the houses do not agree on a layout at all — Castrol prints a single flat list headed 'Product Performance Claims' with its manufacturer approvals loose in the application prose, while TotalEnergies prints three tiers (flat approvals, then 'Meets the requirements of:', then 'Suitable for applications requiring:'). What this token records is who wrote the document and therefore who may withdraw it. Whether an approval was GRANTED or merely DECLARED is a different question again, and this token deliberately does not answer it — a recorded follow-up, not a fourth value.
Specification scheme is answered with one word chosen from the specification schemes list — the same word shared across every product that uses it.
It is a qualifier of meets specification — it has meaning only inside a meets specification statement, never on its own. It belongs with meets specification to identity — who and what it is.
It is answered inside every meets specification statement, not as a standalone question on a kind.
Answered inside every meets specification statement — not a standalone slot on any kind.