| [railML3] Semantic Constraint TT:001 <operationalTrainSectionPart>/@next [message #3679] |
Thu, 31 July 2025 14:52  |
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:
The next attribute shall reference an <operationalTrainSectionPart> that is not referenced by any other next-reference. In other words: Within the chain of <operationalTrainSectionPart>s linked by the attribute next, there can be no element that has more than one predecessor. The @next reference must establish a one to one relationship between two <operationalTrainSectionPart>s.
This constraint is intended to make sure that the structure of the linked operationalTrainSectionParts is easily comprehensible and follows the idea the developer group had when designing the railML 3 timetable model. We decided that a structure that would allow for multiple predecessors for a next operationalTrainSectionPart would be too complex to be easily understood.
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
|
|
|
|
|
|
Members
Search
Help
Login
Home
