| 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/actueelKwaliteitsniveau/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/baggerplichtige/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/bemonsteringsjaar/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/bemonsteringsjaar/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/bemonsteringsjaar/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/bereikbaarheid/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/bereikbaarheidGedetailleerd/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/bergendVermogen/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/bergendVermogen/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/bergendVermogen/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/beschermdeFloraEnFauna/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/bevaarbaarheidsklasse/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 |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/breedteBodem/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/breedteBodem/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/breedteBodem/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/breedteInsteek/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/breedteInsteek/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/breedteInsteek/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/breedteklasseWatergang/description |
| 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/controlefrequentie/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/doelsoort/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/ecologischBeheer/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/floraEnFaunaUitzondering/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/floraEnFaunawetAfwijking/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/folie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/frequentieBaggeren/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/frequentieKroosvissen/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/frequentieVeegboot/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/gedeeldBeheer/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gedeeldEigenaarschap/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gemeente/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/gemetenBodempeil/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/gemetenBodempeil/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/gemetenBodempeil/format |
| 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/hoeveelheid/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/hoeveelheid/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/hoeveelheid/format |
| 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/infiltrerendOppervlak/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/infiltrerendOppervlak/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/infiltrerendOppervlak/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/infiltrerendVermogen/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/infiltrerendVermogen/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/infiltrerendVermogen/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/ingrijpdiepte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/ingrijpdiepte/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/ingrijpdiepte/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/insteekbreedte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/insteekbreedte/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/insteekbreedte/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/kerngebiedId/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/lengteDroogTalud/description |
| 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/ligging/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/maaifrequentie/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/maximaalBodempeil/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/maximaalBodempeil/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/maximaalBodempeil/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/maximaleDiepgang/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/maximaleDiepgang/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/maximaleDiepgang/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/maximumStreefpeil/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/maximumStreefpeil/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/minimumStreefpeil/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/minimumStreefpeil/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/minimumStreefpeil/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/nautischeDiepte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/nautischeDiepte/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/nautischeDiepte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/nietGeheelSloten/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/oeververdediging/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/onderhoudsplichtige/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/ontwerpBodempeil/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/ontwerpBodempeil/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/ontwerpBodempeil/format |
| 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/oppervlakteInsteek/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/oppervlakteInsteek/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/oppervlakteInsteek/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/perceelEcologischeMonitoring/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/porositeit/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/porositeit/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/porositeit/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/schouwen/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/schouwwijze/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/slagwaterpeil/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/slagwaterpeil/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/slagwaterpeil/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/slibaanwas/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/slibaanwas/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/slibaanwas/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/stadsdeelOfKern/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/streefdiepte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/streefdiepte/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/streefdiepte/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/streefpeil/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/streefpeil/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/streefpeil/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/taludsteilte/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/teSlotenBreedte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/teSlotenBreedte/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/teSlotenBreedte/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/teSlotenLengte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/teSlotenLengte/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/teSlotenLengte/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/teSlotenOppervlakte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/teSlotenOppervlakte/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/teSlotenOppervlakte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/tweedeBeheerder/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/tweedeEigenaar/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/typeBewerking/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/typeExtraGedetailleerd/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/typeWaterbodem/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/typeWatergang/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/typeWaterplanten/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/uitstroomniveau/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/uitstroomniveau/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/uitstroomniveau/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/vaarwater/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/vaarwegtraject/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/verbindingszoneId/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/vorm/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/waterbeheergebied/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/watergangDiepte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/watergangDiepte/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/watergangDiepte/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/waternaam/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/waterpeilWinter/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/waterpeilWinter/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/waterpeilWinter/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/waterpeilZomer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/waterpeilZomer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/waterpeilZomer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/waterplanten/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/werkbreedte/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 |