Leveraging semantic technologies for digital interoperability in the European Railway domain

In reply to

Preprint HTML version at https:/​/​julianrojas.org/papers/iswc2021-in-use


The European Union Agency for Railways acts as an European authority, tasked with the provision of a legal and technical framework to support harmonized and safe cross-border railway operations throughout the EU. So far, the agency relied on traditional application-centric approaches to support the data exchange among multiple actors interacting within the railway domain. This lead however, to isolated digital environments that consequently added barriers to digital interoperability while increasing the cost of maintenance and innovation. In this work, we show how Semantic Web technologies are leveraged to create a semantic layer for data integration across the base registries maintained by the agency. We validate the usefulness of this approach by supporting route compatibility checks, a highly demanded use case in this domain, which was not available over the agency’s registries before. Our contributions include (i) an official ontology for the railway infrastructure and authorized vehicle types, including 28 reference datasets; (ii) a reusable Knowledge Graph describing the European railway infrastructure; (iii) a cost-efficient system architecture that enables high-flexibility for use case development; and (iv) an open source and RDF native Web application to support route compatibility checks. This work demonstrates how data-centric system design, powered by Semantic Web technologies and Linked Data principles, provides a framework to achieve data interoperability and unlock new and innovative use cases and applications. Based on the results obtained during this work, ERA officially decided to make Semantic Web and Linked Data-based approaches, the default setting for any future development of the data, registers and specifications under the agency’s remit for data exchange mandated by the EU legal framework. The next steps, which are already underway, include further developing and bringing these solutions to a production-ready state.


The establishment of an interoperable European railway area without frontiers, while guaranteeing railway operation safety, is the prime objective of the European Union Agency for Railways (ERA) [1]. Since 2019 ERA became the European authority1 for cross-border rail traffic in Europe, mandated under the European Union (EU) law, to devise the technical and legal framework for supporting harmonised and safe cross-border railway operations.

The European railway ecosystem presents a particularly challenging scenario for interoperability, not only regarding physical aspects (e.g., infrastructure, energy systems, etc.) but also digital ones (e.g., information). Multiple organisations, such as Infrastructure Managers2 (IMs) and Railway Undertakings3 (RUs) [2], need to interact and exchange information to ensure safe cross-border railway operations. These organisations rely on different information management systems from multiple vendors, that are often incompatible with each other. To increase digital interoperability among heterogeneous data and information systems, ERA supports and maintains a set of base registries4, in the form of relational databases, where organisations input and access the different aspects of the information they manage and require.

However, following such traditional application-centric approach lead to isolated digital environments that consequently add barriers to digital interoperability. Tightly coupling base registries to the applications that operate over them, triggered the proliferation of often overlapping and difficult to manage data models hidden inside application code, which also increased the cost of maintenance and innovation. Moreover, stakeholder organisations such as IMs, are required to report the same information multiple times for different registries, increasing the probability of data inconsistency issues, while adding more costs to IMs due to duplicated efforts.

To address these issues, we propose a digital interoperability strategy for ERA, that adheres to the Linked Data principles5 [3] and relies on standard Semantic Web [4] technologies. We built the foundations to establish a semantic layer for data integration within the agency, initially spanning three different base registries6:, Register of Infrastructure (RINF), Register of Authorized Types of Vehicles (ERATV) and the Centralized Virtual Vehicle Register (ECVVR). We validate the usefulness of the approach by reusing the produced semantic data to support route compatibility checks (RCC), a highly-demanded use case in the railway domain. The RCC use case is stipulated and specified in EU regulations 2016/797 and 2019/773 [5, 6] and was so far, unsupported by ERA due to interoperability issues among base registries. Additionally, we show the flexibility of graph-based data models, by integrating an additional external data source that complement the resulting Knowledge Graph.

The contributions of this paper include (i) an official ontology7, modelling railway infrastructure aspects (e.g. topological, functional, etc.), rolling stock and authorized vehicle types, and 28 independently managed reference datasets; (ii) a public and reusable RDF Knowledge Graph8 with 13.8 million triples about the European railway infrastructure and more than 800 thousand rolling stocks; (iii) a cost-efficient system architecture that enables high-flexibility for use case support; and (iv) an open source and RDF native Web application9 to support and process RCC queries.

