| [railML 2] New semantic constraint for <operatingPeriod> [message #3458] |
Wed, 12 February 2025 10:03  |
Milan Wölke
Messages: 206
Registered: April 2007
|
Senior Member |
|
|
Hi all,
in response to feedback from a railML partner I would like to propose the following semantic constraint for the railML 2 operatingPeriod. It basically just encodes the documented and well known practice of how to use the attribute @bitMask in a semantic constraint.
I propose the following constraint:
The length of the attribute @bitMask is defined by the number of days enclosed by the <timetablePeriod>'s @startDate and @endDate attributes. For each day either a 1 or a 0 is to be included in the @bitMask, each defining if the <operatingPeriod> is active (1) that day or not (0).
What do you think? Any objections on this? How could the wording be improved so that we dont have misunderstandings with people new to railML?
Thank you for your feedback in advance.
Best regards, Milan
Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
[Updated on: Wed, 12 February 2025 12:01] Report message to a moderator |
|
|
|
Members
Search
Help
Login
Home
