| [railML 3] Custom Stop Activities [message #3445] |
Tue, 21 January 2025 11:39  |
David Lichti
Messages: 54
Registered: December 2020
|
Member |
|
|
Dear Community,
In the context of our railML timetable export, we need to include generic stop activities.
The railML 3 standard has the other activity element. The @trainActivityClassification attribute enumeration has suitable values for some, but not all of them. In some cases, a standard classification value may technically apply, without being detailed enough to reliably distinguish all necessary, customer specific variants of an activity.
We could use the other:\w{2,} extension pattern of the @trainActivityClassification enumeration, f.ex. other:crewChangeConductor and other:crewChangeEngineer. But this would conceal the fact that these are just two variants of the commonly understood standard enumeration value crewChange.
We propose to add an optional <name> element to the other activity element type, or possibly to all activity element types. This <name> element could be used to convey the precise, context/region/company specific type of the activity. Meanwhile, the @trainActivityClassification attribute with its pre-defined enumeration could still be used to ensure a rough understandability for all tools that do not know the precise meaning of that name.
What are your thoughts? This may also be relevant for other places that use attribute value enumerations.
Best regards
David
|
|
|
|
| Re: [railML 3] Custom Stop Activities [message #3456 is a reply to message #3445] |
Thu, 06 February 2025 17:18  |
Milan Wölke
Messages: 213
Registered: April 2007
|
Senior Member |
|
|
Hi David,
thanks for the suggestion. I would assume this change would then be aimed for railML 3.4?
In general I think this is a good idea, but I am not sure if a simple name is really what would be useful here. Name implies for me that it is purely descriptive and is not interpreted by reading systems. From your description I understand, however, that this exactly the purpose of this attribute. From what you wrote I was thinking more along the lines of some kind of designator. This would also provide you with a string, some description of context and is intended to be interpreted.
Would that work for you or do you see problems with this?
Best regards, Milan
Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|
|
| Re: [railML 3] Custom Stop Activities [message #3535 is a reply to message #3462] |
Fri, 28 March 2025 15:19 |
Milan Wölke
Messages: 213
Registered: April 2007
|
Senior Member |
|
|
We discussed this issue in the last timetable developer group meeting and decided to add this to railML 3.4. We also discussed how to model this small extension and decided on simply adding a name to all activity elements. This was achieved by changing the base class of the abstract base class of all activities BaseActivity from tElementWithID to tElementWithIDandName. This will allow users to specify a name and a description along with the language in which the name and description are held to any activity. It allows providing 0..* such name elements.
This ticket for this change can be found here: https://development.railml.org/railml/version3/-/issues/644
Best regards, Milan
Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
