Skip to content

Web conference notes, 2021.05.06 (Joint Working Group)

Michael Schnuerle edited this page May 10, 2021 · 12 revisions

Web Conference, 2021.05.06

Joint Working Group - City Services

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

Conference Call Info

#red NOTE NEW ZOOM MEETING ID/LINK/PHONE! (as of Jan 1, 2021)

Meeting ID: 841 7098 9462 - Passcode 612987
https://us02web.zoom.us/j/84170989462?pwd=WTRlY25wOVhNeS8wQk1iM2QzYkQvUT09

One tap mobile: +19294362866,,84170989462#,,,,*612987# US (New York)

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

Attendees

Add your own name, link, and organization during call

Agenda

Main Topics

  1. Discussion around adding /trips endpoint to Agency API #550

WGSC Meeting Organizers

  • Host: Steve Brining
  • Facilitator: ...
  • Outreach: Michael Schnuerle
  • Note taker: Michael Schnuerle

Minutes

  • Spin is ok with this idea now that we are slower with MDS release and they have more technical team resources
  • Possible convergence of Agency / Provider in the future?
    • Not sure yet we can do that. Would be a Major release, so would not be until in 2022.
    • If unified, same data in different directions. Provider could get you in sync if Agency goes down.
    • Made a new Discussion issue to discuss and capture ideas about an Agency and Policy convergence in a future major release
  • Neil: Dangling/orphaned trips from other jurisdictions - push interface in Agency is better than Provider so as not to overwhelm it with requests searching for an end/start to orphaned trop. May require querying provider a ton to find it.
    • Neil will document orphaned trips use case in the issue.
    • See new issue created at #642
  • Agency meant more real time, Provider more historic. That may not be how it is used now, but that was intent. Could go back to that more explicitly.
  • Per Europe conversations, some are concerned with real time aspect of Agency. Cities could choose more RT vs Historic for GDPR. Provider Trips is not meant to be RT.
    • Mentioned example of Dutch city getting fined $600K Euro for tracking personal phone mac addresses with no GDPR rules in place, but this is not the same as shared devices with proper GDPR framework.
    • William: Is RT more sensitive? Historic is maybe more privacy focus. Universal is RT, but not the setting up of tech stack. May not be relevant
  • General information suggestion - add a section of what’s required in trips.
    • Maybe fix this in Provider too to hit both of them.
    • William will create a new issue William or Neil can dig it up.
  • Need more info in taxi trips, and trips in agency is needed then.
  • Emmett from SP will leave feedback on issue.

Notes from OMF: new blog posts

Clone this wiki locally