Add new element Period in PassengerInformationActionStructure

[haeckerbaer]

Pain point to solve:
On PtSituationElement level one can define multiple ValidityPeriods (onbound). However, on Consequence or PassengerInformationAction level one cannot distinguish between these periods! On Consequence level this is solved by providing a corresponding element "Period" that overwrites the top level periods if one has to distinguish. However, on action level no such element exists.

• Alternatively, extend ValidityPeriod element on PtSituationElement level by an “id” so that each period may be referenced on action level.
• Multiple ValidityPeriods might for example be necessary in case of road works that only affects pt objects periodically during the night.
• Also, similar to how Interval on PushedActionStructure level supposedly works, a period (reference) on action level would enable a producer to publish some textual content via journey planner (Perspective ‘whilePlanningTrip’) before the situation actually affects the pt objects. This is not possible with PublicationWindow alone (which is independent from the ValidityPeriods). The only option here is to extend the ValidityPeriod which is certainly not desired for other Perspectives than 'whilePlanningTrip'.

A similar proposal was already discussed extensively within the SG7 group, but multiple counter proposals were suggested instead. These were all discussed within the UmS group (german speaking SX profile VDV736 that conceived the PassengerInformationActionStructure) but unfortunately were not able to solve the issues at hand.

[TuThoThai]

@haeckerbaer, I think it would be good to discuss this one further to reach a consensus. It would help for most of us to make a better use of SIRI-SX.

[SteffenSuhr]

Really necessary even for sending preliminary messages

[TuThoThai]

Since the consensus on this one only comes from stakeholders using the same implementation of SIRI SX, I would suggest to wait until consensus is found at the group level before merging.

[TuThoThai]

Requesting a meeting to address all changes needed for ActionData, Affects & Consequences in SIRI-SX

[TuThoThai]

As per the meeting of 19 December 2025: Agreement to have ActionPeriod as an optional field, but there is the need to:

• improve the description in the XSD to make it clearer when to use it
• provide a couple of XML examples of how the messages will look like with several temporal elements in Actions related to the same Situation / Consequence
• work on clean documentation with illustrations to be included in the next CEN documentation

[TuThoThai]

I spoted a couple of errors in the example file, I will let you check them @haeckerbaer unless you want me to edit the example directly

[haeckerbaer]

@TuThoThai fixed validation errors and also added second example

[SteffenSuhr]

This is urgently needed for the next version of VDV 736. In my opinion, the consultation process is complete.

[TuThoThai]

This is urgently needed for the next version of VDV 736. In my opinion, the consultation process is complete.

I understand the need but there was a long gap I could not control between my previous review and doing the change requested. 😄

[TuThoThai]

Thanks for editing the example and adding the difference with / without the Period

Not blocking for the merge: at a later stage, we should revisit all examplex with xml:lang to ensure the attribute is filled in lowercase as per @skinkie remark in PR #210