Home » railML newsgroups » railml.timetable » Delay Causes Representation in RailML
Re: Delay Causes Representation in RailML [message #832 is a reply to message #831] Fri, 19 October 2012 11:43 Go to previous messageGo to previous message
Andreas Tanner is currently offline  Andreas Tanner
Messages: 52
Registered: March 2012
Member
> Rather I would allow to use the original operating periods from the
> planning data (e.g., "daily") and provide an additional attribute
> "runDay" that identifies the instance the delay refers to.

The attribute could be anchored at the <times> element:

<ocpTT ocpRef=...>
<times scope="actual" runDay="01.01.2012" ... />
<times scope="actual" runDay="02.01.2012" ... />

Then, "runDay" should only be allowed for times with scope actual to
avoid that it is abused as a replacement for OperatingPeriods.

This way, one
> could just "enrich" a timetable with actual run information.
>
... even with information for multiple days within one file, with clear
mapping to the planning data.

--A.

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 05:43:56 CEST 2024