Home » railML newsgroups » railml.timetable » [railML2] Inconsistency in documentation of <timetablePeriod>
[railML2] Inconsistency in documentation of <timetablePeriod> [message #3565] Wed, 16 April 2025 13:07 Go to next message
Marharyta Vyskarka is currently offline  Marharyta Vyskarka
Messages: 21
Registered: April 2025
Junior Member
Hello everyone,

An inconsistency in documentation has been brought up to me. The wiki page for <timetablePeriod> states in the notes "startDate and endDate may be used together only, so there are no "open" periods allowed.»[1], but semantic constraint TT:001 says "if both are given" regarding startDate and endDate of a <timetablePeriod>, from which we can deduce one or both can be left out.

Which one is considered correct?

Best regards,
Marharyta Vyskarka

[1] https://wiki2.railml.org/wiki/TT:timetablePeriod#:~:text=sta rtDate%20and%20endDate%20may%20be%20used%20together%20only%2 C%20so%20there%20are%20no%20%22open%22%20periods%20allowed


Marharyta Vyskarka – Software Developer
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [railML2] Inconsistency in documentation of <timetablePeriod> [message #3666 is a reply to message #3565] Wed, 02 July 2025 09:18 Go to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 213
Registered: April 2007
Senior Member
Hi,

we discussed this issue in the last timetable developer meeting and I updated the wiki page afterwards. There is the option to either not provide startDate and endDate at all, thus indicating that the described schedule is abstract and not fixed to a specific time period, or specify both. If both are specified the timetable is fixed in time. This is necessary for the evaluation of bitMasks of the operatingPeriods to work properly. Accordingly, it is not expected to use the attribute bitMask of operatingPeriod if the startDate and endDate of the timetablePeriod is not set.


Best regards, Milan


Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railML 3] Modelling of Capacity Allocations
Next Topic: [railML3] Proposal for new semantic constraints and change of existing ones
Goto Forum:
  


Current Time: Mon Feb 09 10:09:42 CET 2026