RailML (Data Exchange): Difference between revisions
| [checked revision] | [checked revision] |
m (railML<sup>®</sup> clarified) |
Ferri Leberl (talk | contribs) ({{rtm}}-template inserted) |
||
| Line 1: | Line 1: | ||
{{Overview|text=This page describes the relation between | {{Overview|text=This page describes the relation between {{rtm}} as model and railML as exchange format.}}<br /> | ||
Very closely related to the evolution of the | Very closely related to the evolution of the {{rtm}} is the work done by members of railML.org. | ||
railML<sup>®</sup> is an open-source XML-based data exchange format for IT applications in railways. railML® is developed and maintained by the railML.org initiative and it has been published so far up to version 2.3. Currently, railML.org is actively contributing to the UIC | railML<sup>®</sup> is an open-source XML-based data exchange format for IT applications in railways. railML® is developed and maintained by the railML.org initiative and it has been published so far up to version 2.3. Currently, railML.org is actively contributing to the UIC {{rtm}} Expert Group with the objective to base its new version, railML 3, on the fundament of the {{rtm}}. Thus, railML® 3.0 can be considered to being the exchange format for any infrastructure data base following the {{rtm}} concept. The current state of development of railML<sup>®</sup> 3 is described on the website besides infrastructure, railML<sup>®</sup> is also able to handle information about timetable, rolling stock and interlocking. Thus, being a widely applicable data exchange format, railML<sup>®</sup> is used by many railways, manufacturers and other institutions for internal and external data exchange. | ||
Further information on railML can be found at https://www.railml.org.<br /> | Further information on railML can be found at https://www.railml.org.<br /> | ||
<br /> | <br /> | ||
| Line 8: | Line 8: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| Logical model || '''The | | Logical model || '''The {{rtm}}''' is a generic railway data model designed to support current and future business needs. It is particularly useful for: <br /> | ||
* Engineering activities - mainly based on installations and components, and<br /> | * Engineering activities - mainly based on installations and components, and<br /> | ||
* Circulation activities - mainly based on routing and scheduling. | * Circulation activities - mainly based on routing and scheduling. | ||
|- | |- | ||
| railML<sup>®</sup> || '''railML 3''' is the latest evolution of the format created by railML.org. railML 3 was specifically developed to be compliant to the UIC's | | railML<sup>®</sup> || '''railML 3''' is the latest evolution of the format created by railML.org. railML 3 was specifically developed to be compliant to the UIC's {{rtm}}. | ||
|} | |} | ||
Thus, railML<sup>®</sup> can be viewed as the first benefit of | Thus, railML<sup>®</sup> can be viewed as the first benefit of {{rtm}}. Figure 2 summarises the role that {{rtm}} and railML<sup>®</sup> would play when fully integrated in existing systems.<br /> | ||
Investing in a standardised railway data exchange format will provide multiple benefits for the sector, including:<br /> | Investing in a standardised railway data exchange format will provide multiple benefits for the sector, including:<br /> | ||
| Line 31: | Line 31: | ||
|- | |- | ||
| '''What you should have learned'''<br /> | | '''What you should have learned'''<br /> | ||
* Difference between | * Difference between {{rtm}} and railML | ||
* Aim of railML and railML.org | * Aim of railML and railML.org | ||
* What you can do with | * What you can do with {{rtm}} and railML | ||
|} | |} | ||
Revision as of 17:59, 8 March 2017
|
Very closely related to the evolution of the RailTopoModel® is the work done by members of railML.org.
railML® is an open-source XML-based data exchange format for IT applications in railways. railML® is developed and maintained by the railML.org initiative and it has been published so far up to version 2.3. Currently, railML.org is actively contributing to the UIC RailTopoModel® Expert Group with the objective to base its new version, railML 3, on the fundament of the RailTopoModel® . Thus, railML® 3.0 can be considered to being the exchange format for any infrastructure data base following the RailTopoModel® concept. The current state of development of railML® 3 is described on the website besides infrastructure, railML® is also able to handle information about timetable, rolling stock and interlocking. Thus, being a widely applicable data exchange format, railML® is used by many railways, manufacturers and other institutions for internal and external data exchange.
Further information on railML can be found at https://www.railml.org.
Considering the work done by the railML® initiative project in co-operation with this modelling work, there are currently two products available to facilitate the exchange of data in the domain of railway infrastructure.
| Logical model | The RailTopoModel® is a generic railway data model designed to support current and future business needs. It is particularly useful for:
|
| railML® | railML 3 is the latest evolution of the format created by railML.org. railML 3 was specifically developed to be compliant to the UIC's RailTopoModel® . |
Thus, railML® can be viewed as the first benefit of RailTopoModel® . Figure 2 summarises the role that RailTopoModel® and railML® would play when fully integrated in existing systems.
Investing in a standardised railway data exchange format will provide multiple benefits for the sector, including:
- Improved data quality,
- More efficient business performance,
- Streamlined and re-usable development,
- Integrated IT systems, and
- Return on investments.
Detailed Information about railML® can be found on the railML® website at www.railML®.org.
What you should have learned
|
| Back To | Previous Chapter | Next Chapter |
|---|---|---|
| RTM Use Cases and Application Examples | - | Railway Infrastructure Manager Database |