nits

Author: marie-x

data-types.md

@@ -20,7 +20,7 @@
 A vehicle record is as follows:
 
 | Field                | Type     | Required/Optional     | Comments |
-| -------------------- | -------- | --------------------- | ----- |
+| -------------------- | -------- | --------------------- | -------- |
 | `provider_id`        | UUID     | Required              | A UUID for the Provider, unique within MDS. See MDS [provider list](/providers.csv). |
 | `device_id`          | UUID     | Required              | A unique device ID in UUID format, should match this device in Provider |
 | `vehicle_id`         | String   | Required              | A unique vehicle identifier (visible code, licence plate, etc), visible on the vehicle itself |
@@ -87,7 +87,7 @@ A vehicle status record represents the current or last-known disposition of a ve
 Events represent changes in vehicle status.
 
 | Field | Type | Required/Optional | Comments |
-| ----- | ---- | ----------------- | ----- |
+| ----- | ---- | ----------------- | -------- |
 | `provider_id` | UUID | Required | A UUID for the Provider, unique within MDS. See MDS [provider list](/providers.csv). |
 | `provider_name` | String | Required | The public-facing name of the Provider |
 | `device_id` | UUID | Required | A unique device ID in UUID format |
@@ -104,7 +104,7 @@ Events represent changes in vehicle status.
 
 (?) Do we still want `event_geographies`?
 
-(?) Replace `event_location` GeoJSON with Telemetry
+(?) Replace `event_location` GeoJSON with GPS?
 
 (?) Does anyone use `associated_ticket`?
 
@@ -132,8 +132,6 @@ A standard point of vehicle telemetry. References to latitude and longitude impl
 | `battery_percent`       | Integer          | Required if Applicable | Percent battery charge of vehicle, expressed between 0 and 100 |
 | `fuel_percent`       | Integer          | Required if Applicable | Percent fuel in vehicle, expressed between 0 and 100 |
 
-(?) What about  other types of sensor data, e.g. accelerometer? Scooter tip sensors?  Should that be telemetry or an event or ... ?
-
 ### GPS Data
 
 | Field      | Type           | Required/Optional     | Field Description                                            |

provider/README.md

@@ -249,7 +249,7 @@ Trips that start or end at a [Stop][stops] must include a `stop_id` property in
 
 The `/events/recent` and `/events/historical/` endpoints return a list of Event objects, describing the activity of the Provider's vehicles.  Recent events are at most two weeks old and can be queried with start/stop time, and historical events are packaged in hour-sized chunks for ease of implementation. 
 
-(?) This distinction is a holdover from MDS 1.x.  Dramatic simplification of the query is meant to make cold storage by hourly chunks trivial without a database.  We should ask Providers if that has been a concern in practice.
+(?) This distinction is a holdover from MDS 1.x.  Dramatic simplification of the query is meant to make cold storage by hourly chunks trivial without a database.  We should ask Providers if that has been a concern in practice.  Alternatively they could be the same endpoint with different parameters.
 
 Unless stated otherwise by the municipality, this endpoint must return only those status changes with a `event_location` that [intersects](#intersection-operation) with the [municipality boundary](#municipality-boundary).