railML

<h2 id="motivation">Motivation</h2>

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.<a class="footnote-ref" id="fnref:2" href="#fn:2">2</a> 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.<a class="footnote-ref" id="fnref:3" href="#fn:3">3</a> 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
 
 
 
 
 {\displaystyle {\frac {n\cdot (n-1)}{2}}}
 
 interfaces are required—only one, if n=2, but 10, if n=5—increasing the complexity above average.<a class="footnote-ref" id="fnref:4" href="#fn:4">4</a>
This problem can be mitigated by means of <a href="/facts/Enterprise_application_integration/EaXMz4mI">enterprise application integration</a><a class="footnote-ref" id="fnref:5" href="#fn:5">5</a> 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.<a class="footnote-ref" id="fnref:6" href="#fn:6">6</a> The paradigm is to meet the demands of the data exchange processes of railways, industry and authorities rather than describing the complete railway system.<a class="footnote-ref" id="fnref:7" href="#fn:7">7</a>

<h2 id="outline">Outline</h2>
<h3>History</h3>
The development of railML was initiated in early 2002 by the <a href="/facts/Fraunhofer_Society/JS0cK2Qo">Fraunhofer-IVI</a> (Dresden, Germany) and the <a href="/facts/ETH_Zurich/IxHAFGUU">ETH Zürich – IVT</a> (Zurich, Switzerland) against the background of the chronic difficulty of connecting different railway IT applications.<a class="footnote-ref" id="fnref:8" href="#fn:8">8</a> railML is changed and adapted to the needs of railway infrastructure managers (IMs) and railway undertakings (RUs) within discussions.<a class="footnote-ref" id="fnref:9" href="#fn:9">9</a><a class="footnote-ref" id="fnref:10" href="#fn:10">10</a> The first stable version 1.0 was released in 2005 for productive usage.<a class="footnote-ref" id="fnref:11" href="#fn:11">11</a> 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, incorporating a new topology model based on the <a href="/facts/RailTopoModel/lYr8Mk1o">RailTopoModel</a>, underwent development starting in mid-2015. The beta version was released in mid-2016,<a class="footnote-ref" id="fnref:12" href="#fn:12">12</a> followed by the full release of version 3.1 for productive use in February 2019. The schema evolved further, with version 3.2 being released in 2022, and the latest version 3.3, launched in 2024, based on RailTopoModel v1.5. This version introduced new enhancements, consolidating the evolution of the railML format. Additionally, in 2015, <a href="/facts/File_viewer/H7CWQ3EH">viewer</a> and <a href="/facts/Validator/WUBnT6QT">validator</a> for railML data, named railVIVID, was released.

<h3>Working principle</h3>
railML (railway mark-up language) is a common exchange format, which employs <a href="/facts/XML/clNgUfWk">XML</a> 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 <a href="/facts/Unified_Modeling_Language/3tlNS0tH">UML</a> and the documentation language is English. Every railML developer and user is invited to contribute or propose schema extensions.
Applications can exchange data via railML either via exporting respectively importing railML files, or as a direct <a href="/facts/Inter-process_communication/cIQYyT6y">inter-process communication</a> via <a href="/facts/TCP%2fIP/KNkxtSpw">TCP/IP</a>.<a class="footnote-ref" id="fnref:13" href="#fn:13">13</a>

