Re: <track>@mainDir [message #1996 is a reply to message #1983] |
Wed, 24 October 2018 15:35 |
Thomas Nygreen JBD
Messages: 68 Registered: February 2017
|
Member |
|
|
christian.rahmig wrote on Tue, 02 October 2018 14:33Dear Thomas, dear all,
Am 24.09.2018 um 14:40 schrieb Thomas Nygreen:
> I see that track@mainDir is still on its way to being
> deprecated. Just to make it abundantly clear: THIS ATTRIBUTE
> IS IN USE IN NORWAY. Most of our double track sections are
> normally operated as "drive on the right", while very few
> are operated with bidirectional traffic on both tracks. It
> is useful for us to be able to supply that information in
> the railML IS.
>
> Please do not deprecate this attribute.
>
> https://trac.railml.org/ticket/324
> https://wiki.railml.org/index.php?title=Dev:changes/2.4#.3Ct rack.3E.40mainDir_DEPRECATED
based on your feedback, the plan of marking the attribute
<track>@mainDir as being DEPRECATED has been revoked.
Thank you
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 values "none" (same meaning like "both") and "unknown" (not needed,
because you can leave the optional attribute out, which means
"information is unknown") shall be marked DEPRECATED.
What do you think about these adaptations?
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".
Best regards,
Thomas
Best regards,
Thomas Nygreen
Railway capacity engineer
Jernbanedirektoratet
|
|
|