...
Panel |
---|
borderColor | lightgrey |
---|
bgColor | whitesmoke |
---|
borderStyle | dashed |
---|
|
Extract of requirementRequirementTitle | Out-of-scope and no semantic correspondence established declarations | Identifier | SWIM-INFO-015 | Requirement | 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. | Rationale | An out-of-scope declaration is not verifiable without information about the rationale. | Verification | Completeness | Examples/Notes | 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 | Mandatory |
|
Explanations
Notes - always need a mapping. AIRM gives urns for these if needed.
...
- information definition issue. This can be used when a problem has been identified in the information definition. The problem cannot be resolved during the mapping exercise and it is not clear what the outcome of the resolution will be.
- incomplete mapping. This can be used when the mapping exercise has not been completed. In effect, it highlights areas where the mapping exercise is still to be performed.
- other. Any other text can be added when the rationale is not covered by the other categories.
Verification Support
Completeness: Check that the rationale is present.
Examples/Best Practice
Code Block |
---|
language | xml |
---|
title | Example of SWIM-INFO-015 |
---|
linenumbers | true |
---|
|
<gmd:title> guess what </gmd:title> |
...