Spec / open-values-source
Open Values Source v0.1
Where a score comes from. It is either a short note, or a citation with a one-line note, a web address and the year the claim was true.
- Parts of other formats
- Status: stable
- Version: 0.1.0
- Format name in the file:
open-values-source
Stable. A change that breaks existing files needs a new version. Not a file on its own: a shape used inside other formats.
Who writes it and who reads it
No writer is listed. Read by open-values-entity, open-values-rating, open-values-lens.
Fields
This schema lists no named fields; see the schema file for its shape.
A reader MUST ignore fields it does not know, so a file can carry more than this list and still be read. A writer MUST NOT change what a listed field means.
A file that passes
Legacy plain-string provenance remains readable.
"Monthly fee is waived above a minimum balance."
Citation-object provenance has note, source URL, and asof year.
{
"note": "Annual report names Scope 1 and 2 emissions.",
"source": "https://example.org/report",
"asof": "2026"
}
A file that must be rejected
Citation objects must include an http(s) source.
{
"note": "Annual report names Scope 1 and 2 emissions.",
"asof": "2026"
}
The schema
Its address is https://openvaluesstandard.org/schema/source-v0.1.schema.json. Validators can fetch it there; the file is also in the repository at app/data/standard/schemas/source.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.