<h3>Licensing and pricing</h3>
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 <a href="/facts/Creative_commons_license/6AV3V7UJ">Creative Commons license</a>.
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.<a class="footnote-ref" id="fnref:14" href="#fn:14">14</a>
Version 2.0 to 2.2 used to be licensed with the <a href="/facts/Creative_Commons/b1fKDQHE">Creative Commons</a> license <a href="/facts/Creative_Commons_license/6AV3V7UJ">CC-BY-NC-SA</a> until June 2013. Since July 2013 all versions from 2.0 onward were offered parallelly either with a commercial usable <a href="/facts/CC-BY-NC-ND/6AV3V7UJ">CC-BY-ND</a> (V 3) license or with a restricted <a href="/facts/CC-BY-NC-ND/6AV3V7UJ">CC-BY-NC-ND</a> (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.<a class="footnote-ref" id="fnref:15" href="#fn:15">15</a>
Version 3.x is licensed under the same Creative Commons conditions, but in <a href="/facts/Creative_Commons/b1fKDQHE">CC</a> 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.<a class="footnote-ref" id="fnref:16" href="#fn:16">16</a>
The <a href="/facts/Logo/nUlH9REj">Logo</a> and the word railML are a registered as trademarks by the railML consortium at the <a href="/facts/European_Union_Intellectual_Property_Office/abTgMDgk">EUIPO</a>.<a class="footnote-ref" id="fnref:17" href="#fn:17">17</a>

<h3>Legal entity</h3>
Legal entity for the so-called railML consortium is the railML.org e.V. a registered <a href="/facts/Nonprofit_organization/AmXu2c85">non-profit association</a> by <a href="/facts/B%25C3%25BCrgerliches_Gesetzbuch/3yp6KL5t">German law</a> (registration number VR 5750 at the <a href="/facts/Amtsgericht/JcLT653z">local court</a> in <a href="/facts/Dresden/nKVXxIgq">Dresden</a>/Germany) since April 23, 2012.

<h2 id="railml-schemas">railML schemas</h2>
railML is based on XML and sub-areas use other existing XML-schemas such as <a href="/facts/MathML/uKRIc3Fy">MathML</a> and <a href="/facts/Geography_Markup_Language/IEMlqp0s">GML</a>. It is composed of sub-schemas. Through version 2.4, three sub-schemas are in productive use:

<ul><li><a href="/facts/Public_transport_timetable/aMv9AR8L">timetable</a> for the description of timetables,</li>
<li>infrastructure for the (priority topological) description of tracks and signalling equipment and</li>
<li><a href="/facts/Rolling_stock/xe66VHGf">rolling stock</a> for the description of vehicles.</li></ul>
Since railML version 3.1 an additional sub-schema was introduced due to the demand of the community:

<ul><li><a href="/facts/Interlocking/g8P6RfgC">interlocking</a> for the description of signaling routes</li></ul>
Additional sub-schemas are station facilities (<a href="/facts/Ticket_machine/9UTFXE2u">ticket machines</a>, <a href="/facts/Waiting_room/sRKhEu2e">waiting rooms</a>, <a href="/facts/Vending_machine/3YNz3yKU">vending machines</a>, etc.) or <a href="/facts/Employee_scheduling_software/LHvYPUzp">crew rostering</a> (<a href="/facts/Shift_plan/UuAt3pwL">shift planning</a>/rosters and working time management for <a href="/facts/Conductor_(rail)/1FC9Gvk9">conductors</a>, etc.) are currently on hold, as there is no demand from the users.

<h3>Timetable</h3>
This sub-schema serves the exchange of detailed timetables. Particularly, the schema is designed for the following information:<a class="footnote-ref" id="fnref:18" href="#fn:18">18</a>

<ul><li>Train running times (arrivals, departures and passing times)</li>
<li>Operating Periods: the days on which a train is operated</li>
<li>Train Parts: scheduling and routing information for <a href="/facts/Through_coach/XW4uhC8u">through coaches</a> in trains, e.g. the <a href="/facts/Orient_Express/pjfLGCsm">Orient Express</a> on the traject from <a href="/facts/Budapest/VdcUAkxm">Budapest</a> to <a href="/facts/Beograd/Xeaz5zIy">Beograd</a> on Mondays.</li>
<li>Trains: a collection of train parts, adding up to the colloquial perspective, e.g. the Orient Express.</li>
<li>Rostering: Circulation plans for rolling stock, linked with Train Parts.</li></ul>
<h3>Infrastructure</h3>
The focus of this sub-schema is the infrastructure of railway networks.<a class="footnote-ref" id="fnref:19" href="#fn:19">19</a> Important aspects are:

<ul><li><a href="/facts/Network_topology/rBYE0kke">Network topology</a></li>
<li><a href="/facts/Coordinate/Mtd0q4SP">Coordinates</a></li>
<li>Geometry: track geometry (gradient, curve radius)</li>
<li>Railway infrastructure elements: inventory like <a href="/facts/Balise/y7whlhf5">balises</a> and signals</li>
<li>Further located elements: abstract things that cannot be touched but located, like speed limits and track condition</li></ul>
<h3>Rolling stock</h3>
While the Infrastructure sub-schema is focused on immobile assets, Rolling stock describes assets circulating in the network.<a class="footnote-ref" id="fnref:20" href="#fn:20">20</a>

<ul><li>Vehicles</li>
<li>Formations: the combination of vehicles as a train</li>
<li><a href="/facts/Tractive_effort/8ws6qyt3">Tractive effort</a> of locomotives and motor units</li></ul>
<h3>Interlocking</h3>
<ul><li><a href="/facts/Signal_aspect/NkCzHKtd">Signal aspects</a> derived from train routes through stations</li></ul>
<h3>Code example</h3>
Example for a time table formulated in railML<a class="footnote-ref" id="fnref:21" href="#fn:21">21</a>

<?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.

<h3>Versions</h3>
<table><tbody><tr><th>Version</th><th>Release date<a class="footnote-ref" id="fnref:22" href="#fn:22">22</a></th><th>Supported until<a class="footnote-ref" id="fnref:23" href="#fn:23">23</a></th><th>Licence<a class="footnote-ref" id="fnref:24" href="#fn:24">24</a></th><th>Comment</th></tr><tr><td>Old version, not maintained: 0.x</td><td>2002–2005</td><td>December 2005</td><td>No (internal usage only)</td><td>beta version timetable</td></tr><tr><td>Old version, not maintained: 1.0</td><td>December 2005</td><td>June 2013</td><td>proprietary</td><td>First practical experience</td></tr><tr><td>Old version, not maintained: 1.1</td><td>November 2007</td><td>June 2013</td><td>proprietary</td><td></td></tr><tr><td>Old version, not maintained: 2.0</td><td>November 2009</td><td>March 2017</td><td>restricted <a href="/facts/CC-BY-ND/6AV3V7UJ">CC-BY-ND</a> 2.0</td><td></td></tr><tr><td>Old version, not maintained: 2.1</td><td>July 2011</td><td>March 2017</td><td>restricted <a href="/facts/CC-BY-ND/6AV3V7UJ">CC-BY-ND</a> 2.0</td><td>Downwardly compatible with V2.0</td></tr><tr><td>Old version, not maintained: 2.2</td><td>June 11, 2013<a class="footnote-ref" id="fnref:25" href="#fn:25">25</a></td><td>June 30, 2021<a class="footnote-ref" id="fnref:26" href="#fn:26">26</a></td><td>restricted <a href="/facts/CC-BY-NC-ND/6AV3V7UJ">CC-BY-NC-ND</a> 3.0</td><td>Downwardly compatible with V2.1-V2.0</td></tr><tr><td>Old version, not maintained: 2.3</td><td>March 10, 2016</td><td>June 30, 2024<a class="footnote-ref" id="fnref:27" href="#fn:27">27</a></td><td>restricted <a href="/facts/CC-BY-NC-ND/6AV3V7UJ">CC-BY-NC-ND</a> 3.0</td><td>Predominant downward compatible with V2.2-V2.0</td></tr><tr><td>Old version, still maintained: 2.4</td><td>October 7, 2018</td><td>November 30, 2026<a class="footnote-ref" id="fnref:28" href="#fn:28">28</a></td><td>restricted <a href="/facts/CC-BY-NC-ND/6AV3V7UJ">CC-BY-NC-ND</a> 3.0</td><td>Predominant downward compatible with V2.3-V2.0</td></tr><tr><td>Old version, still maintained: 2.5</td><td>September 1, 2021<a class="footnote-ref" id="fnref:29" href="#fn:29">29</a></td><td>August, 2028<a class="footnote-ref" id="fnref:30" href="#fn:30">30</a></td><td>restricted <a href="/facts/CC-BY-NC-ND/6AV3V7UJ">CC-BY-NC-ND</a> 3.0</td><td>Predominant downward compatible with V2.4-V2.0Also adopted as an <a href="/facts/International_Organization_for_Standardization/IacYR7Yg">ISO</a> 4398:2022 standard<a class="footnote-ref" id="fnref:31" href="#fn:31">31</a></td></tr><tr><td>Old version, not maintained: 3.0</td><td>October 31, 2017<a class="footnote-ref" id="fnref:32" href="#fn:32">32</a></td><td>February 19, 2019<a class="footnote-ref" id="fnref:33" href="#fn:33">33</a></td><td>No (internal usage only)</td><td>based on <a href="/facts/International_Union_of_Railways/oSlgdIJk">UIC</a>'s <a href="/facts/RailTopoModel/lYr8Mk1o">RailTopoModel</a> V1.1</td></tr><tr><td>Old version, still maintained: 3.1</td><td>February 19, 2019<a class="footnote-ref" id="fnref:34" href="#fn:34">34</a></td><td>January, 2026<a class="footnote-ref" id="fnref:35" href="#fn:35">35</a></td><td>restricted <a href="/facts/CC-BY-NC-ND/6AV3V7UJ">CC-BY-NC-ND</a> 4.0</td><td>based on <a href="/facts/RailTopoModel/lYr8Mk1o">RailTopoModel</a> V1.2Infrastructure and Signalling data only</td></tr><tr><td>Old version, still maintained: 3.2</td><td>April 26, 2022<a class="footnote-ref" id="fnref:36" href="#fn:36">36</a></td><td>March, 2029<a class="footnote-ref" id="fnref:37" href="#fn:37">37</a></td><td>restricted <a href="/facts/CC-BY-NC-ND/6AV3V7UJ">CC-BY-NC-ND</a> 4.0</td><td>based on <a href="/facts/RailTopoModel/lYr8Mk1o">RailTopoModel</a> V1.4added support of Timetable and Rolling stock data</td></tr><tr><td>Latest version: 3.3</td><td>November 5, 2024<a class="footnote-ref" id="fnref:38" href="#fn:38">38</a></td><td>October, 2031<a class="footnote-ref" id="fnref:39" href="#fn:39">39</a></td><td>restricted <a href="/facts/CC-BY-NC-ND/6AV3V7UJ">CC-BY-NC-ND</a> 4.0</td><td>based on <a href="/facts/RailTopoModel/lYr8Mk1o">RailTopoModel</a> V1.5</td></tr><tr><td>Future version: 3.4</td><td>June, 2026</td><td></td><td>restricted <a href="/facts/CC-BY-NC-ND/6AV3V7UJ">CC-BY-NC-ND</a></td><td>based on <a href="/facts/RailTopoModel/lYr8Mk1o">RailTopoModel</a></td></tr><tr><td colspan="99">Legend:Old version, not maintainedOld version, still maintainedLatest versionLatest preview versionFuture version</td></tr></tbody></table>
<h2 id="usage-of-railml-data">Usage of railML data</h2>
At the beginning the most employed usage of railML data was timetable data<a class="footnote-ref" id="fnref:40" href="#fn:40">40</a> 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.

<h3>Computer programmes</h3>
Applications using railML version 2.x include a lot of timetable related programmes like OpenTrack (interactive railway simulator<a class="footnote-ref" id="fnref:41" href="#fn:41">41</a>), FBS (planning software for railway operation<a class="footnote-ref" id="fnref:42" href="#fn:42">42</a>), Viriato (scheduling system<a class="footnote-ref" id="fnref:43" href="#fn:43">43</a>) and OpenTimeTable (real time analysis of network operation data<a class="footnote-ref" id="fnref:44" href="#fn:44">44</a>). Applications using railML version 3.x include additionally <a href="/facts/Building_information_modeling/VFVtPmEr">BIM</a> related infrastructure planning software like VIS All 3D<a class="footnote-ref" id="fnref:45" href="#fn:45">45</a> or railway survey systems like GPSinfradat.<a class="footnote-ref" id="fnref:46" href="#fn:46">46</a>
A complete list of programmes with (certified) interfaces is available at <a href="https://www.railml.org/en/introduction/software.html">railML's website of compatible applications</a>.

<h3>railVIVID</h3>
railVIVID® is an advanced tool for viewing and validating railML® files. The versatility of railVIVID allows users to visualise and validate a range of railway data, including timetable, infrastructure, rolling stock data:<a class="footnote-ref" id="fnref:47" href="#fn:47">47</a>

<ul><li>Graphic viewer for Timetable data</li>
<li><a href="/facts/Public_transport_timetable/aMv9AR8L">Tabular viewer for Timetable data</a> with <a href="/facts/Spreadsheet/0cvc1GeB">spreadsheet</a> export</li>
<li>Rolling Stock data viewer</li>
<li>Topologic viewer for Infrastructure data</li>
<li>Geographic viewer for Infrastructure data</li>
<li><a href="/facts/Validator/WUBnT6QT">Schema validator</a> for railML</li></ul>
railVIVID is available via railML.org's website under licence terms similar to those of the railML schema.<a class="footnote-ref" id="fnref:48" href="#fn:48">48</a>

<h2 id="railmlorg-initiative">railML.org initiative</h2>
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 schemas. Obtaining a commercial certification is required before any commercial or productive use of software interfaces for the format.<a class="footnote-ref" id="fnref:49" href="#fn:49">49</a>

<h3>Members</h3>
Members of railML.org are currently:<a class="footnote-ref" id="fnref:50" href="#fn:50">50</a>

<ul><li>Railways like <a href="/facts/Austrian_Federal_Railways/hkFKyUNN">Austrian Federal Railways</a>, <a href="/facts/BLS_AG/MpyRIGnX">BLS</a>, <a href="/facts/SNCF/qfJG2rYt">French Railways</a>, <a href="/facts/Deutsche_Bahn/oF3Fe2bV">German State Railway</a>, <a href="/facts/Infrabel/C2k2obPz">Infrabel</a>, <a href="/facts/Bane_NOR/I5FpnUYr">Norwegian Rail Infrastructure Manager</a>, <a href="/facts/Swiss_Federal_Railways/Ctk524cn">Swiss Federal Railways</a>, ...</li>
<li>Software manufacturers like <a href="/facts/Hacon/GwT3vN64">Hacon</a> (Hanover/Germany), iRFP (Dresden/Germany), <a href="/facts/PTV_AG/Ic31kB14">PTV</a> (Karlsruhe/Germany), SMA (Zurich/Switzerland), <a href="/facts/Trapeze_Software/sf0ee2tB">Trapeze Group</a> (Hamburg/Germany), <a href="/facts/Siemens/coa80TQn">Siemens</a> (Brunswick/Erlangen/Germany), <a href="/facts/Thales_Group/vuBBokok">Thales</a> (Berlin & Ditzingen/Germany), ...</li>
<li>Authorities like <a href="/facts/Bayerische_Eisenbahngesellschaft/aB9bbP50">Bavarian Passenger Transport Authority</a> (Munich/Germany), <a href="/facts/Federal_Ministry_of_Transport_and_Digital_Infrastructure/k5WCb5c4">Federal Ministry of Transport and Digital Infrastructure</a> (Berlin/Germany), <a href="/facts/High_Speed_Two/rSyhlbkc">High Speed Two</a> (London/Great Britain), <a href="/facts/Norwegian_Railway_Directorate/U3VXlm8X">Jernbanedirektoratet</a> (Oslo/Norway), ...</li>
<li>Universities and Research institutes like <a href="/facts/Czech_Technical_University_in_Prague/2FXKwBxH">Czech Technical University Prague</a>, <a href="/facts/Dresden_University_of_Technology/FtSpjB7n">Dresden University</a>, <a href="/facts/German_Aerospace_Center/nIeKtKqd">DLR</a>, <a href="/facts/ETH_Zurich/IxHAFGUU">ETH Zurich</a>, <a href="/facts/University_of_Birmingham/b2YEFk2X">University of Birmingham</a>, ...</li></ul>
A complete and updated list is published at the <a href="https://www.railml.org/en/partners/partnerlist">website of railML.org</a> community.

<h3>Cooperations</h3>
railML.org works in the ERIM (abbreviation for European Rail Infrastructure Masterplan<a class="footnote-ref" id="fnref:51" href="#fn:51">51</a>) project of the <a href="/facts/International_Union_of_Railways/oSlgdIJk">International Union of Railways</a> (UIC) for the development of <a href="/facts/RailTopoModel/lYr8Mk1o">RailTopoModel</a> as a <a href="/facts/Common_data_model/z2z9LppL">common data model</a> in the railway sector.<a class="footnote-ref" id="fnref:52" href="#fn:52">52</a> Also railML.org cooperates with <a href="/facts/Eurocontrol/sYdPuGua">Eurocontrol</a> and <a href="/facts/European_Union_Agency_for_Railways/e2eVSLxM">European Union Agency for Railways</a>.

<h2 id="external-links">External links</h2>
<ul><li><a href="http://www.railml.org/">railML Homepage</a></li>
<li><a href="http://forum.railml.org/">railML discussion board</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">[1], p. PA4, at Google Books <a href="https://books.google.com/books?id=BbWtfTuTHwcC&pg=PAPA4" target="_blank">https://books.google.com/books?id=BbWtfTuTHwcC&pg=PAPA4</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">[1], p. PA4, at Google Books <a href="https://books.google.com/books?id=BbWtfTuTHwcC&pg=PAPA4" target="_blank">https://books.google.com/books?id=BbWtfTuTHwcC&pg=PAPA4</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">"RailTopoModel and railML®" (PDF). uic.org. Retrieved 2016-01-26. <a href="http://www.uic.org/IMG/pdf/160913_erimworkgroup_presentationerimpresentationparis170913.pdf" target="_blank">http://www.uic.org/IMG/pdf/160913_erimworkgroup_presentationerimpresentationparis170913.pdf</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">[1], p. PA4, at Google Books <a href="https://books.google.com/books?id=BbWtfTuTHwcC&pg=PAPA4" target="_blank">https://books.google.com/books?id=BbWtfTuTHwcC&pg=PAPA4</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">[1], p. PA4, at Google Books <a href="https://books.google.com/books?id=BbWtfTuTHwcC&pg=PAPA4" target="_blank">https://books.google.com/books?id=BbWtfTuTHwcC&pg=PAPA4</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">"RailTopoModel and railML®" (PDF). uic.org. Retrieved 2016-01-26. <a href="http://www.uic.org/IMG/pdf/160913_erimworkgroup_presentationerimpresentationparis170913.pdf" target="_blank">http://www.uic.org/IMG/pdf/160913_erimworkgroup_presentationerimpresentationparis170913.pdf</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">"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. <a href="https://web.archive.org/web/20160306124822/http://www.psitrans.de/fileadmin/files/pictures/PSI_Transcom/VT/Messen/Vortr%C3%A4ge_Anwendertag/Standardisiertes_Datenmanagement_mit_RailML_Vasco_Paul_Kolmorgen.pdf" target="_blank">https://web.archive.org/web/20160306124822/http://www.psitrans.de/fileadmin/files/pictures/PSI_Transcom/VT/Messen/Vortr%C3%A4ge_Anwendertag/Standardisiertes_Datenmanagement_mit_RailML_Vasco_Paul_Kolmorgen.pdf</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">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. <a href="https://www.railml.org/files/download/papers/090104_huerlimannnashschuettekrauss.paper.comprail.pdf" target="_blank">https://www.railml.org/files/download/papers/090104_huerlimannnashschuettekrauss.paper.comprail.pdf</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">"RailTopoModel and railML®" (PDF). uic.org. Retrieved 2016-01-26. <a href="http://www.uic.org/IMG/pdf/160913_erimworkgroup_presentationerimpresentationparis170913.pdf" target="_blank">http://www.uic.org/IMG/pdf/160913_erimworkgroup_presentationerimpresentationparis170913.pdf</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">[2], p. PA5, at Google Books <a href="https://books.google.com/books?id=BbWtfTuTHwcC&pg=PAPA5" target="_blank">https://books.google.com/books?id=BbWtfTuTHwcC&pg=PAPA5</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">"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. <a href="https://web.archive.org/web/20160306124822/http://www.psitrans.de/fileadmin/files/pictures/PSI_Transcom/VT/Messen/Vortr%C3%A4ge_Anwendertag/Standardisiertes_Datenmanagement_mit_RailML_Vasco_Paul_Kolmorgen.pdf" target="_blank">https://web.archive.org/web/20160306124822/http://www.psitrans.de/fileadmin/files/pictures/PSI_Transcom/VT/Messen/Vortr%C3%A4ge_Anwendertag/Standardisiertes_Datenmanagement_mit_RailML_Vasco_Paul_Kolmorgen.pdf</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
<li id="fn:12">"5th UIC RailTopoModeland railML® Conference" (PDF). railML. 2016-02-01. p. 29. Archived from the original (PDF) on 2019-02-09. Retrieved 2017-05-06. <a href="https://web.archive.org/web/20190209180721/https://www.railml.org/files/download/events/Presentations%20conferences/5th%20UIC%20RTM/2015-11-04_status.pdf" target="_blank">https://web.archive.org/web/20190209180721/https://www.railml.org/files/download/events/Presentations%20conferences/5th%20UIC%20RTM/2015-11-04_status.pdf</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></li>
<li id="fn:13">[3], p. PA6, at Google Books <a href="https://books.google.com/books?id=BbWtfTuTHwcC&pg=PAPA6" target="_blank">https://books.google.com/books?id=BbWtfTuTHwcC&pg=PAPA6</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></li>
<li id="fn:14">"Licence – railML.org (EN)". railml.org. Retrieved 2023-05-25. <a href="http://www.railml.org/en/user/licence.html" target="_blank">http://www.railml.org/en/user/licence.html</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></li>
<li id="fn:15">"Licence – railML.org (EN)". railml.org. Retrieved 2023-05-25. <a href="http://www.railml.org/en/user/licence.html" target="_blank">http://www.railml.org/en/user/licence.html</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></li>
<li id="fn:16">Augele, Vivian (2019-01-29). "railML Licence: Minor Changes come with railML3". www.railML.org. railML.org; Dresden/Germany. Retrieved 2019-03-23. <a href="https://www.railml.org/en/public-relations/news/reader/railml-licence-minor-changes-come-with-railml3.html" target="_blank">https://www.railml.org/en/public-relations/news/reader/railml-licence-minor-changes-come-with-railml3.html</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></li>
<li id="fn:17">"Licence – railML.org (EN)". railml.org. Retrieved 2023-05-25. <a href="http://www.railml.org/en/user/licence.html" target="_blank">http://www.railml.org/en/user/licence.html</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></li>
<li id="fn:18">"Timetable – railML.org (EN)". railml.org. Retrieved 2016-01-26. <a href="http://www.railml.org/en/user/subschemas/timetable.html" target="_blank">http://www.railml.org/en/user/subschemas/timetable.html</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></li>
<li id="fn:19">"Infrastructure – railML.org (EN)". railml.org. Retrieved 2016-01-26. <a href="http://www.railml.org/en/user/subschemas/infrastructure.html" target="_blank">http://www.railml.org/en/user/subschemas/infrastructure.html</a> <a href="#fnref:19" class="footnote-back-ref">↩</a></li>
<li id="fn:20">"Rollingstock – railML.org (EN)". railml.org. Retrieved 2016-01-26. <a href="http://www.railml.org/en/user/subschemas/rollingstock.html" target="_blank">http://www.railml.org/en/user/subschemas/rollingstock.html</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></li>
<li id="fn:21">"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. <a href="https://web.archive.org/web/20160306124822/http://www.psitrans.de/fileadmin/files/pictures/PSI_Transcom/VT/Messen/Vortr%C3%A4ge_Anwendertag/Standardisiertes_Datenmanagement_mit_RailML_Vasco_Paul_Kolmorgen.pdf" target="_blank">https://web.archive.org/web/20160306124822/http://www.psitrans.de/fileadmin/files/pictures/PSI_Transcom/VT/Messen/Vortr%C3%A4ge_Anwendertag/Standardisiertes_Datenmanagement_mit_RailML_Vasco_Paul_Kolmorgen.pdf</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></li>
<li id="fn:22">"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. <a href="https://web.archive.org/web/20160306124822/http://www.psitrans.de/fileadmin/files/pictures/PSI_Transcom/VT/Messen/Vortr%C3%A4ge_Anwendertag/Standardisiertes_Datenmanagement_mit_RailML_Vasco_Paul_Kolmorgen.pdf" target="_blank">https://web.archive.org/web/20160306124822/http://www.psitrans.de/fileadmin/files/pictures/PSI_Transcom/VT/Messen/Vortr%C3%A4ge_Anwendertag/Standardisiertes_Datenmanagement_mit_RailML_Vasco_Paul_Kolmorgen.pdf</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></li>
<li id="fn:23">"Licence – railML.org (EN)". railml.org. Retrieved 2023-05-25. <a href="http://www.railml.org/en/user/licence.html" target="_blank">http://www.railml.org/en/user/licence.html</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></li>
<li id="fn:24">"Licence – railML.org (EN)". railml.org. Retrieved 2023-05-25. <a href="http://www.railml.org/en/user/licence.html" target="_blank">http://www.railml.org/en/user/licence.html</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></li>
<li id="fn:25">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. <a href="http://documents.railml.org/events/slides/2013-09-18_wunsch-common-news.pdf" target="_blank">http://documents.railml.org/events/slides/2013-09-18_wunsch-common-news.pdf</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></li>
<li id="fn:26">Kolmorgen, Vasco Paul (2019-06-30). "Schema Planning and Lifecycle Policy / V2.2 Support Termination". railML.org News. Retrieved 2023-05-25. <a href="https://www.railml.org/en/public-relations/news/reader/schema-planning-and-lifecycle-policy.html" target="_blank">https://www.railml.org/en/public-relations/news/reader/schema-planning-and-lifecycle-policy.html</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></li>
<li id="fn:27">Kolmorgen, Vasco Paul (2021-06-21). "Announcement of the end of support for railML 2.3". railML.org News. Retrieved 2023-05-25. <a href="https://www.railml.org/en/public-relations/news/reader/announcement-discontinuation-of-railml-2-3.html" target="_blank">https://www.railml.org/en/public-relations/news/reader/announcement-discontinuation-of-railml-2-3.html</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></li>
<li id="fn:28">"railML Version Timeline". railML.org Website. Retrieved 2024-12-19. <a href="https://www.railml.org/en/version-timeline" target="_blank">https://www.railml.org/en/version-timeline</a> <a href="#fnref:28" class="footnote-back-ref">↩</a></li>
<li id="fn:29">"Version Timeline – railML.org (EN)". railml.org. Retrieved 2021-10-04. <a href="https://www.railml.org/en/developer/version-timeline.html" target="_blank">https://www.railml.org/en/developer/version-timeline.html</a> <a href="#fnref:29" class="footnote-back-ref">↩</a></li>
<li id="fn:30">"railML Version Timeline". railML.org Website. Retrieved 2024-12-19. <a href="https://www.railml.org/en/version-timeline" target="_blank">https://www.railml.org/en/version-timeline</a> <a href="#fnref:30" class="footnote-back-ref">↩</a></li>
<li id="fn:31">Mkinsi, Hakim (2023-03-23). "The future of rail is intelligent. Data collection and exchange are key". ISO Geneve/Switzerland (pdf). Retrieved 2023-05-25. <a href="https://www.iso.org/home.isoDocumentsDownload.do?t=HMRcodPqUtRGks5Bk6-RNe_ENRTQDVkQbd00ZUCbZlvBeNpuN-iCBsOn4GtM_A2O&CSRFTOKEN=ZP8N-I9H2-UT1K-PUNC-GTCA-SP9D-21V5-N1W2" target="_blank">https://www.iso.org/home.isoDocumentsDownload.do?t=HMRcodPqUtRGks5Bk6-RNe_ENRTQDVkQbd00ZUCbZlvBeNpuN-iCBsOn4GtM_A2O&CSRFTOKEN=ZP8N-I9H2-UT1K-PUNC-GTCA-SP9D-21V5-N1W2</a> <a href="#fnref:31" class="footnote-back-ref">↩</a></li>
<li id="fn:32">Augele, Vivian (2017-11-15). "Public Presentation of railML 3.1 during 32nd railML Conference". railML.org News. Retrieved 2017-11-25. <a href="https://www.railml.org/en/public-relations/news/reader/public-presentation-of-railml-3-1-32nd-railml-conference.html" target="_blank">https://www.railml.org/en/public-relations/news/reader/public-presentation-of-railml-3-1-32nd-railml-conference.html</a> <a href="#fnref:32" class="footnote-back-ref">↩</a></li>
<li id="fn:33">"railML Version Timeline". railML.org Website. Retrieved 2024-12-19. <a href="https://www.railml.org/en/version-timeline" target="_blank">https://www.railml.org/en/version-timeline</a> <a href="#fnref:33" class="footnote-back-ref">↩</a></li>
<li id="fn:34">"railML Version Timeline". railML.org Website. Retrieved 2024-12-19. <a href="https://www.railml.org/en/version-timeline" target="_blank">https://www.railml.org/en/version-timeline</a> <a href="#fnref:34" class="footnote-back-ref">↩</a></li>
<li id="fn:35">"railML Version Timeline". railML.org Website. Retrieved 2024-12-19. <a href="https://www.railml.org/en/version-timeline" target="_blank">https://www.railml.org/en/version-timeline</a> <a href="#fnref:35" class="footnote-back-ref">↩</a></li>
<li id="fn:36">"railML Version Timeline". railML.org Website. Retrieved 2024-12-19. <a href="https://www.railml.org/en/version-timeline" target="_blank">https://www.railml.org/en/version-timeline</a> <a href="#fnref:36" class="footnote-back-ref">↩</a></li>
<li id="fn:37">"railML Version Timeline". railML.org Website. Retrieved 2024-12-19. <a href="https://www.railml.org/en/version-timeline" target="_blank">https://www.railml.org/en/version-timeline</a> <a href="#fnref:37" class="footnote-back-ref">↩</a></li>
<li id="fn:38">"railML Version Timeline". railML.org Website. Retrieved 2024-12-19. <a href="https://www.railml.org/en/version-timeline" target="_blank">https://www.railml.org/en/version-timeline</a> <a href="#fnref:38" class="footnote-back-ref">↩</a></li>
<li id="fn:39">"railML Version Timeline". railML.org Website. Retrieved 2024-12-19. <a href="https://www.railml.org/en/version-timeline" target="_blank">https://www.railml.org/en/version-timeline</a> <a href="#fnref:39" class="footnote-back-ref">↩</a></li>
<li id="fn:40">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. <a href="https://www.railml.org/files/download/papers/090104_huerlimannnashschuettekrauss.paper.comprail.pdf" target="_blank">https://www.railml.org/files/download/papers/090104_huerlimannnashschuettekrauss.paper.comprail.pdf</a> <a href="#fnref:40" class="footnote-back-ref">↩</a></li>
<li id="fn:41">"OpenTrack Railway Technology – Eisenbahnsimulation". opentrack.ch. Retrieved 2015-10-20. <a href="http://www.opentrack.ch/opentrack/opentrack_d/opentrack_d.html" target="_blank">http://www.opentrack.ch/opentrack/opentrack_d/opentrack_d.html</a> <a href="#fnref:41" class="footnote-back-ref">↩</a></li>
<li id="fn:42">Christian Roessiger (15 September 2016). "railML Schnittstelle – Institut für Regional- und Fernverkehrsplanung" (in German). iRFP e.K.; Dresden/Germany. Retrieved 21 May 2017. <a href="http://www.irfp.de/railml-schnittstelle.html" target="_blank">http://www.irfp.de/railml-schnittstelle.html</a> <a href="#fnref:42" class="footnote-back-ref">↩</a></li>
<li id="fn:43">"Software für die Eisenbahn". sma-partner.ch. Retrieved 2015-10-20. <a href="http://www.sma-partner.ch/de/loesungen/viriato-und-zlr/uebersicht/" target="_blank">http://www.sma-partner.ch/de/loesungen/viriato-und-zlr/uebersicht/</a> <a href="#fnref:43" class="footnote-back-ref">↩</a></li>
<li id="fn:44">"OpenTimeTable". via-con.de. Archived from the original on 2017-04-18. Retrieved 2015-10-20. <a href="https://web.archive.org/web/20170418144636/http://www.via-con.de/development/open-timetable-ott" target="_blank">https://web.archive.org/web/20170418144636/http://www.via-con.de/development/open-timetable-ott</a> <a href="#fnref:44" class="footnote-back-ref">↩</a></li>
<li id="fn:45">"VIS-All® 3D- der einfache Weg in die 3D-Welt!". Software-Service John (in German). Retrieved May 21, 2017. <a href="http://www.john-software.de/produkte/vis-all-3d" target="_blank">http://www.john-software.de/produkte/vis-all-3d</a> <a href="#fnref:45" class="footnote-back-ref">↩</a></li>
<li id="fn:46">"GPSinfradat". Bahnkonzept Dresden/Germany. Retrieved 2019-04-19. <a href="https://www.bahnkonzept.de/en/compendium" target="_blank">https://www.bahnkonzept.de/en/compendium</a> <a href="#fnref:46" class="footnote-back-ref">↩</a></li>
<li id="fn:47">"railVIVID – railML.org (EN)". railml.org. Retrieved 2025-03-06. <a href="https://www.railml.org/en/railvivid" target="_blank">https://www.railml.org/en/railvivid</a> <a href="#fnref:47" class="footnote-back-ref">↩</a></li>
<li id="fn:48">"Licence Terms – railML.org (EN)". Retrieved 2025-03-06. <a href="https://www.railml.org/en/licence" target="_blank">https://www.railml.org/en/licence</a> <a href="#fnref:48" class="footnote-back-ref">↩</a></li>
<li id="fn:49">"Certification – railML.org (EN)". www.railml.org. Retrieved 2019-04-19. <a href="https://www.railml.org/en/certification.html" target="_blank">https://www.railml.org/en/certification.html</a> <a href="#fnref:49" class="footnote-back-ref">↩</a></li>
<li id="fn:50">"Partners – railML.org (EN)". railml.org. Retrieved 2016-01-26. <a href="http://www.railml.org/en/introduction/partners.html" target="_blank">http://www.railml.org/en/introduction/partners.html</a> <a href="#fnref:50" class="footnote-back-ref">↩</a></li>
<li id="fn:51">"Functioning of railML.org and RailTopoModel – railML.org (EN)". www.railml.org. <a href="https://www.railml.org/en/public-relations/news/reader/functioning-of-railml-org-and-railtopomodel.html" target="_blank">https://www.railml.org/en/public-relations/news/reader/functioning-of-railml-org-and-railtopomodel.html</a> <a href="#fnref:51" class="footnote-back-ref">↩</a></li>
<li id="fn:52">"UIC e-news 362: The foundation for a Universal Infrastructure Data Exchange Format". November 30, 2014. <a href="http://www.uic.org/com/uic-e-news/362/" target="_blank">http://www.uic.org/com/uic-e-news/362/</a> <a href="#fnref:52" class="footnote-back-ref">↩</a></li>
</ol>

railML open-in-new

railML