Home » railML newsgroups » railml.timetable » Infrastructure train number
Re: Infrastructure train number [message #1355 is a reply to message #1338] Thu, 02 June 2016 12:16 Go to previous message
Vasco Paul Kolmorgen
Messages: 55
Registered: November 2004
Member
This issue was discussed in the railML's Timetable developer meeting in Berlin on June 2nd, 2016.

Conclusion: The timetable experts wants to keep the operational train number (betriebliche Zugnummer) as the primary number for the infrastructure manager and a additional attribute will reduce interoperability.

Additional for most European IM's and RU's the Unique Train Transport ID by ERA introduced in railML 2.3 (see Ticket 236) will solve the problem.

Regards,
--
Vasco Paul Kolmorgen
railML.org Coordinator
Dresden; Germany www.railml.org
 
Read Message
Read Message
Read Message
Previous Topic: Protocol developer meeting 22nd January 2016 at PSI
Next Topic: Request for a new optional attribute for train coupling and sharing
Goto Forum:
  


Current Time: Sat May 04 17:14:44 CEST 2024