◇ Open Values Standardfor builders

Spec / ovs-tag-registry

Open Values Tag Registry v0.1

The list of labels an option can carry, such as Organic or Fair Trade, with the other spellings that count as the same label and a sentence on what each one means. Conscious Consuming keeps it.

Stable. A change that breaks existing files needs a new version. A file someone writes by hand or with a tool, and keeps.

Who writes it and who reads it

Written by pipeline/build_tags.js. Read by Discover facets, node pages, Ask.

Fields

FieldWhat it meansType
format requiredAlways "ovs-tag-registry". Tells a reader that this file is the list of labels entries can carry.always "ovs-tag-registry"
version requiredThe version of the tag registry format this file follows, 0.1.string
updated requiredThe day the file was last changed, as YYYY-MM-DD.string
minItems requiredThe fewest entries a tag must be found on before it gets its own page and appears in search. The current file uses 10.integer
tags requiredThe tags: labels such as "Organic" or "Fair Trade" that entries carry in their focuses.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

A tag registry entry declares id, label, aliases, kind, meaning, and receipt field.

{
  "format": "ovs-tag-registry",
  "version": "0.1",
  "updated": "2026-07-07",
  "minItems": 1,
  "tags": [
    {
      "id": "ovs:tag/open-source",
      "label": "Open source",
      "aliases": [
        "foss"
      ],
      "kind": "property",
      "reads": "The source code is inspectable or reusable.",
      "receipt": null
    }
  ]
}

A file that must be rejected

Certification tags need receipt links.

{
  "format": "ovs-tag-registry",
  "version": "0.1",
  "updated": "2026-07-07",
  "minItems": 1,
  "tags": [
    {
      "id": "ovs:tag/fair-trade",
      "label": "Fair Trade",
      "aliases": [],
      "kind": "certification",
      "reads": "The item carries a fair-trade certification.",
      "receipt": null
    }
  ]
}

The schema

Its address is https://openvaluesstandard.org/schema/tag-registry-v0.1.schema.json. Validators can fetch it there; the file is also in the repository at app/data/standard/schemas/tag-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.