MDS 2.0 - round-trip car sharing and reservation/reserved

Aperta
#867 8 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Ambito
documentation

Direzione di ricerca

Inizia con le sezioni della documentazione MDS 2.0 che definiscono reservation, reserved, reservation_start, reservation_stop, trip_type e reservation_id. Confronta queste definizioni con i casi d’uso del car sharing basato su stazioni descritti qui; il lavoro è completato quando la terminologia e l’interpretazione dei viaggi multipli sono chiarite in modo coerente, compreso se sia necessaria la modifica proposta del nome dell’evento.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Fleet State Machine

We experience confusion regarding how the terms "reservation" and "reserved" are being used in MDS 2.0 in relation to use cases of station-based car sharing (A to A), and would like to get some clarification on how to interpret and use the specification!

I've tried to sum up our confusion in the following list:

1. The MDS 2.0-documentation states at first that a reservation

… is the duration the customer has continuous exclusive access to the vehicle whether parked or in motion.

2 which again may be considered a journey_attribute:

reservation_id (UUID, optional): unique identifier for an entire car share reservation, tied across multiple journeys and therefore trips.

The definition of reservation given above is all in line with how we use the term reservation in car sharing operations.

3 But - when describing vehicle states, «reserved» points towards the state where a car is only reserved by the user (and not put to motion).

This differs from the definition of «reservation» as mentioned in point 1 above.

4. Then it follows up that the transition to/from "reserved" is triggered by the event_types:

reservation_start
reservation_stop

5 At the same time, the trip_type label «reservation» points towards a trip where the car is in motion and reserved by a customer (but not being driven by the customer):

en route to pickup a customer who has made a reservation, with no passengers in the vehicle

So - to sum up:

A) We need some clarification on the use of terms "reservation" and "reserved".

One suggestion that could help out, would be to rename event_types "Reservation_start/reservation_stop" to "reserved_start/reserved_stop" to hinder confusion.

B) We're struggling a bit to see the use case where a reservation consists of several journeys, especially when the documentation states that a reservation = continuous exclusive access. Right now, it seems like that a reservation is all equal to a journey, and may consist of no more information.

It would make sense if one opens up for concurring reservations (e.g. companies making a reservation for a car every monday (multiple journeys)), but then it still would be available for the other days - and hence not continuously exclusive for the entire duration of reservation.

Reservation

(We've put together a Slides-document to present several of our questions in relation to MDS 2.0 and car sharing, you can find this here: https://docs.google.com/presentation/d/1AbA-gnwvKwZ8BDz7Xp5DzFFRdVNyuiQUHkNIkVn75nY/edit?usp=sharing)

Lingua principale
Nessun dato sulla lingua
Stelle
753
Fork
255
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openmobilityfoundation/mobility-data-specification

Tutte le issue di openmobilityfoundation/mobility-data-specification

Issue simili

Altre issue su Documentation

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.