| 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/gebiedenBouwblokCode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenBouwblokIdentificatie/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/gebiedenBouwblokVolgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenBouwblokVolgnummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/gebiedenBouwblokVolgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenBuurtCode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenBuurtIdentificatie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenBuurtNaam/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/gebiedenBuurtVolgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenBuurtVolgnummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/gebiedenBuurtVolgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenGgwgebiedCode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenGgwgebiedIdentificatie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenGgwgebiedNaam/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/gebiedenGgwgebiedVolgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenGgwgebiedVolgnummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/gebiedenGgwgebiedVolgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenStadsdeelCode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenStadsdeelIdentificatie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenStadsdeelNaam/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/gebiedenStadsdeelVolgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenStadsdeelVolgnummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/gebiedenStadsdeelVolgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenWijkCode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenWijkIdentificatie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenWijkNaam/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/gebiedenWijkVolgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedenWijkVolgnummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/gebiedenWijkVolgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/identificatie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/pandBeginGeldigheid/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/pandEindGeldigheid/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/volgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/volgnummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/volgnummer/format |