Web conference notes, 2022.10.13 (MDS Working Group)
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:
25 Attendees
Main Topics
Policy Changes
- Policy Updates - Justin from Blue Systems, Jean Kao from Populus
- Unknown issue, followup - Jean Kao from Populus
WGSC Meeting Organizers
- Host: Sebastian Berthaud, Blue Systems
- Facilitator: Jean Kao, Populus
- Outreach: Michael Schnuerle, OMF
- Note taker: Michael Schnuerle, OMF
- Sticking with just 8 use case to be defined in spec, Other use cases will be removed
- Need more clarity on GitHub discussion around Operating Area and No Riding
- More discussion is needed for nuance with Parking, concrete examples
- WG to review all examples in detail and leave comments on GitHub
- Update state diagram to remove Unknown - states are either in or out of PROW, no ambiguity
- Heartbeat not needed with this solution, /vehicles can work for this
- No need for lookback periods now
- Need discussion on GitHub about how long before a transition to missing happens. 24 hours, 2 days, 7 days, flexible in Policy Requirements?
Bird Updates
Jay Williams (previous)
Lilian Pen (product lead)
Nathan Villaescusa
Justin Yeo
Policy Definitions
Sticking with just 8 use case to be defined
Other use cases will be removed
Operating Area
Josh: Jurisdictions considered here?
Justin: Operating area bigger than jurisdiction
Jay: Operating areas cannot expand into other jurisdictions legally
Neil: Inverse of riding area/no riding area.
Jay: some cities don't operate to borders
Agree that more guidance for each could be needed
Michael: Not a simple inverse of operating area and no riding
Need more clarity on GitHub discussion around Operating Area and No Riding
Not sure if it should be Time (could be count) needs final definition
Parking
Should be parked or must be parked?
More discussion is needed for nuance here
Need to look at some concrete examples
Need time for WG to look at all of these in detail.
Jean Kao
Unknown State
Break into Temporary PROW state, no heartbeat, unclear if it's missing or technical glitch
More permanent not-PROW state where operators are going to go look for it
Update state diagram to remove Unknown
Missing and non-contactable
Moves to missing after some amount of time
Assumes providers to implement new schema
Do we need heartbeat then if we now have these states?
No need for loopback periods now?
Either in or out of PROW then no ambiguity
Jay: exact timing is a question. When can it go to missing? Offline = non_contactable
Neil: are transition periods customizable by cities
Michael: operator could handle dynamic values? Could be different by program, city, vehicle, mode, etc
Jay: don't want it to be updated all the time or in Agency
Vladimir: solution is already there for my cases
Jay: happy with 24 hours, but have heard cities ask for 2 days or 7 days
Vladimir: would like to know last heartbeat for emergencies even at larger intervals would be useful
Jay: Vehicles endpoint is more often with telemetry with most recent location
Justin: telemetry does act as heartbeat so don't need it with status changes
Vladimir: seems like vehicles can work for this now that it's available
Michael: want to not duplicate for
Intention is any state can go to non_contactable, then back into any other state, not the same state
Bird tries to do multi transitions, but Unknown you could also go to/from any state
Valdimir: I need to join another meeting too. Thank you everyone for your knowledge share. In Solidarity
Continue "time" discussion on GitHub
