| Railway Markup Language | |
| Iconcaption: | Logo of railML file format |
| Icon Size: | 200px |
| Extensions: | .railml, .railmlx |
| Owner: | railML.org |
| Developer: | railML.org; Dresden / Germany |
| Latest Release Version: | 3.2 |
| Genre: | Railway exchange format |
| Extended From: | XML |
| Standard: | Industry standard |
| Open: | No, CC BY-NC-ND with restrictions |
| Url: | www.railml.org |
railML (Railway Markup Language) is a proprietary freeware XML Schema-based data exchange format for data interoperability of railway applications.
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. 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. If there are n applications that are supposed to exchange data, with a special interface for each pair of programs respectively,
| n ⋅ (n-1) | |
| 2 |
This problem can be mitigated by means of enterprise application integration 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 a free and self-describing format close to existing standards. The paradigm is to meet the demands of the data exchange processes of railways, industry and authorities rather than describing the complete railway system.
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.[1] railML is changed and adapted to the needs of railway infrastructure managers (IMs) and railway undertakings (RUs) within discussions.[2] 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.5 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[4] and finally released with 3.1 for productive use in February 2019 and evolved to 3.2 in 2022.In 2015 a viewer and validator programme for railML data named railVIVID was released.
railML (railway mark-up language) is a common exchange format, which employs 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. 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.
The usage of railML is possible at no charge as long as users register at railML.org, do not redistribute or modify the code, and do not use railML commercially. It is a free data exchange format but not open due to being licensed under a heavily restricted and non-permissive Creative Commons license.
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.
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 organization behind railML claims that the restrictions preventing redistribution and modifications are for quality control purposes, the means of which is requiring application developers to purchase a certification.
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.[5]
The Logo and the word railML are a registered as trademarks by the railML consortium at the EUIPO.
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 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:
Since railML version 3.1 an additional sub-scheme was introduced due to the demand of the community:
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.
This sub-schema serves the exchange of detailed timetables. Particularly, the schema is designed for the following information:[6]
The focus of this sub-schema is the infrastructure of railway networks.[7] Important aspects are:
While the Infrastructure sub-schema is focused on immobile assets, Rolling stock describes assets circulating in the network.[8]
Example for a time table formulated in railML[3]
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.
| Version | Release date | Supported until[9] | Licence | Comment | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002–2005 | December 2005 | No (internal usage only) | beta version timetable | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| December 2005 | June 2013 | proprietary | First practical experience | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| November 2007 | June 2013 | proprietary | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| November 2009 | March 2017 | restricted CC-BY-ND 2.0 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| July 2011 | March 2017 | restricted CC-BY-ND 2.0 | Downwardly compatible with V2.0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| June 11, 2013[10] | June 30, 2021[11] | restricted CC-BY-NC-ND 3.0 | Downwardly compatible with V2.1-V2.0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| March 10, 2016 | June 30, 2024[12] | restricted CC-BY-NC-ND 3.0 | Predominant downward compatible with V2.2-V2.0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| October 7, 2018 | restricted CC-BY-NC-ND 3.0 | Predominant downward compatible with V2.3-V2.0 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| September 1, 2021[13] | restricted CC-BY-NC-ND 3.0 | Predominant downward compatible with V2.4-V2.0 Also adopted as an ISO 4398:2022 standard[14] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| October 31, 2017[15] | February 19, 2019[16] | No (internal usage only) | based on UIC's RailTopoModel V1.1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| February 19, 2019 | restricted CC-BY-NC-ND 4.0 | based on RailTopoModel V1.2 Infrastructure and Signalling data only | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| April 26, 2022 | restricted CC-BY-NC-ND 4.0 | based on RailTopoModel V1.4 added support of Timetable and Rolling stock data | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ≥ 2023 | restricted CC-BY-NC-ND | based on RailTopoModel | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| not yet decided | restricted CC-BY-NC-ND | based on RailTopoModel | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
At the beginning the most employed usage of railML data was timetable data 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.
Applications using railML version 2.x include a lot of timetable related programmes like OpenTrack (interactive railway simulator[17]), FBS (planning software for railway operation[18]), Viriato (scheduling system[19]) and OpenTimeTable (real time analysis of network operation data[20]). Applications using railML version 3.x include additionally BIM related infrastructure planning software like VIS All 3D[21] or railway survey systems like GPSinfradat.[22]
A complete list of programmes with (certified) interfaces is available at railML's website of compatible applications.
railVIVID is a free 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. The intention of the tool is to allow less technical users access to data described in railML. Therefore, some sights of railway data can be shown, copied and printed with railVIVID:[23]
railVIVID is available via railML's website under terms similar to those of the railML schema. There are binary versions for Microsoft Windows and Java, also the source code was published in Autumn 2015 under the EUPL licence.[24]
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 railML.org Consortium membership 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.[25]
Members of railML.org are currently:[26]
A complete and updated list is published at the website of railML.org community.
railML.org works in the ERIM (abbreviation for European Rail Infrastructure Masterplan[27] ) project of the International Union of Railways (UIC) for the development of RailTopoModel as a common data model in the railway sector.[28] Also railML.org cooperates with Eurocontrol and European Union Agency for Railways.