News List Latest

The Journey of the railML3 Development

The railML3 development has continuously been carried out since almost 3 years. Under the lead of railML.org infrastructure coordinator, Christian Rahmig, more and more needs of the railway community were integrated via use cases. Amongst others these contain Schematic ...

Read more …

Adjustments of railML Wiki for railML 3 documentation

railML® 3 will bring a structural break, as it has been developed from scratch. On the one hand this means, that it will not be downward compatible. Yet it also bears the huge advantage of starting new and therefore coming to an end with difficulties in railML 2. In order ...

Read more …

railML 2.4/3.1 Roadmap: 33rd railML Conference

33rd railML Conference at Thales Headquarter in Berlin Spring is always the time for the German speaking railML community to come together and exchange about completed, ongoing and future railML.org development work. In 2018 everybody came together on invitation ...

Read more …

Collaboration Improved: railML3 Dissemination and Feedback Workshops

The most important requirement railML schemas shall meet, is to satisfy the needs of practical application of todays and tomorows railways. Therefore, the developments always take place on the foundation of use cases and in collaboration with the railway sector. In order ...

Read more …

Current changes and future enhancements in the railML Wiki

For all developers of railML interfaces the railML Wiki is the first point of contact for background information and questions concerning the programming of interfaces. Therefore, a constant maintenance and clear categorization of the contents, and an extension of the ...

Read more …

Handover of railML Interlocking Coordination towards a Continuous Development

Following his decision of May 17th, 2017 Mr. Dr. ir. Bob Janssen from Siemens Netherlands resigned from his role as railML Interlocking coordinator on November 8th, 2017 and handed over the work to Dr. Jörg von Lingen from Institut für Bahntechnik. We would like to thank ...

Read more …