Home » railML newsgroups » railml.timetable » Delay Causes Representation in RailML
Re: Delay Causes Representation in RailML [message #822 is a reply to message #820] Thu, 11 October 2012 22:21 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
> Nevertheless I would prefer an approach to define the delay causes
> as extensible enumeration lists.

I agree.

> I would presume there could be multiple causes to be defined for a
> single delay. Am I right?

Not basically. If you allow multiple reasons you should also create a
possibility to note the basic (earliest) reason - the other's being caused
by that one. Possibly a time-stamp per reason could be useful - time when
the certain reason was added. The basic one is the one with the earliest
time-stamp.

I would suggest to allow multiple reasons in a kind they could easily be
extended later (e. g. enumerable element).

Best regards,
Dirk.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: reference from timetable's <stopDescription> to infrastructure's <stopPost>
Next Topic: Internationalized 'messageText' in 'connection'
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun May 19 04:50:59 CEST 2024