<!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>Turn Transportation Data into EU Compliance through Semantic Web-based Solutions</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Marco Comerio</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alessio Carenini</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mario Scrocca</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>- Milano</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Italy E-mail:</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>marco.comerio</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>alessio.carenini</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>mario.scrocca</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>irene.celino}@cefriel.com</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>The establishment of National Access Points (NAPs) to transportation data, as requested by the EU Regulation 2017/1926, represents a first step towards the realization of semantic interoperable travel information services. This paper presents challenges and opportunities introduced by the Regulation and its impact on transport stakeholders. The design and development of solutions based on Semantic Web technologies for supporting the establishment of NAPs represent research and business opportunities for the Semantic Web community.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>Semantic interoperability in the transportation sector is one of the European
Commission challenges: establishing an interoperability framework enables European
travel and transport industry players to make their business applications ‘interoperate’
and provides the travelers with a new seamless travel experience.</p>
      <p>
        The EU-report [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] on the provision of EU-wide multimodal travel information
services highlighted several barriers for the realization of comprehensive travel
information services in the EU, such as insufficient accessibility of travel and traffic data
and the lack of travel and traffic data interoperability. Key enablers to address these
barriers are (i) ensuring that users have access to the right scope of data and information
with the appropriate data sharing mechanism, and (ii) making travel and traffic data
interoperable with a common set of data exchange standards.
      </p>
      <p>
        A first step towards the realization of multimodal travel information services is the
