| [railML2] Re: Documentation of attribute "pathStatus" and proposal for new value "offered" [message #2416 is a reply to message #2349] |
Tue, 07 April 2020 15:36   |
Milan Wölke
Messages: 139
Registered: April 2007
|
Senior Member |
|
|
Hi all,
in the last timetable developer phone conferences we discussed about the different enum values of @pathStatus. We came to the conclusion that the current states of @pathStatus are not enough for modelling of a basic slot ordering process. Therefore we decided to extend the enum with two new values: offered and conceptual. The general idea of the statemachine behind that is the following:
A train starts out as "conceptual", which means that a slot for that train is not to be ordered (yet).
If a slot for a train is to be ordered but no order has been issued yet, the train is annotated with the state "planned".
Once a slot for a train has been ordered the state "ordered" is used. Now the IM will have to respond to the order. The possible results of that could be: "notAvailable", if the IM cannot fulfill the request; "offered", if the IM can provide the requested slot or "detailedRefused" if the IM cannot fulfill the request but offers a slot that is similair to the requested one.
If the IM is chooses "detailsRefused" or "offered" in the response to the request is up to the IM. Very often an offered slot of the IM will not be exactly fitting the requested one. By choosing "offered" or "detailedRefused" the IM can decide if from his point of view the request is fully complied with or not and inform the RU accordingly.
If the slot offered by the IM suits the RU the state "confirmed" is used. If it is not, the state "cancelled" is used to cancel the ordering process.
As I said initially this means introducing two new states: conceptual as a new starting point and allowing to include trains in railML that are not (yet) ready for the ordering process; and offered for the IM to indicate that a request has been fully complied with.
If it is necessary to encode further states for modelling slot ordering those states should be defined using other:anything.
@Torben: Would you agree with the meaning and usage of the existing and new enum values of @pathStatus.
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
