Home » railML newsgroups » railml.timetable » [railML2] Scope of ocpTT.trainReverse
[railML2] Scope of ocpTT.trainReverse [message #2865] Thu, 16 December 2021 15:00 Go to next message
Andrea Hoffmann is currently offline  Andrea Hoffmann
Messages: 3
Registered: October 2020
Junior Member
Dear TT community,

Could anyone please clarify the scope of the attribute ocpTT.trainReverse? According to this Wiki entry (section "Semantical background"), it refers to the train containing it. For various reasons (I'd be willing to give an example if the topic should prove to be controversial), I would expect it to relate to its trainPart only.

Best regards,
Andrea Hoffmann
Re: [railML2] Scope of ocpTT.trainReverse [message #2866 is a reply to message #2865] Tue, 21 December 2021 11:22 Go to previous messageGo to next message
Milan Wölke is currently offline  Milan Wölke
Messages: 120
Registered: April 2007
Senior Member
Hi Andrea,

after discussing this internally, we have come to the conclusion that in general that statement is correct. <ocpTT>.trainReverse does apply to the full train and it is expected that all train parts that are travelling alongside it have it set as well. There are a few borderline cases like for example a train that changes direction partially when being split at a station, but even then it is the full commercial train (one of the two being split there) that changes direction completely. Looking at the operational trains its also a true statement, either you model this with 3 operational trains, which would mean that none really reverses direction as they are all starting or ending. Alternatively you could model it with two operational trains then one of them starts the other may change direction, but if it does then it does so completely.

The argumentation is that a train cannot really partially change direction. Originally the attribute was introduced to encode that a change of direction occurs at a station in order to allow printing a "<->" symbol in train schedules. In this use case usually detailed formation information is missing and the attribute was intended to also allow encoding direction change in such cases.

I hope that helps. If it doesnt please dont hesitate to ask further.

Best regards, Milan


Milan Wölke - Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [railML2] Scope of ocpTT.trainReverse [message #2867 is a reply to message #2866] Tue, 21 December 2021 11:44 Go to previous message
Andrea Hoffmann is currently offline  Andrea Hoffmann
Messages: 3
Registered: October 2020
Junior Member
Hi Milan,

thanks for the thorough reply. Since the attribute rather seems to be referring to all elements contained in the same <trainPartSequence> as the <trainPartRef> that refers to the <trainPart> where trainReverse is set (and not the <train> element which could easily be confused with the physical train), I'd appreciate it if you could change the documentation accordingly. Thank you.

Best regards,
Andrea
Previous Topic: [railML 3] Level of detail for describing classes and capabilities of rolling stock
Next Topic: [railML3] Need for midOfTrain
Goto Forum:
  


Current Time: Sun May 29 04:57:07 CEST 2022