Home » railML newsgroups » railml.timetable » Timetable updates
Re: Timetable updates [message #573 is a reply to message #572] Tue, 13 April 2004 14:57 Go to previous messageGo to previous message
thomas.kauer is currently offline  thomas.kauer
Messages: 15
Registered: January 2004
Junior Member
In respect to possible future use of the timetable-schema as an interface
for programs that treat with actual trains and not only with longtime
planning it should support the possibility to give delta-informations for
existing timetable data. So it would be useful to add the proposed
attribute <status>.
The <date> of the last change would be used in this respect to decide for
multiple changes which one is the last, that is to say which one is valid.



Joachim Rubröder wrote:

> This case is not especially treated in the schema. But you are free to
> put a whole big timetable with thousand trains in a file, or to send
> just a few update-trains. I think this is a task for the receiving
> program to identify the trains as new or known ones.

> There is the <date> attribute in <train> which could be used as date of
> the last change and I thought about adding another optional attribute
> <status> in the <train> element (as used within SBB) wich could have
> values like "new", "changed", "omitted", ...
> Would this be helpful?

> Joachim Rubröder

> Tobias Bende schrieb:
>> I have a question on updates of existing timetables. Given that a file
>> with a complete timetable (especially in a format like RailML) is very
>> large it is in practice often desirable to be able to send updates when
>> something changes as opposed to recreate and send the entire file. Is this
>> something that has been considered?
>>
>> Tobias Bende
>>
>>
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Daylight saving time
Next Topic: [Proposal]
Goto Forum:
  


Current Time: Fri Apr 19 22:44:15 CEST 2024