Clarify which vehicles to include in the `/vehicles` endpoint

[jiffyclub]

MDS Pull Request

Explain pull request

The description of the Provider vehicles endpoints was never really updated in the MDS 1 -> 2 transition so this rearranges and clarifies some things now that there are two vehicle information endpoints, one for static information like vehicle/propulsion type and another for realtime status. These changes are mostly rearranging/clarifying, but there is one major addition to the description of the /vehicles endpoint describing that when called without a device ID it is expected to return every vehicle ever deployed in a jurisdiction. This closes #879.

Is this a breaking change

• No, not breaking. This makes no changes to the spec format, only clarifies content expectations.

Impacted Spec

Which spec(s) will this pull request impact?

• provider

Additional context

See also #879.

[schnuerle]

@jiffyclub do you think you can present some slides to explain this change at this Thursday's working group meeting? If so it can be the main agenda item.

[jiffyclub]

Yes, can do!

[jiffyclub]

Based on discussion on today's MDS call I'll update this to specify:

• /vehicles must return all vehicles deployed in a region in the last 30 days
• /vehicles/{device_id} must return vehicle information for all device IDs present in MDS data available from other endpoints regardless of when the device was deployed. If the vehicle information has changed over time the most recent information should be returned.