Re: [railML2] extension suggestion for the element <state> for working zones [message #2724 is a reply to message #2722] |
Fri, 21 May 2021 14:05 |
christian.rahmig
Messages: 465 Registered: January 2016
|
Senior Member |
|
|
Dear Thomas, dear Torben,
following your remarks I come to the following conclusions:
1) A <state> should have an identifier or designator to make it adressable and usable e.g. within graphical representations. Currently, a <state> has no ID and no designator.
2) Connecting an "additional running time" with a state of an infrastructure element (e.g. a track) seems to be more some kind of a workaround instead of a proper solution. Why not using an <area> element to explicitly define a construction area, that causes additional running times?
What does the rest of the community think about it?
Best regards
Christian
PS: The whole issue is filed in Trac ticket #395 (https://trac.railml.org/ticket/395)
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|