| Re: Delay Causes Representation in RailML [message #901 is a reply to message #851] |
Tue, 27 November 2012 12:40  |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Hello Joachim, Matteo and others,
At the railML-conference in Zurich we agreed on discussing the aspect of
"actual/real-time" data in a work group after publishing the 2.2
release.
Nevertheless the current railML schemas provide some possibilities for
"actual" data - e.g. the ocpTT/times/@scope attribute.
<ocpTT ...>
<times scope="scheduled" arrival="10:15:00" departure="10:25:00"/>
<times scope="actual" arrival="10:20:17" departure="10:24:13"/>
</ocpTT>
That means that the train part arrived ca. five minutes too late and
departed ca. one minute too early.
coord(at)timetablerailmlorg (Joachim Rubröder) writes:
> 1. There is currently no entity for a 'delay' event in the timetable but
> several '...Delay' attributes within the statistic element
For simple arrival and departure delays the 'statistics' element is not
needed, as shown above.
> 2. A definit list of delay causes would be preferable, but is not
> obvious to define
We agreed on an free string field, that may be pre-defined by a separate
XML file from the railML domain and/or pre-defined by a customer
specific XML file. The UIC-Leaflet would be a good starting point.
> I would therefore suggest to provide an additional "any"-attribute for the
> elements with delay information (mean, median, standardDeviation) as
> immediate quickfix measure for the version 2.2
I would welcome an 'anyAttribute' in the 'times' element. As shown
above, the 'statistics' elements are not needed for this kind of
'actual' data.
As discussed at the railML-conference in Zurich there are strong
arguments against the exchange of 'statistics'-results because of the
lack of transferring its algorithms and covered data set.
> and keep the discussion
> running to get an idea of the appropriate way of describing current data
> and delays in a later version 2.3 or 3.0 of railML.
http://trac.assembla.com/railML/ticket/170
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
