MDS Working Group

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

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

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

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

21 Attendees

Main Topics

Announcements

• ...

MDS 2.0 wrap up to make release candidate

• Review work on MDS 2.0
• Goal of finalizing work now, release candidate for OMF approval in 2 weeks

Review High Priority Items and Open PRs

1. Modes work
2. Policy issues and PRs
3. Agency/Provider Unification #796
4. Policy Requirements use case support
5. Provider Reports

WGSC Meeting Organizers

• Host: Michael Schnuerle, OMF
• Facilitator: Michael Schnuerle, OMF
• Outreach: Michael Schnuerle, OMF
• Note taker: Jean Kao, Populus

1. Review and leave feedback on any MDS 2.0 issues referenced during the meeting, on the agenda, or on GitHub by Jan 13.

Goal

• wrap up work for v2.0
• release candidate ready in 2 weeks
• next week steering committee checkpoint, what needs more work, what should be cut
• see Release 2.0.0 Plan in wiki for overview of what’s being included and schedule for release

Modes work

Tony Geara (Detroit)

• no aerial or water modes yet, do we envision adding these in the future?

MS

• conscious decision to include new modes that were being actively used by cities with a modified version of MDS, was able to incorporate those real-life MDS changes and experience into release,
• Tony can open a new issue for next release for other modes
• after v2.0 can add new modes now without making a breaking change

AGH

• MDS is iterative and v2.0 represents a major step forward from micro mobility but this is not the end
• some cities are interested in OMF convening a conversation around aerial mobility
• major areas of jurisdiction with aerial, for example FAA

Policies issues and PRs

• Review of open
• Question about trips definition with review of defined 60 second duration

OpenAPI

TG

• changes from jsonschema to new format, would that require IT team to make changes to how data is validate, if they are doing that now. Does not impact general use of the spec. MS
• not breaking change technically because an org doesn’t have to use it

Policy Requirements

Use case work and moving out of beta looks good.

Provider Reports

No comments or objections

Agency/Provider Unification

• Robust review of changes and what is left to be done and how to leave feedback
• No other comments or objections

Anything else anyone wants to cover for MDS 2.0?

No comments