<!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>Semantic-enhanced National Access Points to Multimodal Transportation Data</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Alessio Carenini</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marco Comerio</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>alessio.carenini</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>marco.comerio</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 represents a first step towards the realization of semantic interoperable travel information services. This paper presents the Semantic Assets Manager, i.e., an organized collection of asset types (i.e., datasets, APIs, ontologies, and schemas) enhanced by tools for their publication, governance and discovery that represents a semantic-enhanced solution for the establishment of a NAP to multimodal transportation data.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        2017 [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], only a few countries have planned their NAPs, and very few operators are
ready to be compliant with the requested standards.
      </p>
      <p>This paper presents the Semantic Assets Manager, i.e., an organized collection of
different asset types (i.e., datasets, APIs, ontologies, and schemas) enhanced by tools
for their publication, governance, and discovery. The Semantic Assets Manager
represents a semantic-enhanced solution for the establishment of NAPs. Moreover, it
promotes the sharing of semantic converters, i.e., software components supporting
transport authorities, operators and infrastructure managers in transforming their data
into the correct formats/standards.</p>
      <p>The paper is organized as follows. Section 2 describes the requirements for a
Semantic-enhanced National Access Point. Section 3 proposes our solution. Section 4
outlines future and ongoing work.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Requirements for a National Access Point</title>
      <p>
        According to [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], EU Member States shall set up the first version of their NAPs
within December 2019. For this reason, the first requirement to be considered is that
the proposed solution must be market-ready.
      </p>
      <p>Additional requirements come from the following categories of stakeholders
involved in the management/usage of the NAP:
 NAP Manager: is in charge of realizing the NAP governance by managing the
technical and procedural aspects. The NAP Manager needs to provide a trusted
environment with clearly defined authentication and authorization procedures.
Moreover, the NAP Manager needs support in quality assurance and lifecycle
management of the published assets.
 Transport authorities, transport operators and transport infrastructure
managers: need support in publishing their data in the NAP and making them
discoverable. Moreover, they potentially need support in turning their data in the required
formats/standards.
 Intelligent Transport System (ITS) providers: need support in discovering and
using datasets and API from the NAP for ITS app development.
 Travelers: need support in discovering and using NAP information for their
journey planning.</p>
      <p>In summary, a solution for the establishment of a NAP should address the following
requirements:</p>
      <p>R1. Authorization and authentication mechanisms;
R2. Tools for the publication of the datasets, their metadata descriptions and storage;
R3. A dataset lifecycle management that includes an “IN REVIEW” status where a
specific NAP management committee verifies the quality of the dataset and its
compliance with the EU regulation;
R4. Trustworthiness in the datasets management;
R5. Tools for the discovery of the datasets;</p>
      <p>R6. Semantic converters of datasets between different format/standards.</p>
    </sec>
    <sec id="sec-3">
      <title>The Semantic Assets Manager</title>
      <p>The Semantic Assets Manager is our semantic-enhanced solution for the
establishment of a NAP to multimodal transportation data. To be market-ready and to reuse
basic existing features, we decided to start from the popular and open source WSO2
Governance Manager3 that, out of the box, satisfies requirements R1-R4. We
configured the Semantic Assets Manager by extending WSO2 in order to manage the
following asset types: (i) ontologies, shared reference domain ontologies; (ii) other
schemas, e.g., XSD definitions of the standards, such as NeTEx and GTFS4; (iii)
datasets, travel and traffic data of different transport modes; (iv) service descriptions,
made available by transport stakeholders to dynamically access data; (v) exploration
APIs, supporting the discovery of available assets; (vi) converter services, transforming
data between different standards. Each asset type is published according to a specific
semantically-enhanced metadata profile and associated with a specific lifecycle
management. The Semantic Assets Manager5 is composed of two Web application, namely
the publisher6 and the store7, supporting the publishing and the discovery of the assets,
respectively.</p>
      <p>
        To further strengthen the satisfaction of R4, we have included blockchain technology
[
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]: a transaction is added to a distributed ledger each time an asset changes its lifecycle
state. Such transaction contains all accounting information, enabling all the ecosystem
participants to check the complete history of an asset on a trusted platform.
      </p>
      <p>
        To cover also R5, the WSO2 Governance Manager is extended with modules
supporting the transformation, storage, and discovery of the published assets descriptions
in RDF, thus enabling more expressive queries on such data. Following the approach
in [
        <xref ref-type="bibr" rid="ref3 ref8">3,8</xref>
        ] of SPARQL query templates, we introduce a new asset type, the exploration
