The Forge

[TuThoThai]

Overview

This discussion is the "live" documentation of the Forge. It is primarily maintained by the Editor, @TuThoThai, during the Forge time. It is not to be considered as a stable draft of OTI v0 which will be made in a separate addition to this repository.

Template for this thread

To be used for the documentation, either per day or sub-topic.

Context

• Date:
• Main topic:
• Related business use-case, if relevant:

Discussion

Consensus

[TuThoThai]

Context

• Date: 1 June 2026
• Main topics: Basic principles & Search offers (request)
• Related business use-case, if relevant: Business Use Case A (Search offers - request)

Discussion

Proposed agenda & Organisation

• Approved agenda: Welcome, Work on BUC A
• All were given 5-7 minutes to write down their expectations for the Forge and the 'must-haves' from the standards they are reprensenting

Basic principles

• Review of the basic principles agreed on at the start of the project
• Only some of them were clarified to ensure alignment (please refer below)

Scope for the Forge

To be added: link to the slide
Clarification:

• In orange, priorities for the Forge
• In green, out of the scope of EUDIT

Work on the BUC A

• The work was done with in 2 parts for the part "Search offers - requests": who, what
• For results of the discussions, please refer below

Follow-up of the work

• Needs to clean up the Enterprise Architect modelling (attributes, collections, etc.)
• Needs to move to OpenAPI specification
• All to map what has been drafted to their standard

Consensus

Basic principles - clarification

• End-customer / traveller is primary though whenever possible the team should make the API Specificaiton as readable and easy to understand as possible to prevent from misunderstanding when implementing
• Use Transmodel as the basis for our work but are open to select the concepts we need, request for changes (adding concepts) or fine-tuning the definitions
• Clarification of the link with OJP (refer to the Team 1 input)
• Ensure we have the process to include the guarantees / redresses

General agreement

• Language is in the header of each exchanged messages and/or in the meta data. It does not belong to each request / response payload as an attribute
• Methodology: stick with Transmodel as much as possible, go through what information are needed, check that all from pre-existing API specifications are covered, note questions for later

BUC A - General agreement

Elements to add later to "Search offers - Request":

• corporate participation
• account details
• fare media
• fare class (to check if it has been reported back in the 'filter'
• type of travel document

Filters for the offers are optional

To discuss in next phase:

• Direct purchase of a product later
• Enumeration of offer parts
• business rules on refund / exchangeable
• inbound dates
• addition of product for unlimited urban products