planning application data
Links a planning application to authoritative structured application data as submitted and, where applicable, as validated.
Fields
- Reference
-
The reference for the planning application data record
- Reference
reference- Cardinality
1- Datatype
string- Requirement level
MUST
No needs satisfied by this field.
- Planning application
-
The reference for the related planning application
- Reference
planning-application- Cardinality
1- Datatype
string- Related dataset
- Planning application dataset
- Requirement level
MUST
Needs this field satisfies
Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.
- This field and field
submitted-data-urisatisfy need dd-need-097. - This field and field
validated-data-uriand fieldpermission-process-event(dataset planning-permission-timeline) satisfy need dd-need-098.
- Submitted data URI
-
The URI identifying the authoritative structured application data as first received by the planning authority
- Reference
submitted-data-uri- Cardinality
1- Datatype
string- Requirement level
Not specified
Needs this field satisfies
Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.
- This field and field
planning-applicationsatisfy need dd-need-097.
- Validated data URI
-
The URI identifying the authoritative structured application data accepted through planning validation
- Reference
validated-data-uri- Cardinality
1- Datatype
string- Requirement level
Not specified
Needs this field satisfies
Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.
- This field and field
planning-applicationand fieldpermission-process-event(dataset planning-permission-timeline) satisfy need dd-need-098.
Examples
Submitted and validated application data
This example distinguishes the structured data first received by the planning authority from the data subsequently accepted through validation. The URIs identify authoritative data artefacts and do not imply that they are publicly accessible.
Example formats
Table
| Field | Value |
|---|---|
reference |
application-data-2026-0123 |
planning-application |
2026/0123/FUL |
submitted-data-uri |
urn:planning-application-data:2026-0123-ful:submitted |
validated-data-uri |
urn:planning-application-data:2026-0123-ful:validated |
JSON
{
"reference": "application-data-2026-0123",
"planning-application": "2026/0123/FUL",
"submitted-data-uri": "urn:planning-application-data:2026-0123-ful:submitted",
"validated-data-uri": "urn:planning-application-data:2026-0123-ful:validated"
}
Needs satisfied by this dataset
Datasets should only be included in the specification if they satisfy user needs.
No recorded links yet.