MDS 2.0 - Stops should have same response structure as vehicles or vice versa

[lastalfriday]

I'm refer to the links property here..

https://openmobilityfnd.stoplight.io/docs/mds-openapi/bd99c2440acf4-stops

https://openmobilityfnd.stoplight.io/docs/mds-openapi/817070d4bd451-vehicles

[lastalfriday]

...also I see a new property version in the response here. If you are going to use this, please use it in all responses across all endpoints

[schnuerle]

Version will be available in all responses.

I don't think all responses have pagination options. But not sure if they should.

[thekaveman]

also I see a new property version in the response here. If you are going to use this, please use it in all responses across all endpoints

version is returned in every GET payload across MDS, we added it to the few missing ones in this OpenAPI update. Except for the following endpoints:

• GET /reports/{filename} in Provider - this is summary data and version is not meangingful
• GET /metrics in Metrics - this is the discovery endpoint for metrics, version is not meanginful
• GET /requirements in Policy - the metadata key contains information about the MDS version requirement

Paging (the links object) is explicitly disallowed in some endpoints, such as /trips and /events/historical in Provider:

The /trips and /events/historical endpoints must not use pagination.

[schnuerle]

I think this was resolved in 2.0. @lastalfriday let us know if there is something here that needs more work for a future release.