| [railML2] New semantic constraint for <trainPart> [message #3671] |
Wed, 09 July 2025 16:44  |
Milan Wölke
Messages: 217
Registered: April 2007
|
Senior Member |
|
|
Hi all,
we got a suggestion for a new semantic constraint for railML 2. It was pointed out to us that there is no semantic constraint yet making sure that when connecting two <trainPart>'s in a <trainPartSequence> the last <ocpTT> of the previous <trainPart> references the same <ocp> as the first <ocpTT> of the succeeding <trainPart>.
Therefore we suggest introducing the following semantic constraint:
When connecting <trainPart>'s in a <trainPartSequence> it shall be ensured, that the <ocp> referenced by the last <ocpTT> of the previous <trainPart> and the <ocp> referenced by the first <ocpTT> of the succeeding <trainPart> are the same.
Please let us know if you dont agree to the introduction of a semantic constrain like this.
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
