| [railML2] New semantic constraint for //trainPartSequence/brakeUsage [message #3480] |
Mon, 24 February 2025 09:29  |
Milan Wölke
Messages: 178
Registered: April 2007
|
Senior Member |
|
|
Hi all,
when going through the railML 2.x timetable schema we came across the element <brakeUsage>, a child element of <trainPartSequence>. In particular we found that there is an attribute @airBrakeApplicationPosition that is dependent on another attribute @brakeType of that same element. We would propose to formalize this dependency with a new semantic constraint:
The attribute @airBrakeApplicationPosition if specified shall have the value "N/A" if the attribute @brakeType indicates a different type of brake than a pneumatic brake system (value "compressedAir").
What is your opinion. I dont think this will impact existing system, as it simply formalizes a rule that has been present less prominently for a long time already. Let me know what you think.
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
[Updated on: Mon, 24 February 2025 09:29] Report message to a moderator |
|
|
|
| Re: [railML2] New semantic constraint for //trainPartSequence/brakeUsage [message #3502 is a reply to message #3480] |
Mon, 10 March 2025 11:07  |
Christian Rößiger
Messages: 79
Registered: March 2015
|
Member |
|
|
Hello Milan,
my first suggestion would have been to define in the SemCon that the attribute 'airBrakePosition' is only to be used if 'brakeType=compressedAir', as this is the usual procedure when attributes do not apply in some cases.
However, I have now seen that your suggestion for the SemCon is already in the wiki, but directly in the 'Attributes' section. So we will probably have to continue to live with this deviating solution and I agree to move this text to a SemCon.
By the way, I'm not at all sure whether, in contrast to the wiki, 'airBrakePosition' can also occur in practice with vacuum brakes (brakeType=vacuum).
Best regards
Christian
[Updated on: Wed, 12 March 2025 08:50] Report message to a moderator |
|
|
|
|
|
| Re: [railML2] New semantic constraint for //trainPartSequence/brakeUsage [message #3520 is a reply to message #3507] |
Thu, 20 March 2025 16:17 |
Thomas Nygreen
Messages: 89
Registered: March 2008
|
Member |
|
|
Dear all,
Then we should probably also deprecate the "N/A" value of @airBrakeApplicationPosition? In general, I cannot see that such a value for any optional attribute makes sense, as the attribute should then not be used.
Best regards,
Thomas
Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
| Re: [railML2] New semantic constraint for //trainPartSequence/brakeUsage [message #3528 is a reply to message #3520] |
Thu, 27 March 2025 17:43 |
Milan Wölke
Messages: 178
Registered: April 2007
|
Senior Member |
|
|
Hi Thomas,
in principle I do agree with you, but unfortunately as this is railML 2.x we cannot deprecate it as long as we don't have the demand for development of a new version of railML 2. So for the time being, I suppose we will have to live with this.
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
| Re: [railML2] New semantic constraint for //trainPartSequence/brakeUsage [message #3529 is a reply to message #3528] |
Thu, 27 March 2025 17:53 |
Milan Wölke
Messages: 178
Registered: April 2007
|
Senior Member |
|
|
Hi all,
in our last timetable developer meeting we decided to implement the semantic constraint as follows:
The attribute @airBrakeApplicationPosition if specified shall have the value "N/A" if the attribute @brakeType indicates a different type of brake than a pneumatic brake system (value "compressedAir" or "vacuum").
We decided to add the value "vacuum" to the values allowing the @airBrakeApplicationPosition after discussing it in the group and deciding that vacuum was also a pneumatic brake system. We decided to go back to the initial wording, because the second approach would interfere with the possibility to express that the information is not known.
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
