| Set a concise non-empty title at the top level of the schema to explain what the definition is about | |
| Set a non-empty description at the top level of the schema to explain what the definition is about in detail | |
| Set a non-empty examples array at the top level of the schema to illustrate the expected data | |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/kgco2_1990/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/kgco2_1990/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/kgco2_1995/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/kgco2_1995/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/kgco2_2000/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/kgco2_2000/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/kgco2_2005/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/kgco2_2005/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/kgco2_2010/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/kgco2_2010/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/kgco2_2012/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/kgco2_2012/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/kgco2_2013/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/kgco2_2013/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/sbi_code/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/sbi_code/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/tj_warmte/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/tj_warmte/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/weergave/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/weergave/format |