Meeting Minutes 2025

Link to Team Meeting

2025-03...:

• DB presentation on PRMs

2025-02-21 - Focus on Ancillary

• Presentation by Odile & Gurpreet.

2025-02-14 - Publication of 3.5

2025-02-07 - Focus on Coach Layouts

• Improved version of coach layouts - proposal by SBB
• Graphical seat map and layoutIds - discussion 817

2025-01-31

• Publication of 3.5 - Final Meeting would be on 13.2.

• https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/773

  • We have three scenarios, where we need to define the semantics:

    1. Overrule Code Unsupported (cancellation)
    2. Overrule Code Not Applicable (cancellation)
    3. No Overrule Code Given & no offers are available for that product:

    All scenarios are replied via sending a HTTP 200 OK with an empty offer list and a Problem describing the reason why the list of offers is empty.

    If the receiver changes the overrule code it should returned the appliedOverruleCode in the response.

  • This semantics applies to the following

    • /refund-offers
    • /exchange-offers
    • /release-offers
    • /bookings/{bookingId}/cleanup (No offer list is returned)

  • @josef improves the documentation.

• How to react if no offers are available?

  • Two Options

    1. 200 with empty offer list and problem details
    2. 400 indicating no offers are available

  • Decision: Option 1

• Discussion on an extension of the current online Implementation Guide (https://github.com/UnionInternationalCheminsdeFer/OSDM/wiki/Implementation-Details) (like: which roles are with which version implemented, supported endpoints, contact persons, supported authentication, implementation details like supported overrule codes, ... (ÖBB)

  • Reasons to have such a list:
    1. Tailoring of use cases to a given implementation
    2. Official point of contact
    3. Reporting towards management or regulators, especially the ticketing roadmap.

2025-01-24

Note: PR on On Demand Services have been merged.

• Decision on #804 --> Decision taken and documented in the issue. JP will create a pull request.
• PR for #775 --> PR already merged, issue is closed.
• Decision on #849 --> Decision taken and flag to be removed. JP will create a pull request.
• Decision on #827 --> Decision taken, JP will create a pull request
• Discussion on ReservationGroup / AncillaryGroup: ID and Name are superfluous and should be removed. Klaus to open an issue.
• Discussion on OfferPartReference / BookingPartReference: summary and _links attributes are superfluous and should be removed. Klaus to open an issue.
• Question on "Reservation only requests" - what should be returned in different cases on such requests? Suggestion to be given by ÖBB.
  • Additional question: how to express that reservations are mandatory in such a request?
• Merged 3 outstanding PRs.
• Please have a look at PR regarding #816 and comment, please. Need to discuss this on 31.01.2025 and agree on it.
• Discussion on #850. Tim and Linus will check how it has been implemented in TurnitRide. Discuss further on 31.01.2025.
• Discussion on #848 --> provided some answers.
• Teaser on #838 --> discuss next week.
• Discussion on #820 --> agreed on new endpoint, need for another issue regarding a product tag masterdata endpoint (Martin@eurail).

2025-01-17 - Focus: Fulfillments of Fares

Fulfillment of fares

• leads to an empty fulfillment
• granularity: 1 fulfillment per section per passenger except you are doing collective pricing (analogously to the offer flow).

Other topics:

• language in Masterdata (version 4.0)

other topics:

• Iteration of "transportable proposal" -- request parameter
• Pass Products
• Graphical seat map and layoutIds question (discussion 817)

2025-01-10 - Focus: On Demand

• Experts:

  • Clemens
  • Ralf
  • trenitalia (tbd)
  • Andreas

• Aims:

  • Make On-Demand Content (Bikes, Scooters,...) bookable via OSDM
  • Price indication, needs tracking (time, route)
  • Vehicle activation/deactivation flow
  • First consumption, settlement after
    • Delcredere risk - how to manage?
  • Billing (?)
    • Who is sending the bill
  • New after sales process
    • Incorrect tracking leads to incorrect bills leads to customer complaints...