This work demonstrates how data-centric system design, powered by Semantic Web technologies, provides a framework to achieve data interoperability and unlock new and innovative use cases and applications. The results of the work presented in this paper had a strong impact on ERA10, which decided on making Semantic Web technologies the default setting for any future development of data, registers and specifications, under the agency’s remit, for data exchange mandated by the EU legal framework. The next steps, which are already underway, include further extending the ontology to consider additional aspects, aligned with the requirements of the railway domain and evolving the system architecture towards a production-ready solution, fully integrated with the data management workflows of ERA.

The remainder of this paper is organized as follows. Section 2 presents an overview of related work in the context of modelling approaches and interoperability for the railway domain. Section 3, describes the RCC use case its requirements. Section 4 gives an overview and description of our proposed solution architecture components. Section 5 discusses the advantages and limitations of the approach, and Section 6 presents our conclusions and perspectives for future work.

Data Sources and Use Case

In this section we present an overview of the different data sources reused by our proposed solution. We also describe the RCC use case as a main motivator for this work.

ERA’s base registries

Our approach considers, so far, 3 of the base registries maintained by ERA, namely the Register of Infrastructure (RINF), the Register of Authorized Types of Vehicles (ERATV) and the Centralized Virtual Vehicle Register (ECVVR). These registries contain overlapping conceptual definitions, represented as properties of different type of entities, which are locked within their respective data silos. Next we give a brief description for each of these registries.

Register of Infrastructure

The European Register of Infrastructure (RINF) was introduced following Article 35 of the EU regulation 2008/57/EC [15]. RINF contains the main features of fixed installations related to the subsystems of infrastructure, energy and parts of control-command and signaling. It publishes performance and technical characteristics mainly related to interfaces with rolling stock and operation. It is maintained as a relational database and its content is provided by the different European IMs, by means of a predefined XML Schema16.

Register of Authorized Types of Vehicles

The European Register of Authorized Types of Vehicles (ERATV) is introduced by Article 5 of the EU regulation 2011/665/EU [16]. It aims to publish and keep an up-to-date set of authorized types of vehicles including information that references the technical specifications for each parameter. ERATV is maintained as a relational database populated through a Web application by multiple authorizing entities. ERATV provides also additional information for a certain vehicle type, such as manufacturing country, manufacturer, category and different physical and operational parameters.

Centralized Virtual Vehicle Register

The European Centralised Virtual Vehicle Register (ECVVR) is a base registry maintained by ERA, in accordance with the EU regulation 2018/1614 [17]. ECVVR defines a decentralized architecture for information search and retrieval of rolling stock data, where each Member State hosts and publishes their own national vehicle registry(ies), accessible through Web-based interfaces.

External data source

There are known limitations for ERA’s base registries, as is the case of RINF and the limited granularity it gives over the railway topology. RINF provides a view over the railway infrastructure, commonly referred as a meso-level view17, where complex topological structures inside stations, junctions, switches, etc., are abstracted into single nodes in the network graph. Route calculations over this limited view, may wrongfully assume certain direction changes, not possible in the real world. Calculating end-to-end routes with high accuracy, requires further data about the connectivity within each network node. This connectivity issue currently stands as one of the main challenges, for an accurate and reliable data source description of the European railway infrastructure topology. For this reason we also consider an external data source, provided by the Dutch IM ProRail, which provides an additional topological description for addressing this issue limited to the region of Utrecht in The Netherlands.

Connectivity data in the Utrecht area

The Dutch IM ProRail, provided us with an additional data source for exploring an alternative solution for the lack of real information about the internal connectivity inside network nodes (also called operational points). It consists of a table that groups all the different permutations of incoming and outgoing tracks for a set of operational points, and states if they are connected or not.

[Figure 1]
Fig. 1: a) shows a schematic diagram of an operational point where its internal connections are unknown. b) shows how this information can be completed from the data provided in Table 1.

