Out-of-scope and no semantic correspondence established declarations
A semantic correspondence declaring that a concept in an information definition is out-of-scope of the AIRM or that no semantic correspondence has been established shall provide a rationale.
An out-of-scope declaration is not verifiable without information about the rationale.
|Note: The following were used in SESAR related work as rationales for an out-of-scope declaration:|
- container (e.g. XML complexTypes);
- messaging (e.g. Aeronautical Fixed Telecommunication Network address);
- network (e.g. datalink protocol version, IP address);
- system (e.g. technical identifiers, availability flags);
- non-atm (e.g. human resource related information);
- local (e.g. data only making sense for on specific service instance); and
- other (not covered by the other categories).
Note: The declaration that no semantic correspondence has been established allows the authors of an information definition to perform the mapping exercise in an iterative manner. However, it is important that a rationale is made available to make clear why no semantic correspondence has been established.
Level of Implementation
A rationale has to be given in order to justify the use of the out-of-scope declaration and the declaration that no semantic correspondence has been established. This requirement ensures that the use of these options is verifiable.