| 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 | /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/beginGeldigheid/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/domeincode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/eindGeldigheid/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedscode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedsnaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedsomschrijving/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebruiksdoel/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/indicatieZichtbaar/description |