-
Notifications
You must be signed in to change notification settings - Fork 41
OpenAPI entry page
Create and commit bookings, resulting in booked trip options, ready to go.
All kinds of operations to execute the legs of the booked trip. It allows you to operate assets.
When implemented, the travelers can rely on these functions to cope with unexpected events.
When implemented, the MP can find out what it has to pay to the TO.
Term | Description |
---|---|
TO | Transport Operator, delivers a Transport Service by providing assets |
MP | MaaS Service Provider, uses services from the TOs to get the end user(s) from A to B |
booking | a recording of an agreement between the end-user and TO, to execute a trip (=set of legs) according to a specification, including all conditions |
leg | part of a trip by person(s), executed using one asset (might be replaced only in exceptional cases) |
asset | tangible object that is used to execute the leg, like a car, plane, scooter, and so on. Can be privately held, owned by a private or public organisation |
traveler | someone who moves from A to B, could be the end-user |
end-user | the person who has an account and normally pays for the trip |
Introduction
- Roadmap
- Semantic versioning
- Use cases
- Changes per version
- Contribution
- Participants
Workflow
- Operator information
- Planning phase
- Booking phase
- Trip execution phase - start
- Trip execution phase - on route
- Trip execution phase - end
- Support
- Payment
Points of attention
- Modalities
- Specifying locations
- GDPR
Eco system
- Relations
Introduction
Scope of the TOMP-API
Versioning and releases
Process Flows
- Authentication
- Operator Information
- Privacy and Registration
- Planning Module
- Booking Module
- Trip Execution Module
- Payment Module
- Support Module
Meta-Information
Reference implementations
To-dos and risks
Technical Specifications
A1 List of terms and definitions
A2 Passenger characteristics dictionary
A3 APIs available on the transportation ecosystem
A4 Overview of the User stories
A5 Authors, Architects, collaborators and stakeholders involved
A6 Adoption and Implementation of the TOMP-API