| "Actual" train data (was: "stop post" / "platform edge" reference from ocpTT) [message #869 is a reply to message #867] |
Fri, 09 November 2012 15:20   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Dear Dirk, Andreas and others,
Dirk Bräuer <dirkbraeuer(at)irfpde> writes:
>> By the way, now that we are going to support delay infos, what about
>> changes in tracks and platforms? Well, maybe an issue for 3.0 and a
>> dedicated scheme for operation...
>
> This is a much more general question: To take a train to a different
> track in a station can be generalised to redirect a train not only in
> a station. At least, the topic of 'actual' train information in
> contrary to 'timetable' information is much wider (redirecting
> trains, replacing trains, replacing vehicles, wrong formation order,
> splitting trains...). We cannot possibly provide alternative 'actual'
> attributes for each 'timetable' attribute.
>
> We should provide a solution for 'actual' train information in general
> later (earliest in 3.0). This should start with providing a solution
> to specify a certain operating day out of the scheduled days as you
> already have claimed in another tread. Until that, we should keep
> discussions on 'actual' information out of the 'timetable' scheme. In
> my opinion this includes the delay information.
Thank you, Dirk, for separating this part of discussion.
I filed a Trac ticket for this issue:
http://trac.assembla.com/railML/ticket/188
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
