| Set a concise non-empty title at the top level of the schema to explain what the definition is about | |
| Set a non-empty examples array at the top level of the schema to illustrate the expected data | |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/_links/description |
| Titles should not contain leading or trailing whitespace | /properties/_links/title |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/categorieKerngebied/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gidssoort/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/guid/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/id/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/id/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/id/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/mutatieDatum/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/objectnaam/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/objectnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/objectnummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/objectnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/objecttype/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/omtrekGis/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/omtrekGis/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/omtrekGis/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/oppervlakteGis/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/oppervlakteGis/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/oppervlakteGis/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/stadsdeelNaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/waterschapNaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/wijkNaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/woonplaatsNaam/description |