establishment of National Access Points (NAPs) to multimodal transportation data as
defined in the recent Commission Delegated Regulation (EU) 2017/1926 [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. This
Regulation establishes the specifications necessary to ensure the accessibility, exchange,
and update of transportation data for the provision of multimodal information services
in the European Union. In the Regulation, each EU Member State is required to set up
a NAP accessible through APIs that allows access to static data (e.g., timetables,
network topology, list of services offered at a station / airport) and dynamic data (e.g.,
delays, cancellations) relating to different transportation modes (air, train, road vehicle,
bus, ferry, metro, tram, shuttle bus, car-sharing, car-pooling, bike-sharing, etc.). In
order to foster interoperability across Europe, the Regulation requires to provide data to
the NAP defined according to specific standard data formats such as NeTEx CEN / TS
166141 and SIRI CEN / TS 155312 and described using national application profiles
(e.g., DCAT-AP [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]). This EU Regulation 2017/1926 has been already adopted
(October 2017), and the first deadline for the provisioning of specific types of static
transportation data through NAPs is December 1st, 2019.
      </p>
      <p>
        Different transport stakeholders (i.e., transport authorities, transport operators, and
infrastructure managers) shall be able to continue to use their current systems at the
national level (often based on languages / formats different from NeTEx and SIRI), but
they will have to provide their data to the NAP after translation and conversion.
Unfortunately, as emerged from the EU EIP SA46 Annual NAP Report 2018 [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], very few
transport stakeholders are ready to provide their data and services in compliance with
the standards requested by the EU Regulation. To enable a data conversion process,
they rely on their in-house support (which may lack knowledge and skills related to the
Regulation) or turn to external technology providers that provide custom and often
expensive solutions.
      </p>
      <p>The challenges in the transportation sector, as well as the full compliance with the
EU Regulation, clearly call for Semantic Web-based solutions: in this paper, we
summarize the opportunities for semantic interoperability, and we give some hints on our
work to achieve such goal.</p>
      <p>This paper is organized as follows. Section 2 describes the impact of the Regulation
on transport stakeholders in terms of obligations, challenges, and benefits. Section 3
highlights research and business scenarios for the Semantic Web Community. Section
4 outlines ongoing and future work.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Requirements from and Impact on Transport Stakeholders</title>
      <p>The establishment of NAPs for multimodal transportation data impacts different
categories of transport stakeholders. In this section, we describe obligations, challenges,
and benefits for each category in order to provide a comprehensive analysis of the
impact and to facilitate the elicitation of requirements for Semantic Web-based solutions.
</p>
      <p>NAP Management Board: (i.e., the entity that is in charge of defining and
managing the NAP for a specific EU country)
o Obligation:
 Establish the NAP and defining its governance framework;
 Define a national metadata profile for multimodal transportation
datasets.
o Challenge:
 Regrouping the existing public and private access points in a single
point enabling access to available data that fall within the scope of the
Regulation, solving interoperability and compliance issues;
1 http://netex-cen.eu/
2 www.transmodel-cen.eu/standards/siri/


 Provide a metadata profile aligned with the one adopted by other EU</p>
      <p>NAPs in order to promote interoperability.</p>
      <p>Benefit:
 The NAP may take various forms such as a database, data warehouse,
data marketplace, repository, web portal, or similar depending on the
type of data. The NAP Management Board could define a business
model covering potential commercial aspects of multimodal data
transport sharing, brokerage, and trading.</p>
      <p>
        Transport authorities (i.e., any public authority responsible for the traffic
management or the planning, control or management of a given transport network or
modes of transport, or both, falling within its territorial competence) and
Transport operators (i.e., any public or private entity that is responsible for the
maintenance and management of the transport service, including transport
on-demand service):
o Obligation:
 Provide static data (e.g., timetables, network topology, fares) and
dynamic data (e.g., delays, cancellations) to the NAP compliant to the
requested data formats. The full list of data categories to made accessible
through the NAP is in Annex I of the EU Regulation [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ];
 Provide the metadata in order to allow users to discover and use the
datasets made accessible through the NAPs.
o Challenge:
 Turn available data into the requested data formats and, in case,
complement/enrich them with additional data sources.
o Benefit:
 Published datasets are interoperable and could be easily used by
Intelligent Transport System (ITS) applications. This, of course, potentially
augments the knowledge and the adoption of their transport offerings;
 In case of a NAP realized as data marketplace, transport authorities and
operators could receive revenues from the trading of their data.
      </p>
      <p>Transport infrastructure managers (i.e., any public or private body or
undertaking that is responsible in particular for establishing and maintaining transport
infrastructure, or part thereof):
o Obligation:
 Provide data (e.g., list of stop facilities access nodes including platform
information, help desks/information points, ticket booths, lifts/stairs,
entrances, and exit locations) and the related metadata to the NAP
compliant to the requested data formats.
o Challenge:
 Turn available data into the requested data formats and, in case,
complement/enrich them with additional data sources.</p>
      <p>o Benefit:


3

</p>
      <p>Published datasets are interoperable and could be easily integrated into
ITS applications for e.g., indoor navigation and location-based
experiences.</p>
      <p>Transport Standardization Bodies (i.e., European committees whose mission is
to foster the economy of the EU providing an efficient infrastructure for the
development, maintenance, and distribution of coherent sets of standards and
specifications):
o Obligation:
 Notify the NAP Management Board on the release of new versions of
the data formats/standards requested by the EU Regulation.
o Challenge:
 Support the definition of metadata and also the data conversion process
providing a reference vocabulary for the transportation sector.
o Benefit:</p>
      <p> Improve and enhance the adoption of developed standards.</p>
      <p>Intelligent Transport System (ITS) providers (i.e., any provider of advanced
application which aims to provide innovative services relating to different
transportation modes enabling users to be better informed and make safer, more
coordinated, and 'smarter' use of transport networks) and Mobility-as-a-Service
(MaaS) providers (i.e., any mobility provider that aggregates multiple mobility
service providers’ offerings and supplies them to users through a single digital
platform, providing real-time information and online payment options):
o Obligation:
 Follow terms and conditions established by the NAP Management</p>
      <p>Board concerning the NAP data usage.
o Challenge:
 Use datasets and APIs offered by NAPs to enhance their mobility
service offerings and to improve their businesses.
o Benefit:
 The NAP represents a structured solution to obtain interoperable
transport data to be elaborated for providing innovative mobility
services to users/travelers.</p>
    </sec>
    <sec id="sec-3">
      <title>The EU Regulation 2017/1926: challenges, opportunities for semantic interoperability</title>
      <p>From the analysis of the impact of the EU Regulation 2017/1926 to transport
stakeholders, three different opportunities for semantic interoperability emerge:
Definition of reference ontologies for the transportation sector: the first
opportunity for semantic interoperability comes from the need for reference ontologies
to unambiguously describe the operational aspects of the transportation domain.

</p>
      <p>
        Definition of metadata profiles for transportation datasets: as described in
Section 2, metadata descriptions of datasets according to a specific application profile
are required by the EU Regulation. The second opportunity for Semantic Web
technologies is to harmonize the metadata description of transportation datasets
through the definition of a semantically-enhanced metadata profile. This
application profile could be based on DCAT-AP [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], extended with the new concept of
Data Service introduced by DCAT Version 2 [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] as a collection of operations that
provide access to one or more datasets or data processing functions.
Design and development of Semantic Web-based transportation data converters:
the EU Regulation asks to turn available transportation data into specific data
formats and, in case, complement/enrich them with additional data sources. Due to
the heterogeneity of the used data models, as of today, there are no holistic
solutions on the market covering all the needed data conversion and enrichment
processes. Therefore, the design and development of transportation data converters
based on Semantic Web technologies represent another research and business
opportunity for the Semantic Web community. Transportation data converters should
be software components supporting the conversion between transportation
standards by means of an intermediate step where data are mapped to a common
semantic model. As an example, a specific (semantic) converter enables the translation
of transportation schedule, geographic and fare information expressed in GTFS to
a NeTEx specification preserving the original meaning.
4
      </p>
    </sec>
    <sec id="sec-4">
      <title>Ongoing and Future Work</title>
      <p>Due to the delay of several EU countries in establishing the NAP to multimodal
transport data according to EU Regulation 2017/1926, transport stakeholders do not
perceive the need for data conversion as an urgent task. This effect is increased by the
lack of understanding of how the NAP could positively affect their businesses.
However, the authors of this paper believe that the needs for reference transportation
ontologies, metadata profiles, and transportation data converters will emerge very soon. In
this section, we give some hints on our work aiming at moving towards Semantic
Webbased solutions for these needs.</p>
      <p>The SNAP project3 is addressing the challenge of defining a reference ontology for
the transportation sector. The ongoing activity consists in deriving a reference ontology
from a sub-part of the CEN Transmodel4 (i.e., an abstract model of common public
transport concepts and data structures that can be used to build many different kinds of
public transport information system). The resulting ontology will represent a starting
point for a potential collaboration with the CEN TC278- WG3-SG45 that has formally
defined the Transmodel.</p>
      <p>
        Concerning the definition of metadata profiles, we proposed the Semantic Asset
Manager [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], i.e., an organized collection of asset types (e.g., datasets, APIs) enhanced
3 www.snap-project.eu
4 www.transmodel-cen.eu/
5 www.transmodel-cen.eu/standards-context/
by tools for their publication, governance, and discovery. An enhanced version of the
Semantic Asset Manager is under development in the context of the SPRINT project6
where the description of each asset type is made through a DCAT-AP metadata profile.
This enhanced version will be tested in the context of the Shift2MaaS project7 as an
enabling component for MaaS solution providers.
      </p>
      <p>
        For what concerns the design and development of transportation data converters, a
potential solution is based on the any-to-one approach to semantic interoperability
described in [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]: legacy data schemas used by transport stakeholders are mapped to a
reference ontology, and this ontology is mapped, e.g., to formats/standards requested
by the EU Regulation. This approach simplifies the mapping activities and their
reusability. We adopted this approach in a different domain [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], and we are bringing and
adopting such experience in the transportation domain. An annotation-based solution
to data transportation conversion is described in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], and a new RML-based solution [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]
has been recently developed in the context of the SNAP project.
      </p>
      <p>Acknowledgments
