Spec / open-values-format-registry
Open Values Format Registry
The list of every Open Values file format, one entry each: what the format is for, where its schema is, which files and code write it, which code reads it, and which checks enforce it. The project keeps it by hand at app/data/standard/registry.json; the standard audit and the spec pages on openvaluesstandard.org read it.
- Files people or tools write
- Status: draft
- Version: 0.1.0
- Format name in the file:
open-values-format-registry
Draft. It may still change before it is called stable. A file someone writes by hand or with a tool, and keeps.
Who writes it and who reads it
No writer is listed. Read by audit:standard, standard documentation, pipeline/build_kit.js, pipeline/build_site.py.
Fields
| Field | What it means | Type |
|---|---|---|
format required | Always "open-values-format-registry". Tells a reader which Open Values format this is. | always "open-values-format-registry" |
version required | The version of the registry format this file follows, as a semantic version such as "0.1.0". | see semver |
standard required | Always "open-values-standard", the standard this registry belongs to. | always "open-values-standard" |
standardVersion required | The version of the Open Values Standard the registry describes, as a semantic version such as "1.0.0-draft.1". | see semver |
updated required | The date the registry was last changed, as YYYY-MM-DD. | string |
entries required | One entry per file format. At least one. | list |
This format allows no fields beyond the list above. A writer MUST NOT add any.
A file that passes
A minimal registry has semver versions and at least one entry.
{
"format": "open-values-format-registry",
"version": "0.1.0",
"standard": "open-values-standard",
"standardVersion": "1.0.0-draft.1",
"updated": "2026-07-07",
"entries": [
{
"id": "open-values-example",
"version": "0.1.0",
"declaredVersion": "0.1.0",
"status": "draft",
"kind": "source",
"purpose": "Fixture registry entry.",
"marker": {
"mode": "explicit-format",
"format": "open-values-example"
},
"schema": null,
"schemaNote": "Fixture entry has no schema.",
"sourceOfTruth": [],
"generatedOutputs": [],
"builders": [],
"audits": [],
"ownerLane": "data-lane",
"runtimeConsumers": [],
"compatibility": {
"acceptsLegacyVersion": false
}
}
]
}
A file that must be rejected
Explicit-format registry markers must name the same format as the entry id.
{
"format": "open-values-format-registry",
"version": "0.1.0",
"standard": "open-values-standard",
"standardVersion": "1.0.0-draft.1",
"updated": "2026-07-07",
"entries": [
{
"id": "open-values-example",
"version": "0.1.0",
"declaredVersion": "0.1.0",
"status": "draft",
"kind": "source",
"purpose": "Fixture registry entry.",
"marker": {
"mode": "explicit-format",
"format": "open-values-other"
},
"schema": null,
"schemaNote": "Fixture entry has no schema.",
"sourceOfTruth": [],
"generatedOutputs": [],
"builders": [],
"audits": [],
"ownerLane": "data-lane",
"runtimeConsumers": [],
"compatibility": {
"acceptsLegacyVersion": false
}
}
]
}
Bare legacy declared versions require an explicit compatibility flag.
{
"format": "open-values-format-registry",
"version": "0.1.0",
"standard": "open-values-standard",
"standardVersion": "1.0.0-draft.1",
"updated": "2026-07-07",
"entries": [
{
"id": "open-values-example",
"version": "0.1.0",
"declaredVersion": "0.1",
"status": "draft",
"kind": "source",
"purpose": "Fixture registry entry.",
"marker": {
"mode": "explicit-format",
"format": "open-values-example"
},
"schema": null,
"schemaNote": "Fixture entry has no schema.",
"sourceOfTruth": [],
"generatedOutputs": [],
"builders": [],
"audits": [],
"ownerLane": "data-lane",
"runtimeConsumers": [],
"compatibility": {
"acceptsLegacyVersion": true
}
}
]
}
Schema gaps must carry an explicit note instead of disappearing silently.
{
"format": "open-values-format-registry",
"version": "0.1.0",
"standard": "open-values-standard",
"standardVersion": "1.0.0-draft.1",
"updated": "2026-07-07",
"entries": [
{
"id": "open-values-example",
"version": "0.1.0",
"declaredVersion": "0.1.0",
"status": "draft",
"kind": "source",
"purpose": "Fixture registry entry.",
"marker": {
"mode": "explicit-format",
"format": "open-values-example"
},
"schema": null,
"sourceOfTruth": [],
"generatedOutputs": [],
"builders": [],
"audits": [],
"ownerLane": "data-lane",
"runtimeConsumers": [],
"compatibility": {
"acceptsLegacyVersion": false
}
}
]
}
Registry versions use semver.
{
"format": "open-values-format-registry",
"version": "draft",
"standard": "open-values-standard",
"standardVersion": "1.0.0-draft.1",
"updated": "2026-07-07",
"entries": []
}
The schema
Its address is https://openvaluesstandard.org/schema/format-registry-v1.schema.json. Validators can fetch it there; the file is also in the repository at app/data/standard/schemas/format-registry.schema.json.
The key words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY are used as described in RFC 2119 and RFC 8174 when, and only when, they appear in capitals.
Whether this format fits your app is your call. The spec says what a file MUST hold. Which formats you read and write, and what your app does with them, is yours to decide.