| 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 |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/aanleghoogte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/aanleghoogte/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/aanleghoogte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/actueelKwaliteitsniveau/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/beginGarantieperiode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/beheerafspraak/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/beheerder/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/beheerderGedetailleerd/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/beheergebied/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/breedte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/breedte/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/breedte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/buurt/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/conditiescore/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/datumInwinning/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/eigenaar/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/eigenaarGedetailleerd/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/eindeGarantieperiode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/fundering/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebiedstype/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gebruiksfunctie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gemeente/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gewenstKwaliteitsniveau/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/hoogte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/hoogte/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/hoogte/format |
| 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/idUitOudeBeheerindeling/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/identificatie/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/jaarLaatsteConservering/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarLaatsteConservering/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/jaarLaatsteConservering/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/jaarUitgevoerdOnderhoud/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarUitgevoerdOnderhoud/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/jaarUitgevoerdOnderhoud/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/jaarVanAanleg/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarVanAanleg/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/jaarVanAanleg/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/kleur/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/lengte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/lengte/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/lengte/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/lengteGis/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/lengteGis/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/leverancier/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/ligging/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/locatieaanduiding/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/materiaal/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/model/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/objectnaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/onderhoudsplichtige/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/openbareRuimte/description |
| 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 |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/relatieveHoogteligging/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/relatieveHoogteligging/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/relatieveHoogteligging/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/revisie/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/revisie/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/revisie/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/stadsdeelOfKern/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/type/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/typeGedetailleerd/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/waterschap/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/wijk/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/woonplaats/description |