Data model
The planning application data standard is made from connected parts that describe applications, reusable data groups and individual fields.
Model elements
The data model contains these elements:
How the parts fit together
At a high level the standard works like this:
- an application definition says what is needed for a given application type
- every application includes submission details for submission-level information
- an application uses modules
- a module groups related fields
- a component defines a reusable group of fields used inside modules or other field definitions
- a field defines an individual data item, including its datatype
- if a field is controlled, the field definition points to a codelist
- the codelist defines the allowed values
- co-constraints describe conditional rules, such as when a field applies or becomes required
- datasets describe record data captured and shared as a planning application moves through the planning permission process
The simple path through the model is:
application -> module -> component / field -> datatype / codelist
Datasets are related to this model, but they are not part of an application definition. An application definition describes the data needed for a specific application type. Datasets describe records created and reused through the wider process, such as applications, sites, documents, decisions, conditions, section 106 agreements and timeline events.
Design decisions
Design decisions record why parts of the standard are modelled in a particular way.