Related subschemas: RS
Reported by: SNCF Réseau
|For general information on use cases see UC:Use cases
Use case / Anwendungsfall
railML® for RINF Reporting; railML® für RINF Meldung
Description / Beschreibung
This use case aims at providing a railML3 file, fulfilling the functional requirements published by ERA for RINF data, including all concepts and data required. In a first step, considering the current non-acceptance of the railML® standard by ERA, this railML3 file will be translated by a railML_TO_RINF translator tool, supported by the community, into the ERA RINF-XML format, as currently done for railML2.2 files. The objective, in a second step, is to get ERA to accept railML3 file as an alternative to the specific ERA RINF-XML, and therefore support and maintain natively the railML3 RINF file description according to the evolutions of the project.
The railML3 file for RINF should be structured in two parts
- First part being the generic description of infrastructure topology, geometry, installations and attributes (no specificity relative to RINF, re-usable for any other description of infrastructure, e.g. ETCS)
- Second part supporting all specific parameters of RINF file
The detailed functional specification is the latest official version of RINF Application Guide published by ERA RINF project team.
Data Flows and Interfaces / Datenflüsse und Schnittstellen
The railML for RINF file will be produced by Infrastructure Managers from their national repository or by National Register Entity (NRE) after merging of multiple railML files produced by each IM.
|Topology (Section Of Lines, Operational Points,…)
|IM Repository or National Repository
|Geometry and geography
|Installation and equipments (existence and properties)
Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen
- rolling stock
The main interaction, not directly related to the file specification, is about functional description and qualification of parameters related to compatibility between infrastructure and rolling stock. railML.org should ensure the consistency on definition of parameters on both sides.
Characterizing Data / Charakterisierung der Daten
refer to RINF Application guide
How often do the data change (update)?
quarterly (European Decision)
How big are the data fragments to be exchanged (complexity)?
to be completed based on railML2.2 for RINF
Which views are represented by the data (focus)?
Which specific data do you expect to receive/send (elements)?
Fill in your application-specific data structure elements, which you want to see modelled in railML® 3.