Repository navigation
Description
Revised 2026-11-14: every enum takes the open form, except discriminators; x-closed is dropped.
Problem
A value list whose receivers must accept unknown values isn't an enum, yet the schemas declare every such list with enum, which a strict validator enforces. So a conforming strict receiver rejects what the versioning page tells it to accept:
Clients must tolerate unknown values and fall back to sensible defaults. (versioning.mdx L228)
With #8915, a 3.3 adagents.json using the new match_keys value full_name fails 3.2.10 validation as a whole file. advertiser-industry.json says "Sellers MUST accept unknown values", and its own enum rejects them.
In static/schemas/source at main bf4aa6dbb3:
enum sites |
Count |
|---|---|
All string enums, outside tests such as not and if |
1,006 |
| Discriminators, which stay closed | 18 |
| Everything else, lifecycles included, which takes the open form | 988 |
Extension branches beside an enum |
4, in three grammars: custom:{key}, x_{key}, an HTTPS URI |
Values containing : |
3, in chroma_subsampling |
This gist has every site, the citations and the scripts.
Proposal for 4.0
- One form for every list. Every
enumtakes the open form:A minor adds core values, and anyone may send an extension term. Only discriminators differ: a one-value{"oneOf": [{"enum": ["automotive", "finance"]}, {"$ref": "/schemas/core/extension-term.json"}]}enumbecomesconst, and a branch-selecting key stays plain. - One extension-term schema. A term is
{domain}:{key}, on a domain its definer controls, as in BrandRef, so no registry is needed. Core values never contain:, sooneOfis exact;chroma_subsamplingis respelled. - No exemption. The tolerate-unknown text goes: a sender uses a core value only with peers served a release that defines it, as with fields.
- Unknown terms. Each open position's
x-adcp-unknown-termisignoreor the core value an unknown term counts as. - One lint. Every
enumis a discriminator or an open-form core, and every extension branch references the shared schema. Its 4.0.0 baseline is empty.
Why 4.0
Moving custom:, x_ and the URI branches to the shared grammar changes wire values, and dropping the exemption changes what sellers may send. It fits T2 beside #8900 and #8901. For #8885, error.code takes the open form.
I'm happy to take this on.
Analyzed and generated with the help of Claude, fully reviewed by me.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsNo status
Activity
[-]4.0: every value list is a closed enum or an open vocabulary, with one extension-term schema, checked by the build[/-][+]4.0: every value list takes one open form, with a shared extension-term schema, checked by the build[/+]