railML
railML (Railway Markup Language) is an open, XML based data exchange format for data interoperability of railway applications.[1]
Logo of railML file format | |
Filename extensions |
.railml, .railmlx |
---|---|
Internet media type | application/xml, text/xml, application/zip |
Developed by | railML.org; Dresden / Germany |
Initial release | 22 December 2005 |
Latest release | 3.1 (19 February 2019 ) |
Type of format | Railway exchange format |
Extended from | XML |
Standard | Industry standard |
Open format? | Yes, CC BY-NC-ND |
Website | www.railml.org |
Motivation
The growing number of computer applications modeling different aspects of railway operations, with different operators developing separate solutions parallelly, bore a chronic difficulty of connecting different railway IT applications.[1] The exchange of data for operation concepts, slot management, simulation or infrastructure planning, etc. was possible either by hand or with a lot of special developed interfaces with loss of time and cost problems for railway companies.[2] If there are n applications that are supposed to exchange data, with a special interface for each pair of programs respectively, interfaces are required — only one, if n=2, but 10, if n=5 — increasing the complexity above average.[1]
This problem can be mitigated by means of Enterprise application integration[1] with a single, universal exchange format that is supported by all applications and meets the needs of all kinds of data exchange in the field of railway operation: The number of required interfaces decreases to n — one interface to the exchange format for each application respectively. railML tries to place at disposal an open and free, easy and handy, self-describing format close to existing standards.[2] The paradigm is to meet the demands of the data exchange processes of railways, industry and authorities rather than describing the complete railway system.[3]
Outline
History
The development of railML was initiated in early 2002 by the Fraunhofer-IVI (Dresden, Germany) and the ETH Zürich - IVT (Zurich, Switzerland) against the background of the chronic difficulty of connecting different railway IT applications.[4] railML is changed and adapted to the needs of railway infrastructure managers (IM's) and railway undertakings (RU's) within discussions.[2][5] The first stable version 1.0 was released in 2005 for productive usage.[3] Up to now the versions 1.0; 1.1; 2.0 to 2.4 were released for download and productive use. railML's version 3 with a new topology model based on RailTopoModel and other evolutions was under development since mid 2015 to be released as beta in mid 2016[6] and finally released for productive use in February 2019. In 2015 a viewer and validator programme for railML data named railVIVID was released.
Working principle
railML (railway mark-up language) is a common exchange format, which employs the systematic of XML for the description of rail-specific data. railML enables the exchange of railway data between internal and external railway applications. railML is developed within the so-called “railML consortium” from railML.org. It is an open source exchange format under creative commons license (A free registration on railML is mandatory for the usage and download of railML schemes). The model language of railML is UML and the documentation language is English. Every railML developer and user is invited to contribute or propose scheme extensions.
Applications can exchange data via railML either via exporting respectively importing railML files, or as a direct Inter-process communication via TCP/IP.[7]
Licensing and pricing
The usage of railML is possible at no charge for the users and developers, only consulting and certification for professional usage could be liable to pay costs for the software developer.[8]
Versions 0.x and 1.x were licensed under a proprietary license, where version 0.x was intended only for internal use and shared within the consortium.[9]
Version 2.0 to 2.2 used to be licensed with the Creative Commons license CC-BY-NC-SA until June 2013. Since July 2013 all versions from 2.0 onward were offered parallelly either with a commercial usable CC-BY-ND (V 3) license or with a restricted CC-BY-NC-ND (V 3) license. The restrictions serve quality measures, e.g. by requiring applications to be certified to grant for smooth interoperability.[9]
Version 3.x is licensed under the same Creative Commons conditions, but in CC version 4.0. With this railML.org adapts the enhancements made by CC and garanties schema user the same usage rights as in previous years and railML versions.[10]
The Logo and the word railML are a registered as trademarks by the railML consortium at the EUIPO.[9]
Legal entity
Legal entity for the so-called railML consortium is the railML.org e.V. a registered non-profit association by German law (registration number VR 5750 at the local court in Dresden/Germany) since April 23, 2012.
railML schemes
railML is based on XML and sub-areas use other existing XML-schemes such as MathML and GML. It is composed of sub-schemes. Through version 2.4, three sub-schemes are in productive use:
- timetable for the description of timetables,
- infrastructure for the (priority topological) description of tracks and signalling equipment and
- rolling stock for the description of vehicles.
Since railML version 3.1 an additional sub-scheme was introduced due to the demand of the community:
- interlocking for the description of signaling routes
Additional sub-schemes are station facilities (ticket machines, waiting rooms, vending machines, etc.) or crew rostering (shift planning/rosters and working time management for conductors, etc.) are currently on hold, as there is no demand from the users.
Timetable
This sub-schema serves the exchange of detailed timetables. Particularly, the schema is designed for the following information:[11]
- Train running times (arrivals, departures and passing times)
- Operating Periods: the days on which a train is operated
- Train Parts: scheduling and routing information for through coaches in trains, e.g. the Orient Express on the traject from Budapest to Beograd on Mondays.
- Trains: a collection of train parts, adding up to the colloquial perspective, e.g. the Orient Express.
- Rostering: Circulation plans for rolling stock, linked with Train Parts.
Infrastructure
The focus of this sub-schema is the infrastructure of railway networks.[12] Important aspects are:
- Network Topology
- Coordinates
- Geometry: track geometry (gradient, curve radius)
- Railway infrastructure elements: inventory like balises and signals
- Further located elements: abstract things that cannot be touched but located, like speed limits and track condition
Rolling stock
While the Infrastructure sub-schema is focused on immobile assets, Rolling stock describes assets circulating in the network.[13]
- Vehicles
- Formations: the combination of vehicles as a train
- Tractive effort of locomotives and motor units
Interlocking
- Signal aspects derived from train routes through stations
Code example
Example for a time table formulated in railML[3]
<?xml version="1.0" encoding="UTF-8"?>
<railml xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" xsi:noNamespaceSchemaLocation="timetable.xsd">
<timetable version="1.1">
<train trainID="RX 100.2" type="planned" source="opentrack">
<timetableentries>
<entry posID="ZU" departure="06:08:00" type="begin"/>
<entry posID="ZWI" departure="06:10:30" type="pass"/>
<entry posID="ZOER" arrival="06:16:00" departure="06:17:00" minStopTime="9" type="stop"/>
<entry posID="WS" departure="06:21:00" type="pass"/>
<entry posID="DUE" departure="06:23:00" type="pass"/>
<entry posID="SCW" departure="06:27:00" type="pass"/>
<entry posID="NAE" departure="06:29:00" type="pass"/>
<entry posID="UST" arrival="06:34:30" type="stop"/>
</timetableentries>
</train>
</timetable>
</railml>
Line 3 expresses that the employed railML-version is 1.1.
Line 4 bears the train code.
Lines 5 and 15 frame the itinerary with, in this case, 8 itinerary entries.
The itinerary entries in line 6 to 14 have arguments like position ID (e.g. a station), time of departure or arrival, and in line 9 an obligation to stop.
Versions
Version | Release date[3] | Supported until[9] | Licence[9] | Comment | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0.x | 2002-2005 | December 2005 | No (internal usage only) | beta version timetable | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1.0 | December 2005 | June 2013 | proprietary | First practical experience | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1.1 | November 2007 | June 2013 | proprietary | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2.0 | November 2009 | March 2017 | restricted CC-BY-ND 2.0 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2.1 | July 2011 | March 2017 | restricted CC-BY-ND 2.0 | Downwardly compatible with V2.0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2.2 | June 11, 2013[14] | June 30, 2021[15] | restricted CC-BY-NC-ND 3.0 | Downwardly compatible with V2.1-V2.0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2.3 | March 10, 2016 | restricted CC-BY-NC-ND 3.0 | Predominant downward compatible with V2.2-V2.0 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2.4 | October 7, 2018 | restricted CC-BY-NC-ND 3.0 | Predominant downward compatible with V2.3-V2.0 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2.5 | End of 2020[16] | restricted CC-BY-NC-ND 3.0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3.0 | October 31, 2017[17] | February 19, 2019[16] | No (internal usage only) | based on UIC's RailTopoModel V1.1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3.1 | February 19, 2019[16] | restricted CC-BY-NC-ND 4.0 | based on UIC's RailTopoModel V1.2 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3.2 | not yet decided (≥ 2021)[16] | restricted CC-BY-NC-ND 4.0 | based on UIC's RailTopoModel V1.x | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3.3 | not yet decided | restricted CC-BY-NC-ND 4.0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Old version Older version, still maintained Latest version Latest preview version Future release |
Usage of railML data
At the beginning the most employed usage of railML data was timetable data[4] for passenger information, duty planning for conductors and drivers and timetable simulation, following the usage of railML data for interlocking planning and infrastructure like network statements of IM's.
Computer programmes
Applications using railML version 2.x include a lot of timetable related programmes like OpenTrack (interactive railway simulator[18]), FBS (planning software for railway operation[19]), Viriato (scheduling system[20]) and OpenTimeTable (real time analysis of network operation data[21]). Applications using railML version 3.x include additionally BIM related infrastructure planning software like VIS All 3D[22] or railway survey systems like GPSinfradat.[23]
A complete list of programmes with (certified) interfaces is available at railML's website of compatible applications.
railVIVID
railVIVID is an open source freeware tool provided by UIC and railML.org to validate railML files of version 2.x or higher and to show the content of railML files in some special views. This shall give also non-IT-experts an easy and handy access to railML data. Therefore, some sights of railway data can be shown, copied and printed with railVIVID:[24]
- Graphic viewer for Timetable data
- Tabular viewer for Timetable data with spreadsheet export
- Rolling Stock data viewer
- Topologic viewer for Infrastructure data
- Geographic viewer for Infrastructure data
- Schema validator for railML
railVIVID is available via railML's website for free. There are binary versions for MS Windows and Java, also the source code was published in Autumn 2015 under the EUPL licence.[25]
railML.org initiative
The development of railML is driven by the railML.org – Initiative, a development partnership of independent companies and organizations and European railways. The participation on the development and semi-annual conferences to exchange experience and discuss basics is open. The continuous development work is mainly internet-based (German and English forums). The organisation of the discussions is managed by so-called railML Coordinators. The (free) membership of the railML.org Consortium is mandatory for the download and usage of railML schemes. Obtaining a commercial certification is required before any commercial or productive use of software interfaces for the format.[26]
Members
Members of railML.org are currently:[27]
- Railways like Austrian Federal Railways, BLS, French Railways, German State Railway, Infrabel, Norwegian Rail Infrastructure Manager, Swiss Federal Railways, ...
- Software manufacturers like Hacon (Hanover/Germany), iRFP (Dresden/Germany), PTV (Karlsruhe/Germany), SMA (Zurich/Switzerland), Trapeze Group (Hamburg/Germany), Siemens (Brunswick/Erlangen/Germany), Thales (Berlin & Ditzingen/Germany), ...
- Authorities like Bavarian Passenger Transport Authority (Munich/Germany), Federal Ministry of Transport and Digital Infrastructure (Berlin/Germany), High Speed Two (London/Great Britain), Jernbanedirektoratet (Oslo/Norway), ...
- Universities and Research institutes like Czech Technical University Prague, Dresden University, DLR, ETH Zurich, University of Birmingham, ...
A complete and updated list is published at the website of railML.org community.
Cooperations
railML.org works in the ERIM (abbreviation for European Rail Infrastructure Masterplan[28]) project of the International Union of Railways (UIC) for the development of a common data model in the railway sector.[29] Also railML.org cooperates with Eurocontrol and European Union Agency for Railways.
References
- , p. PA4, at Google Books
- "RailTopoModel and railML®" (PDF). uic.org. Retrieved 2016-01-26.
- "Daten für PSItraffic: Standardisiertes Datenmanagement mit railML® und dem UIC RailTopoModel" (PDF). psitrans.de. Archived from the original (pdf) on 2016-03-06. Retrieved 2015-10-20.
- Nash, Andrew; Huerlimann, Daniel; Schuette, Joerg; Kolmorgen (Krauss), Vasco Paul (2004). RailML – A standard data interface for railroad applications (PDF). Dresden: Proc. of the 9th International Conference on Computer in Railways (Comprail IX), WIT Press, Southampton, United Kingdom.
- , p. PA5, at Google Books
- "5th UIC RailTopoModel and railML® Conference" (PDF). railML. 2016-02-01. p. 29.
- , p. PA6, at Google Books
- "railML - Costs". railML.org. railML.org. 2019-03-15. Retrieved 2019-03-23.
- "Licence - railML.org (EN)". railml.org. Retrieved 2016-01-26.
- Augele, Vivian (2019-01-29). "railML Licence: Minor Changes come with railML3". www.railML.org. railML.org; Dresden/Germany. Retrieved 2019-03-23.
- "Timetable - railML.org (EN)". railml.org. Retrieved 2016-01-26.
- "Infrastructure - railML.org (EN)". railml.org. Retrieved 2016-01-26.
- "Rollingstock - railML.org (EN)". railml.org. Retrieved 2016-01-26.
- Susanne Wunsch, Vasco Paul Kolmorgen; et al. (18 September 2013). "News of railML common parts on 24th railML.org meeting" (PDF). The railML.org initiative. railML.org e.V.; Dresden/Germany. p. 6. Retrieved 21 May 2017.
- Kolmorgen, Vasco Paul (2019-06-30). "Scheme Planning and Lifecycle Policy / V2.2 Support Termination". railML.org News. Retrieved 2019-09-03.
- "railML Version Timeline". railML.org Website. Retrieved 2020-03-10.
- Augele, Vivian (2017-11-15). "Public Presentation of railML 3.1 during 32nd railML Conference". railML.org News. Retrieved 2017-11-25.
- "OpenTrack Railway Technology - Eisenbahnsimulation". opentrack.ch. Retrieved 2015-10-20.
- Christian Roessiger (15 September 2016). "railML Schnittstelle - Institut für Regional- und Fernverkehrsplanung" (in German). iRFP e.K.; Dresden/Germany. Retrieved 21 May 2017.
- "Software für die Eisenbahn". sma-partner.ch. Retrieved 2015-10-20.
- "OpenTimeTable". via-con.de. Retrieved 2015-10-20.
- "VIS-All® 3D- der einfache Weg in die 3D-Welt!". Software-Service John (in German). Retrieved May 21, 2017.
- "GPSinfradat". Bahnkonzept Dresden/Germany. Retrieved 2019-04-19.
- "railVIVID - railML.org (EN)". railml.org. Retrieved 2016-01-26.
- SNCF Réseau and TU Dresden (April 28, 2015). "4th UIC RailTopoModel and railML Conference: Achievements" (PDF).
- "Certification - railML.org (EN)". www.railml.org. Retrieved 2019-04-19.
- "Partners - railML.org (EN)". railml.org. Retrieved 2016-01-26.
- https://www.railml.org/en/public-relations/news/reader/functioning-of-railml-org-and-railtopomodel.html
- "UIC e-news 362: The foundation for a Universal Infrastructure Data Exchange Format". November 30, 2014.