Web conference notes, 2022.04.14 (MDS Working Group)

MDS Working Group

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:

21 attendees

Main Topics

Kickoff - Sebastien Berthaud, Blue Systems (5 mins)
Agency and Provider Unification Discussion (40 mins)
- Unification Task Force
- Issue #759 - MDS Agency and Provider Unification
- Summary and 4 options by Marie Maxham
Discuss need for schema/open api/swagger definitions (if time allows)
- Issue #281 - Use OpenAPI to define MDS API request shapes and query parameters

WGSC Meeting Organizers

Leave feedback here
- Issue #759 - MDS Agency and Provider Unification
- Summary and 4 options document comments and edits
- Issue #281 - Use OpenAPI to define MDS API request shapes and query parameters, use of schema

Marie’s Overview

Agency and Provider are symmetrical at this point with /vehicles endpoint. One is pull and the other is push. Should be able to use either for use cases.
Still some places where there’s not perfect symmetry and/or the spec could be simplified. See https://docs.google.com/document/d/134DrPFjSpapW1auTT2M_BuL2E9tdO1At0yu6VII1cPA/edit
Liang - Agency doesn’t get trip data, why?
Marie - Agency was created for LADOT because Provider didn’t handle active mgmt (before /vehicles)
Alex - Provider gets historical data, right?
Matt D - vehicles endpoint doesn’t provide location of vehicles while on a trip
Marie - real time telemetry frowned upon but totally inbounds to track taxis in real-time not like scooters
Alex - SF in same boat, telemetry pushed to us but not sure of “real-time” definition for taxis
Marie - LA has delay on real-time trip but asap for other states
Joe - Are there additional Agency use cases coming down the pipe for real time vehicle management? e.g. “POST vehicle” response: “400: no you can't register or park here now”
Michael - are there additional use cases coming down the pipe for real-time vehicle mgmt?
Marie - haven’t heard of any

Option 1

Marie - When do I need telemetry data as an event and when do I need to send it during a trip?
Liang - no point to send same data over and over again when vehicle is on a trip if no telemetry, but what if there are issues during trip?
Marie - events for stops is included

Option 2

Matt - assume there’s some known definition of a trip and there’s not (“in trip” vs “out of trip” telemetry)
Matt - does seem super useful to say from somewhere this segment of the telemetry was from the shed to the restaurant, this segment is for restaurant to another restaurant, and to be able to put that all together
Marie - recycle taxi journey/stops concept to deliveries, still be able to assign info to a given telemetry point

Option 3

Option 4

No questions
Jean - do Marie or Michael have a preference or recommendation of the options?
Marie - 3 would be easiest to do, preference for 2 over 1, make sure all use cases continue to be supported
Michael - just want what’s best for community, any of them can work, don’t want to lose any use cases
Matt D - what criteria are different groups using? Populus looking primarily what makes it most tenable to use both in same place, combine best of each, how will decision be made, what rubric will be used

Use OpenAPI to define MDS API request shapes and query parameters

https://github.com/openmobilityfoundation/mobility-data-specification/issues/281
BlueSystems using schema
Seb: go for it, regardless of tool some value
Marie: good idea, OpenAPI or swagger
Michael: does it replace schema?
Neil: OpenAPI builds on json schema, could be additive
Michael: generating json schema by hand has been cumbersome, would rather just move to new but don’t want to leave ppl behind who depend on current schema. Must work with CDS too.