|
|
| Re: [railML2] Inconsistency in documentation of <timetablePeriod> [message #3666 is a reply to message #3565] |
Wed, 02 July 2025 09:18  |
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
|
|
|
|