-
Notifications
You must be signed in to change notification settings - Fork 41
Start up guide
A TO can complete this list of bullets to facilitate setting up a connection with a MP.
- Do you have a standard contract (OpenBikeII, OpenWheels)?
- What is the agreed pricing model?
- How the clearance should be handled?
- Please supply brand logo, URLs, images, asset images
- What personal information should be exchanged?
- Do you need end-user documents (passport, driver license), the validation policy
- What other information should be exchanged (= requested from the MP)
- What certificates do you have / other compliance aspects (GDPR)?
- What type of authentication do you have?
- How is your end-user support implemented?
- Are there any conditions around cancelling a leg?
- Do you have a development environment (or test)?
- Do you require a deposit?
- What are the SLA agreements (response times, error return, webhook policies, etc)?
- Timing sequences (times between booking and pickup, too early, too late, expiry times)
- max/min usages (f.x. at least 10 min, max 1 day, max 100km, travelers per asset)
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