Joint Working Group - Provider Services

NOTE NEW TIME TWO HOURS SOONER

• Every other week call at 9am PT / 12pm ET / 6pm CET

NOTE NEW ZOOM MEETING ID/LINK/PHONE NUMBER

Meeting ID: 671 331 832 - https://zoom.us/j/671331832

One tap mobile: +19294362866,,671331832# US

Dial by phone: +1 929 436 2866 (US) (Find your local number)

Add your own name, link, and organization during call

• Michael Schnuerle, OMF
• Steve Brining, Blue Systems
• Kegan Maher
• Neil Goldader, E&A
• Joseph Yawn, ARC
• 25 attendees

Main Topics

1. City suggestions to new proposed release features while the are in beta

   1. Metrics - allow only cities (or organizations they designate) to serve the endpoints
   2. Special Groups - remove from Metrics and allow providers to serve this as a new endpoint with data not included currently in MDS
   3. Geography-Driven Events - location data must still be returned to allow cities to judge efficacy and audit events.

2. Release 1.1.0 Timeline.

Notes and or transcript of the call with presentation, document, GitHub links and calls to action.

Intro of Steve Brining as new chair of Provider Working Group Steering Committee.

Metrics

• William Ride Report - supports idea
• Todd - wondered about K values, but we don't have clarity yet. Maybe a normative statement is appropriate.

Community seemed ok with recommended changes.

Special groups

Bill Dirks, Max - constrained version of metrics API is good

• Will - Geographies endpoint is optionally public now, and Policy is required to be public at the same time. Maybe a requirement to make geography public as well if a city is using special groups.
• For future release beyond this beta, making Geography areas public connected to special groups use would be good.
• Michael to create an issue about this.

Community seemed ok with recommended changes. Not sure about the details of how it will play out in Provider and how it will be stripped down from Metrics spec. May need some collaborative technical breakout sessions.

Geography-Driven Events

• Brian - GPS variability means it’s good to require location data for beta for validation
• Do we need some OMF Guidance for consistency of GPS data for providers when implementing?
• William - noted that one client city was ready for only geography-driven events.
• Community discussed balancing needs of cities that either want data or only want geography-driven events to ensure that either could be an acceptable choice as a data requirement for operators.

Community seemed ok with recommended changes. William to make adjustments to PR

General Comments

• Josh - comments as privacy committee co-chair: underlying tension with MDS - new privacy features are needed
• Todd - clear on use cases, auditability is big city concern
• William - this GDE change may not impact city power dynamics with providers. Danger of people forking spec, which no one wants.
• Range of city spectrum on privacy data. Need some city choice
• Sean - idea of meta policy for MDS: what are the requirements cities request during provider implementation? Digital spec for providers and data needs and optional data. Lists digitally what optional fields are required, what endpoints to use, SLA info, etc. Good to think about for next release.

Release Timeline

Working Group Dates

• Dec 3 - WG Discuss city recommendations: metrics, GDEs, special groups
• Dec 10 - WG Finalize release discussion
• Dec 17 - WG meeting if needed or open questions
• Dec 24 - WG cancelled
• Dec 31 - WG cancelled
• Jan 7 - Kickoff next release (1.2, 2.0?)

Release Work

• Dec 11, 14 - Michael work on release candidate
• Dec 15 - release candidate ready
• End of Dec - Tech council review
• Mid January - Board Review
• February 28 - Board Approval Vote (earliest possible per bylaws)