Home » railML newsgroups » railML.infrastructure » <track>@mainDir
Re: <track>@mainDir [message #2050 is a reply to message #1996] Wed, 19 December 2018 15:49 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Thomas, dear all,

Am 24.10.2018 um 15:35 schrieb Thomas Nygreen:
> [...]
> Quote:
>> However, it is suggested to adapt the list of possible
>> enumeration values. It makes sense to have a main driving direction
>> * up
>> * down
>> * both
>>
>> [...]
>
> The currently allowed values are only "up", "down",
> "unknown" and "none". In order not to break backwards
> compatibility, I suggest just removing "unknown", not
> replacing "none" with "both".

thank you for your feedback. I modified the Trac ticket #324 [1]
accordingly, so that we may implement this adaptation of @mainDir
enumeration value list with a future version of railML (railML 2.5 or
railML 3.x).

[1] https://trac.railml.org/ticket/324

Best regards
Christian

--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: infrastructure "state"
Next Topic: Published railML extension railML2.4nor (IS)
Goto Forum:
  


Current Time: Tue Apr 30 21:47:43 CEST 2024