-
Notifications
You must be signed in to change notification settings - Fork 41
Use cases TE
home > Use cases > Use cases Technical
As a TO I want to describe my implementation of the TOMP-API, to facilitate external parties to discover the interface and have a clear overview of what I do have and how I want to be treated.
Implementation
| Type | object | remarks |
|---|---|---|
| Endpoint | POST /operator/meta |
Applies to
All modalities, and is especially applicable when acting in a data space or ecosystem.
As a routing structure, I request information where to deliver the messages. The ID of the TO must be in the header field 'addressed-to', so I can deliver it to the right address.
Implementation
| Type | object | remarks |
|---|---|---|
| Process identifier | TO_OPERATOR_REQUIRED | |
| Endpoint | ALL | all endpoint calls must be accomodated with the addressee |
Applies to
All modalities.
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