PS - updates based on feedback

Author: schnuerle

modes/passenger-services.md

@@ -8,7 +8,7 @@ See the [modes overview](/modes) for how the mode specific information below app
 
 ## Taxi vs. TNC implementation differences
 
-Taxis typically require explicit tracking of maintenance while TNCs typically do not.
+Taxis typically require explicit tracking of maintenance while TNCs typically do not. Public agency regulations, legal authority, differ based on local, state, and federal laws and jursidictions between taxis, TNCs, CTAs, PHV, etc.
 
 ## Table of Contents
 
@@ -64,7 +64,7 @@ Example 2: three shared trips, some overlapping
 
 The `journey_attributes` array **may** have the following key value pairs:
 
-- ...
+- `shift_id` (UUID, optional): unique identifier for an entire driver's work shift, tied across multiple journeys and therefore trips.
 
 [Top][toc]
 
@@ -95,10 +95,13 @@ The `trip_attributes` array **may** have the following key value pairs:
 - `app_name` (text, optional): name of the app used to reserve the trip which could be provider's app or 3rd party app
 - `passenger_count` (integer, required): unique count of passengers transported during trip duration
 - `request_time` (timestamp, required): when the passenger requested the trip
-- `trip_wait_time` (milliseconds, optional): part of the passenger trip where the vehicle was moving slow or stopped (e.g. <12mph), which is a different rate in some jurisdictions
+- `trip_wait_time` (milliseconds, optional): part of the passenger trip where the vehicle was moving slow or stopped (e.g. <12mph), which is a different fare rate in some jurisdictions
+- `trip_fare_time` (milliseconds, optional): part of the passenger trip where the vehicle was moving more quickly (e.g. >12mph), which is a different fare rate in some jurisdictions
 - `pickup_address` (text, optional): street address where the trip originated from
+- `dropoff_address` (text, optional): street address where the trip ended
 - `permit_licence_number` (string, optional) - The permit licence number of the organization that dispatched the vehicle
 - `driver_id` (string, optional): Universal identifier of a specific driver, static across operators, like a driver's license number. Could also be used as a lookup in an agency's internal driver system.
+- `wheelchair_transported` (boolean, optional) - was a wheelchair transported as part of this trip?
 
 _See more available trip attributes for any mode in the [trips endpoint](/provider#trips)._
 
@@ -110,6 +113,7 @@ The `fare_attributes` array **may** have the following key value pairs:
 
 - `payment_type` (enumerated, required): `cash`, `credit_card`, `mobile`, `voucher`, `paratransit`, `no payment`, `test`
 - `fare_type` (enumerated, required): `meter_fare`, `upfront_pricing`, `flat_rate`. Indicator of which rate was charged.
+- `meter_fare_amount` (currency, conditionally required): if `upfront_pricing` is used as a `fare_type` include what the metered fare would have been if `meter_fare` would have been used. Allows cost comparison in evalutation of programs and pilots.
 - `tolls` (currency, optional) - Sum of any and all tolls charged for the trip, such as bridge tolls
 - `base_rate` (currency, optional) - Minimum fare to be charged as soon as the trip starts.
 - `exit_fee` (currency, optional) - Fee to exit location, like an airport
@@ -138,6 +142,7 @@ The `vehicle_attributes` array **may** have the following key value pairs:
 - `color` (string, optional)
 - `vin` (string, optional) - the Vehicle Identification Number of the vehicle
 - `placard_number` (string, optional) - the registered placard number of the vehicle
+- `license_plate` (string, optional) - the registered vehicle license/number/registartion plate identifer on the vehicle
 - `inspection_date` (date YYYY-MM-DD, optional) - the date of the last inspection of the vehicle
 
 _See more available vehicle attributes for any mode in the [vehicles endpoint](/provider#vehicles)._