◇ Open Values Standardfor builders

Conformance

Check a file against the standard, in this page or from the command line. The page reads the file in your browser; nothing is uploaded.

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.

Check a file

Choose a file or paste one. Its format field picks the schema; a file without one asks which format it is.


From the command line

Clone the repository; the checker needs Node 18 or later and nothing else.

node scripts/ovs-validate.mjs my-values.json
node scripts/ovs-validate.mjs --format open-values-lens my-facts.json
node scripts/ovs-validate.mjs --vectors     # the conformance examples
node scripts/ovs-validate.mjs --all         # every file in the repository the registry points at

The page and the command line use the same file, ovs-validate.mjs, so they always agree. It checks the parts of JSON Schema the Open Values schemas use and reports any part it does not check instead of passing it silently.

What a schema checks, and what it does not

The standard comes with 107 conformance examples, each a file that MUST pass or MUST fail. Checked by schema alone, 91 of 107 come out as expected.

These rules span more than one field, so a schema cannot express them; research/standard_audit.js in the repository checks them:

3 examples that MUST pass fail their schemas today, which means the schema is stricter than the standard intends: ovs-ask-index, ovs-ask-core-index, open-values-decision-contracts. These are being fixed in the schemas.

What an app must keep

A file can pass its schema and an app can still break the standard's promises. The promises an app MUST keep to call itself compatible are on the kit's front page.