This repository contains the documentation and work products for harmonizing various transportation and mobility standards with Transmodel. The project follows a structured approach through multiple phases, with a central wiki serving as the single source of truth.

This is the main page for functional discussions. We will prepare discussion items per meeting. They will be placed in this page, and you can already react on the discussions in the weeks before the next meeting. So, if even when you're not in the meeting, your opinion can be taken into account. The discussions will be prefixed with the date of the meeting when they will be addressed.

Don't create discussions on your own, please request them in our biweekly meetings.

Contains most work-in-progress documentation, including documents we can use or have to build on. PLEASE DON'T MODIFY!!! Use the discussions, so we can analyse the requested changes before they're applied to this part!

The Wiki serves as the authoritative source for all foundational concepts, principles, and mappings. It contains:

• Scope Project scope definition and boundary conditions. This also contains the CoRoM deliverables!

• Basic Principles Fundamental principles that underpin the entire project.

• Roles Definition and description of stakeholder roles within the project.

• Interoperability & Governance Where can we expect problems when merging? What are the 'soft' aspects around the standard and what are the options for these, to mitigate risks?

• Concepts & Definitions Structured list of concepts and their definitions, based on Transmodel terminology.

• Architecture Project scope definition and boundary conditions.

• Use Cases Collection of use cases, CoRoM input.

• User Actions Detailed descriptions of user interactions and workflows.

• External documentation External resources we can use to deliver. This also contains the CoRoM deliverables!

• Specifications The technical specifications of the standards (fixate the version?)

Technical specification The draft specification(s), after each meeting, a copy will be made and the agreed changes will be applied.

Each supported standard has its own directory containing mapping documentation to Transmodel:

• OSDM
• TOMP-API
• BoB
• FerryGateway
• OMSA
• InterMOD

Each standard mapping follows this structure:

The project follows a five-phase approach, metaphorically inspired by the blacksmithing process:

Initiation and Foundation

• Purpose: Project setup, team formation, and initial exploration
• Deliverables:
  • Scope definition
  • Basic principles
  • Role description
  • Interoperability issues & governance options
  • Concept / definitions
  • Use cases / user actions
  • Architecture/structure options
  • Plan for the forge

→ Read phase README

Make the first proposal

• Purpose: Deliver the first technical documents, based on what we already have
• Deliverables:
  • Conceptual mappings
  • First draft (or options), based on the use cases and existing standards
• Activities:
  • design session

→ Read phase README

Hammering the drafts

• Purpose: Complete, extend and finetune the drafts
• Deliverables:
  • Implementation specification
  • Prototypes and demos (?)
• Activities:
  • Biweekly meetings, with a fixed agenda for each meeting (* based on the drafts *)
  • Once in the 5 meetings, a retro session, where we'll look back, and finalize the functionality we've addressed in the past months.

→ Read phase README

Validation and Stakeholder Review

• Purpose: Results to CEN, ballotting
• Deliverables:
  • Presentation of the TS and the required document
• Activities:
  • consistency check of the TS (OpenAPI)
  • finalize the documentation

→ Read phase README

Refinement and Finalization

• Purpose: Incorporate feedback and finalize deliverables
• Deliverables:
  • Final specifications
  • Implementation guidelines
• Activities:
  • Refinement,
  • documentation,
  • knowledge transfer

→ Read phase README