-
Notifications
You must be signed in to change notification settings - Fork 41
Technical Specifications
The technical working group suggests to implement this interface using REST-APIs. Other quality specifications are:
Criteria | Value |
---|---|
Time To Live | Max. 30 seconds |
Reliability | 95% |
API-call max radius around asset | 500 meters |
API-call min radius around asset | 10 meters |
Pagination of API-responses | t.b.d. after testing of v. 1.1/1.2 |
Rate limiting | t.b.d. after testing of v. 1.1/1.2 |
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