| [railML 2] <speedChange> semantic constraints revision [message #3078] |
Fri, 28 April 2023 13:16  |
Larissa Zhuchyi
Messages: 33
Registered: November 2022
|
Member |
|
|
Dear all,
railML 2 <speedChange> wiki page [1] includes semantic constraints that are quite ambiguous:
- Every <track> has to have at least one <speedChange> at the track begin with parameters @pos="0" and @dir="up".
- Every <track> has to have at least one <speedChange> at the track end with parameters @pos="{value equal to trackEnd@pos}" and @dir="down".
It would be good to extend them with the following points (based on the TT working group's view). Please communicate your thoughts in this regard:
(1) Only applies if speedChanges are exported at all [as they are not required by XSD (editor's comment)].
(2) It also only applies if both directions can be accessed, otherwise corresponding exceptions would have to apply.
(3) There is also the question of whether the SemCon is meant to apply to the entire file or only per <track>. So if speedChanges are issued in the file for one track, must the SemCon also be applied to all other <tracks>?
[1] https://wiki2.railml.org/wiki/IS:speedChange
Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
