Web conference notes, 2021.12.16 (MDS Working Group)
MDS Working Group
- Every other Thursday at 9am PT / 12pm ET / 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:
X Attendees
Main Topics
- Modes in MDS
- Review work done by LADOT on taxis in MDS and suggested PR on how they have incorporated that work into MDS based on the WG's collaborative Modes draft document. Presented by Neil and Marie from E&A.
- See PR #735 here
- Meetings Dec 23/30 cancelled, but back Jan 6.
- OMF announcement, interim executive director
WGSC Meeting Organizers
- Host: Sébastien Berthaud, Blue Systems
- Facilitator: Michael Schnuerle, OMF
- Outreach: Michael Schnuerle
- Note taker: Marie Maxham, E&A
...
Notes
Neil presentation
Q&A:
William: "elsewhere" can cause a bunch of edge conditions, how are those addressed? Neil: New trip structure handles much of the missing event info
William: Will you have to poll /events AND /trips to know the state of the vehicle? Neil: Only if you're trying to get info outside the jurisdiction
William: Could we ditch 'elsewhere' and have out-of-jurisdiction events drop telemetry? Neil: Possibly! Michael: Maybe we can collect events that are out-of-jurisdiction-but-not-in-some-other-MDS-jurisdiction Neil: Maybe the no-telemetry/no-geography events implicitly mean "out of jurisdiction" and we wouldn't need "elsewhere" Marie: Leaving jurisdiction and entering is also important for cap counting in real time
Michael: Two separate taxi/tnc modes seems like a tricky split, we should try to combine them
William: we should be optimizing for simplicity of spec over simplicity of implementation
Neil: multiple similar modes are pretty easy to implement and give flexibility to similar but different modes
Johnathan I: In NYC, a single "mode" can have multiple statuses. One example is the "green taxi" which is an FHV and can operate like one, but also has a separate set of rules while operating as something else. Complete edge case, but in NYC there are a few like this.
JFH: Potentially related concern with a TNC vehicle that can do both passenger and goods delivery through a single platform.
Sanjiv: How do passenger counts get managed? Neil: Currently they do not, because we don't know if taxis and TNCs track this themselves. We can use trip-metadata to collect extra data on a per-jurisdiction basis, as described in the Requirements API.
Alex D: What if a passenger requests a trip but it is never served (like when Neil didn't get his taxi to the airport)? Would we get the request but never associate it with a vehicle? [didn't get a chance to address this]
Michael: Let's continue the conversation in the PR, I will restructure 2.0 modes PR to extract micro
Neil: What's the appetite for TNC in 2.0? Michael: We are aiming for Taxi + TNC + delivery robots
JFH's last meeting is today
JFH: Farewell, I'm heading back to Boston. Angela is the interim director. Keep in touch!
Angela: The community is in good hands! It should be an exciting new year!
