| [railml3.1] Make @applicationDirection optional [message #2061] |
Sat, 29 December 2018 00:36  |
Thomas Nygreen JBD
Messages: 68
Registered: February 2017
|
Member |
|
|
Dear all,
In the 3.1-RC @applicationDirection is required for both <spotLocation>s and <linearLocation>s. Consequently it is not possible to position an infrastructure element without including @applicationDirection, even if most element types do not have any specific direction (see the discussion on @dir, including my review of elements in 2.3/2.4). I fear that this will lead to the same confusion that exists in 2.x.
The problem can be reduced by making the attribute optional, although this would still allow misuse (which is better than forcing it). I would prefer an alternate implementation that also separated elements that need a direction from the ones that do not, but I acknowledge that it would go against the general design. (After all, one is free to choose any location type for any element.)
As a side note: so far, the documentation of this attribute and its values is scarce. This increases my fear that this attribute will be misinterpreted and misused.
Best regards,
Thomas Nygreen
Railway capacity engineer
Jernbanedirektoratet
|
|
|
|
Members
Search
Help
Login
Home
