<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>A Proof-of-Concept Implementation of a Semantic Container Management System for Air Tra c Management</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Eduard Gringinger</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Christoph Fabianek</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Christoph G. S</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Johann Stobich</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Bernd Neumayr</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Frequentis AG</institution>
          ,
          <addr-line>Vienna</addr-line>
          ,
          <country country="AT">Austria</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Johannes Kepler University Linz</institution>
          ,
          <addr-line>Linz</addr-line>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>As part of the BEST project { a collaborative research effort under the Single European Sky ATM Research (SESAR) initiative { we developed the concept of the semantic container, aiming to facilitate information sharing and reuse in air tra c management (ATM) and air tra c operations, enabled by semantic technologies. In this context, a semantic container is a package of ATM information with an ontology-based description of the contents. The description serves for the management of semantic containers: The formal de nition of the contents of a semantic container allows to automatically match existing semantic containers with an application's information need. This demonstration showcases a proof-of-concept implementation of a system for the distributed and versioned storage of semantic containers.</p>
      </abstract>
      <kwd-group>
        <kwd>Semantic Technologies Distributed Databases Control System Wide Information Management</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Air tra c management (ATM) aims to ensure safe and e cient ight operations
through the timely provisioning of relevant information to stakeholders such
as pilots, air tra c controllers and others. Among the most common types of
information exchanged in ATM, are messages such as Digital Notices to Airmen
(DNOTAMs), which notify stakeholders of important events like runway closures
and malfunctioning airport equipment, and Meteorological Terminal Air Reports
(METARs), which report current weather conditions at airports. Other types of
messages report on weather in regions of airspace, weather forecasts at airports
or in regions of airspace, and signi cant meteorological events.</p>
      <p>Di erent tasks in ATM and air tra c operations have di erent information
needs. For example, planning of air tra c ow requires di erent types of
information than piloting a ight. Furthermore, piloting a ight from Vienna (VIE)
to Frankfurt (FRA) requires di erent information content-wise than a ight from
Frankfurt (FRA) to Rio de Janeiro (GIG). While pilot brie ngs for both routes
contain, among other message types, DNOTAMs and METARs, the brie ng for
the VIE-FRA ight contains DNOTAMs and METARs relevant for VIE and
FRA airports as well as messages relevant for en-route segments of the ight;
messages for GIG airport will not be part of the VIE-FRA brie ng.</p>
      <p>
        The System Wide Information Management (SWIM) concept, which is
currently being developed as part of the Single European Sky ATM Research
(SESAR) initiative, stipulates a service-oriented architecture and standard
exchange models for sharing ATM information (see [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] for further information).
Hence, information services, which are indexed in the SWIM registry, provide
stakeholders with relevant ATM information in a standard format. In order to
facilitate the packaging and sharing of ATM information inside the SWIM
environment, the BEST project3 developed the semantic container approach. A
semantic container is a package of data items such as DNOTAMs or METARs
with an ontology-based, semantic description of the contents which allows to
match an application's information need to existing semantic containers. SWIM
information services will then receive semantic containers as input and return
semantic containers as output.
      </p>
      <p>
        In this demonstration4, we present a proof-of-concept implementation of a
semantic container management system (SCMS) for the distributed, versioned
storage of semantic containers in ATM. We refer to Deliverables 3.1 [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] and 3.2 [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]
of the BEST project for further information on use case scenarios and the
implementation, respectively. The remainder of this paper is organized as follows.
In Sect. 2, we sketch the semantic container approach. In Sect. 3, we present an
overview of the SCMS and sketch integration with the SWIM concept.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Semantic Containers</title>
      <p>
        A semantic container has a semantic description, which de nes the membership
condition for data items [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]: Every data item, e.g., DNOTAM or METAR, that
ful lls the membership condition belongs to the container. Such a membership
condition has multiple facets { dimensions of content description. With each
facet, a membership condition associates a concept from an ontology. For
example, a container's membership condition may associate a concept LOVV with
a spatial facet to indicate that the container incorporates all DNOTAMs
relevant for a particular region. Using subsumption reasoning, an information need
expressed as an ontology class can be matched to existing semantic containers.
For example, a membership condition indicating relevance for the LOVV-TS1
route segment is subsumed by a membership condition indicating relevance for
the LOVV region as a whole, which contains that speci c route segment.
3 \Achieving the bene ts of SWIM by making smart use of semantic technologies".
      </p>
      <p>For more information, visit the project website: https://project-best.eu/
4 A demonstration video of the implementation is available on the website of the BEST
project: http://project-best.eu/video/best_180604_final.mp4</p>
      <p>Client Browser
Frontend</p>
      <sec id="sec-2-1">
        <title>Semantic Container Management System 3</title>
        <p>REST
REST</p>
        <p>Node 1
Backend</p>
        <p>...</p>
        <p>Node n
Backend
«XML DB»
Data Item Store
«RDF DB»
Local Registry
«RDF DB»
Global Registry
«XML DB»
Data Item Store
«RDF DB»
Local Registry</p>
        <p>
          In order to separate the semantics from the storage concerns, i.e.,
distribution and versioning, we distinguish between logical and physical semantic
containers [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. Each logical container can be allocated at multiple server nodes,
resulting in multiple physical containers { one for each server where the logical
container is allocated. Furthermore, a physical container maintains multiple data
sets to account for di erent versions of the physical container when updates
occur. When looking for a semantic container that matches a certain information
need, the logical containers are relevant.
3
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>System Overview and SWIM Integration</title>
      <p>Figure 1 illustrates the architecture of the distributed semantic container
management system (SCMS). For demonstration purposes, we provide a web
frontend that allows to create and allocate containers at multiple server nodes. The
frontend accesses via REST API multiple backend nodes at di erent locations,
e.g., in Vienna, Frankfurt or even on an aircraft. Each backend node maintains
an XML database for the storage of the actual data and an RDF database that
serves as a local registry of physical containers. The di erent backend nodes
share a global registry of logical containers, which may be (fully) replicated for
increased availability. Thus, the SCMS comprises both a knowledge base for
metadata and a database that contains the actual data items.</p>
      <p>Using the presented proof-of-concept prototype, we demonstrate potential
integration of semantic containers from the BEST project into the SWIM
network { a BEST-enabled SWIM. In this scenario, an adapted Frequentis SWIM
Registry provides not only information about SWIM services but also about
semantic containers. The SCMS is used to de ne and create containers that are
then visible in the SWIM registry. On an organizational level, the Frequentis</p>
      <sec id="sec-3-1">
        <title>Gringinger et al.</title>
        <p>SWIM Integration platform (MosaiX) is used to con gure the SWIM
information for the speci c SWIM applications. Finally, the information is accessed by
the SWIM applications. To show BEST integration on an application level, we
used an existing prototype { the Integrated Digital Brie ng { which was
developed in SESAR 1.</p>
        <p>In a BEST-enabled SWIM, semantic containers would facilitate reuse and
caching of information as well as redundant allocation of safety-critical
information, in addition to tracking changes of the relevant information over time.
Consider, for example, that there are several main routes of air tra c. For each
of these most frequent routes, a semantic container could package the static
information that does not change very often and many ights on that route
require. When collecting the relevant information for a speci c ight on such
a route, rather than starting from scratch, the application could start with the
already existing container. An application could then customize the container by
creating a new container, based on the existing container, that adds additional
information relevant for the speci c ight. Redundant allocation of semantic
containers is important for safety reasons. Important information could be stored
in multiple locations, including the aircraft. Tracking changes in the actual data
set of a physical container over time is important to ensure auditability in case of
accidents. That way, the version of a physical container in a particular location
at a particular point in time can be reconstructed.</p>
        <p>Acknowledgments. This project has received funding from the SESAR Joint
Undertaking under grant agreement No 699298 under the European Union's
Horizon 2020 research and innovation program. The views expressed in this
paper are those of the authors.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. EUROCONTROL:
          <article-title>System wide information management (</article-title>
          <year>2018</year>
          ), https://www. eurocontrol.
          <source>int/swim (Accessed: 26 October</source>
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Gringinger</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fabianek</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schuetz</surname>
            ,
            <given-names>C.G.</given-names>
          </string-name>
          :
          <source>D3</source>
          .2 {
          <string-name>
            <surname>Prototype</surname>
            <given-names>SWIM-Enabled</given-names>
          </string-name>
          <string-name>
            <surname>Applications</surname>
          </string-name>
          .
          <source>Tech. rep., BEST Consortium</source>
          (
          <year>2018</year>
          ), http://project-best.eu/downloads/
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Gringinger</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Neumayr</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fabianek</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Savulov</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <source>D3.1 { Use Case Scenarios. Tech. rep., BEST Consortium</source>
          (
          <year>2018</year>
          ), http://project-best.eu/downloads/
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Gringinger</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schuetz</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Neumayr</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schre</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Wilson, S.:
          <article-title>Towards a valueadded information layer for SWIM: The semantic container approach</article-title>
          .
          <source>In: Proc. 18th ICNS Conference</source>
          . pp.
          <source>3G1{1{3G1{14</source>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Neumayr</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gringinger</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schuetz</surname>
            ,
            <given-names>C.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schre</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Wilson,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Vennesland</surname>
          </string-name>
          ,
          <string-name>
            <surname>A.</surname>
          </string-name>
          :
          <article-title>Semantic data containers for realizing the full potential of system wide information management</article-title>
          .
          <source>In: Proc. 36th DASC</source>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>