| Re: [railML3] Additional Train Identifiers [message #3733 is a reply to message #3722] |
Mon, 06 October 2025 12:19  |
Milan Wölke
Messages: 217
Registered: April 2007
|
Senior Member |
|
|
Hi Edward,
thanks for your post. I have a few questions for better understanding your requirements:
The headcode you are talking about, is this for commercial or operational trains?
The TSDUID is just a secondary ID used beside the head code in another system?
Are you additionally also using operational and commercial train numbers? Or are the ones mentioned above basically your version of this? Is there any relationship to the commercial and operational train numbers as they are known in railML?
Regarding the TRUST ID, is this just a 3rd external ID or id this semantically a little different. From your post I understand that is is used for collecting data regarding the actual operation of a train (in contrast to the other ones that seem focused on the planning of a timetable). If this is the case does the same daily train have the same TRUST ID every day or do these IDs imply a specific day?
The unique ID for an operating day or like you say timetable day is something, that we have not included so far. Might be interesting adding this.
Regarding the last one, Im afraid, I did not understand that. Could you make an example of what that last ID is and in what relationship it is with the timetable days included in a railML document. Thanks in advance.
Best regards, Milan
Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
