Date: Fri, 29 Mar 2024 08:20:03 +0000 (UTC) Message-ID: <1777319001.276.1711700403627@pmtpub41.ops.cfmu.eurocontrol.be> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_275_29760327.1711700403626" ------=_Part_275_29760327.1711700403626 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The end-point marks the target of the trace. In all cases this is the AI= RM. An information definition always maps to the AIRM. The end-point must o= bviously be =E2=80=98resolvable=E2=80=99 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 specifica= tion's requirement on identifiers.
Check that:
[ ] Each trace in the information definition uses the unique identifier p= rovided by the AIRM concept at its end-point.
The example below shows how the AIRM's unique identifier is embedded int= o a trace in XML Schema format.
<xs:an= notation> <xs:documentation> <semanticCorrespondence> <mapping> <trace type=3D"informationConceptT= race">urn:aero:airm:1.0.0:LogicalModel:Subjects:BaseInfrastructure:Aerod= romeInfrastructure:Aerodrome</trace> </mapping> </semanticCorrespondence> </xs:documentation> </xs:annotation>=20