| 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 |
| Set `properties` to identifier names that can be easily mapped to programming languages (matching [A-Za-z_][A-Za-z0-9_]*) | /properties/wet-en-regelgevingen |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/wet-en-regelgevingen/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/wet-en-regelgevingen/items/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/wet-en-regelgevingen/items/properties/landen/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/wet-en-regelgevingen/items/properties/link/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/wet-en-regelgevingen/items/properties/tekst/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/wet-en-regelgevingen/items/properties/tekst/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/wet-en-regelgevingen/items/properties/titel/description |