Policy Requirements

[schnuerle]

This pull request is written to fulfill the needs of the discussions started in Issue #608 around agencies expressing data sharing requirements more clearly.

Explain pull request

This would add a new endpoint Requirements under the Policy API that allows agencies to digitally express only the data they need for their jurisdiction and operating permit.

Is this a breaking change

• No, not breaking

Impacted Spec

Which spec(s) will this pull request impact?

• policy

Additional context

The initial PR is a draft that will require feedback and edits from the MDS community before becoming part of the release, including external guidance documents and a new OMF repo to host requirement files for some agencies.

[jrheard]

just some typo fixes!

[jfh01]

What do you think about reordering the list of examples here? https://github.com/openmobilityfoundation/mobility-data-specification/blob/ms-requirements/policy/examples/requirements.md. Thinking from most->least common/complex. e.g. start with a simple MDS provider + GBFS and then get into some of the other options

[schnuerle]

What do you think about reordering the list of examples here? https://github.com/openmobilityfoundation/mobility-data-specification/blob/ms-requirements/policy/examples/requirements.md. Thinking from most->least common/complex. e.g. start with a simple MDS provider + GBFS and then get into some of the other options

That was the intention with this list. Here's the current order (with my comment as to order chosen):

1. Policy and Geography (easiest, just a city serving up 2 potentially static files for providers to use)
2. Vehicles Only (easiest, one provider endpoint, a way to use MDS for regulation instead of GBFS)
3. Trips Only (easy, one provider endpoint, but a bit more too it than vehicles)
4. Trips with No Routes, Vehicles IDs, or Dates (easy, a version related to the previous example, with less data)
5. Provider and Other APIs (medium, getting multiple APIs from providers)
6. Agency (harder, implementing push APIs hosted by agencies)
7. Geography Driven Events (outlier - example of a specific feature implementation since it's a special case)
8. GBFS Only (easiest, but last since it's outside of OMF purview).

So if you think the order should be different, let me know how.

[schnuerle]

After lots of great review and feedback from dozens of people over the last few months, I believe this is ready to be merged to 'dev'! Thanks to @quicklywilliam for the original idea with #608, and this has grown to solve other issues raised by the community as well including #507 and #639.

If there are new suggested changes that come up, we can open an Issue or Discussion to resolve them before the 1.2.0 release candidate is made for approval, or even make minor updates once the RC is made.