meeting minutes - UnionInternationalCheminsdeFer/OSDM GitHub Wiki

Link to Team Meeting

• Proposal to make only low-risk yet breaking changes with 4.0 to set a sound basis for future evolutions (benerail/sqills)
• Proposal to split the swagger in a few smaller blocks and separate non sales-process items from the core (masterdata, layouts, booking documents, complaint management...) (benerail/sqills)
• Continue work on ancillary harmoinzation

• Best practice / experience of multi-inventory transaction handling (SJ)
• Continue work on ancillary harmoinzation

• Starter: https://github.com/UnionInternationalCheminsdeFer/OSDM/pull/502

PR is accepted by group and merged. However we need to harmonize/clean up the accommodation sub type list.

• proposal on language handling (#401)=> please review (benerail)

PR is accepted by group and merged. Thanks Nicolas!

• Does it make sense to have the a list of refundOffers in the post response ? we would rather return only 1 refund offer, potentially referring multiple fulfillments (benerail)

a valid usecase would be to get multiple refundoffer, all covering all the fulfillments but f ex different fulfillment methods associated with different amounts (f ex vouchers => 100% and cash =>90%). so we keep the array but all offers have to cover the complete scope of fulfillments we still enforce the rule to have only one ongoing refundoffer at a time. one onging refund offer needs to be confirmed or deleted before another one can be added

• We are repeating complete fulfillments in refundoffers (also in get booking responses) which does not seem very efficient => should be changed like we did with products (benerail)

it is another breaking change=> a good change to propose for v.4 we could however alreayd return the fulfillmentRef so we can already prepare the change

• valid until in refund is mandatory but does not make sense on a confirmed refundOffer (benerail)

• can be filled with confirmed on value

• Should we still get something for get /booking where everything has been cancelled/refunded ? (benerail)

• Still get the booking
• We could introduce a flag indicating whether we only want to see active bookings or also cancelled ones

• What is now the ancillary offer/booking process ? (benerail)

• to be put on the agenda of a future meeting

• proposal on languages handling is ready for discussion (benerail) => https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/401 (to be discussed next week)
• Issue 488: clarification will be done by Andreas (done already)
• Issue 490: Josef to propse flow authentication (Backend-to-Frontend), will provide branch with documentation (proposal in 1-2 weeks)
• Issue 491: Ralf proposed flow for authentication (Machine-to-Machine), will provide branch with documentation (approved)
• #361: new meeting will be planned to complete the error handling proposal
• #402 check if documentation need an update on fulfillment process (see last comments)
• #437 needs PR
• #448 needs to find mime types for wallets, PR
• #449 needs PR
• #362 needs PR
• #494 Usual cases to be described to design more detailed webhook event. Odile will check how IATA NDC handles that.

• Issue 489: need to think about possible solutions
• Issue 488: clarification will be done by Andreas (done already)
• Issue 490: Josef to propse flow authentication (Backend-to-Frontend), will provide branch with documentation (proposal in 1-2 weeks)
• Issue 491: Ralf proposed flow for authentication (Machine-to-Machine), will provide branch with documentation (approved)

• RFC for Error detail -- Josef to review if RFC 9547 is backward compatible with RFC 7807. If so, make PR to update docs https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/486 -- https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/361 tracking changes on error handling once all recommendations are compiled by the group
• Initial results of discussion on bicycles as admissions vs ancillaries was presented. Participants willing to join contact Odile to get invite to the next session.
• Providers, distributors, IT vendors are again encouraged to fill in the https://github.com/UnionInternationalCheminsdeFer/OSDM/wiki/Implementation-Details and state their product support of OSDM

• Discussed changes in On-Hold Offer endpoints https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/469 Suggested to align release offers and fulfillment cancellation https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/485

• Proposed recommendation on having just a single refund offer in the booking in the same time. https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/437

• Proposed limitation on mime types used by different kinds of documents https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/448

• Continue work on ancillary modelling

• Quick update on demo

  • Partially successful, still doubts whether completely neutral to all parties
  • We will receive a list of technical question, which we will address

• Finalize work on language handling

  • Nicolas will provide a patch

• Address issues identified by DB

  • Ralf will provide patches

• OSDM 3.2 has been shipped

• up to 10:00: discussion on how to model ancillaries

  Grande plan to address the topic

  1. Structure the notion of ancillaries (--> Airline Taxonomy)

  2. How to request ancillaries?

  3. How to represent ancillaries in an offer?

• short update on preparation of demo

  Preparation with samtrafiken on February, 28th to GD Move

• open issues

• if time allows: introduce language handling (benerail) => https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/401

• Update of OSDM EC
  • Concerns of skeptics:
    1. Journey tied to railway so they favor their inventory
    2. Combination of offers only possible by railway only
    3. Booking can not be cancelled
    4. Lack of support for multi-modality
  • Need for a visual client by a distributor to convince skeptics:
    • Turnit is checking whether they can provide a client (3.0.3)
    • Sqills is checking whether they can provide a client (3.0.3)

    Patrick Heuget coordinates effort to provide a convincing demo on February, 28th

• Finalizing Version 3.2.
  • Andreas will provide PDF
  • Compile a release note passed on Items in GitHub
• Adding Bileto and Bene sandboxes to page.
• Scoping Version 3.3.
• Check on OSDM's implementation details

• Update of UIC Meeting in Rome.
• Life Cycle of Major Versions, including sun setting of versions < Version 3.*
  • As a group we decide to no longer work on specifications < Version 3.*, bug fixes only.
  • Legally we can not force parties to upgrade, that needs to be defined bi-lateral
• Address SBB issue (#465)

  Patch defined for v. 3.2

• Address Issues (#437) and (#446)
• Home Work: Please update supported/planned version of OSDM implementations Implementation Details

• Bundle 3.2 release

• (Tunit) ReductionCardType (appliedReductionCardTypes) doesn't hold information of cardNumber and cardType #420
• (Tunit) ReturnSearchParameters in tripSpecification is missing #434
• (Tunit) Possibility to display saving/reduction amounts for all types of reductions in an offer and booking #419

• State of Certification Process
• Experience feedback on average response time in non functional specifications (Benerail/Nicolas S) -- Outcome: rephrase the non functional documentation to clarify, that --- it is not mandatory, rather guidelines --- should be considered for specific condition: 1 passenger 1 segment, own inventory, neglecting network latency, ...
• Who should be in the purchaser entity (mentioned as mandatory) ? (Benerail/Nicolas S) -- expectation: would be the "most end-customer" actor of the story, not the distributor, not the agent, not the agent employee, rather the person sitting in front of him. -- it would be a company in case of a corporate booking for example (b2b booking site etc)
• partial offers & clustering logic => which are the parties intending to use it ? and how (making sure there is still alignment there) ? (Benerail/Nicolas S)

• ReductionCardType (appliedReductionCardTypes) doesn't hold information of cardNumber and cardType #420

• Questions by DB

  • Remove "houseNumber" from addresses

    Clarification needed that if street contains number, then the street number must not be set.

  • Third Party Accounting Reference

    Will be added to spec with minor changes

  • Booking provisionalPrice and confirmedPrice

    Improve description, @Rolan writes a patch

• Questions by DB
  • Mapping back from BookingParts to OfferParts (https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/412)

    Resolution found by adding an externalRef, @ralfbayer-db provides a patch.

  • Need single "soldProductId" on offer parts (https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/408)

    Discussion: Adding as "master product" has potential big impact on OSDM.

  • Questions and fixes on TripCoverage (https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/406)

    Clarification on documentation needed, @ralfbayer-db provides a patch.

  • Transfer Legs and local transport (https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/407)

    Clarification on documentation needed, @ralfbayer-db provides a patch.