Extension of Enum @trainUsage of <category> [message #2271] |
Mon, 11 November 2019 16:02 |
Milan Wölke
Messages: 146 Registered: April 2007
|
Senior Member |
|
|
Hi,
in unserer letzten TT-Developer Telco haben wir uns die Wiki Beschreibung zu <category> angeschaut. Also der Klassifikation von Zügen, etwa in Regio oder IC. Dabei ist uns aufgefallen, dass das verwendete Enum für @trainUsage auf die Werte "passenger", "goods" und "mixed" festgelegt ist. In der Diskussion stellte sich heraus, dass es durchaus Bedarf gäbe, mindestens den Wert "locomotive" hinzuzufügen, um etwa Loküberführungen besser beschreiben zu können. Ausserdem wurde angeregt, das Enum - wie viele andere auch - erweiterbar zu machen. Diese Änderungen könnten mit der Version 2.5 in den Standard aufgenommen werden.
Welche weiteren Werte sollte das Enum aufweisen? Gibt es Gründe von einer Erweiterbarkeit des Enums abzusehen?
----------------------------------------------
in our last TT-Developer Telco we looked at the Wiki page for <category>. In other words, the classification of trains, for example in commuter or express trains. We noticed that the used enum for @trainUsage is fixed to the values "passenger", "goods" and "mixed". In the discussion it turned out that there would be a need to add at least the value "locomotive" in order to describe locomotive transfers better. In addition, it was suggested that the enum - like many others - should be made extendable. These changes could be included in the standard with version 2.5.
What other values should the enum have? Are there any reasons not to extend the enum?
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|
Re: Extension of Enum @trainUsage of <category> [message #2300 is a reply to message #2285] |
Fri, 03 January 2020 15:09 |
Milan Wölke
Messages: 146 Registered: April 2007
|
Senior Member |
|
|
Hi Janne,
in order to better support your request here, could you please outline the semantics of the new enum value? This is important in order to understand if new semantic constraints need to be put in place.
Thanks in advance.
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Re: Extension of Enum @trainUsage of <category> [message #2379 is a reply to message #2343] |
Mon, 09 March 2020 14:49 |
Milan Wölke
Messages: 146 Registered: April 2007
|
Senior Member |
|
|
Hi all,
we discussed this topic in our last developer telephone conference. We decided that we will not extend the enum by any new values as part of the standard. Reason for this is that we found that it would be very hard to impossible to define a complete list of values once we started with this. Therefore we will stick with the existing values in the standard. However we also agreed, that other values may make sense in certain use cases. In consequence we will allow custom tags for the enum of @trainUsage so that these use cases can be handled, although some clarification between producer and consument will be necessary.
Ticket for the change: https://trac.railml.org/ticket/375
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|