Home » railML newsgroups » railml.timetable » Proposal for new timetable schema version 2.0(?)
Re: operatingPeriods [message #664 is a reply to message #663] Tue, 26 September 2006 20:14 Go to previous messageGo to previous message
Joachim.Rubröder is currently offline  Joachim.Rubröder
Messages: 33
Registered: September 2004
Member
Hello,

I don't think we should regard operatingPeriods as a subelement of
timetablePeriods.

The operatingPeriod "11" in Switzerland means "on every days, treated as
mondays" (i.e. all mondays and days after a holiday). It is therefore
depending on a special timetablePeriod (wich is referenced by
"timetablePeriodID") and has its own bitMask. Anyway, you need different
serviceIDs (like "2005_11", "2006_11") to distinguish between the
operatingPeriod "11" in separate timetablePeriods.

But the german "TGL" or the swiss "17" (meaning "daily") or the real "on
every monday" are operatingDays with a short 7-day bitmask and clearly
independent of any timetablePeriod. They could be defined in any train and
keep valid, even if you transfere the timetable from one timetablePeriod
to the next.

Cheers,

Joachim

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Correct use of arrivalDay/departureDay
Next Topic: stopDescription
Goto Forum:
  

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

Current Time: Wed May 15 12:00:14 CEST 2024