Main Page: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
m (Webmaster moved page Hauptseite to Main Page)
No edit summary
Line 1: Line 1:
=== Welcome to the railML Wiki / {{Deu| Willkommen im railML-Wiki}}===
{| class="wikitable" style="float:right; margin-left:10px; text-align:center"
|<!--[[file:RailML logo.png|200px]]-->
{| style="text-align:left; vertical-align:top"
|style="width:95px;vertical-align:top"|Filename extension&nbsp;
|style="width:95px;vertical-align:top"|.railml, .railmlx
|-
|Developed by
|railML.org
|-
|Initial release
|22 December 2005
|-
|Latest release
|2.2 (11 June 2013)
|-
|style="vertical-align:top"|Type of format&nbsp;
|Railway exchange format
|-
|Extended from
|XML
|-
|Standard
|Industry standard
|-
|Open format?
|Yes, CC BY-NC-ND
|-
|Website
|http://railml.org
|}
|}
=== Welcome to the railML<sup>®</sup> wiki / {{Deu| Willkommen im railML<sup>®</sup>-Wiki}} / {{Fra|Bienvenue au Wiki<sup>®</sup> du railML}}===
{| class="wikitable toptextcells" style="text-align:left vertical-align:top"
|- style="vertical-align:top;"
|style="width:30%" | railML<sup>®</sup> ('''rail'''way '''M'''arkup '''L'''anguage) is an open, XML based data exchange format for data interoperability of railway applications. For further information please visit the [http://www.railml.org official project website] or [http://en.wikipedia.org/wiki/RailML Wikipedia].


RailML® is not the finished development of a central group. Instead, railML grows through the joint work of the partners and is steadily being extended. We invite you to participate on this future-oriented project and to take advantage of these standardized interfaces. Our [http://forum.railml.org Forum] is meant to help coordinate the joint work of the development partners and provides an open discussion platform.
This wiki should support you in the development of railML<sup>®</sup> interfaces and inform you about the basic elements and modelling concepts of the railML<sup>®</sup> schema.


This wiki should supporting the development of railML-schemes. It allows users to create new content and edit existing articles, and setup a comprehensive knowledge database to the railML standard.
This wiki is being kept in English. At certain points information is provided additionally also in {{Deu|German}} and/or {{Fra|French}}. You are invited to contribute to this wiki. Please, see our guideline "''[[How_to_join,_edit_and_create_the_railML_wiki#How_to_join_the_Wiki|How to join the railML wiki]]''" to get to know the standards of railML's wiki and the procedure for getting a writer's account.


'''See our FAQ pages to see [[How_to_join,_edit_and_create_the_railML_wiki#How_to_join_the_Wiki|how to join the railML wiki]] and especially to contribute to this Wiki by [[How_to_join,_edit_and_create_the_railML_wiki#Edit_element_documentation_sites|editing element documentation sites]] or [[How_to_join,_edit_and_create_the_railML_wiki#Edit_or_create_FAQ_sites|editing or creating FAQ sites]].'''
|style="width:38%" | {{Deu|railML<sup>®</sup> ('''rail'''way '''M'''arkup '''L'''anguage) ist ein offenes, XML-basiertes Datenaustauschformat zur gegenseitigen Benützbarkeit der Daten von Anwendungen im Eisenbahnbereich. Für weitere Informationen besuchen Sie bitte die [http://www.railml.org offizielle Projektwebsite] oder [http://de.wikipedia.org/wiki/railML Wikipedia].}}


{{Deu|RailML® lebt von der Mitarbeit der Nutzer des Standards. Sie können an der Entwicklung teilhaben und Ihre Bedürfnisse und Erfahrungen in zukünftige railML-Teilschemen einbringen. Unser [http://forum.railml.org Diskussionsforum] steht Ihnen für allgemeine Fragen zum Projekt oder zu den einzelnen Teilschemen zur Verfügung.<br>
{{Deu|Ziel dieses Wikis ist, Sie bei der Entwicklung von railML<sup>®</sup>-Schnittstellen zu unterstützen und Sie über die grundlegenden Elemente und Modellierungskonzepte des railML<sup>®</sup>-Schemas zu informieren.}}
Mit Hilfe dieses [http://de.wikipedia.org/wiki/Wiki Wikis] soll der Einstieg in die Entwicklung der railML-Teilschemen erleichtert werden. Es ermöglicht den Benutzern neue Inhalte zu schaffen, sowie vorhandene Beiträge zu bearbeiten und damit eine umfassende Wissensdatenbank zum railML-Standard aufzubauen.


'''Auf unseren Hilfeseiten finden Sie Informationen [[How_to_join,_edit_and_create_the_railML_wiki#How_to_join_the_Wiki|zum registrieren für das railML-Wiki]] und insbesondere, wie Sie zum Wiki beitragen können durch das [[How_to_join,_edit_and_create_the_railML_wiki#Edit_element_documentation_sites|Ergänzen oder Verbessern der Elemente-Dokumentation]] oder durch das [[How_to_join,_edit_and_create_the_railML_wiki#Edit_or_create_FAQ_sites|Erstellen oder Ergänzen von Hilfeseiten]].'''}}
{{Deu|Dieses Wiki wird auf}} Englisch {{Deu|geführt. Einzelne Informationen stellen wir außerdem auf Deutsch und}} {{Fra|Französisch}} {{Deu|zur Verfügung. Sie sind herzlich eingeladen, sich an der Entwicklung dieses Wikis zu beteiligen. Lesen Sie dazu bitte unseren Leitfaden ''„[[How_to_join,_edit_and_create_the_railML_wiki#How_to_join_the_Wiki|How to join the railML wiki]]“'', um sich mit den Standards des railML®-Wikis vertraut zu machen und die Vorgangsweise zur Erteilung eines Autorenaccounts kennenzulernen.}}
|style="width:*" | {{Fra|railML<sup>®</sup> (railway Markup Language) est un format public, fondé sur XML et destiné à l’échange de données ferroviaires, en vue de l’interopérabilité des applications informatiques. Pour plus d’informations, veuillez consulter la [http://www.railml.org page de projet officielle] dans [http://fr.wikipedia.org/wiki/railML Wikipedia].}}


== Current railML subschema ==
{{Fra|Le présent wiki vous aidera à développer des interfaces railML<sup>®</sup>, notamment en vous présentant les éléments de base et les concepts fondamentaux du schéma railML<sup>®</sup>.}}


=== Infrastructure (IS) ===
{{Fra|Ce wiki est tenu en}} anglais. {{Fra|Des informations particulières sont parfois fournies en français ou en}} {{Deu|allemand}}{{Fra|. Vous êtes invité(e) à y contribuer : veuillez consulter notre guide "[[How_to_join,_edit_and_create_the_railML_wiki#How_to_join_the_Wiki|How to join the railML wiki]]", qui vous indiquera les règles applicables au wiki, ainsi que la marche à suivre pour y contribuer en tant qu’auteur.
 
}}
==== General Information ====
|}
 
The Infrastructure subschema contains a data structure for the storage of
 
* tracks, switches and the topology of a line
* various operations and control elements (e. g. signals along the track)
* tunnels, bridges
* any kind of "border" (owner change, gauge change, axle load change, electrification, ...)
* visualization data for displaying a net
 
Please visit the [http://www.railml.org railML-Website] for more detailed information about the Infrastructure subschema or send an [mailto:coord@infrastructure.railml.org email] to the coordinator of the subschema.
 
==== Documentation ====
 
The following lists provide links to Infrastructure Documentation sites:


* [[:Category:Infrastructure_Elements | Infrastructure Elements]]
== Current railML schema ==
* Infrastructure Examples


==== Use Cases ====
Currently there exist four subschemata: Infrastructure (IS), Timetable and Rostering (TT), Rollingstock (RS) and Interlocking (IL). Elements that do not fit into this structure are subsumed in the class Common (CO).
 
A list of the infrastructure data exchange use cases can be found [[:IS:UseCases | here]].  
 
==== FAQ ====
 
Some general questions about infrastructure related aspects in railML files are summarized on the following wiki-sites:
 
* [[IS:TrackConnections|Connection between tracks]]
* [[Diskussion:IS:mileageChange‎ | Remarks and open issues on mileage changes]]


Open http://www.railml.org/index.php/railml-schemas.html for a list of the current coordinators of the respective schemas.
=== Timetable and Rostering (TT) ===
=== Timetable and Rostering (TT) ===
 
The [[timetable|timetable subschema]] is part of the complete [http://www.railml.org railML] schema providing a data structure in XML language for the exchange of railway specific data. It is the subschema that is employed most.
==== General Information ====
 
The timetable subschema is part of the complete [http://www.railml.org railML] schema providing a data structure in XML language for the exchange of railway specific data.


The timetable schema provides container for all data about any kind of timetables for operational or conceptional purposes. A flexible description of operating periods, which are important elements while dealing with timetables, is also included in the schema.
The timetable schema provides container for all data about any kind of timetables for operational or conceptional purposes. A flexible description of operating periods, which are important elements while dealing with timetables, is also included in the schema.


The root element is always {{CO:Tag|railml}}, thus it is even possible to combine data of timetable with those of other railML schemas within one file. The main element for this schema is {{TT:Tag|timetable}}, which is the root for data about any timetable.
The subschema contains the following information:
* Operating Periods: The operating days for train services or rostering.
* Train Parts: The basic parts of a train as a sequence of operation or control points with the same characteristics such as formation and operating period. The train part includes the actual information regarding the path of the train as well as the corresponding schedule information.
* Trains: One or more train parts make up a train and represent either the operational or the commercial view of the train run.
* Rostering: Train parts can be linked to form the circulations necessary for rostering (rolling stock schedules).


With the new branch of {{TT:Tag|rosterings}} it is intended to use this data schema as well for conceptional rolling stock schedules.
=== Infrastructure (IS) ===
 
The railML® [[Infrastructure|Infrastructure subschema]] is focused on the description of  
Please visit the [http://www.railml.org railML-Website] for more detailed information about the Timetable subschema or send an [mailto:coord@timetable.railml.org email] to the coordinator of the subschema.
the railway network infrastructure including all its various facets that
 
are needed by the data exchange applications. In particular, the railML
==== Documentation ====
infrastructure schema contains the following information:
 
* Topology. The track network is described as a topological node edge model.
The following lists provide links to Timetable Documentation sites:
* Coordinates. All railway infrastructure elements can be located in an arbitrary 2- or 3-dimensional coordinate system, e.g. the WRG84 that is widely used by today's navigation software.
 
* Geometry. The track geometry can be described in terms of radius and gradient.
* [[:Category:Timetable_Elements | Timetable Elements]]
* Railway infrastructure elements enclose a variety of railway relevant assets that can be found on, under, over or next to the railway track, e.g. balises, platform edges and level crossings.
* [[TT:attributes | Timetable Attributes]]
* Further located elements encompass elements that are closely linked with the railway infrastructure, but that "cannot be touched", e.g. speed profiles and track conditions.
 
 
The future railML development shall be based on so called use cases which specify the usage scenarios of railML data. Please refer to the [[TT:UseCases | use cases abstract page]] for further information.
 
==== Use Cases ====
 
A list of the timetable data exchange use cases can be found [[:TT:UseCases | here]].  
 
==== FAQ ====
 
Some general questions about timetable related aspects in railML files are summarized on the following wiki-sites:
 
* [[TT:Train_Coupling_And_Sharing | Train coupling and sharing]]
* [[TT:How_To_Reference_Infrastructure | How to reference infrastructure]]
* [[TT:Reversing_trains_and_formations | About reversing trains and formations]]
* [[TT:categoryUsage‎ | How to find out whether a train or train part is for passengers or freight? (Train types, categories, products, and passenger usage)]]
* [[TT:Midnight_overrun | How to indicate midnight overruns in railML]]
 
The following lists provide links to external Timetable Documentation sites from some railML partners:
 
* [http://www.irfp.de/download/railml_doku_beispiele.pdf Timetable Examples from iRFP Dresden] A selection of mainly special cases relating to TT and IS sub-schemes (external link)


=== Rollingstock (RS) ===
=== Rollingstock (RS) ===
The [[rollingstock|rollingstock subschema]] is part of the complete [http://www.railml.org railML] schema providing a data structure in XML language for the exchange of railway specific data.


==== General Information ====
The rollingstock schema provides container for all data about any kind of rail vehicles including locomotives, multiple units, passenger and freight wagons. The second part of the schema enables the combination of single vehicles to formations as a fixed composition within a train or an entire train. It is intended to use this data schema for vehicle management as well as for detailed run-time calculations.
 
The rollingstock subschema is part of the complete [http://www.railml.org railML] schema providing a data structure in XML language for the exchange of railway specific data.
 
The rollingstock schema provides container for all data about any kind of rail vehicles including locomotives, multiple units, passenger and freight wagons. The second part of the schema enables the combination of single vehicles to formations as a fixed composition within a train or an entire train. The root element is always {{CO:Tag|railml}}, thus it is even possible to combine data of rolling stock with those of other railML schemes within one file. The main element for this schema is {{RS:Tag|rollingstock}}, which is the root for data about any rolling stock.
 
It is intended to use this data schema for vehicle management as well as for detailed run-time calculations. Depending on the purpose only the {{RS:Tag|vehicles}} branch of the data tree may be populated or the {{RS:Tag|formations}} branch appears or both of them. The {{RS:Tag|vehicles}} branch contains all data related to single vehicles. However, there are data, which are mainly used in relation to a composition of vehicles. Therefore the {{RS:Tag|formations}} branch is used to reflect the characteristics an entire train or a composition of vehicles within a train.


The Rollingstock schema comprises the following features:
The Rollingstock schema comprises the following features:
Line 109: Line 95:
* combination of vehicles to formations, i.e. train parts or complete trains
* combination of vehicles to formations, i.e. train parts or complete trains


Please visit the [http://www.railml.org railML-Website] for more detailed information about the Rollingstock subschema or send an [mailto:coord@rollingstock.railml.org email] to the coordinator of the subschema.
=== Interlocking (IL) ===
 
==== Documentation ====
 
The following lists provide links to Timetable Documentation sites:
 
* [[:Category:Rollingstock_Elements|Rollingstock Elements]]
* [[RS:attributes|Rollingstock Attributes]]
 
==== Use Cases ====


A list of the rollingstock data exchange use cases can be found [[:RS:UseCases | here]].  
The [[interlocking|interlocking subschema]] is under ''active'' development from 2015.


=== Common (CO) ===
=== Common (CO) ===
 
The [[Common]] class shall cover all topics, which affect all other railML-schemas alike.
==== General Information ====
 
This subschema shall cover all topics, which affect all other railML-schemas alike.


The actual planned tasks and enhancements can be found at [http://trac.railml.org/report Trac-Tickets] of the railML development space.
The actual planned tasks and enhancements can be found at [http://trac.railml.org/report Trac-Tickets] of the railML development space.
Line 132: Line 106:
There is also a "historic" collection of proposed [[CommonDataTypes | Data Types]] for the Common subschema. It was developed in the preparation works of railML version 1.1. Some of the suggestions are already implemented in the stable railML 2.0 release. Other extensions wait for users with strong needs for them.
There is also a "historic" collection of proposed [[CommonDataTypes | Data Types]] for the Common subschema. It was developed in the preparation works of railML version 1.1. Some of the suggestions are already implemented in the stable railML 2.0 release. Other extensions wait for users with strong needs for them.


==== Documentation ====
== Prospect on Future Schemata ==
 
The following lists provide links to Common Documentation sites:
* [[:Category:Common_Elements | Common railML elements]]
* [[CO:attributes | Common railML Attributes]]
 
==== FAQ ====
 
Some general questions about handling railML files are summerized on the following wiki-sites:
 
* [[CO:fileConventions | Conventions for railML files]] (file name extensions, compressed files, and other)
* [[CO:identities | Handling identities]] ({{Attr|id}} values)
* [[CO:catalog | Local versus web-based validation]] (XML catalogs and XML namespaces)
* [[CO:versions | Versioning policy]] (version numbers, versioned XML namespaces)
* [[CO:versioning | Officially released versus developer version]] (Homepage, Subversion)
* [[CO:tickets | Discussed versus agreed features]] (Newsgroup, Trac Tickets)
* [[CO:xmlSyntax | XML Syntax issues]] (Attribute delimiters, Character references)
* [[CO:usingAny | Using "xs:any" elements, "anyAttribute"s and "other:anything" enumeration values]] for enhancing the railML files with your special needs
* [[CO:outsourcing | Using content libraries]] and fully validating without any error or warning messages
* [[CO:changes | Changes]] sorted by released versions
 
== railML subschema under development ==
 
=== Interlocking (IL) ===
 
The interlocking Schema is under ''active'' development from 2015.
 
Please visit the [http://www.railml.org railML-Website] for more detailed information about the Interlocking subschema or send an [mailto:coord@interlocking.railml.org email] to the coordinator of the subschema.
 
==== Documentation ====
 
The first attempt for documentation is provided at the [[IXL_Data_Dictionary | railML IXL glossary]].
 
An [[IL_IntendedFeatures | intended features list]] is stored in the Wiki.
 
All topics, that are covered by the current developments, will be removed from this [[IL_IntendedFeatures | features list]] and described at the [[IXL_Data_Dictionary | glossary]] instead. Later on, the typical railML documentation with wiki sites for each element will be provided.
 
==== Use Cases ====
 
A list of the interlocking data exchange use cases can be found [[:IL:UseCases | here]].
 
== Proposed railML subschema ==


=== Shift planning ===
=== Shift planning ===
Additional to (vehicle) rosterings, there are ideas for implementing (personnel) shift planning.
Additional to (vehicle) rosterings, there are ideas for implementing (personnel) shift planning.
It should be discussed in the [news://news.railml.org/railML.timetable timetable forum] (or click [http://www.railml.org/forum/ro/?group=2 here] for access via HTTP).
=== Station asset management and properties ===
=== Station asset management and properties ===
A schema for station databases, asset management and properties was developed in the early 2000's but place on hold due to the very limited use cases at this time. With a focus to the upcoming [[http://www.era.europa.eu/Document-Register/Pages/PRM-TSI.aspx|TSI PRM]] a reopening of the development might be started depending from sectors needs in 2016 ff.


A schema for station databases, asset management and properties was developed in the early 2000's but place on hold due to the very limited use cases at this time. With a focus to the upcoming [[http://www.era.europa.eu/Document-Register/Pages/PRM-TSI.aspx|TSI PRM]] a reopening of the development is planned for 2015.
== Users and Developers Guides ==
== Users and Developers Guides ==
 
* [[User:Ferri Leberl/Dev:Downloading and using railML®|Downloading and using railML®]]
* [[Dev:Syntactic_Guidelines | Syntactic guidelines for a corporate code base]]
* [[Dev:Syntactic_Guidelines | Syntactic guidelines for a corporate code base]]
* [[Dev:Coding_XML_Components | Coding styles for XML components in railML schemas]]
* [[Dev:Coding_XML_Components | Coding styles for XML components in railML schemas]]
* [[Dev:Wiki_Documentation_Guidelines | Guidelines to enhance the wiki documentation]]
* [[Dev:Wiki_Documentation_Guidelines | Guidelines to enhance the wiki documentation]]
* [[Dev:Subversion_Guidelines | Guidelines for handling the Subversion repository]]
* [[Dev:Subversion_Guidelines | Guidelines for handling the Subversion repository]]
* [[How_to_join,_edit_and_create_the_railML_wiki#How_to_join_the_Wiki|How to join the railML® wiki]]
==Contact==
==Contact==
Feel free to direct any comments, questions or remarks to the coordinators of railML.
Feel free to direct any comments, questions or remarks to the coordinators of railML.

Revision as of 15:07, 2 February 2016

Filename extension  .railml, .railmlx
Developed by railML.org
Initial release 22 December 2005
Latest release 2.2 (11 June 2013)
Type of format  Railway exchange format
Extended from XML
Standard Industry standard
Open format? Yes, CC BY-NC-ND
Website http://railml.org

Welcome to the railML® wiki / Willkommen im railML®-Wiki /

railML® (railway Markup Language) is an open, XML based data exchange format for data interoperability of railway applications. For further information please visit the official project website or Wikipedia.

This wiki should support you in the development of railML® interfaces and inform you about the basic elements and modelling concepts of the railML® schema.

This wiki is being kept in English. At certain points information is provided additionally also in German and/or . You are invited to contribute to this wiki. Please, see our guideline "How to join the railML wiki" to get to know the standards of railML's wiki and the procedure for getting a writer's account.

railML® (railway Markup Language) ist ein offenes, XML-basiertes Datenaustauschformat zur gegenseitigen Benützbarkeit der Daten von Anwendungen im Eisenbahnbereich. Für weitere Informationen besuchen Sie bitte die offizielle Projektwebsite oder Wikipedia.

Ziel dieses Wikis ist, Sie bei der Entwicklung von railML®-Schnittstellen zu unterstützen und Sie über die grundlegenden Elemente und Modellierungskonzepte des railML®-Schemas zu informieren.

Dieses Wiki wird auf Englisch geführt. Einzelne Informationen stellen wir außerdem auf Deutsch und zur Verfügung. Sie sind herzlich eingeladen, sich an der Entwicklung dieses Wikis zu beteiligen. Lesen Sie dazu bitte unseren Leitfaden „How to join the railML wiki“, um sich mit den Standards des railML®-Wikis vertraut zu machen und die Vorgangsweise zur Erteilung eines Autorenaccounts kennenzulernen. 


anglais.  allemand

Current railML schema

Currently there exist four subschemata: Infrastructure (IS), Timetable and Rostering (TT), Rollingstock (RS) and Interlocking (IL). Elements that do not fit into this structure are subsumed in the class Common (CO).

Open http://www.railml.org/index.php/railml-schemas.html for a list of the current coordinators of the respective schemas.

Timetable and Rostering (TT)

The timetable subschema is part of the complete railML schema providing a data structure in XML language for the exchange of railway specific data. It is the subschema that is employed most.

The timetable schema provides container for all data about any kind of timetables for operational or conceptional purposes. A flexible description of operating periods, which are important elements while dealing with timetables, is also included in the schema.

The subschema contains the following information:

  • Operating Periods: The operating days for train services or rostering.
  • Train Parts: The basic parts of a train as a sequence of operation or control points with the same characteristics such as formation and operating period. The train part includes the actual information regarding the path of the train as well as the corresponding schedule information.
  • Trains: One or more train parts make up a train and represent either the operational or the commercial view of the train run.
  • Rostering: Train parts can be linked to form the circulations necessary for rostering (rolling stock schedules).

Infrastructure (IS)

The railML® Infrastructure subschema is focused on the description of the railway network infrastructure including all its various facets that are needed by the data exchange applications. In particular, the railML infrastructure schema contains the following information:

  • Topology. The track network is described as a topological node edge model.
  • Coordinates. All railway infrastructure elements can be located in an arbitrary 2- or 3-dimensional coordinate system, e.g. the WRG84 that is widely used by today's navigation software.
  • Geometry. The track geometry can be described in terms of radius and gradient.
  • Railway infrastructure elements enclose a variety of railway relevant assets that can be found on, under, over or next to the railway track, e.g. balises, platform edges and level crossings.
  • Further located elements encompass elements that are closely linked with the railway infrastructure, but that "cannot be touched", e.g. speed profiles and track conditions.

Rollingstock (RS)

The rollingstock subschema is part of the complete railML schema providing a data structure in XML language for the exchange of railway specific data.

The rollingstock schema provides container for all data about any kind of rail vehicles including locomotives, multiple units, passenger and freight wagons. The second part of the schema enables the combination of single vehicles to formations as a fixed composition within a train or an entire train. It is intended to use this data schema for vehicle management as well as for detailed run-time calculations.

The Rollingstock schema comprises the following features:

  • separate parts for vehicles and for train parts or complete trains
  • possible specification of vehicle families and individual vehicles using the common features of the family
  • different level of detail for data
  1. vehicle as black box (with respect to dynamic characteristics) with only mean values
  2. vehicle as black box (with respect to dynamic characteristics) with curves for particular values being variable within the operating range
  3. vehicle as white box with details about the internal propulsion system
  • vehicles with motive power, for passenger or freight use
  • combination of vehicles to formations, i.e. train parts or complete trains

Interlocking (IL)

The interlocking subschema is under active development from 2015.

Common (CO)

The Common class shall cover all topics, which affect all other railML-schemas alike.

The actual planned tasks and enhancements can be found at Trac-Tickets of the railML development space.

There is also a "historic" collection of proposed Data Types for the Common subschema. It was developed in the preparation works of railML version 1.1. Some of the suggestions are already implemented in the stable railML 2.0 release. Other extensions wait for users with strong needs for them.

Prospect on Future Schemata

Shift planning

Additional to (vehicle) rosterings, there are ideas for implementing (personnel) shift planning.

Station asset management and properties

A schema for station databases, asset management and properties was developed in the early 2000's but place on hold due to the very limited use cases at this time. With a focus to the upcoming [PRM] a reopening of the development might be started depending from sectors needs in 2016 ff.

Users and Developers Guides

Contact

Feel free to direct any comments, questions or remarks to the coordinators of railML.

For our contact information see Contact

Enjoy the Wiki!

Retrieved from "https://wiki2.railml.org/index.php?title=Main_Page&oldid=4521"