-
Notifications
You must be signed in to change notification settings - Fork 41
Traveler
home > Planning phase > Traveler
A generic description of a traveler, not including any identifying information. It is anonymously.
field | required | description |
---|---|---|
isValidated | Whether this traveler's identity and properties have been verified by the MaaS provider | |
age | Age of the traveler, may be approximate. Mandatory in case of MANDATORY_TRAVELER_AGE (see processIdentifiers) | |
referenceNumber | reference number of the traveler. This number could be used to refer to in the planning result. (Planning Request.travelers.referenceNumber]) | |
cardTypes | array of cards the end user has, without any end user information (like card number). See Card types | |
licenseTypes | array of licenses the end user has, without any end user information (like license number). See License types | |
requirements | array of requirements the end user has, not formalized yet, but the Reizigerswoordenboek (CROW) can be used in here. Requirement |
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