Web conference notes, 2021.10.07 (MDS Working Group)

Web Conference

MDS Working Group

• Every other Thursday at 9am PT / 12pm ET / 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

• Discussion about adding new modes in MDS 2.0 (review before meeting)

  • Draft Extending MDS to New Modes document
  • Discussion and Feedback
  • New: Modes Open Issues document

• Modes Overview Meeting (please watch recording and view slides to prepare for this meeting)

  • Modes in 2.0 meeting details and notes
  • Slides
  • Meeting Recording - Passcode: C71*9gZ=

• Previous WG discussions about modes

  • Web conference, 2021.07.01 - New Modes Discussion
  • Web conference, 2021.01.28 - Modes, Robots

WGSC Meeting Organizers

• Host: Jascha Franklin-Hodge
• Facilitator: Michael Schnuerle
• Outreach: Michael Schnuerle
• Note taker: Jean Kao, Populus

Discussion points

• Slides
• Meeting Recording and Chat - Password: !7SM0Y3p

Recap

Review the 4 Design Goals slide Distilled discussions from Aug WG meeting for this meeting and presentation

Open Issues Presentation

Mode

• A mode is a distinct regulator framework for a mobility service

Mode Trip Attributes

• Multi leg trips. Optional journey_id above trip_id
• Trip attributes flexible under mode
• Journey does not have other attributes

Trip data

• Key value attributes per trip

Specifying Mode

• Practically how to implement this
• Connected to provider_id or at trip/event record level
• Know what mode trips are associated with
• Explicitly know by looking at data
• Could allow multiple modes in one response, though we recommend different mode

Discussion

Mode

Mode Trip Attributes

Trip Data

Specifying Mode

Different solutions in agency and provider Ben onerous to lookup Agency vs Provider could have different solutions - attached to vehicles to Ben bikes and scooters in one micromobility feed Ben says maybe sidewalk Redundancy on purpose in Provider endpoints, May not be able to answer. Devices be multimodal itself? Multiple uses at once… food and passenger Boundary around state machines - per mode -

Provider is like a pre-baked database schema, and does not need a lot of joins Add to status changes, events, trips Seb at least wants mode Both - issue with what is canonical. Ben Introduce modes things, provider id to mode? GBFS/MDS url need to be added in CSV too.

• Use case for why to mix modes across endpoints? May add more complexity and could have bad overlaps.
• ...

Ben some ability to providers to define and publish this Provider reqs equivalent, how trips overlap, how journeys work per trip

Action Items

• ...