The operational point OPx (Figure 1a), has two incoming tracks (T1 and T2) coming from OPy and belonging to the national line LineJ. We know these are incoming tracks thanks to the logical direction defined for LineJ, despite T1 being a bidirectional track. OPx also has two outgoing tracks (Ta and Tb), going towards OPw and belonging to another national line LineK. Based on this information we establish the correct connectivity that reflects real-world behavior.

IN_Line IN_OP IN_Track OP OUT_Track OUT_OP OUT_Line Connected
LineJ OPy T1 OPx Ta OPw LineK true
LineJ OPy T2 OPx Tb OPw LineK true
LineJ OPy T1 OPx Ta OPw LineK false
LineJ OPy T2 OPx Tb OPw LineK true

Table 1: All the possible permutations between incoming and outgoing tracks of OPx, plus a column that states if there is a possible connection between two pairs of tracks.

Use Case: Route Compatibility Check

Article 23 (point b) of the European regulation 2016/797 stipulates [5] that:

Before a railway undertaking uses a vehicle in the area of use specified in its authorisation for placing on the market, it shall check: …(b) that the vehicle is compatible with the route on the basis of the infrastructure register, the relevant TSIs or any relevant information to be provided by the infrastructure manager free of charge and within a reasonable period of time, where such a register does not exist or is incomplete

The specific procedures for assessing if a certain vehicle is compatible with a certain route, are further specified by the Annex D1 of the EU regulation 2019/773 [6]. These specifications directly refer to specific data properties within RINF and ERATV, of 22 different technical aspects that need to be compared to determine if there is technical compatibility. This specification already highlights a clear need for interoperability at least between RINF and ERATV, which we address with the proposed ontology and derived Knowledge Graph.

To determine if a certain vehicle type is compatible with a certain route, is necessary to first find possible routes through the railway infrastructure, which involves a very particular type of queries, namely graph path finding queries. The standard query language for RDF graphs (SPARQL) does not support finding complex relation paths between RDF entities [18]. The Property Paths querying syntax, introduced in SPARQL 1.1, only allows for testing path existence but falls short on counting and retrieving the actual paths between two nodes [19], which is crucial for the RCC use case. Currently there exist non-standard extensions to SPARQL (e.g. Stardog path queries18) that address this limitation they are not widely supported across RDF graph databases. We consider this limitation in our proposed architecture and propose an alternative solution (see Section 4.2) to non-standard SPARQL extensions and according to the current Web standards to prevent vendor lock in issues.

Proposed Solution

Considering the interoperability obstacles that exist among the base registries maintained by ERA, we propose and design a solution architecture, capable of creating a semantic interoperability layer for data integration over them. Moreover, we exploit the inherent flexibility of graph-based data models to also include an external data source, that enriches the resulting Knowledge Graph (KG) and addresses intrinsic limitations of the original base registries. The proposed architecture relies on an ontology, defined to cover, but not limited to, the explicit interoperability requirements brought forth by the RCC use case. The architecture implements an ETL (Extract Transform Load)-based pipeline that relies on a fully declarative approach for the KG generation process, and leverages fundamental Web principles such as caching, to reduce computational infrastructure costs while maintaining a high querying flexibility.

In this section we present a description of the main architectural components of our proposed solution. We describe the proposed ontology and give an full overview of the solution architecture, which includes a fully functional application to support route compatibility checks (available online19).

The ERA Vocabulary

Our proposed ontology, namely the ERA Vocabulary7, was created in a collaborative effort including domain experts from ERA, ProRail, SNCF and Semantic Web experts from DG DIGIT and IDLab-imec. The ERA Vocabulary provides unique identifiers and semantic definitions for concepts and properties, common to the railway domain. We make its documentation available online using Widoco [20] as a template generator. The source files are available in a public GitHub repository20.

[Figure 2]
Fig. 2: Layered data model of the ERA Vocabulary.