API, for an intelligent asset discovery (e.g., finding all transport datasets/services
proving information about bike sharing in a specific Italian region). When a new exploration
API method is created, the Semantic Asset Manager automatically generates its
OpenAPI/Swagger documentation8. The benefits introduced by this asset type are: (i) a better
control on RDF data access; (ii) improved usability for users involved in dataset
discovery; (iii) easy integration with external systems.
      </p>
      <p>
        Finally, to cover also R6, the semantic converters proposed in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and based on the
approach in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], are also added as assets. The semantic converters are software
components supporting the conversion between transportation standards. 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.
      </p>
      <sec id="sec-3-1">
        <title>3 http://wso2.org</title>
        <p>4 http://gtfs.org
5 A detailed description of the Semantic Assets Manager is available at: https://bit.ly/2JG8zL8
6 https://ns3056488.ip-213-32-26.eu:9443/publisher (usr:guest, psw: $ISWC2018_guest#)
7 https://ns3056488.ip-213-32-26.eu:9443/store (usr:guest, psw: $ISWC2018_guest#)
8 https://www.openapis.org/</p>
        <p>
          The Semantic Assets Manager satisfies the FAIR principles9 since the assets,
accessible through public APIs, are associated with metadata profiles and are defined
according to specific standards that make them interoperable and reusable. Moreover, our
solution overcomes most of the limitations of data management platforms mentioned in
[
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] since we provide (i) access to the source code to permit customization and
extensions, (ii) APIs to support easy integration, and (iii) unique identifiers for the assets to
improve findability.
4
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Ongoing and Future Work</title>
      <p>Together with a network of transport stakeholders, we are defining a governance
framework for the Semantic Assets Manager, to enable its adoption and sustainability
as a semantic-enhanced NAP for multimodal transportation data. Moreover, we are
currently exploring the use of SHACL Advance Features10 to improve the automation of
ontology-based annotations and mappings and to enhance further the approach used for
the realization of semantic converters.</p>
      <p>Acknowledgments
This work has been supported by IT2Rail (H2020-636078), ST4RT (H2020-730842)
and GoF4R (H2020-730844).</p>
      <sec id="sec-4-1">
        <title>9 https://www.force11.org/group/fairgroup/fairprinciples</title>
        <p>10 https://www.w3.org/TR/shacl-af/</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Amorim</surname>
            ,
            <given-names>R. C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Castro</surname>
            ,
            <given-names>J. A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Da</surname>
            <given-names>Silva</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>J. R.</given-names>
            , &amp;
            <surname>Ribeiro</surname>
          </string-name>
          ,
          <string-name>
            <surname>C.</surname>
          </string-name>
          (
          <year>2017</year>
          ).
          <article-title>A comparison of research data management platforms: architecture, flexible metadata, and interoperability</article-title>
          .
          <source>Universal Access in the Information Society</source>
          ,
          <volume>16</volume>
          (
          <issue>4</issue>
          ),
          <fpage>851</fpage>
          -
          <lpage>862</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <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="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Daga</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Panziera</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pedrinaci</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>A BASILar Approach for Building Web APIs on top of SPARQL Endpoints</article-title>
          .
          <source>In Proc. of SALAD@ESWC</source>
          <year>2015</year>
          :
          <fpage>22</fpage>
          -
          <lpage>32</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <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="ref5">
        <mixed-citation>
          5.
          <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="ref6">
        <mixed-citation>
          6.
          <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://bit.ly/2zSoOFv
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <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>2017</year>
          ).
          <article-title>Monitoring and Harmonisation of National Access Points in Europe</article-title>
          . Available at: https://www.its-platform.eu/filedepot_download/
          <year>1971</year>
          /6320
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Meroño-Peñuela</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hoekstra</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          (
          <year>2017</year>
          ).
          <article-title>Automatic Query-Centric API for Routine Access to Linked Data</article-title>
          .
          <source>International Semantic Web Conference (2)</source>
          <year>2017</year>
          :
          <fpage>334</fpage>
          -
          <lpage>349</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Swan</surname>
          </string-name>
          , Melanie. Blockchain:
          <article-title>Blueprint for a new economy.</article-title>
          <string-name>
            <surname>O'Reilly Media</surname>
          </string-name>
          , Inc.,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>