| [railML3] Semantic Constraint TT:002 <operationalTrainVariant> [message #3680] |
Thu, 31 July 2025 15:11  |
Milan Wölke
Messages: 213 Registered: April 2007
|
Senior Member |
|
|
Hi all,
in order to properly follow to the process of introducing semantic constraints I want to inform you about the following semantic constraint that was proposed by the timetable developer group:
When calculating which <operationalTrainVariant> of an <operationalTrain> is valid on a particular day always a maximum of one active <operationalTrainVariant> shall be the result. If the result is more than one <operationalTrainVariant>, all except one shall be marked as <isCancelled> or <isOnRequest>.
This constraint ensures that on any given day, only one active <operationalTrainVariant> exists, preventing ambiguity in train operations. For exporters, it clarifies which variants and how many to output, while importers can reliably interpret the data without the need of resolving conflicts. This simplifies understanding of railML 3's timetable logic by aligning it with the real-world principle that a train follows only one operational plan per day.
This post is intended to give you, the community, the opportunity to let us know if you disagree with this semantic constraint. If you do, please let us know what your intended usage would be that lies outside the proposed constraint.
Thanks 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: Thu, 31 July 2025 15:16] Report message to a moderator
|
|
|
|
| Re: [railML3] Semantic Constraint TT:002 <operationalTrainVariant> [message #3717 is a reply to message #3680] |
Tue, 09 September 2025 12:59  |
Milan Wölke
Messages: 213 Registered: April 2007
|
Senior Member |
|
|
As there have been no objections, we decided to change the state of the above semantic constraint to approved at the last coordinators meeting.
The wiki has been updated accordingly.
Best regards, Milan
Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|