| [railML2] New semantic constraint for <trainPart> [message #3459] |
Wed, 12 February 2025 10:26  |
Milan Wölke
Messages: 240 Registered: April 2007
|
Senior Member |
|
|
Hi all,
in response to feedback from a railML partner I would like to propose two new semantic constraints for the <trainPart>.
The first ones purpose is to encode the intended relationship between a <trainPart>'s @timetablePeriodRef and its referenced <operatingPeriod>. I would propose the following wording:
The <operatingPeriod> referenced via a <trainPart>'s <operatingPeriodRef> child element and the referenced <timetablePeriod> referenced by its attribute @timetablePeriodRef must not contradict each other. If the referenced <operatingPeriod> references a <timetablePeriod> via its attribute @timetablePeriodRef it must be the same as the one referenced by the <trainPart>'s attribute @timetablePeriodRef if specified.
This should probably be displayed on the wiki page of <trainPart> as well as on the page of <operatingPeriodRef>.
The other semantic constraint I would like to proposed tries to ensure that all <trainPart>'s of a <train> only reference a single <timetablePeriod>. This rule is documented already in the wiki on the page of the <timetablePeriod>. I am proposing the following wording:
All <trainPart>'s of a <train> referenced via its child element <trainPartSequence> shall reference the same <timetablePeriod> via its optional attribute @timetablePeriodRef if specified.
This should be displayed at the <train> as well as at the <trainPart>.
What do you think? Do you have concerns? How could the wording be improved to avoid misunderstandings especially for people new to railML?
Thanks 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:04] Report message to a moderator
|
|
|
|
| Re: [railML2] New semantic constraint for <trainPart> [message #3510 is a reply to message #3459] |
Wed, 12 March 2025 11:08  |
Christian Rößiger
Messages: 85 Registered: March 2015
|
Member |
|
|
Hello Milan,
I generally agree with the content of your suggestions and don't see any great danger of misunderstandings.
However, there are a lot of other operatingPeriods (connections, announcementRef, replacementOf, ...) within a train, which should consequently also belong to the same timetablePeriod. So we could perhaps generalise that all operatingPeriods that are referenced by a train or its trainParts (directly or indirectly) must belong to the same timetablePeriod.
Best Regards
Christian
|
|
|
|