Date: Thu, 28 Mar 2024 09:08:26 +0000 (UTC) Message-ID: <756488589.206.1711616906755@pmtpub41.ops.cfmu.eurocontrol.be> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_205_1396605488.1711616906754" ------=_Part_205_1396605488.1711616906754 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
IETF RFC 3986 is available at https://= tools.ietf.org/html/rfc3986. It details the generic syntax for uniform = resource identifiers (URIs). The standard gives the following examples of U= RI schemes:
The ATM Information Reference Model uses the urn sch= eme.
The specification accepts that not all information d= efinitions adopt the IETF RFC 3986 approach. Therefore it permits other way= s to ensure a concept is uniquely identifiable. This means the requirement = can be satisfied by:
The specification does not put any requirements on w= ho generates the identifier or how it is generated. However, it is assumed = that they are generated by the organisation responsible for creating the in= formation definition.
Check that either:
[ ] Each concept has a unique identifier in accordance with IETF RFC 3986= .
or
[ ] Each concept can be uniquely identified through some other mechanism = e.g. by being uniquely named in a namespace.
The following examples show how to add explicit identifiers in XML Schem= a when needed.
The example below shows how a simple identifier can be embedded into an = XML schema. It makes use of the "id" attribute within the XML schema defini= tion language. It is "simple" in the sense that the identifier has no intri= nsic semantics of its own.
A complete example is available at: complete example.
<xs:el= ement name=3D"tobt" id=3D"donlon003">=20
The example below shows a more advanced identifier. This takes the form = of a URN that links to a given resource.
<xs:el= ement name=3D"tobt" id=3D"http://swim.donlon-airport.com/property/tobt">==20