Skip to content

Web conference notes, 2020.01.07 (Joint Working Group)

tybaltspark edited this page Jan 21, 2021 · 11 revisions

Web Conference, 2021.01.07

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

  1. Update on 1.1.0 Approval Process
  2. Goals for this release
    • What are the priorities for this next release?
    • Ref: unresolved PRs and issues.
  3. Next feature candidates
    • Audit API: PR #493
    • Compliance API: PR #333, to be rewritten
    • Policy Author API Issue #496, PR #497
    • Geography Author API: PR #498
    • City Requirements API - a digital way for cities to express what endpoints and optional fields they require. Issue #608
  4. Current priority issues/PRs and new suggestions from the community

Minutes

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

Audit API

  • in use in LA
  • Validate ground truth by comparing with providers data
  • Maybe for next release, need more support

Compliance

  • Only for one provider
  • Allows enforcement by device id
  • Some metrics could be compliance metrics
  • Be "Metrics sensitive" now that Metrics exists as it is rebuilt and submitted in a new PR
  • In use in LA but good time for feedback
  • Vianova has a compliance API - providers use it now to see what’s out of compliance
  • Louisville and Baltimore would like realtime notifications this could provide
  • Bill Dirk ride report thinks it could be needed
  • Seems useful for next release

Policy Author

  • Way to update policies - create/add, draft, and deactivate policy
  • Providers could get early access to review, heads up beforehand, part of conversation (not written that way now)
  • Adds scope and access control levels to changes
  • Maybe useful, as is doesn’t have connection between providers and agencies
  • Where should this live, in its own MDS Admin new repo? WGSC conversation.
  • Sherie Tan San Jose - wants it to be fair to vendors, could be helpful to have a testing area for providers.
  • Explore it's use on the vendor side. Dirk says it could be useful to them

Geography Author

  • Just like Policy. Useful to see and have them in draft
  • Maybe both this and Policy in some new Authoring repo on top of MDS
  • Both help cities make changes and drafts to APIs they serve: Policy, Geography

City Requirements API

  • Discovery for what cities require - APIs, endpoints, optional fields, version supported
  • Can be tied to a multi-jurisdictional thing
  • Like a specification guide for cities and MDS - digital representation of what’s in the data section of the permit (as it relates to MDS).
  • OMF could create a process/checklist to pick what you want and generate text you put into the permit.
  • Permits can reference this API directly
  • Meg from Baltimore: immensely helpful - could be public for discovery and aggregation and transparency
  • Would be public like Policy, Geography
  • Could be part of policy but it seems clearer to have it be higher level
  • Note: a proposal #608 for this was made by Ride Report based on previous WG discussions
Clone this wiki locally