This work has been supported by SNAP (EIT Digital-19281), SPRINT
(H2020826172) and Shift2MaaS (H2020-826252).
6 www.sprint-transport.eu/
7 www.shift2maas.eu/</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>EU</given-names>
            <surname>Commission</surname>
          </string-name>
          (
          <year>2016</year>
          ).
          <article-title>Study on ITS Directive, Priority Action A: the Provision of EUwide Multimodal Travel Information Services</article-title>
          . Available at: http://ec.europa.eu/transport/themes/its/consultations/doc/2015
          <article-title>-its-mmtips/consultation-report</article-title>
          .pdf
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>EU</given-names>
            <surname>Commission</surname>
          </string-name>
          (
          <year>2017</year>
          ).
          <article-title>Commission Delegated Regulation (EU)</article-title>
          <year>2017</year>
          /1926. Available at: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%
          <fpage>3A32017R1926</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. ISA working group (
          <year>2015</year>
          ).
          <article-title>DCAT application profile for data portals in Europe</article-title>
          . Available at: https://joinup.ec.europa.eu/system/files/project/dcat-ap
          <source>_final_v1.00_0</source>
          .html.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Hendriks</surname>
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jorna</surname>
            <given-names>R.</given-names>
          </string-name>
          , et Al. (
          <year>2018</year>
          ).
          <article-title>Monitoring and Harmonisation of National Access Points in Europe</article-title>
          . Available at: www.its-platform.eu/filedepot_download/
          <year>1971</year>
          /6491
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Carenini</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dell'Arciprete</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gogos</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kallehbasti</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rossi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Santoro</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <article-title>ST4RT - Semantic Transformations for Rail Transportation</article-title>
          .
          <source>In Proc. TRA</source>
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>Della</given-names>
            <surname>Valle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>Cerizza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Celino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            , ...
            <surname>Monteleone</surname>
          </string-name>
          ,
          <string-name>
            <surname>G.</surname>
          </string-name>
          (
          <year>2007</year>
          ).
          <article-title>SEEMP: a semantic interoperability infrastructure for e-government services in the employment sector</article-title>
          .
          <source>The Semantic Web: Research and Applications</source>
          ,
          <volume>220</volume>
          -
          <fpage>234</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Carenini</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Comerio</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Celino</surname>
            <given-names>I.</given-names>
          </string-name>
          (
          <year>2018</year>
          ).
          <article-title>Semantic-Enhanced National Access Points to Multimodal Transportation Data</article-title>
          .
          <source>In Proc. of the Int. Semantic Web Conference</source>
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Vetere</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lenzerini</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2005</year>
          ).
          <article-title>Models for semantic interoperability in service-oriented architectures</article-title>
          .
          <source>IBM Systems Journal</source>
          ,
          <volume>44</volume>
          (
          <issue>4</issue>
          ),
          <fpage>887</fpage>
          -
          <lpage>903</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Comerio</surname>
            <given-names>M.</given-names>
          </string-name>
          <article-title>An Innovative Semantic Solution to Turn Transport Data into EU Compliance</article-title>
          .
          <source>In Proc. of SEMANTiCS 2019 - Industry &amp; Use Case Presentations.</source>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Albertoni</surname>
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Browning</surname>
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cox</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Perego</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Winstanley</surname>
            <given-names>P.</given-names>
          </string-name>
          (
          <year>2019</year>
          ).
          <article-title>Data Catalog Vocabulary (DCAT) V2 - W3C Working Draft</article-title>
          . Available at: www.w3.org/TR/vocab-dcat-2
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>