Working Groups

Currently the development of railML® is formed by four different active working groups; the Timetable Working Group, the Infrastructure Working Group, the Interlocking Developers Working Group and Ontology Working Group, which meet every four to eight weeks to exchange and discuss ideas and to identify needs.

(The rolling stock schema has been developed to a point where no further enhancements are currently necessary. Therefore no active working group exists for this subschema.)

The Infrastructure Working Group and the Interlocking Working Group have an international participant base from across the rail industry and are conducted in English. The Timetable Working Group primarily comprises members from German-speaking countries and communicates in German, although English-speaking participants are also encouraged to join.

Further information on the different subschemas can be found here.

If you are interested participating in one of our working groups and joining the railML community please do not hesitate to contact us.

Participation Guidelines

The participation of technical experts in the working groups is highly desired and contributes greatly to the goal-oriented modelling of the exchange format. For this purpose, the following conditions for participation are binding:

  • Dispatching enterprise is registered at railML.org (Status: Developer or User/Supporter in long term cooperation [usually > 3 years]);
  • 1-2 representative domain experts and 1-2 proxy domain experts (but a maximum of 3 in total) per enterprise and subscheme working group;
  • Long term participation (at least 9 months or one specified project) for the named domain expert in the working group
  • Regular and active participation in developers meetings/telcos (more than 3 times absence without excuse may lead to expelling)
  • Joining the development activities following the coordination of the responsible railML.org coordinator
  • Acceptance of the railML.org T&C (domain experts knowledge could become part of railML's specification) and Code of Conduct