View source for Main Page

{{navi}}
=== Welcome to the {{rml}} wiki / {{Deu| Willkommen im {{rml}}-Wiki}} / {{Fra|Bienvenue au Wiki du {{rml}}}}===
{| class="wikitable toptextcells" style="text-align:left vertical-align:top"
|- style="vertical-align:top;"
|style="width:45%" | {{rml}} ('''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 [https://www.railML.org official project website] or [https://en.wikipedia.org/wiki/RailML Wikipedia].

This wiki is dedicated to all Versions of {{rml|2}}. A separate wiki for {{rml|3}} is available {{wiki3|2=here}}. This wiki should support you in the development of {{rml}} interfaces and inform you about the basic elements and modelling concepts of the {{rml}} schema.

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 and to the development of the {{rml}} schema. Please, see our guideline "''[[dev: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. You can find further guidelines on {{rml}} in section [[#Users_and_Developers_Guides]].

|style="width:*" | {{Deu|{{rml}} ('''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 [https://www.railML.org offizielle Projektwebsite] oder [https://de.wikipedia.org/wiki/railML Wikipedia].}}

{{Deu|Dieses Wiki ist sämtlichen Versionen von {{rml|2}} gewidmet. Ein separates wiki für {{rml|3}} finden Sie {{wiki3|hier}}. Ziel dieses Wikis ist, Sie bei der Entwicklung von {{rml}}-Schnittstellen zu unterstützen und Sie über die grundlegenden Elemente und Modellierungskonzepte des {{rml}}-Schemas zu informieren.}}

{{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 sowie des {{rml}}-Schemas zu beteiligen. Lesen Sie dazu bitte unseren Leitfaden ''„[[dev:How_to_join,_edit_and_create_the_railML_wiki#How_to_join_the_Wiki|How to join the {{rml}} wiki]]“'', um sich mit den Standards des {{rml}}-Wikis vertraut zu machen und die Vorgangsweise zur Erteilung eines Autorenaccounts kennenzulernen. Weitere Leitfäden, die {{rml}} betreffen, finden Sie im Abschnitt [[#Users_and_Developers_Guides]].}}
|}

== Current {{rml|2}} subschemas ==

There are three subschemas for productive use: Infrastructure (IS), Timetable and Rostering (TT) and Rollingstock (RS). Elements that are needed by all subschemas or do not fit into this structure are subsumed in the class Common (CO). Please contact the coordinator of the respective schema (see {{site|https://www.railML.org/en/user/subschemes.html}}) for questions and enquiries. Additional subschemas will be developed only in the {{rml|3}} domain. Please, frame the regarding suggestions and contributions to this end.



=== Infrastructure (IS) ===
{{main|Infrastructure}}
The {{rml}} [[Infrastructure|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 {{rml}} 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 WGS84 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) ===
{{main|Rollingstock}}
The [[rollingstock|rollingstock subschema]] is part of the complete [https://www.railML.org railML] schema providing a data structure in XML language for the exchange of railway specific data.

The rollingstock schema provides a container for all data about any kind of railway vehicle 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
:# vehicles as black boxes (with respect to dynamic characteristics) with only mean values
:# vehicles as black boxes (with respect to dynamic characteristics) with curves for particular values being variable within the operating range
:# vehicles as white boxes 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

=== Timetable and Rostering (TT) ===
{{main|Timetable|Timetable and Rostering}}
The [[timetable|timetable subschema]] is part of the complete [https://www.railML.org railML] schema providing a data structure in XML for the exchange of railway specific data. It is the subschema that is most widely used.

The timetable subschema is used for all data necessary to exchange any kind of timetable for operational or conceptional purposes including the following information:
* Operating Periods: The operating days for train services or rostering.
* Train Parts: The basic parts of a train with the same characteristics such as formation and operating period. The train part includes the actual information regarding the path of the train as a sequence of operation or control points together with 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.
* Connections: The relevant connections/associations between trains at a particular operation or control point.
* Rostering: Train parts can be linked to form the circulations necessary for rostering (rolling stock schedules).

=== Common (CO) ===
{{main|Common}}
The [[Common]] class shall cover all topics, which affect all other railML-schemas alike.

The actual planned tasks and enhancements can be found {{ticket|in the {{rml|2}} ticketing system}}.

== Codelists ==
{{main|dev:codelists|Codelists}}
Certain attributes require a choice from a vast, highly standardized but shifting set of values. For instance, there are many regional {{external|https://en.wikipedia.org/wiki/Loading_gauge|clearance gauge standards}}. As to facilitate the usage and update of the sets, this Information is outsourced into [[dev:codelist|codelists]] outside the {{rml}} schema.

The codelists are identically available for {{rml|2}} and {{rml|3}}.

==Versions==
The current {{rml}}2 version is {{current}}. For more details see {{site|https://www.railml.org/en/developer/version-timeline.html|our version timeline}}. An overview of the regarding licenses can be found under {{site|https://www.railml.org/en/user/licence.html}}. To learn about the version history and the changes between the respective versions see [[Dev:changes]].

== Users and Developers Guides ==
{{main|Dev:Guides}}
===Using and developing {{rml}}===
* complete {{rml|2}} trees with links to the corresponding wiki pages:
**[[Dev:XMLtree|The  {{rml|2.5}} tree]] (current)
**[[Dev:XMLtree/2.4|The  {{rml|2.4}} tree]]
**[[Dev:XMLtree/2.3|The  {{rml|2.3}} tree]]
* [[:category:concept|Basic {{rml}} Concepts]]
* [[Dev:example|{{rml}} example files]]
* [[Dev:Downloading and using railML®|Downloading and using {{rml}}]]
* [[Dev:Syntactic_Guidelines | Syntactic guidelines for a corporate code base]]
* [[Dev:Coding_XML_Components | Coding styles for XML components in railML schemas]]
* [[Dev:Guideline for participating in the development process|Guideline for participating in the development process]]
* [[Dev:Creating_instructions|Creating instructions for new {{rml}} elements]]
* [[Dev:Subversion_Guidelines | Guidelines for handling the Subversion repository]]
* [[Dev:Use_cases|Guideline on Use cases]] — what is a use case, where to find them and how to contribute to them.
* {{site|https://www.railml.org/en/developer/certification.html|Certification guideline|inlang=silent}}
* [[Dev:Semantic Constraints|How to deal with Semantic Constraints]]

===Improving the Wiki===
* [[Dev:Wiki_Documentation_Guidelines | Guidelines to enhance the wiki documentation]]
* [[dev:How_to_join,_edit_and_create_the_railML_wiki#How_to_join_the_Wiki|How to join the {{rml}} wiki]]
* [[:category:template|Wiki-Templates]]
* [[Special:PopularPages|Access statistics]]

==Contact==
Feel free to direct any comments, questions or remarks to the coordinators of {{rml}}.

For our contact information see ''[[wiki.railML.org:Contact|Contact]]''
<hr>
Enjoy the Wiki!

[[railml3:Main Page]]