Following Semantic Web best practices, the ontology reuses external ontologies such as OGC GeoSPARQL, Schema.org and the EU publications office authority table21 for country definitions. It defines a layered model (see Figure 2), inspired from RINF’s relational model, where the topological and functional aspects of the railway infrastructure are defined by independent entity types. Two layers are defined: abstraction and implementation. The abstraction layer defines logical entities form the network topology graph, with era:NodePorts acting as nodes and both era:MicroLinks and era:InternalNodeLinks acting as edges. The implementation layer, represents concrete and functional objects in the real world, such as tracks, operational points (stations, switches, etc.) and vehicles (types). The link between these two layers is given by the era:MicroNode - era:OperationalPoint and era:MicroLink - era:Track relationships.

Additionally, 28 reference datasets22 were extracted from the base registries and defined as SKOS controlled vocabularies. They contain definitions for different domain-related technical aspects, which are envisioned to be independently managed by relevant authorities.

Architecture Overview

Our proposed solution architecture is composed by 4 main modules (see Figure 3), namely the Data Sources, KG Generation, KG Querying and User Application modules. The Data Sources module represents the considered data sources (previously described in Section 3). The components from the KG Generation module, access the data sources to produce the RDF triples that compose the ERA KG. The ERA KG is published and made available for querying by the KG Querying module, which provides the necessary interfaces for the User Application module to support specific use cases. Next, we provide a description and the rationale behind these modules.

[Figure 3]
Fig. 3: Overview of the proposed solution architecture for semantic data interoperability across ERA’s base registries.

KG Generation

The KG generation process in our solution follows an ETL-based approach and uses the RML [21] technology stack for declaratively generating the RDF triples of the ERA Knowledge Graph. RML was selected for handling heterogeneous data sources, which in our case are relational DBs and CSV files, but XML Schema-based data sources (e.g., RailML) are also envisioned as a next step. The steps followed in this process are:

  1. The declarative RDF mapping rules23 specified in human-friendly YARRRML [22] syntax.
  2. YARRRML rules are transformed to RML using the yarrrml-parser Node.js application.
  3. The RMLMapper24, a Java application that reads the specified data sources and produces RDF data according to the set of given rules.
  4. The resulting KG is published and loaded in a triple store. At the time of writing the ERA KG, had a total of 13.8 million triples, which we also make available as a raw data dump25.

KG Querying

We published the ERA KG in two different triple stores (GraphDB26 and Virtuoso27) to prove that our proposed solution is vendor-independent. This module includes one of the core components of the architecture: the ERA Geo-LDF, which is implemented as a Node.js application28. The main purpose of this component is exposing a Linked Data and Hypermedia-based API over the ERA KG. It builds on the Linked Data Fragments [23] approach to provide metadata annotated fragments (tiles) of the ERA KG, based on a predefined geospatial pattern. It follows the slippy maps specification29, where the grid-based partition of the world is specified based on a zoom level z and the x and y cartesian coordinates. A live example of a tile for the area of Brussels can be accessed on http:/​/​era.ilabt.imec.be/ldf/sparql-tiles/implementation/10/524/343.

The tiles are built by the ERA Geo-LDF component via template SPARQL queries that select and filter the entities based on their geospatial properties. In this way, client applications can request relevant data for their purposes and since the API returns unmodified triples from the KG, further querying and processing becomes possible on the client-side. Following this approach, we address the limitation of performing graph path finding queries directly on the SPARQL endpoints. Our client application implements a shortest-path algorithm and proceeds to download the relevant tiles based on the geospatial information given by origin-destination queries. Furthermore, tiles can be cached both on client- and server-side, which reduces the overall computational load on the server and improves query performance for client applications.

User Application

This module represents any user-oriented applications that would perform querying tasks over the ERA KG to support a given use case. So far, we developed a React-based Web application9 for supporting the RCC use case and demonstrating the achieved data interoperability via the ERA KG. The application allows users to select an origin-destination pair of operational points (visible in map-based UI) to calculate one or more possible routes between them. Once selected, it proceeds to download the relevant KG tile fragments and perform the path finding process. It handles RDF triples natively and implements the A* [24] and Yen’s [25] algorithms for graph shortest path and top-k shortest path calculations respectively. Once a route is found, users may select a vehicle type or also a specific vehicle instance, for which the compatibility checks will be performed. Currently the application implements compatibility evaluation for 15 different parameters of both track sections and vehicle (types). The users can also visualize the internal connectivity inside the operational points that form part of a calculated route, by means of a schematic diagram, that shows the possible internal connections defined in the ERA KG. This feature is particularly interesting for operational points around the city of Utrecht in The Netherlands, considering the additional data source from ProRail (Section 3), that was integrated into the KG.

