-
Notifications
You must be signed in to change notification settings - Fork 41
Scan for bluetooth devices nearby and book one of them
DRAFT
This scenario is not yet completely in the API, but for now we can do it like this:
- Do a bluetooth scan to find nearby assets.
- call /planning/ with booking-intent=true and fill the field 'assetIds'. It should contain an array of scanned bluetooth (or other technique) devices.
- let the user decide which asset to use (or select on yourself, based on their profile)
- book it using /bookings/. It should result in a PENDING booking.
- whenever the call is successful, call the /bookings/{provided id}/events { "operation": "COMMIT" } This way you have 2 points in time to verify that the asset is still available.
- Now it's time to unlock the asset. Request information to open the lock ( using /executions/{id}/events { "operation": "PREPARE" } ). The result contains a field 'assetAccessData'. As far we know now, every (bike) operator has his own way of unlocking. This is unfortunally not yet standardised. The MP should only show assets in their app they know how to open these!
- After a successful unlock, the start of the trip should be registered: using /executions/{id}/events { "operation": "SET_IN_USE" }.
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