Date: Fri, 29 Mar 2024 10:37:55 +0000 (UTC) Message-ID: <1548949372.290.1711708675624@pmtpub41.ops.cfmu.eurocontrol.be> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_289_228537469.1711708675624" ------=_Part_289_228537469.1711708675624 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The abstract to the SWIM Information Definition Specification states:
The following diagram illustrates the role of the SWIM Information Definition Specification. In it:
This identifies some key topics to be discussed:
exchanged information - information exchange
The term information exchange is a well-established term in the ATM =
domain. For the good understanding of the term it should be clear tha=
t this does not necessarily imply that an "exchange" takes place in the nor=
mal meaning of the word "exchange".
Information exchange is=
used in ATM to refer to processes that allow information generated at one =
location to be made available at one or more other locations. T=
he meaning is very broad, and makes no restrictions on the mechanism used t=
o enable sharing of information, or how many parties might be involved in t=
hat. It does not imply that if information is transferred from A to B=
then some "reply" back from B to A is always required. In fact, it c=
overs multiple ways of sharing information regardless whether between two o=
r more parties. This can be confusing because the word "exchange" in normal=
usage means "an act of giving one thing and receiving another (especially =
of the same kind) in return". This suggests that "information exchang=
e" would imply a transfer of information from one party to another, followe=
d by some other information being sent in return. But that is o=
nly one possible style of "information exchange" in the way the term is use=
d in ATM.
Semantic interoperability is the ability of computer system= s and organisations to exchange data with unambiguous, shared meaning.
The ATM Information Reference Model (AIRM) is a key part in facilitat= ing semantic interoperability within the context of the modern= ised European ATM network. It is the common reference language for avi= ation information and data. The AIRM contains the civil and military i= nformation constructs relevant to ATM in support of information exchan= ge via SWIM. The AIRM represents the ATM related aviation information const= ructs in a harmonised way.
The specification contains semantic correspondence requirements t= o ensure that information definitions conform to the semantics of the AIRM.=
It is worth noting that the specification does not put requirements =
on the format or notation (such as Unified Modeling Language (UML) or Extensible Markup Language (XML=
) Schema) used in information definitions. Nor does it put require=
ments on the AIRM.
Information definitions, the formal descriptions of exchanged informatio= n, are produced or reused by operational stakeholders. They act as the mean= s whereby the exchanged information is clearly defined. This promotes a com= mon understanding of the definition of the information between stakeholders= . Examples of information definitions are:
In addition to the semantic correspondence requirements, the specificati= on contains general requirements for information definitions. These= include, for example, the need for an edition and a reference date. These = requirements cover the ability to discover and decide on the use of a parti= cular information definition. They also cover the concepts contained in an = information definition - the concepts define the exchanged information.
The requirements contained in the specification are visualised below. Th= e figure includes the requirement number (e.g. SWIM-INFO-001). It = groups the requirements and gives a broad summary of the content of the req= uirement.
Some requirements (SWIM-INFO-001 and SWIM-INFO-002) ap= ply to the information definition as a whole and are added at the top of th= e diagram.
SWIM-INFO-003 to SWIM-INFO-006 and SWIM-INFO-012= em> are applied once and define the content of the information definition. = For example, SWIM-INFO-003 requires that a title, edition and refe= rence date be given in order to identify the information definition.
The remaining requirements apply to all of the concepts in the informati= on definition. These include the basic needs such as to name and define the= concept. There is also a need to give a semantic correspondence statement = for each concept. The semantic correspondence requirements (SWIM-INFO-0= 13 to SWIM-INFO-019) explain how the concepts in an informati= on definition are "related" to the AIRM concepts.
The requirements for information definitions are to be seen in the conte=
xt of Initial System Wide Information Management (iSWIM) in Europe.
=
Initial System Wide Information Management (iSWIM) is o=
utlined in the European Union=E2=80=99s Pilot Common Project Regulation =
(PCP). Among other things, the PCP requires that service implementations in=
support of the listed information exchanges =E2=80=9Cbe compliant with=
the applicable version of the ATM Information Reference Model (AIRM), the =
AIRM Foundation Material and the Information Service Reference Model (ISRM)=
Foundation Material=E2=80=9D
The specification can be applied in different contexts. It can be used t= o improve information exchanges between any organisation. Information defin= itions that follow the specification will have an increased chance of being= interoperable.