| 0001: Use enum field instead of nullable boolean |
Proposed |
2025-07-01 |
| 0002: Explicitly set if application payloads can contain additional properties |
Proposed |
2025-12-16 |
| 0003: Require documents to be submitted as files within the application record |
Proposed |
2025-12-18 |
| 0004: Name the application record dataset `planning-application` |
Proposed |
2025-12-18 |
| 0005: Name the decision notice dataset `decision-notice` |
Proposed |
2026-01-09 |
| 0006: Single document reference pattern for modules |
Proposed |
2026-01-14 |
| 0007: Require WGS84 for exchanged location coordinates |
Proposed |
2025-10-08 |
| 0008: Record date precision explicitly using a separate `date_precision` attribute |
Proposed |
2026-01-26 |
| 0009: Use a `parent` field for simple hierarchical codelists |
Proposed |
2026-03-10 |
| 0010: Use separate usage tables when codelists need context-specific subsets |
Proposed |
2026-03-19 |
| 0011: Use explicit schedule days for hours of operation |
Proposed |
2026-03-24 |
| 0012: Use a controlled list for combined application types |
Proposed |
2026-04-14 |
| 0013: When to use explicit not applicable fields |
Proposed |
2026-04-22 |
| 0014: Link named individuals by reference, not name matching |
Proposed |
2026-05-19 |
| 0015: Model declarations as confirmation facts, not digital signatures |
Proposed |
2026-05-19 |
| 0016: Keep form generation details separate from structured data |
Proposed |
2026-05-21 |
| 0017: Do not duplicate dates across decision-stage datasets |
Proposed |
2026-05-28 |
| 0018: Reference authoritative application artefacts without prescribing storage |
Proposed |
2026-06-04 |