Web conference notes, 2023.01.19 (MDS Working Group)

Web Conference

MDS Working Group

• Every other Thursday at 9am PT, 12pm ET, 5/6pm CET

Conference Call Info

Zoom Registration Link: https://us02web.zoom.us/meeting/register/tZAscOmhpjIuHNakPx6CNbACpjUjw1Gsucr4

One tap mobile: +19294362866,,84170989462#,,,,*612987# US (New York) - though we encourage Zoom

Attendees

Note: Attendees register upon entry into the Zoom meeting. An attendee count will be posted here after the meeting:

X Attendees

Agenda

Main Topics

Announcements

• OMF held an All Member Meeting Jan 18

MDS 2.0 release candidate updates

• Review MDS 2.0 Release
• Checkpoint #3 Consensus notes
• Review Open Work
• Targeting two weeks for release candidate wrap up with Feb 16 announcement at WG meeting, and release approval after OMF governance process before announcing on April 19.
• WGSC will be working on supporting materials, like implementation supporting doc and upgrade cohort.
• Some WG meetings may be cancelled as we work on the release, and allow some time off and breathing room for the Working Group

WGSC Meeting Organizers

• Host: Michael Schnuerle, OMF
• Facilitator: Michael Schnuerle, OMF
• Outreach: Michael Schnuerle, OMF
• Note taker: Alex Demisch, SFMTA

Action Items and Decisions

1. Review MDS 2.0 in dev branch
2. Leave any comments for Agency/Provider Alignment in PR 796

Minutes

WGSC held consensus checkpoint meeting last week

• Modes work merged to dev.
• Policy work largely moved to dev. Some work on rates remains.
• Agency/Provider Unification draft almost complete.
• Some Miscellaneous tasks remain. See 2.0 Checkpoint Consensus for more details.

Open items

• See items tagged with 2.0 in Github for full list.
• Drover AI items will be included (parking validation, scooter detection)
• OpenAPI - OMF to hire contractor to move MDS 2.0 into OpenAPI. This will allow MDS producers/consumers to use OpenAPI tools to validate schemas.

Provider/Agency Alignment

• Big change is that both APIs will have the same endpoints and data structures. Provider API involves cities pulling data from operators. Agency involves operators pushing data to cities.
• The goal is that if either or an Agency or Provider has an implementation of one API, they are 85% of the way to the other.
• Alignment within Agency as well, e.g., bulk operations/payloads available in all endpoints
• Review dev to see how it all looks. Leave any comments for Agency/Provider Alignment in PR 796

Release Plan

• WGSC will meet next week to finalize release candidate. Then start internal review process: Privacy Committee, Strategy Committee, and Tech Council. Then to OMF Board for review.
• Goal is to bring release candidate to WG at February 16th meeting, and wider release announcement for April 19, but it’s possible that the review process may extend the timeline.
• WGSC will produce upgrade supporting materials. Will aim to have an upgrade cohort so that those who are upgrading can go through it together.
• Working Group meetings may be cancelled to focus on release, or meetings will have a targeted focus on release or upgrading.