| Re: Attribute processStatus to be declared deprecated for <train>, <trainPart> and <trainGroup> [message #2333 is a reply to message #2331] |
Wed, 19 February 2020 12:23   |
Milan Wölke
Messages: 139
Registered: April 2007
|
Senior Member |
|
|
Hi,
i think this issue can be linked with the topic discussed here. A discussion in the timetable developer group showed that in order to communicate a track change the use of a status like element is to be preferred over some individual modelling for the use case of a track change. This would have the benefit to be able to communicate all kind of changes to trains (track change, formation change, etc).
Looking at the requirements mentioned in the other thread, it should be possible to express the originator of the change (or reason for the new version) as well as the time when this change occured. Furthermore the timetable developer group discussion considered introducing some kind of version counter which would allow to describe different version within the same planning state.
In general I still think that processStatus needs to be replaced with some new well defined element to express state information, since as Christian pointed out data exchange regarding the state seems highly unlikely given the different semantics currently in use by implementing systems.
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
[Updated on: Wed, 19 February 2020 12:24] Report message to a moderator |
|
|
|
Members
Search
Help
Login
Home
