-
Notifications
You must be signed in to change notification settings - Fork 41
Damage
home > Trip execution phase > Damage
The damage object holds information regarding a damage of an asset, typically a vehicle.
When renting a shared car the user is responsible for any damages of the vehicle caused by carelessness. Such a damage might happen when the door is opened too wide so that it hits the wall next to the car and e.g. the paint chips of at some place.
In order to be not accountable for damages already existent the user needs to check the condition of the vehicle before starting his trip. This is done based on the list of already known damages. Therefore the TO has to expose the list of damages when the vehicle is SET_IN_USE.
"damages": [ {
"vehicleComponent": "FRONT",
"description": "front bumper lower grill loose",
"pictures": [ "https://car.sharing.com/files/X16072016Z.png", "https://car.sharing.com/files/X16072016Z.png" ]
} ]
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