Spec / open-values-edges
Open Values Edges v0.1
A list of sourced links between options, brands and companies, such as which company owns a brand or which bank is an alternative to another. Each link carries a source and a date.
- Files built from other files
- Status: stable
- Version: 0.1
- Format name in the file:
open-values-edges
Stable. A change that breaks existing files needs a new version. A file a build step makes from other files. Change the sources, not this file.
Who writes it and who reads it
Written by pipeline/build_datasets.py, pipeline/build_site.py. Read by ownership node pages, graph tests.
Fields
| Field | What it means | Type |
|---|---|---|
format required | Always "open-values-edges". Tells a reader that this file is a list of sourced links between entries. | always "open-values-edges" |
version required | The version of the edges format this file follows, 0.1. | string |
note | A paragraph for maintainers saying what the edges cover and which checks hold them. | string |
edges required | The links. Each one says that one entry, brand or company relates to another in a named way, with a source and a date. | list |
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
An edge graph carries sourced relationships between namespaced nodes.
{
"format": "open-values-edges",
"version": "0.1",
"edges": [
{
"from": "ovs:cat/banking",
"rel": "alternative-to",
"to": "ovs:cat/payments",
"source": "Fixture source.",
"asof": "2026"
}
]
}
A file that must be rejected
Duplicate edge triples should not be accepted.
{
"format": "open-values-edges",
"version": "0.1",
"edges": [
{
"from": "ovs:cat/banking",
"rel": "alternative-to",
"to": "ovs:cat/payments",
"source": "Fixture source.",
"asof": "2026"
},
{
"from": "ovs:cat/banking",
"rel": "alternative-to",
"to": "ovs:cat/payments",
"source": "Fixture source.",
"asof": "2026"
}
]
}
The schema
Its address is https://openvaluesstandard.org/schema/edges-v0.1.schema.json. Validators can fetch it there; the file is also in the repository at app/data/standard/schemas/edges.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.