-
Notifications
You must be signed in to change notification settings - Fork 41
Discovery service
home > Ecosystem > Discovery service
The discovery service is a role in a MaaS ecosystem, telling at least where everyone operates ('yellow pages'). This role can be fulfilled by a National Access Point (in Europe).
More advanced versions of a discovery service also provide functionality (roles) about:
- governance (are participants (MPs/TOs) allowed to operate in their claimed area)
- authentication (validate a requesting party; is it really who it is claiming to be)
- authorization ("how owns the data and who is allowed to use it")
- registration of other MaaS ecosystem roles (Clearing houses, Personal Data Stores, other discovery services, etc.)
These functions can be added, since they are closely intertwined with the registration of MaaS participants.
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