The table below lists the themes to be covered when detailing the service definitions.
| Name | Description | Notes | Priority |
|---|---|---|---|
General service information | Name and abstract. | The name should be agreed on soon. The abstract can be written at the end. | 1 |
Service definition provider and contact details | Defaults to EUROCONTROL for the moment. | ||
Service characteristics | Geographical considerations and service categories | Service category will give an overall feel for the service. Make reference to EU Regs, ICAO where needed. | 1 |
High level description of the service offer | Operational context, functions, etc. | This needs to be done with the all of the services and use cases in mind. | 1 |
Limitations and constraints on using the service | Access and use, security mechanisms | ||
Quality aspects | ...of service, data. | ||
Behaviour of the service | How the service works | ||
Service implementation and structural details | How the service is realised | Discuss any required implementations from SWIM-TI soon. | |
Information aspects of the service | Information definition, filtering | Discuss use of AIXM soon. | |
| Resources | Models, etc. that help those using the service definition |
The themes can be tied to the requirements for service definitions:
