Field reference
Every field of OTE Spec v0.3. This page is generated from the JSON Schemas, so it cannot drift from what the validator actually enforces.
Not generated from the schemas
The field you need isn't here
Add it. OTE's schemas do not forbid extra fields, on purpose: your document stays valid, and a consumer that doesn't understand them can ignore them safely. This is how the spec grows — through fields someone already uses, not fields we imagine will be needed.
Candidate for the core
A generic field that could become part of OTE. Write it without a prefix. If enough people need it, it gets standardised — and your local meaning gives way to the normative one.
"capacity": 80
Someone else's vocabulary
A field whose meaning is defined by another project, and that will never belong to OTE. Write it with a prefix. It cannot collide with a core field, today or at 1.0.
"combuilders:communityId": "gdg-madrid"
OTE will never mint a field name containing a colon. That reservation is what makes the second column safe — and what lets OTE connect to other specifications without being coupled to them.