Meeting Minutes - UnionInternationalCheminsdeFer/OSDM GitHub Wiki

Upcoming

Link to Team Meeting

2024-03-22

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

2024-03-15

2024-03-08

2024-03-01

  • 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

2024-02-23

  • 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

2024-02-16

  • 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

2024-02-09

  • 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

2024-02-02

  • Bundle 3.2 release

2024-01-26

  • (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

2024-01-19

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

2024-01-12

2024-01-05