| Re: [railML2] Adding the RouteId to the TafTapTsiTrainID [message #3141 is a reply to message #3117] |
Mon, 16 October 2023 16:50  |
Milan Wölke
Messages: 141
Registered: April 2007
|
Senior Member |
|
|
Hi Bert,
Thanks for bringing this up. If I understand you correctly you are suggesting to add the value RO from TAF TSI ObjectType to the objectType attribute enumeration ( https://wiki2.railml.org/wiki/TT:tafTapTsiTrainID_train#Attr ibutes_of_tafTapTsiTrainID_.2F_Attribute_von_tafTapTsiTrainI D).
In general I would agree with this idea, however this would imply to publish a railML 2.6 with this extension. Also when doing this I would opt to also correct the cardinality of tafTapTsiTrainID, so that more than one can be specified per train as this is better in line with the TAF/TAP TSI.
Is this what you are asking for? If, so, this would be the first clearly defined requirement for railML 2.6. Is there others who would be interested in this? If this is indeed what you are asking for, then we should also ask this question at the conference on November 8th, 2023 in Rome. It is a big decision for us as railML and we need to carefully consider the pros and cons.
The other option you would have is to specify a custom extension to allow specification of the RouteID. I think the best possible approach for this would be to create an extension for train called sth like additionalTafTapTsiObjectIdentifier and populate this with a structure that is built like the existing tafTapTsiTrainID with an extended objectType enumeration.
Please let me know what you think.
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
