General repository for Rail System Model. RSM, also "semantic RSM", is the successor model of RTM (IRS30100: 2016).
Reasons for evolution are multiple:
- extended coverage, esp. railway operations
- changed technology: RSM uses ontologies (RDF/OWL) rather than class diagrams (UML).
- cooperation with, or explicit re-use of other models
- licensing conditions (currently: CC BY SA 4.0, by default)
RSM is modular. The modules can be:
- Domain ontologies with a clear focus on one aspect of the railway domain (e.g. network topology, rolling stock consist, ...)
- adapter ontologies, helping align RSM semantics with external ontologies
- helper ontologies, for want of widely shared ontologies about apects that are not specific to railways
- SKOS concept schemes; in our context, these are mostly the equivalent of "enumerations" or "enumerated classes"
RSM modules make use of various external ontologies for things that are not railway-specific, such as:
- upper ontology: DOLCE+DnS Ultralite, about physical objects, information objects, events, processes, situations, etc.
- ancillary ontologies:
- QUDT, about quantities, units, uncertainties and tolerances
- GeoSPARQL, about geograhic features, their geometries, and geometry data serialisation
- SOSA/SSN, about sensors, actuators, and sampling
Following modules are the continuation of former RTM/RSM works:
- Topology :
- Localisation
- Network
In addition to the above, following modules were derived from existing works:
- Signalling: EULYNX DapaPrep 1.2 (UML) automated conversion into OWL
- Linear referencing: manually derived from ISO 19148 (which is UML-based)
The former RTM positioning package does no longer exist as such, as it is split between GeoSPARQL (geographic positioning), RSM-LinearReferencing, and local cartesian coordinates available either under RSM-Localisation, or in future links with IfcOwl or similar.
- Rolling stock consist, about oriented vehicles in oriented formations or trainsets
- Rolling stock typology, about locomotives, wagons, and their capabilities (not: vehicles types in the sense of ERA-TV)
- Operations ontology (not broken down yet)
- List ontology, derived from the list ontology used by IfcOwl
- Parts and views ontology, dealing with mereology
- Ontology visual representation: GRAPHOL
- Ontology design: EDDY 3.8, a desktop GRAPHOL-based editor
- Ontology formal verification:
- Protégé Desktop with Pellet and HermiT reasoners
- ROBOT ontology and OWL profile checker (command-line tool, used by OntoQA template)