Joint Working Group - Provider Services

• Every other week call at 9am PT / 12pm ET / 6pm CET

Meeting ID: 627 957 166 - https://zoom.us/j/627957166

One tap mobile: +19294362866,,627957166# US

Dial by phone: +1 929 436 2866 (US) (Find your local number)

Add your own name, link, and organization during call

• Michael Schnuerle, OMF
• Jonathan Internicola, NYC TLC
• Neil Goldader, E&A
• Kegan Maher
• Mark Maxham, E&A
• Jascha Franklin-Hodge, OMF
• Steve Brining, Blue Systems
• Alex Demisch, SFMTA
• Bill Dirks, Ride Report

1. Geography Feature Branch
   1. Discussion on General State of the Branch and Changes
   2. How it connects to the rest of the MDS spec
   3. Discuss Thoughts On Merging To Dev
2. Jurisdiction Spec + Spec's README
   1. E&A To Justify The Need
   2. Discussion
3. Future Meeting Topics

Geography Feature Branch

• Endpoint for Geography API will be /geographies to be consistent with other pluralized endpoint names (e.g., /policies, /trips).
• Discussion on authorization. If Geography will be public along with Policy and other APIs, then authorization needs to be optional. The authorization method also does not need to be required as JWT, just a bearer token method. JWT is only required for Agency. To do: open a new issue/PR to discuss auth docs across the spec.
• Additional examples would be helpful to illustrate more complex geographies (e.g., multi-polygon). Would be good to put in a folder like with /policy - Michael will do this before merging. Include an actual city and geographies in the examples - create a new issue for this.
• So that there isn't a breaking change, it's expected that the /geographies endpoint in the Policy API is identical to the Geography API. This is to ensure backwards compatibility, but the overall intent is to remove the /policy/geographies endpoint at the next major release. Create a new section called ‘Transition from Policy’ with language saying this is a temporary solution to avoid breaking compatibility. Michael will draft this for the feature branch.
• After merging to dev there is a new PR #581 that adds an optional geography type field. Will have proposed standard enumerated values and definitions, but you can create your own too.
• Need further clarification that agencies are publishing the geographies in the spec. Michael to draft for feature branch.
• Discussion on prev_geographies requirement. This is helpful to ensure that the relationships of which geographies were applicable at any given time are maintained, but should be optional. Some clarifying language needed to soften the proposed wording and and make it totally optional to implement - Michael to add draft. Discussed that maybe it’s removed in the next major release. But if it’s kept it may need a retire_date/end_date field to show that some geographies are not used at all any more.

Jurisdiction Spec

• Brian provided a brief overview, but discussion will be tentatively postponed until 10/29 to see if it can make the 1.1.0 release.