| [railML3] Extension of border type enum [message #3335] |
Fri, 11 October 2024 17:45 |
Vasco Paul Kolmorgen
Messages: 64
Registered: November 2004
|
Member |
|
|
Hi all,
in a recent certification we came across the problem that when exporting infrastructure describing your tracks correctly can sometimes become challenging. In particular the certification applicant had the need to define tracks that ended at signals.
Modelwise the railML track expects the two properties trackBegin and trackEnd to be a track node. A track node is defined to one of the following:- <switchIS>,
- <crossing>,
- <bufferStop> or
- <border>.
Unfortunately in railML 3.2 there was no type enumeration value of <border> to indicate that the track was ended at that place just because it was considered to be ending at a signal, which was placed there. In order to mitigate this we decided to add a new enumeration value for border in railML 3.3. The border type will then have the following options:- area
- country
- infrastructureManager
- state
- station
- tariff
- and the new value 'track'
Hopefully this will give exporting systems the freedom needed to encode their model while still being restrictive enough to minimize the implementation effort for importer.
We will publish this for review with the upcoming beta2 of railML 3.3 next week. All the railML v3.3 betas can be downloaded free of charge from our website after login: https://www.railml.org/en/download/schemas.html
We invite you to download the beta version and give us your feedback until October 23rd via the railML forum, by e-mail or in the working group meetings.
A ticket for this has been created under: https://development.railml.org/railml/version3/-/issues/579
Best regards,
--
Vasco Paul Kolmorgen - Governance Coordinator
railML.org (Registry of Associations: VR 5750)
Phone railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany
[Updated on: Fri, 11 October 2024 17:55] by Moderator Report message to a moderator |
|
|
|
Members
Search
Help
Login
Home
