Figure 1 shows the main classes and properties of this ontology, which represent concepts related to the railway infrastructure in RINF and their interactions with other domains.

ERA ontology overview — Figure 1. Conceptual model for the representation of the information related to the railway infrastructure

Figure 2 shows the new topology with location and positioning for micro-level.

ERA topology overview — Figure 2. Conceptual model for locating and positioning infrastructure elements on the topology

Figure 3 shows the functional diagram with technical characteristics classes.

ERA functional diagram — Figure 3. Functional diagram with technical characteristics

The ontology is also aligned with routebook concepts from Appendix D2 in Commission Implementing Regulation (EU) 2019/773 on the technical specification for interoperability relating to the operation and traffic management subsystem of the rail system within the European Union.

Routebook classes include, for example, signals (era:Signal) and special areas such as safe or restricted areas (era:SpecialArea). Most routebook concepts are represented as properties. Examples are era:operatingLanguage that corresponds to "3.5.1 Operating language", or era:hasWalkway corresponding to "3.2.3 Tunnels: location, name, length, specific information such as the existence of walkways and points of safe egress".

Some concepts in the ontology are also RINF, such as era:SectionOfLine, which maps to routebook concept "2.1.1 Line sections". Another example is era:etcsDegradedSituation, covering both RINF 1.1.1.3.10.1 and routebook concept "3.1.7 Means of communication with the traffic management/control centre in normal, degraded and emergency situations". Implementations reference Appendix D2 via the annotation property era:appendixD2Index.

The ontology also includes parameters from Appendix D3 on ERTMS trackside engineering information relevant to operation. For example, era:dNvovtrp represents the maximum distance for overriding the train trip, aligned with concept 1.5.5. These are documented under era:appendixD3Index, with further details in Subset 26, chapter 7.

Some classes represent track parameters constituted by multiple properties. For example, era:LoadCapability combines era:loadCapabilityLineCategory and era:loadCapabilitySpeed. Each track can have several load capability resources with values for category and speed.

The ontology also reuses external ontologies such as Time Ontology (for temporal aspects), Organization Ontology (for roles), and OGC GeoSPARQL (for geospatial elements). Figure 5 illustrates these external classes.

external classes ERA ontology — Figure 5. External classes reused in the ontology

ERA Ontology: Description back to ToC