[Figure 4]
Fig. 4: Screenshot of the RCC Web application showing a route calculated from the Charles de Gaulle airport in Paris to the Schipol airport in Amsterdam. On the lower left panel, the results of the compatibility check process are shown for the TGV Thalys PBKA vehicle type.


The implementation of our proposed solution architecture allowed us to achieve semantic interoperability over the considered data sources, which stood as independent and disconnected data silos before. Our architecture relies entirely on semantic web technologies and tools, starting from the KG generation process and ending with a RDF native Web application that supports the addressed RCC use case.

Solution Features

Next we outline the main features of our proposed solution:

Fully declarative KG generation

One key feature of our proposed solution relates to the ERA KG generation process, which is accomplished following a fully declarative approach. In other words, no pre-processing steps nor dedicated software/scripts are required to generate the RDF triples of the ERA KG. The KG generation rules are defined as RML mapping rules, which are executed by an existing and general purpose engine, that follows the given rules to produce the desired RDF triples. This feature has an important value from a data governance perspective, considering that no additional ad hoc software needs to be maintained. The RML mapping rules become the central resource for the ERA KG generation process, which can be adjusted or extended to include additional data sources, with significantly less effort compared to developing and maintaining additional software for every new data source to be included in the ERA KG. Furthermore, the mappings can be reused and adapted by IMs to produce their own internal KGs.

KG enrichment flexibility

We were also able to explore and alternative solution to integrate additional data originated directly from an IM, to address the missing connectivity issue of the railway infrastructure. This approach demonstrated the flexibility that graph-based data models hold, considering that adding additional data sources requires significantly less effort, than for example, altering a relational data model, potentially introducing breaking changes for the applications that depend on it.

Cost-efficient KG publishing and quering

Our architecture design was made, with data publishing and querying cost-efficiency as a guiding principle. As described in Section 4.2, the ERA KG is published on triple stores with support for SPARQL querying. However the user application that supports the RCC use case does not perform direct SPARQL queries over these triple stores. Instead, it downloads specific parts of the KG via an API, over which it applies its business logic. Such an approach is no different to traditional REST-based application design over relational databases, where applications are given access to data via APIs only, and do not have unbounded querying access to the database(s) [26, 27]. In contrast to most API implementations, the APIs implemented in this architecture, follow the hypermedia constraints defined by REST, providing self-describing data responses via hypermedia metadata controls. In other words, the API data responses include additional metadata that describe how it can be used by client applications to retrieve more relevant data for a particular query. Such descriptions enable the creation of smarter and more autonomous client applications, avoiding the need of hard-coding the application according to specific API interfaces.

More importantly the API design in this architecture, has been done to maximize the cacheability of API responses. By following a geospatial fragmentation approach, which suits the RCC use case, the API publishes fragments of the ERA KG that can be cached both on client- and server-side. This further reduces the computational cost on the triple stores, which only need to process once the query for a given fragment. A client application that has requested a certain data fragment does not need to request it again (client cache) and has full flexibility to perform any type of further processing on the data it contains. When another client application needs access to the same type of data, it can rely on server-side cached API responses which also improve overall application performance.

Shortest path querying over an RDF KG

The ability to indirectly support calculation of path finding queries, is an important feature of our architectural design. Our approach not only, enables solving this particular type of queries, but also opens the door for clients to implement any path finding algorithm they prefer, and further customize them to better suit their requirements. Such level of specialization of algorithms is not always possible to be defined through general purpose query languages or it could potentially result in highly inefficient queries.

Limitations and Open Challenges

The identified limitations of our approach include:

Performance of long distance queries

