<!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>Modular Ontology for Event-Based Data Sharing in the Logistics Domain</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Cornelis Bouter</string-name>
          <email>cornelis.bouter@tno.nl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Giulia Biagioni</string-name>
          <email>giulia.biagioni@tno.nl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Thom van Gessel</string-name>
          <email>thom.vangessel@tno.nl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Wouter Korteling</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Erik de Graaf</string-name>
          <email>erik.degraaf@tno.nl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Wout Hofman</string-name>
          <email>wout.hofman@tno.nl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>TNO</institution>
          ,
          <addr-line>Anna van Buerenplein 1, The Hague</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2022</year>
      </pub-date>
      <fpage>13</fpage>
      <lpage>15</lpage>
      <abstract>
        <p>We present ongoing work on developing a modular ontology to support event-sharing in the logistics domain across modalities (e.g., road and rail) as envisioned by the Digital Transport and Logistics Forum (DTLF). Our main contribution is an event module that describes a change in the state of logistics activities. Additionally, we contribute a modularised ontology architecture to relate existing (semantic) modelling eforts to the event module. All contributions are publicly available. ogy. Logistics, ontology development, interoperability, modularisation, data sharing, event, semantic technol0000−0002−5448−0543 (C. Bouter); 0000−0002−4686−0490 (T. v. Gessel); 0000−0001−8269−4402 (W. Korteling);</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        The Digital Transport and Logistics Forum (DTLF), an expert group organised by the Directorate
