| Re: Delay Causes Representation in RailML [message #851 is a reply to message #818] |
Wed, 07 November 2012 16:38   |
Joachim Rubröder railML
Messages: 0
Registered: November 2019
|
|
|
|
Hello everybody,
Matteo Anelli wrote:
> Since the project want to integrate the FICHE UIC 450-2 delay causes (a
> two-digit number) I'd like to
> see some extended attributes on the Delay Entity. I think a generic
> attributes field should be sufficient,
> if not a string field for "causes". It's that possible?
Let me try to summarize the current discussion related to the delays.
1. There is currently no entity for a 'delay' event in the timetable but
several '...Delay' attributes within the statistic element
2. A definit list of delay causes would be preferable, but is not obvious
to define
3. The timetable schema was not intended for, but could be used to
describe real ex post data for statistical purposes, as it is done by SBB
with OTT
4. There is not yet a consensus about the proper way of describing delay
events
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 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.
Are there any objections?
Kind regards,
Joachim
-------------------------------------
Joachim Rubröder
Schema Coordinator: railML.timetable
--
----== posted via PHP Headliner ==----
|
|
|
|
Members
Search
Help
Login
Home
