MDS Policy Reimagining and Vision

[schnuerle]

Have you been using MDS Policy and do you have thoughts on how it's working for you and how it's not? Please leave them below and start the discussions for MDS 2.0.

• Variety of geography types for the same policy implementation?
• How complex are the polygons supposed to be? Some are large and hard for joins. Guidelines needed
• Overlapping geographies and how they are implemented and presented to the user/rider in the app
• What about the expected precision of GPS for enforcement
• Similar policies across multiple geographies can be hard to understand, maybe some grouping would help?
• Clarity on how to execute on common policies - Policy is so flexible some agencies use it in "creative" ways.
• Previous policy may need to be a required field instead of optional, and how they change over time. Is the current replacement mechanism working?
• Should Policy be able to allow automatic processing and ingestion and how complex is that?
• Specify mechanism for determining only active policies in the spec
• Should policies always have an end date? Guidance for how far ahead to publish upcoming active policies?
• Does Policy need pagination support, like other parts of MDS?

The WGSC has also created a Use Cases for MDS Policy document that we will discuss at the Nov 10 WG meeting. We'd like to know your real world uses cases for Policy so we can ensure a reimagined Policy API meets your needs.