-
Notifications
You must be signed in to change notification settings - Fork 42
TOMP‐API v2.0 Functionalities
- serves both station-based and free-floating setups. Even dynamic setups.
- direct booking of assets on the street AND search for assets
- use GBFS's published vehicles
- book assets in the (near) future
- use deposits
- can be used to open locks of any kind.
- can be used to open lockers
- and chargers
- copes with helmets and helmet boxes
- start, stop, pause and resume trips.
- deliver proof (photos) of correct parking
- facilitates any support scenario, even the replacement of the asset
- allows for adjusting the rental until the start of the trip
- reuse existing published data, like MDS policies: (no-)parking zones, speed limits, etc.
- offers functionalities for different payment methods
- charge different prices based on pause status
- request payment directly after the trip has finished
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