General for Mobility and Transport of the European Commission, has adopted a proposed
solution for multi-modal (e.g., between rail, road, and air transport) decentralised data sharing
based on “events” [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Each future or current change in the state of logistics activities is
represented by an event.
      </p>
      <p>For example, a load event establishes the association between a piece of equipment (e.g., a
container) and a transport means (e.g., a truck). An arrival event establishes the assignment
between a transport means and an infrastructural or geographical location. Each event also
has a counterpart that indicates the end of the assignment: a discharge and a departure event,
respectively. A complete collection of events encompasses the whole logistics process.</p>
      <p>
        In this work we present the main modules of the FEDeRATED Semantic Model to show how
the DTLF principles can be adopted in the Connecting Europe Facility (CEF) FEDeRATED [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
We show how the ontology modularisation can facilitate the process towards multi-modal
event-based data-sharing. We first describe the Semantic Web background. Then we give an
overview of the ontology through its functional requirements, modularisation, and a dedicated
look at the Event concept.
nEvelop-O
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Background</title>
      <p>
        The Semantic Web is based on the principle of linking and reusing all relevant data sources [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
This principle is supported by the process of modularisation, which is the practice of dividing
ontologies into smaller parts that can be reused independently. This process additionally decreases
the complexity of the model and may increase understandability and query scalibility [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        The principle of reusing existing models is relevant for logistics, because many standards and
ontologies have already been developed for the logistic modalities. Existing work is typically
concerned with modelling the entities and/or the documents involved in the logistics process.
The ERA Railway ontology [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], SmartRail1, and the Rail Topology Ontology [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] model the domain
from the perspective of the entities it contains. In the airways modality the International Air
Trafic Association (IATA) OneRecord ontology takes a document centric view [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. The Open
Trip Model2 (OTM), developed for the road modality, takes a combined view by modelling
events, documents, and entities.
      </p>
      <p>
        Similarly, there are multiple eforts geared towards semantic modelling infrastructure and
geography, consisting of, among others, the EU Knowledge Graph [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], Geonames 3, GeoSPARQL4,
Kadaster KG [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. These combined eforts provide dereferenceable URIs for every geographical
or infrastructural location across the globe.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Ontology overview</title>
      <p>The FEDeRATED Semantic Model5 contributes to the existing literature by supporting the
capacity for event-based and multi-modal sharing of logistics data. The event-based
contribution lies in the domain-specific event module that we present, which conceptualises the
various activities of the logistics process (e.g. pick-up, arrival, and discharge). The multi-modal
contribution arises from the modularised ontology architecture that facilitates reuse of existing
models of the various modes of transport.</p>
      <p>
        The functional requirements of the ontology are described in a set of competency questions
(CQs), derived by analysing the requirements set out in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. In Table 1 we highlight some
competency questions of the Event module ordered by complexity, including the SPARQL query
pattern to verify the CQ. The first questions therefore indicate the basic functionalities. The
last indicate emergent properties of a set of events: by combining events from multiple sources
in the semantic model, we can trace the unique identifier of a single entity (e.g., a container)
across modalities.
1https://ontology.tno.nl/smart-rail/
2https://otm5.opentripmodel.org/
3http://www.geonames.org/
4https://www.ogc.org/standards/geosparql
5The current version of the FEDeRATED Semantic Model can be inspected on GitHub (https://github.com/
Federated-BDI/FEDeRATED-Semantic-Model and browsed in a VoCol viewer [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] (http://www.federatedplatforms.
eu/index.php/developer-portal).
      </p>
      <sec id="sec-3-1">
        <title>Competency question</title>
      </sec>
      <sec id="sec-3-2">
        <title>Example answer</title>
      </sec>
      <sec id="sec-3-3">
        <title>SPARQL pattern</title>
      </sec>
      <sec id="sec-3-4">
        <title>Which type of event is [this event]?</title>
      </sec>
      <sec id="sec-3-5">
        <title>Arrival</title>
        <p>$ t h i s a e v e n t : E v e n t , ? a d d i t i o n a l T y p e .</p>
      </sec>
      <sec id="sec-3-6">
        <title>Vessel  and container</title>
        <p>$ t h i s e v e n t : i n v o l v e s D i g i t a l T w i n ? d t .</p>
      </sec>
      <sec id="sec-3-7">
        <title>Which digital twin(s) are involved in</title>
        <p>[this event]?
At what time did or will [this event] 2022-06-01 at 08:31:06,
take place? What is the qualifier of the actual time
timestamp?</p>
      </sec>
      <sec id="sec-3-8">
        <title>Is the estimated time still before the required time of an event? Yes</title>
      </sec>
      <sec id="sec-3-9">
        <title>What is the planned route of [this transport means]?</title>
      </sec>
      <sec id="sec-3-10">
        <title>Rotterdam, Antwerp,</title>
      </sec>
      <sec id="sec-3-11">
        <title>Brussels, Luxembourg,</title>
      </sec>
      <sec id="sec-3-12">
        <title>Brussels, Antwerp,</title>
      </sec>
      <sec id="sec-3-13">
        <title>Rotterdam</title>
        <p>$ t h i s e v e n t : h a s T i m e s t a m p ? t s ;</p>
        <p>e v e n t : h a s D a t e T i m e T y p e ? t y p e .
$ r e q E v e n t e v e n t : h a s T i m e s t a m p ? r e q T i m e .
$ e s t E v e n t e v e n t : h a s T i m e s t a m p ? e s t T i m e .</p>
        <p>F I L T E R ( ? r e q T i m e &gt; ? e s t T i m e )
? e v e n t e v e n t : i n v o l v e s D i g i t a l T w i n $ t h i s ;
a e v e n t : A r r i v a l E v e n t ;
e v e n t : h a s D a t e T i m e T y p e e v e n t : P l a n n e d ;
e v e n t : i n v o l v e s P h y s i c a l I n f r a s t r u c t u r e ? p i ;
e v e n t : h a s T i m e s t a m p ? t s .</p>
        <p>F I L T E R ( ? t s &gt; ” 2 0 2 2 - 0 7 - 0 4 T 0 0 : 0 0 : 0 0 ” ^ ^ x s d : d a t e T i m e )
O R D E R B Y ? t s
3.1. Modularisation
We identified six ontology modules based on the FEDeRATED architecture requirements: the
main Event module; Business Service describing enterprises and contracts, Digital Twin
concerning all physical objects in the logistics domain, ranging from transport means to equipment (e.g.,
containers) and goods; Classifications to reuse existing non-Linked Data code lists; Physical
Infrastructure for geographical and infrastructural objects; and Logistic Roles for a taxonomy of
roles.</p>
        <p>The Event module takes a central place in the modularisation (Figure 1). The type of an event is
defined by its involved business transaction(s), physical object(s) and/or physical infrastructure
elements. These entities are respectively described in the Business Service, Digital Twin, and
Physical Infrastructure modules. The Logistics Roles module provides a taxonomy of roles that
an enterprise, part of the Business Service module, may play in the context of an event.</p>
        <p>The modules directly surrounding the Event module are intended as “interfaces” to align
with and between external standards. In Section 2, we already identified several models for the
various logistic modalities that can be aligned with Digital Twin, of which we implemented an
alignment to the ERA ontology. The PhysicalInfrastructure module also facilitates the reuse of
external vocabularies, namely Geonames, Place from Schema.org, and Geo (WGS84). In the
Classifications we provide an RDF implementation of several commonly used codelists to reuse
ERA Ontology</p>
        <p>Digital Twin
event:involves</p>
        <p>event:involves</p>
        <p>Event
event:involves
Business
Service</p>
        <p>Physical</p>
        <p>Infrastructure
Logistic Roles</p>
        <p>Geonames</p>
        <p>WSG 84
Geo-SPARQL</p>
        <p>EU KG
existing attributes about physical entities or business transactions.
3.1.1. Event module
The properties that link the Event (Figure 2) to the other modules indicate that the Event has an
association to those elements. The milestone of an event indicates whether the association is
established (“Start”) or removed (“End”). The type of event is defined by its associations. For
example, a load event is the establishment of an association between a transport means and a
container. A discharge event would constitute the end of that association. If an event has an
association to another event we call it a complex event. This way we create a composite event.
For example, a pickup event consists of an arrival event, some load events, and a departure
event. Otherwise, we call it an atomic event. Additionally, each event has a qualifier on its
timestamp: actual, expected, estimated, planned or requested. Taken altogether, Figure 3 shows
an example event in Turtle syntax.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Discussion</title>
      <p>
        In this work we have presented a modularised ontology consisting of a main Event module and
complementary extensions to support multi-modal event-based data sharing in the logistics
domain [
        <xref ref-type="bibr" rid="ref1 ref2">2, 1</xref>
        ]. Our main ongoing work is the integration of the semantic model with the proposed
data sharing architecture [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], validating the model in ongoing usecases, the transformation
of various data sources (e.g., OTM or enterprise data) using an RML-based mapper [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], and
supporting the alignment of additional standards with the FEDeRATED Semantic Model.
      </p>
      <p>DateTimeType
hasDateTimeType
hasMilestone
rdf:type</p>
      <p>Actual
Estimated</p>
      <p>Requested</p>
      <p>Expected
Planned</p>
      <p>involvesEvent
AtomicEvent</p>
      <p>ComplexEvent</p>
      <p>Milestone</p>
      <p>rdf:type
End</p>
      <p>Start
CallEvent
MilkRun
DepartureEvent</p>
      <p>ArrivalEvent
...</p>
      <p>DropOffEvent</p>
      <p>DischargeEvent</p>
      <p>@prefix event: &lt;https://ontology.tno.nl/logistics/federated/Event#&gt; .
@prefix dt: &lt;https://ontology.tno.nl/logistics/federated/DigitalTwin#&gt; .
@prefix bs: &lt;https://ontology.tno.nl/logistics/federated/BusinessService#&gt; .
@prefix data: &lt;https://www.example.com/enterprise/event#&gt; .
@prefix lsp: &lt;https://www.example.com/logisticServiceProvider#&gt; .
data:event_1 rdf:type event:Event, event:ArrivalEvent ;
rdfs:label ”Example arrival event” ;
event:hasDateTimeType event:Planned ;
event:hasMilestone event:Start ;
event:hasTimestamp ”2022-01-19T14:04:00.9”^^xsd:dateTime ;
event:involvesDigitalTwin lsp:transportMeans_1 ;
event:involvesPhysicalInfrastructure &lt;http://data.europa.eu/949/functionalInfrastructure/operationalPoints/NLERP&gt; ;
event:involvesBusinessService data:thisCompany .
lsp:transportMeans_1 rdf:type dt:Truck ;</p>
      <p>dt:hasLicensePlateNumber ”00-BBB-1” .
data:thisCompany rdf:type bs:Enterprise ;</p>
      <p>bs:actorName ”someCompany”^^xsd:string .</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgments</title>
      <p>This work is based on developments in the CEF FEDeRATED Action and the Digital Transport
and Logistics Forum. This work is partly supported by the Horizon 2020 Magpie project under
grant agreement 101036594.</p>
      <p>The presented work is not adopted by EC DG Move as eFTI Implementing Act and is solely
the proposal of the authors, based on concepts, principles, and architecture developed by the
Connecting European Facility (CEF) FEDeRATED Action and adopted by the DTLF.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Digital</given-names>
            <surname>Transport and Logistics Forum</surname>
          </string-name>
          ,
          <source>Subgroup 2 - Corridor freight information systems - Intermediate report</source>
          ,
          <year>2022</year>
          . URL: https://transport.ec.europa.
          <article-title>eu/transport-themes/ digital-transport-and-logistics-forum-dtlf_en#about-the-dtlf.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <article-title>[2] FEDeRATED, Milestone 2 FEDeRATED interim master plan</article-title>
          ,
          <year>2021</year>
          . URL: http:// federatedplatforms.eu/index.php/library/category/2-masterplan.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A.</given-names>
            <surname>Hogan</surname>
          </string-name>
          ,
          <source>The Web of Data</source>
          , Springer International Publishing, Cham,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>C.</given-names>
            <surname>Parent</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Spaccapietra</surname>
          </string-name>
          ,
          <article-title>An overview of modularity, Modular ontologies (</article-title>
          <year>2009</year>
          )
          <fpage>5</fpage>
          -
          <lpage>23</lpage>
          .
          <source>doi:1 0 . 1 0</source>
          <volume>0 7 / 9 7 8 - 3 - 6 4 2 - 0 1 9 0 7 - 4</volume>
          { \ _ }
          <fpage>2</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>J. A.</given-names>
            <surname>Rojas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Aguado</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Vasilopoulou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            <surname>Velitchkov</surname>
          </string-name>
          ,
          <string-name>
            <surname>D. Van Assche</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Colpaert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Verborgh</surname>
          </string-name>
          ,
          <article-title>Leveraging semantic technologies for digital interoperability in the European railway domain</article-title>
          , in: A.
          <string-name>
            <surname>Hotho</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Blomqvist</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Dietze</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Fokoue</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Ding</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Barnaghi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Haller</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Dragoni</surname>
          </string-name>
          , H. Alani (Eds.),
          <source>The Semantic Web - ISWC 2021</source>
          , Springer International Publishing, Cham,
          <year>2021</year>
          , pp.
          <fpage>648</fpage>
          -
          <lpage>664</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>S.</given-names>
            <surname>Bischof</surname>
          </string-name>
          , G. Schenner,
          <article-title>Rail topology ontology: A rail infrastructure base ontology</article-title>
          ,
          <source>in: The Semantic Web - ISWC 2021</source>
          , Springer International Publishing,
          <year>2021</year>
          , pp.
          <fpage>597</fpage>
          -
          <lpage>612</lpage>
          .
          <source>doi:1 0 . 1 0</source>
          <volume>0 7 / 9 7 8 - 3 - 0 3 0 - 8 8 3 6 1 - 4</volume>
          { \ _ } 3
          <fpage>5</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>A.</given-names>
            <surname>Blaj</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Mulder</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Sauv</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Lambert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Lambert</surname>
          </string-name>
          , ONE record:
          <article-title>One step closer to digital cargo with ontologies and linked data</article-title>
          ., in: ISWC (Demos/Industry),
          <year>2020</year>
          , pp.
          <fpage>384</fpage>
          -
          <lpage>386</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>D.</given-names>
            <surname>Diefenbach</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. D.</given-names>
            <surname>Wilde</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Alipio</surname>
          </string-name>
          ,
          <article-title>Wikibase as an infrastructure for knowledge graphs: The EU knowledge graph</article-title>
          , in: A.
          <string-name>
            <surname>Hotho</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Blomqvist</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Dietze</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Fokoue</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Ding</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Barnaghi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Haller</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Dragoni</surname>
          </string-name>
          , H. Alani (Eds.),
          <source>The Semantic Web - ISWC 2021</source>
          , Springer International Publishing, Cham,
          <year>2021</year>
          , pp.
          <fpage>631</fpage>
          -
          <lpage>647</lpage>
          .
          <source>doi:1 0 . 1 0</source>
          <volume>0 7 / 9 7 8 - 3 - 0 3 0 - 8 8 3 6 1 - 4</volume>
          { \ _ } 3
          <fpage>7</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>S.</given-names>
            <surname>Ronzhin</surname>
          </string-name>
          , E. Folmer,
          <string-name>
            <given-names>P.</given-names>
            <surname>Maria</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Brattinga</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Beek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Lemmens</surname>
          </string-name>
          , R. van't
          <string-name>
            <surname>Veer</surname>
          </string-name>
          ,
          <article-title>Kadaster knowledge graph: Beyond the fith star of open data</article-title>
          ,
          <source>Information</source>
          <volume>10</volume>
          (
          <year>2019</year>
          ).
          <source>doi: 1 0 . 3 3 9 0 / i n f o 1 0</source>
          <volume>1 0 0 3 1 0 .</volume>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>L.</given-names>
            <surname>Halilaj</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Petersen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            <surname>Grangel-González</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Lange</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Auer</surname>
          </string-name>
          , G. Coskun, S. Lohmann,
          <article-title>VoCol: An integrated environment to support version-controlled vocabulary development</article-title>
          ,
          <source>2016. doi:1 0 . 1 0</source>
          <volume>0 7 / 9 7 8 - 3 - 3 1 9 - 4 9 0 0 4 - 5</volume>
          { \ _ } 2
          <fpage>0</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>W.</given-names>
            <surname>Hofman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Bouter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Burghoorn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Boertjes</surname>
          </string-name>
          , E. d. Graaf,
          <string-name>
            <surname>A.</surname>
          </string-name>
          <article-title>d'Auria, Towards a mobility data space: Data sharing via linked semantic data, an example for eFTI</article-title>
          ,
          <source>in: Transport Research Arena (TRA) Conference</source>
          <year>2022</year>
          ,
          <year>2022</year>
          . In press.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>A.</given-names>
            <surname>Dimou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. Vander</given-names>
            <surname>Sande</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Colpaert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Verborgh</surname>
          </string-name>
          , E. Mannens, R. Van de Walle,
          <article-title>RML: a generic language for integrated RDF mappings of heterogeneous data</article-title>
          , in: C. Bizer,
          <string-name>
            <given-names>T.</given-names>
            <surname>Heath</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Auer</surname>
          </string-name>
          ,
          <string-name>
            <surname>T.</surname>
          </string-name>
          Berners-Lee (Eds.),
          <source>Proceedings of the 7th Workshop on Linked Data on the Web</source>
          , volume
          <volume>1184</volume>
          <source>of CEUR Workshop Proceedings</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>