Home » railML newsgroups » railML.infrastructure » railML 3.2: Additional information for travel paths in a macroscopic netElement
Re: railML 3.2: Additional information for travel paths in a macroscopic netElement [message #2955 is a reply to message #2949] Mon, 14 March 2022 15:36 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Thomas,

thank you for your feedback. I understand your concerns and I agree with your conclusion to better leave the RTM foundation of topology unchanged. Consequently, only your proposal remains on the list of options.

If there are no objections until 16.03.2022, I am going to implement your solution as summarized in Git issue #452 [1] with one change proposal: rename <travelPathInformation> into <travelPath>. Any last comments from the community are highly appreciated...

[1] https://development.railml.org/railml/version3/-/issues/452

Best regards
Christian

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Single and double derailer
Next Topic: [railML 3.2] "isSpeedSignal": Suggestion to delete the value "midOfTrain" of element "trainRelation"
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun May 12 14:42:59 CEST 2024