Requirement

Guidance

The end-point marks the target of the trace. In all cases this is the AIRM. An information definition always maps to the AIRM. The end-point must obviously be ‘resolvable’ and this is done by enforcing the use of a unique identifier.

The AIRM makes use of the URN format. This is in line with the specification's requirement on identifiers.

Verification Support

Correctness

Check that:

[  ] Each trace in the information definition uses the unique identifier provided by the AIRM concept at its end-point.

Examples

The example below shows how the AIRM's unique identifier is embedded into a trace in XML Schema format.

<xs:annotation>
  <xs:documentation>
    <semanticCorrespondence>
      <mapping>
        <trace type="informationConceptTrace">urn:aero:airm:1.0.0:LogicalModel:Subjects:BaseInfrastructure:AerodromeInfrastructure:Aerodrome</trace>
      </mapping>
    </semanticCorrespondence>
  </xs:documentation>
</xs:annotation>