CR090a: Harmonization of ActionStatus and Progress in SX

[haeckerbaer]

See https://3.basecamp.com/3256016/buckets/9672657/vaults/5470139022

[prirey]

Thanks!

[gthiesing]

It seems to me there is a misunderstanding of SIRI processes underliying.
In SIRI there is a Situation Progress State (refer to 5.3.6.3) which refers to the status of the situation itself and this status comprises the status 'closing' already descibing that the situation itself is in process of getting regular (refer to annex E.3.2). If as the example shows it getting only partly to regular operation SIRI requests an update of the situation with exactly this information.
The status element of the publishing action reports the status of publishing not of the situation itself therefore 'closing' is meaningless since the information about a situation can only be prepared (open), can be published (published) or can be deleted (closed)

[Aurige]

You are right @gthiesing , we shall not mix Situation Progress State and Publishing Action Status. However, my understanding from @haeckerbaer proposal is to add a real Publishing Action Status, dedicated to the communication to passenger (see https://3.basecamp.com/3256016/buckets/9672657/messages/5836829085 - Public is informed about ongoing normalisation) and related to the specific Publishing Action (not to all consequences of the Situation).
So the documentation and XSD comment must state this very clearly.
I still agree with the proposal on my side (in fact I found the same use case in France ...)

[haeckerbaer]

update incoming as discussed in the basecamp: A boolean SituationIsClosing is introduced on PtSituationElement level that corresponds to ActionIsClosing. We should not correlate the closing value of ProgressEnum with a boolean.

[prirey]

pls separate the interpretation of Progress and ActionIsClosing.
Progress is not required for showing the "Closing icon"