Web conference notes, 2022.03.03 (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:

29 attendees

Agenda

Main Topics

• Kickoff - Sebastien Berthaud, Blue Systems
• WGSC Plan Checkpoint results - Michael S, OMF and WGSC members
• Modes Architecture Task Force - Marie Maxham, Lacuna
  • Review latest pull request details and technical solution for implementing modes in general in MDS, splitting out micromobility into its own mode, and allowing space for other new modes to be added.
    • Pull Request (merged) - see this PR for the latest
    • Browsable spec changes
• Policy Reimagining Task Force - Jean Kao, Populus
  • New Issues create from last meeting action items:
  • vehicle "heartbeat"
  • Standardize lookback period
  • Trip definition
  • Should MDS Policy include fees or should fees be separate

WGSC Meeting Organizers

• Host: Sebastien Berthaud, Blue Systems
• Facilitator: Michael Schnuerle, OMF
• Outreach: N/A
• Note taker: Alex Demisch, SFMTA

Action Items and Decisions

1. Leave comments on Mode Architecture Pull Request
2. Leave comments on the 4 new Policy Issues (see agenda above for links)

Minutes

WGSC Plan Checkpoint Results

• We have clarity on what MDS 2.0 will contain: Modes Architecture, Policy Reimagining, and Agency/Provider Unification.
• This is the first of four checkpoints.
• Report has been sent to Privacy Committee and Strategy Committee

Modes Architecture Task Force

• Marie took the white paper and developed PR 745 to show what micromobility under the new modes framework in MDS would look like.
• Michael also prepared a new feature branch with browsable spec changes.
• Created separate files for some of the general architecture (e.g., readme, event_types, vehicle_states), and created a separate micromobility file to describe the micromobility mode.
• Event types and vehicle states are intended to be relevant across all modes.
• Defining a mode involves describing what overall elements are relevant/not relevant to the mode, indicate which attributes are relevant, enumerate valid micromobility states, describe what the states mean, and define the state machine diagram.
• Marie's proposal is for a provider_id applies to a provider implementing a single mode. The other option is to have provider_id apply to multiple modes, but this requires being specific in every relevant endpoint.
• Michael also proposed vehicle_attributes in the trips endpoint -- this helps with Agency/Provider Unification
• Need to consider implementation of trips in Agency API.
• Provider/Agency Unification will likely influence how modes are implemented across both APIs as well.
• Differences in TNC and Taxi appear in state machine, largely due to TNCs sometimes operating as private vehicles and separate regulatory authority. Taxis are currently being implemented in LA, but there are no TNC implementation. We will still need to decide if/how TNC would be reflected in MDS 2.0.
• Very little changes to Jurisdiction, Geographies, and Policy.
• Please leave comments in PR 745, either as a general comment or inline.

Policy Reimagining Task Force

• Jean posed a couple of issues for consideration https://github.com/openmobilityfoundation/mobility-data-specification/issues/created_by/jean-populus
• Should fees be included in Policy? What should be counted when we are counting fees? E.g., if we are assessing per trip fees, how do we define a trip?
• Should we standardize the lookback period? When counting vehicles via status changes, we need to determine how far back in time to look for events.
• Leave feedback in the relevant Issues linked in agenda.