| 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/huisnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/huisnummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/huisnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/huisnummertoevoeging/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/plaatsnaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/postcode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/straatnaam/description |
| Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types | /properties/type/enum – /properties/type/type |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/type/description |