Meeting Minutes 2025 - UnionInternationalCheminsdeFer/OSDM GitHub Wiki

Link to Team Meeting

2025-09-12

Discussion on how to bundle fares and offerpart, results will be added to the OSDM specification.

2025-09-05

Issues discussed:

2025-08-29

  • Allow bulk operations on passengers (see: #1142)
  • Discussion on how to activate passes (see: #1143)
  • #1139
  • question OBB: what is in VAT.percentage when VAT.amount is the calculated tax amount #1144

2025-08-22

  • approving the prepare endpoint

  • clarify relations and constrictions between tripCoverage on offer level and on offerPartLevel

    • is it allowed to provide it on part level only?
    • must the coverage on part level be a subset of the coverage on offer level?

  • preparation for OSDM EC meeting 9.9.

    • what should be announced to the EC?

  • Aligning enum with code list for PRM v3.4 and 3.5: #1135

Issues discussed:

2025-08-15

  • booking of return trips
  • finalizing booking preparation step

Issues discussed:

The finalisation meeting for version 3.7 will be held in London on the October 16th. If you want an invitation to the meeting (either virtual or in person), please contact Clemens Gantert.

2025-08-08

Issues discussed:

2025-08-01

Issues discussed (mostly housekeeping, some PRs merged):

More detailed discussion on these:

2025-07-25

  • Discussion on the semantics of Leg in OSDM and OJP 2.0 and how to align them.

Decision: Leg in OSDM will stay to be the entire section where the passenger stays in one service on his seat.

Other issues discussed:

2025-07-18

Issues discussed:

Pull Requests discussed:

2025-07-11

Issues discusssed:

2025-07-04

  • #902

  • Is it possible to understand the reasons for the absence of available offers in the offer search (POST offers response)?

    TODO: extend the code list - fully booked - booking not yet open - booking already closed - booking temporarily closed - ....

  • List of Implementations:

    • remove versions and state
    • add logos (also on first OSDM page)

2025-06-27

Changelog provided by Velvette, see here: tbd

Issues discussed:

2025-06-20 - No meeting

2025-06-13

2025-06-12 - Finalization Meeting (Paris, at UIC premises)

2025-06-06

  • requiredCards in Fares (#1025, Patrick)
  • requestedInformation grammar (#1024, Klaus)
  • Exchange/Refund price places (#772, Ralf)
  • Offer Overview endpoint proposal (#599, Josef)
  • TransportableType (#1017, Velvette)
  • Code list suggestions (#1018, Velvette)
  • Aligning Code lists and API (#1016, Velvette)
  • Errors and problems page (#1010, Velvette and Ralf)
  • Seating preferences for Ancillaries (#1013, Velvette)
  • Headers (#921, Ralf)
  • Aligning PassengerTypes (#962, Velvette)
  • Medium/Media (#1020, Kevin)
  • Attributes without URN (#1009, Ralf)

2025-05-30 - No Meeting

2025-05-23

  • Discussion on error endpoint (#997)
  • Questionss on Errors/Warnings/Problems (#1010)
  • Issues and PRs

2025-05-16

  • Document Accessability #944 --> Ralf showed document, will create PR
  • Currency conversion --> already resolved, see Price.appliedCurrencyConversion from 3.5 onwards
  • looked at other issues and merge requests
    • PlaceProperty codelist related field usage and description inconsistency #996 the changes would be breaking, so moved the issue to 4.0.0.
  • looked at other issues and pull requests

2025-05-09

  • Discussion on #967 / #772 refund amounts in RefundOffer, BookingPart, Booking (version 4) - see comment.
  • https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/993 (ÖBB/DB) -> resolved, Ralf to create PR.
  • Discussion on Applied Reductions (#991/#992) -> see comments
  • Discussion on Change Log / Release Notes (#990) - thank you for the offer, and we will revisit this with Clemens and/or Andreas when they are back
  • Improvements #987 / #988 on patch behaviour / nullables
  • looked at other issues and merge requests

2025-05-02 - No Meeting

2025-04-25

  • Organisation of next meetings, planning the release of 3.6 (12.6.2025)
  • discussion on Default direction on internals #977
  • discussion on ancillaries
  • Should the summary oof Flexibility be mandatory (Question from OTST)

2025-04-18 - no meeting

2025-04-11

  • #790 fees and fares as booking parts - initial draft

2025-04-04

  • Incomplete list of Booking Part states (#959)
  • Missing stopBehavior in POST trips collection/POST offers (#956)
  • TI Question on AnonymousPassengerSpecification (#927)
  • Exchange state model inconsistency (#939). Align with current implementations

2025-03-28

  • TI request on transient refund offer (#916)
  • TI questions (#928, #929)
  • Use of accounting Reference (#929)
  • improve handling of trip replacements on provider side (#902)

2025-03-21 - Focus on PRMs and Ancillaries

  • DB presentation on PRMs

    • Slides can be found here: PRM in OSDM.pdf
    • Documentation page "Accessibility & PRMs" needed
      • Clarify PRM needs
      • Point to relevant part in specification:
        • in trip planning (see BaseTripPolicyFilter and TripMobilityFilter in TripSearchCriteria)
        • in offer request (see PRMNeedType and modelling of disability documents as reduction cards)

  • Presentation by Amadeus (Odile & Gurpreet)

    • Slides can be found here:
    • Next steps:
      • revise type and sub type code list for ancillaries --> consult members which type and sub type are actual being used
      • use product search to get ancillary --> adding types and sub types to products

2025-03-15 - Scoping Next Version

2025-03-07 - Finally finalizing Version 3.

2025-02-28 - Finalizing Version 3.5

2025-02-14 - Focus on Coach Layouts & Publication of 3.5

  • Improved version of coach layouts - proposal by SBB
  • Graphical seat map and layoutIds - discussion 817
  • Set rules about graphical seat map definition 866

2025-02-13 Finalisation of OSDM 3.5.0

  • #850 Josef PR with new field amountToBePaid
  • #856 Andreas/Clemens PR with missing operationId for on-demand services API while working on it on 2025-02-14
  • #766 Josef PR documentation
  • #816 Ralf PR on reservation code lists
  • #788 find the original issue and create PR, or move to 3.6.0/delete
  • #820 has PR, review on 2025-02-14 and approve, or complete
  • #773 Josef PR documentation
  • #860 Clemens to answer followup question on OSDM Offline

2025-02-07 - Focus on Open Issues

  • What documentation is needed for a patch/features:

    • Update Requirements
    • Update Business Processes
    • Update Processes (*most important for other to understand how the flow)
    • Update Model (coarse granularly)
      • First update Plantuml/SVG and then generate a PNG
    • Update State Model
      • First update Plantuml/SVG and then generate a PNG
    • Update Code List
    • Update Compliance (assuming optionality)

  • #820

  • #850

2025-01-31

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

  • #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)

    • @pjosef 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.

    • Decision: Validate with management and provide sufficient privacy.

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 master data (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...