| 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/bagWoonplaatsId/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/bagWoonplaatsNaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gbdStadsdeelId/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gbdStadsdeelNaam/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/gbdStadsdeelVolgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gbdStadsdeelVolgnummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/gbdStadsdeelVolgnummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/id/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indAfdeling/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indBeginPeriode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indBron/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indDatatype/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indDefinitie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indDirectie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indDoelenboom/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indDoelenboomActiviteit/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indDomeinNaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indEenheid/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indEindPeriode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indFrequentieAfleiding/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indGrootheid/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indNaam/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/indNoemer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indNoemer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/indNoemer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indNorm/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indNormBron/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indNormDefinitie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indPeildatumAfleiding/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/indTeller/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indTeller/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/indTeller/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/indTempDag/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indTempDag/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/indTempDag/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/indTempDecennium/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indTempDecennium/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/indTempDecennium/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/indTempHalfjaar/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indTempHalfjaar/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/indTempHalfjaar/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/indTempJaar/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indTempJaar/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/indTempJaar/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/indTempKwartaal/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indTempKwartaal/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/indTempKwartaal/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/indTempLustrum/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indTempLustrum/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/indTempLustrum/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/indTempMaand/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indTempMaand/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/indTempMaand/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/indTempUur/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indTempUur/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/indTempUur/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/indTempWeek/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indTempWeek/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/indTempWeek/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indVariableType/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/indWaarde/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/indWaarde/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/indWaarde/format |