| 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 | |
| Future versions of JSON Schema will refuse to evaluate unknown keywords or custom keywords from optional vocabularies that don't have an x- prefix | /properties/hoofdstad/nullable |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/hoofdstad/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/hoofdstad/oneOf/0/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/hoofdstad/oneOf/0/properties/id/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/hoofdstad/oneOf/0/properties/naam/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/hoofdstad/oneOf/0/properties/tijdsverschil/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/hoofdstad/oneOf/0/properties/tijdsverschil/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/hoofdstad/oneOf/0/properties/tijdsverschil/format |