One of the main limitations of our proposed solution is related to the trade-off between server computational cost and query performance, that is introduced when shifting query processing tasks to the client. This is particularly visible when dealing with long distance route calculations, due to the increasing amount of data fragments that needs to be fetched and processed by the client. Different alternatives could be explored to address this limitation:

  • Server-side route planning engine: This is the most common approach followed by route planning solutions. It requires setting a dedicated engine (e.g., postGIS-based system30), which imports the whole topology graph and then is capable of executing a route planning algorithm over it. The drawbacks of this approach include the considerable increase of computational load for the server and less flexibility for client applications to select and tailor the algorithms for their own needs. But more importantly, available solutions do not support RDF data out of the box, which introduces an additional burden for the architecture by having to convert and keep in sync the ERA KG towards the required format of the route planning engine.

  • Non-standard Graph Database: Another alternative is to replace the standard RDF triple store by a graph database that has support for route plan querying (e.g. Stardog18 or Neo4J31 both with RDF support). Again the drawbacks of this approach are related to scalability and application flexibility, but they also may lead to vendor-locking issues, since they rely on non-standard solutions.

  • Speed-up Techniques: The application of speed-up techniques for shortest path algorithms, such as Contraction Hierarchies [28] or Multilevel Dijkstra [29], stands as a possible solution. These techniques rely on preprocessing steps that create summarizations of the graph topology, allowing to quickly compute long-distance path queries. They have been applied mostly to road networks graphs, where hierarchies of roads (highway, road, residential street, etc) can be used to create summaries for long distances. In principle they could also be applied to the railway topology graph. The drawbacks of these approaches are related to the introduction of additional complexity for creating the graph summaries that need to be managed and kept in sync with the original KG. However, they could still allow full flexibility for client applications to perform any business logic, since the summaries are only additional data that does not change the original RDF triples of the ERA KG.

KG based on stale sources

The KG generation process is periodically performed over stale versions of the base registry relational DBs. To accurately reflect the real state of the railway network, is necessary to capture in real-time the changes introduced into the source DBs, and immediately reflect them in the ERA KG. Other use cases such as signalling and interlocking, require precise and accurate data to guarantee safe vehicle operations. Approaches such as Linked Data Event Streams, remain to be investigated to support this requirements.

Hardcoded compatibility check rules

The compatibility check rules, were directly implemented into the source code of the RCC client application. This constitutes a limitation, given that it makes more difficult to maintain and evolve the rules. Also, it makes the rules to be indistinguishable from the application, hindering their potential reusability in other use cases. Alternatives to address this issue could explore the use of Notation3 or SHACL Rules to declaratively define the RCC rules, which can be then independently managed and published for applications such as the RCC client to consume and evaluate.

Conclusion and Future Work

The most important achievement of this work, is the strong impact it had on the decision taken by ERA10 to make Semantic Web technologies the default setting for any future development of data, registers and specifications, under the agency’s remit. Considering ERA’s position as an European authority this decision could potentially influence the different stakeholders in the railway domain, to take similar paths.

The results obtained from this work, demonstrated with a practical approach, how Semantic Web technologies enable higher data interoperability. Data integration is achieved at the data level (data-centric) instead of being locked into application-specific business logic (application-centric), opening the door for new and innovative use cases. We were able to create a semantic interoperability layer over the different considered data sources, which requires significantly less effort to be created and managed, compared to developing ad hoc applications and 1-to-1 interfaces between different information systems. Futhermore, this work also demonstrated that Semantic Web technologies can be used to create functional Web applications based on modern and developer-friendly frameworks such as React with little additional effort from a development perspective and in a reasonable time frame.

The choice of architecture design made for this prototype leverages HTTP caching mechanisms to achieve higher scalability while providing full querying flexibility to client applications. This is demonstrated by the ability of the RCC client application to perform route planning calculations over the ERA KG, which are not supported by standard RDF triple stores. Yet, this approach establishes a trade-off between scalability and flexibility vs. performance. Further optimizations are required to achieve production-level performance without losing the benefits of the proposed solution architecture.

For future work, we aim to explore how more granular descriptions of the railway topology can be integrated, to increase the reliability of the ERA KG. From an architectural perspective, stream-processing and KG virtualization approaches may be studied to support use cases with higher requirements on up-to-date data.


The authors would like to thank ProRail and SNCF for their invaluable contributions to this work.