Adding PublicationRef and ConsequenceCode

[TuThoThai]

Request primarily made by the French mirror group.

Context

What is happening in real life:

• Situation A occurs: there is a satefy threat due to unattended luggage at station S affecting the entire service on Line L1 but partially impacting the service L2
• Consequence A.1: the service is suspended without resuming time yet
• Consequence A.2: the service will resume in 30 minutes
• Consequence A.3: the service is back to normal (i.e., situation is closed)
• Consequence B.1: no aligthing at station S until the situation is solved
• Consequence B.2: passengers can alight at station S (i.e., situation is closed)
• For Consequence A.1 and A.2, there is a ParametrisedAction (PublishToWeb) PA.A with a specific message for travellers on affected Line L1
• For Consequence B.1. and B.2., there is another ParametrisedAction (PublishToWeb) PA.A with a specific message for travellers on partially affected Line L2

On the data consumers' side:

• No possibility to track which ParametrisedAction relates to which Consequence
• Whenever the Consequence evolve, they have to reprocess the entire payload to publish the right information

Hence, the double need:

• Possibility to track a ParametrisedAction via an unique identifier
• Possibility to add a link between a ParametrisedAction and a Consequence of a situation

Change request

• Adding PublicationRef to identify a ParametrisedAction for easier updates on data consumers side
• Adding ConsequenceRef in ParametrisedAction to strenghten the link between the Consequence of a Situation and its publication
• Adding ConsequenceCode in PtConsequence as a unique identifier of the Consequence that can be referrenced elsewhere

This request for change was discussed on 7 Apil 2026 in the SIRI-SX task force with positive outcome.

[skinkie]

I don't understand the need. For now -1.

[TuThoThai]

I don't understand the need. For now -1.

We discussed it at the previous SIRI-SX task force meeting. Let me detail the context to better reflect what was presented. 😊

==> Change done at the beginning of the PR

[TuThoThai]

On 22 April, discussions

• add more details on the PR description with actual messages
• suggested changed PublicationRef to PublishedRef

[haeckerbaer]

Please add an example that details in what scenarios these new references can/should be used (as already discussed in the SX task force). Otherwise approved