| 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/aantalWerkdagen/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/aantalWerkdagen/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/aantalWerkdagen/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/aantalWerkdagenAdam/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/aantalWerkdagenAdam/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/aantalWerkdagenAdam/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/dagInTertaalNummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/dagInTertaalNummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/dagInTertaalNummer/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/dagVanJaarNummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/dagVanJaarNummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/dagVanJaarNummer/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/dagVanKwartaalNummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/dagVanKwartaalNummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/dagVanKwartaalNummer/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/dagVanMaandNummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/dagVanMaandNummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/dagVanMaandNummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/dagVanWeekKnaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/dagVanWeekNaam/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/dagVanWeekNummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/dagVanWeekNummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/dagVanWeekNummer/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/dagenInJaar/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/dagenInJaar/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/dagenInJaar/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/dagenInKwartaal/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/dagenInKwartaal/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/dagenInKwartaal/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/dagenInMaand/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/dagenInMaand/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/dagenInMaand/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/dagenInTertaal/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/dagenInTertaal/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/datum/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/feestdagAdamIndicatie/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/feestdagAdamIndicatie/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/feestdagAdamIndicatie/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/feestdagIndicatie/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/feestdagIndicatie/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/feestdagIndicatie/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/isoWeekEindeDatum/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/isoWeekNummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/isoWeekNummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/isoWeekNummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/isoWeekStartDatum/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarEindeDatum/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarIsoWeekNummer/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarKnaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarNaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarStartDatum/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarTertaal/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/jaarWaarde/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarWaarde/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/jaarWaarde/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarkwartaal/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarmaand/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/jaarnaamKort/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/juliaanseDatum/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/juliaanseDatum/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/juliaanseDatum/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/kwartaalEindeDatum/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/kwartaalNaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/kwartaalStartDatum/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/kwartaalWaarde/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/kwartaalWaarde/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/kwartaalWaarde/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/laatsteDagVanJaarIndicatie/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/laatsteDagVanJaarIndicatie/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/laatsteDagVanJaarIndicatie/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/laatsteDagVanKwartaalIndicatie/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/laatsteDagVanKwartaalIndicatie/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/laatsteDagVanKwartaalIndicatie/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/laatsteDagVanMaandIndicatie/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/laatsteDagVanMaandIndicatie/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/laatsteDagVanMaandIndicatie/format |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/laatsteDagVanTertaalIndicatie/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/laatsteDagVanTertaalIndicatie/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/laatsteDagVanTertaalIndicatie/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/maandEindeDatum/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/maandKnaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/maandNaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/maandStartDatum/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/maandWaarde/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/maandWaarde/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/maandWaarde/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/niveaucode/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/schoolvakantieNlMiddenIndicatie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/schoolvakantieNlNoordIndicatie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/schoolvakantieNlZuidIndicatie/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/seizoen/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/tertaal/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/tertaal/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/tertaal/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/vorigeDagVanWeekKnaam/description |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/vorigeDagVanWeekNaam/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/weekInJaarNummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/weekInJaarNummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/weekInJaarNummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/weekInMaandEindeDatum/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/weekInMaandNummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/weekInMaandNummer/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/weekInMaandNummer/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/weekInMaandStartDatum/description |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/weekendIndicatie/format |
| Descriptions should not end with a period to give user interfaces flexibility in presenting the text | /properties/weekendIndicatie/description |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/weekendIndicatie/format |