| Re: Referenzierung von ausgefallenen Zügen / Referencing of canceled trains [message #1442 is a reply to message #1436] |
Tue, 08 November 2016 16:47   |
Philip Wobst
Messages: 47
Registered: November 2013
Location: Hanover, Germany
|
Member |
|
|
Hello Mico,
currently there is no such attribute for the train. This is most likely do to the fact that we do not have a unique train identification across individual railML files at this time. With the possibility to add cancellations in railML 2.3 it might be a better approach to include the cancelled train in the file as well and then use the direct ID reference to the train instead of the 'soft link' to a code of a train that is not in the file.
I do have comments/remarks regarding your approach and these
1. Reference to the train code
The reference in the @replacementOf attribute looks like the @code attribute of another train. Currently we do not yet have a unique key for a specific 'train' in railML and thus the code in your example would have to be such an internal key to identify two train elements across two railML files.
2. Partial replacement
How would you expect to handle instances where the operating days of the original train do not match the replacement train? Can two original trains be replaced by 1 replacement train and vice versa?
3. Attribute namespace
I gues this is already clear but your own extension would have to have a different namespace - e.g. sbb:replacementOf="..."
I would hope that there is a way to identify this in the TAF/TAP TSI context and will ask one of our TT developers (in the railML TT developer group) to provide feedback if possible.
Best regards,
Philip
--
Philip Wobst
railML.org Timetable coordinator
Phone: +49-511-33699 498
Dresden; Germany www.railml.org
[Updated on: Wed, 09 November 2016 14:17] by Moderator Report message to a moderator |
|
|
|
Members
Search
Help
Login
Home
