-
Notifications
You must be signed in to change notification settings - Fork 232
Web conference notes, 2020.08.20 (City Services WG)
Michael Schnuerle edited this page Aug 20, 2020
·
13 revisions
- Every other week call at 11am PT / 2pm ET
Meeting ID: 671 331 832
One tap mobile:
- +19294362866,,671331832# US
Dial by phone:
- +1 929 436 2866 (US)
Add your own name, link, and organization during call
- Henri Bourdeau, Blue Systems
- Michael Schnuerle, OMF
- Bill Dirks, Ride Report
- Joseph Yawn, Atlanta Regional Commission
- Mark Maxham, E&A / LADOT
- Brooke McKim, Stae
- Thibault Castagne, Vianova
- Neil Goldader, E&A
- Sean Holman
- Andrea Arjona, San Jose DOT
- Brian Ng, E&A
- Dheeraj Putlur, Populus
- James Delgado, Blue Systems
- Jean Kao, Populus
- Joe Girton, Stae
- Joseph Al-hajeri, Austin, TX
- Sanjiv Nanda, SANDAG
- Sharada Strasmore, DDOT
- Sherie Tan, San Jose DOT
See minutes from Provider WG meeting last week.
- Working Group Steering Committee member introduction
- Henri Bourdeau, BlueSystems (chair)
- Andrea Arjona, City of San Jose
- Mark Maxham, E&A
- Sanjiv Nanda, SANDAG
- Joseph Yawn, Atlanta Regional Commission
- Looking to 1.1.0
- Metrics/Reports, Geography, Stops updates, Policy driven events,
/trips
in Agency - Currently in the formal proposal time according to release process
- Release Plan
- Metrics/Reports, Geography, Stops updates, Policy driven events,
- Call for release ideas/proposals for your city/company in Github now.
Notes and or transcript of the call with presentation, document, GitHub links and calls to action.
- Michael introduced new WGSC and they give quick hellos.
- See links to these items on the new 1.1.0 Release Plan page.
- Metrics - needs feedback from people. Tries to align to SAE's MDC and uses just data within MDS feeds.
- Removed Jurisdiction from the 1.1 release since it is less of a priority than the other items
- Geography API - used to reference geographies by ID across the MDS spec. Won't be a breaking change. ID can be optional, still defined in existing parts of spec. Max to create a PR to pull it out of Policy.
- Recommended Rule Option #557 - for Policy. Something to nudge consumer behaviour and provider without repercussions or enforcement required. An 'incentive' or 'recommended' or 'preferred' rule. Example is preferred device drop off locations. Could be handled with 'info' rule type now but not in an ideal way. Many ways to solve for this, needs discussion on issue.
- Discussion about adding /trips endpoint to Agency, minus some fields already in Agency. See #550
- Talked about the release process, where we are, the Release Plan page.
- ACTION: Now is the time for everyone to get their feedback, ideas, and proposals into Github for consideration and discussion.
MDS Links
Working Groups
2.1.0 Release
0.4.1 Release Planning Meetings