Dirk Bräuer Messages: 313 Registered: August 2008
Senior Member
Dear Thomas and Christian,
I think this is very much related to the topic "Reversing trains and formations" which is already dealt with at <timetable> in railML 2.x [1]. The need for a Change of direction information is imho commonly agreed.
Currently, I do not see why there should be a greater problem to deal with this under railML 3.x than at 2.x. So, I would expect we get a similar solution at 3.x as we use in 2.x, a solution which gives the COD information at a certain train or train path under <timetable>.
If you see a crucial reason why this should be handled at <IS> rather than at <TT>, or may be I misunderstood the main point, please enlight me.