...
| Expand |
|---|
|
| Panel |
|---|
| borderColor | lightgrey |
|---|
| bgColor | whitesmoke |
|---|
| borderStyle | dashed |
|---|
| Title | Forms of semantic correspondence | Identifier | SWIM-INFO-014 | Requirement | A semantic correspondence shall be:- a mapping from a concept in the information definition to a concept or concepts in the AIRM; or
- a declaration that the concept in the information definition is out-of-scope of the AIRM; or
- a reference to a change request for the AIRM that intends to change the AIRM to cover the concept from the information definition; or
- a declaration that no semantic correspondence has been established for the concept.
| Rationale | This requirement ensures that the expression of semantic correspondence becomes verifiable. It allows gaps with the AIRM to be identified so that they can be managed. A reference to the change request is designed to allow an information definition to cause an evolution of the AIRM. | Verification | Completeness | Examples/Notes | Note: There are several methods for documenting a semantic correspondence. For example, this requirement can be satisfied in a tabular format using the unique identifier of the concept in the information definition and the unique identifier of the related AIRM concept. Semantic correspondences could also be represented using: - UML trace relationships; or
- metadata fields attached to the concept in the information definition that contains the unique identifier of the AIRM concept.
Example: The following is an example of a semantic correspondence written in tabbed-outline format. + concept: …name: Airspace …semantic correspondence: ……mapping: ………trace: urn:x-ses:sesarju:airm:v410:ConsolidatedLogicalDataModel:SubjectFields:AirspaceInfrastructure:Airspace:Airspace
Note: This requirement ensures that the documentation of semantic correspondence is complete. It is important to ensure that there are no gaps in the documentation as gaps are difficult to interpret. | Level of Implementation | Mandatory |
|
|
Guidance
The specification gives four types of semantic correspondence. The first of these is the best outcome of the semantic correspondence analysis:
...
| Tip |
|---|
|
The option to use out-of-scope or change request may not be obvious. In this case, the best practice is to use the change request option. This will allow the AIRM change control board to consider the input and whether the AIRM's scope needs to be changed. |
Verification Support
Completeness
...
This example shows how to embed a mapping into an XML schema document using the annotation element. It shows how the trace (or multiple traces) should use the AIRM's unique identifier as required by SWIM-INFO-019. Further mapping examples are available on the Understanding and recording mappings page.
| Code Block |
|---|
| language | xml |
|---|
| title | Example of SWIM-INFO-014 |
|---|
| linenumbers | true |
|---|
|
<xs:annotation>
<xs:documentation>
<semanticCorrespondence>
<mapping>
<trace type="informationConceptTrace">-AIRM unique identifier-</trace>
...
<trace> <trace type="narrowingTrace">-AIRM unique identifier-</trace>
</mapping>
</semanticCorrespondence>
</xs:documentation>
</xs:annotation>
|
...
| Code Block |
|---|
| language | xml |
|---|
| title | Example of SWIM-INFO-014 |
|---|
| linenumbers | true |
|---|
|
<xs:annotation>
<xs:documentation>
<semanticCorrespondence>
<noSemanticCorrespondence rationale="incomplete mapping"/>
</semanticCorrespondence>
</xs:documentation>
</xs:annotation> |
This example shows how to embed a mapping into an XML schema document using the annotation element. It builds on the other examples and includes the <xs:appinfo> element that specifies information to be used by the application. This is an optional element and can be used when the intention is to use an application to further process the semantic correspondences.
| Code Block |
|---|
| language | xml |
|---|
| title | Example of SWIM-INFO-014 |
|---|
| linenumbers | true |
|---|
|
<xs:annotation>
<xs:appinfo>Semantic Correspondence</xs:appinfo>
<xs:documentation>
<semanticCorrespondence>
<mapping>
<trace type="informationConceptTrace">-AIRM unique identifier-</trace>
...
<trace type="narrowingTrace">-AIRM unique identifier-</trace>
</mapping>
</semanticCorrespondence>
</xs:documentation>
</xs:annotation>
|