-
Notifications
You must be signed in to change notification settings - Fork 41
Personal data store
The personal data store contains personal information about the end-user. The end-user should be in full control of his data. The MyData initiative guidelines should be applied.
The current status of this is, that most MPs register users and store their information. When a TO needs some of this information, it can be requested by the MP. We assume that this will be the same situation in the upcoming year, but to anticipate, the MPs could implement the PDS-M API. TOs still can request personal information, but now in a standardized way. Shifting to another location with the same personal information will be easier later on.
This opens also up the possibility to 'roam': hopping from one MaaS 'island' to another.
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