| [railML2] Usage of //ocpTT/times/@scope [message #2492] |
Tue, 14 July 2020 15:37  |
Milan Wölke
Messages: 139
Registered: April 2007
|
Senior Member |
|
|
Hi community,
the railML's TT developer group has decided to clarify the documentation
on <trainPart/ocpsTT/ocpTT/times>@scope
(https://wiki2.railML.org/index.php?title=TT:times). In that regard we
first collected how <times> is used among the members of the developer
group. The following list describes the common understanding as of today:
"calculated": Times resulting from the running time simulation; not yet
communicated to a party.
"scheduled": Operational times agreed between IM and RU; the arrival and
departure time as operationally scheduled
"published": Customer related times communicated from the RU to the end
customer (passenger/freight forwarder/...; e.g an earlier departure time
than @scheduled which is communicated to the passengers).
Sometimes they could be also less precise than the @scheduled times,
e.g. scheduled times are precise down to the second, while published
times could be limited to minutes. Also published times are often
provided only for the ocpTTs of a train, where a difference between
@scheduled and @published occurs (to be confirmed by the community!).
"actual": Describes measured times that the train generated by its run.
So far we do not know of usage for the other enumeration values of
<trainPart/ocpsTT/ocpTT/times>@scope ("earliest" and "latest").
Which of the 6 values are you using in your tools and systems? What is
the current semantics in place?
You would help us a lot, if you could provide your understanding of
<times> in your tools, so we can see if we have a consensus and thus can
sharpen the documentation to improve understanding for new people using
railML. This also allows us to choose correct and clear modelling when
developing the TT section of railML 3.x.
Thanks in advance.
Best regards, Milan
--
Milan Wölke - Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany
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
