-
Notifications
You must be signed in to change notification settings - Fork 41
Roadmap
The TOMP WG consists out of 4 sub-workgroups. Each workgroup has its own roadmap, but these consist mostly out of internal milestones. For the API itself these are the milestones we want to reach for:
2020 Q3: version 1.0 - released. Milestone 'Dragonfly'. First implementations have been done.
2020 Q4: version 1.1 - released. Containing changes with respect to GBFS 2.0
2021 Q2: version 1.2, containing the first changes to cope with a MaaS ecosystem - personal information.
- Operator module extension, possibly with 'terms and conditions' and 'known cards/memberships'
2021: version 1.3, changes to cope with MaaS ecosystem - discovery service, clearing house
somewhere in the future: version 2.0, milestone 'Elephant', MaaS ecosystem compliant.
Each API version can also contain extra functionality, but until the release of 'Elephant' we try to avoid breaking changes and they will be backward compatible with the initial release of 'Dragonfly' (1.0).
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