Main Page: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[unchecked revision][checked revision]
(typos)
 
(92 intermediate revisions by 9 users not shown)
Line 1: Line 1:
=== Welcome to the railML Wiki / {{Deu| Willkommen im railML-Wiki}}===
{{navi}}
=== Welcome to the {{rml}} wiki / {{Deu| Willkommen im {{rml}}-Wiki}} ===
{| 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 {{wikipedia|railML|the wikipedia {{rml}} article}}.


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 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 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. Some information is provided additionally also in {{Deu|German}}. 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]].


'''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:*" | {{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 {{wikipedia|railML|den Wikipedia-Artikel über {{rml}}|de}}.}}


{{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|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.}}
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 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 railML subschema ==
== Current {{rml|2}} subschemas ==


=== Infrastructure (IS) ===
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.


==== General Information ====


The Infrastructure subschema contains a data structure for the storage of


* tracks, switches and the topology of a line
=== Infrastructure (IS) ===
* various operations and control elements (e. g. signals along the track)
{{main|Infrastructure}}
* tunnels, bridges
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:
* any kind of "border" (owner change, gauge change, axle load change, electrification, ...)
* Topology. The track network is described as a topological node edge model.
* visualization data for displaying a net
* 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.
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.
* 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.
==== Documentation ====
 
The following lists provide links to Infrastructure Documentation sites:
 
* [[:Category:Infrastructure_Elements | Infrastructure Elements]]
* Infrastructure Examples
 
==== Use Cases ====
 
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]]
 
=== Timetable and Rostering (TT) ===
 
==== 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 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.
 
With the new branch of {{TT:Tag|rosterings}} it is intended to use this data schema as well for conceptional rolling stock schedules.
 
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.
 
==== Documentation ====
 
The following lists provide links to Timetable Documentation sites:
 
* [[:Category:Timetable_Elements | Timetable Elements]]
* [[TT:attributes | Timetable Attributes]]
 
 
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) ===
{{main|Rollingstock}}
The [[rollingstock|rollingstock subschema]] is part of the complete [https://www.railML.org {{rml}}] schema providing a data structure in XML language for the exchange of railway specific data.


==== General Information ====
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 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 103: Line 42:
* possible specification of vehicle families and individual vehicles using the common features of the family
* possible specification of vehicle families and individual vehicles using the common features of the family
* different level of detail for data
* different level of detail for data
:# vehicle as black box (with respect to dynamic characteristics) with only mean values
:# vehicles as black boxes (with respect to dynamic characteristics) with only mean values
:# vehicle as black box (with respect to dynamic characteristics) with curves for particular values being variable within the operating range
:# vehicles as black boxes (with respect to dynamic characteristics) with curves for particular values being variable within the operating range
:# vehicle as white box with details about the internal propulsion system
:# vehicles as white boxes with details about the internal propulsion system
* vehicles with motive power, for passenger or freight use
* vehicles with motive power, for passenger or freight use
* 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.
=== Timetable and Rostering (TT) ===
 
{{main|Timetable|Timetable and Rostering}}
==== Documentation ====
The [[timetable|timetable subschema]] is part of the complete [https://www.railML.org {{rml}}] schema providing a data structure in XML for the exchange of railway specific data. It is the subschema that is most widely used.
 
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 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) ===
=== Common (CO) ===
{{main|Common}}
The [[Common]] class shall cover all topics, which affect all other {{rml}} schemas alike.


==== General Information ====
The currently planned tasks and enhancements can be found {{site|https://development.railml.org/railml/version2/-/issues|in the {{rml|2}} ticketing system}}.


This subschema shall cover all topics, which affect all other railML-schemas alike.
== 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 actual planned tasks and enhancements can be found at [http://trac.railml.org/report Trac-Tickets] of the railML development space.
The codelists are identically available for {{rml|2}} and {{rml|3}}.


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.
==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]].


==== Documentation ====
== Users and Developers Guides ==
 
{{main|Dev:Guides}}
The following lists provide links to Common Documentation sites:
===Using and developing {{rml}}===
* [[:Category:Common_Elements | Common railML elements]]
* complete {{rml|2}} trees with links to the corresponding wiki pages:
* [[CO:attributes | Common railML Attributes]]
**[[Dev:XMLtree|The  {{rml|2.5}} tree]] (current)
 
**[[Dev:XMLtree/2.4|The  {{rml|2.4}} tree]]
==== FAQ ====
**[[Dev:XMLtree/2.3|The  {{rml|2.3}} tree]]
 
* [[:category:concept|Basic {{rml}} Concepts]]
Some general questions about handling railML files are summerized on the following wiki-sites:
* [[Dev:example|{{rml}} example files]]
 
* [[Dev:Downloading and using railML®|Downloading and using {{rml}}]]
* [[CO:fileConventions | Conventions for railML files]] (file name extensions, compressed files, and other)
* [[Dev:Syntactic_Guidelines | Syntactic guidelines for a corporate code base]]
* [[CO:identities | Handling identities]] ({{Attr|id}} values)
* [[Dev:Coding_XML_Components | Coding styles for XML components in {{rml}} schemas]]
* [[CO:catalog | Local versus web-based validation]] (XML catalogs and XML namespaces)
* [[Dev:Guideline for participating in the development process|Guideline for participating in the development process]]
* [[CO:versions | Versioning policy]] (version numbers, versioned XML namespaces)
* [[Dev:Creating_instructions|Creating instructions for new {{rml}} elements]]
* [[CO:versioning | Officially released versus developer version]] (Homepage, Subversion)
* [[Dev:Use_cases|Guideline on Use cases]] — what is a use case, where to find them and how to contribute to them.
* [[CO:tickets | Discussed versus agreed features]] (Newsgroup, Trac Tickets)
* {{site|https://www.railml.org/en/developer/certification.html|Certification guideline|inlang=silent}}
* [[CO:xmlSyntax | XML Syntax issues]] (Attribute delimiters, Character references)
* [[Dev:Semantic Constraints|How to deal with Semantic Constraints]]
* [[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.
===Improving the Wiki===
 
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 ===
 
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 ===
 
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.
== Developers Guides ==
 
* [[Dev:Syntactic_Guidelines | Syntactic guidelines for a corporate code base]]
* [[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: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]]


Feel free to direct any comments, questions or remarks to the coordinators of railML.
==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!
Enjoy the Wiki!
{{interwiki}}

Latest revision as of 12:29, 22 February 2024

RailML Trademark RGB V2.png
XML Railway exchange format
https://railML.org
Latest release: 2.5
(September 1st, 2021)
 
Main Menu
 
Subschemas
XML tree
UML diagrams
Use cases
Versions & Changes

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 the wikipedia railML® article (Wiki banner.png).

This wiki is dedicated to all versions of railML® 2. A separate wiki for railML® 3 is available here. 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. Some information is provided additionally also in German. You are invited to contribute to this wiki and to the development of the railML® schema. 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. You can find further guidelines on railML® in section #Users_and_Developers_Guides.

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 den Wikipedia-Artikel über railML® (Wiki banner.png 🇩🇪).

Dieses Wiki ist sämtlichen Versionen von railML® 2 gewidmet. Ein separates wiki für railML® 3 finden Sie hier. 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 zur Verfügung. Sie sind herzlich eingeladen, sich an der Entwicklung dieses Wikis sowie des railML®-Schemas 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. Weitere Leitfäden, die railML® betreffen, finden Sie im Abschnitt #Users_and_Developers_Guides.

Current railML® 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 https://www.railML.org/en/user/subschemes.html (link to the railML® website)) for questions and enquiries. Additional subschemas will be developed only in the railML® 3 domain. Please, frame the regarding suggestions and contributions to this end.


Infrastructure (IS)

→Main Article: Infrastructure

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 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 Article: Rollingstock

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 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
  1. vehicles as black boxes (with respect to dynamic characteristics) with only mean values
  2. vehicles as black boxes (with respect to dynamic characteristics) with curves for particular values being variable within the operating range
  3. 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 Article: Timetable and Rostering

The timetable subschema is part of the complete 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 Article: Common

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

The currently planned tasks and enhancements can be found in the railML® 2 ticketing system (link to the railML® website).

Codelists

→Main Article: Codelists

Certain attributes require a choice from a vast, highly standardized but shifting set of values. For instance, there are many regional clearance gauge standards (external link). As to facilitate the usage and update of the sets, this Information is outsourced into codelists outside the railML® schema.

The codelists are identically available for railML® 2 and railML® 3.

Versions

The current railML®2 version is 2.5. For more details see our version timeline (link to the railML® website). An overview of the regarding licenses can be found under https://www.railml.org/en/user/licence.html (link to the railML® website). To learn about the version history and the changes between the respective versions see Dev:changes.

Users and Developers Guides

→Main Article: Dev:Guides

Using and developing railML®

Improving the Wiki

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=15409"