Web conference notes, 2020.04.16 : City Services WG

• biweekly call at 9am PST / 12pm EST
• Join Zoom Meeting https://zoom.us/j/671331832

Meeting ID: 671 331 832

One tap mobile:

• +16699006833,,671331832# US (San Jose)
• +19294362866,,671331832# US (New York)

Dial by your location:

• +1 669 900 6833 US (San Jose)
• +1 929 436 2866 US (New York)

Find your local number: https://zoom.us/u/aeJWJsuC2b

add your name at beginning or end of call

• Jascha Franklin-Hodge, Open Mobility Foundation
• Henri Bourdeau, BlueSystems
• William Henderson, Ride Report
• Mike McDonald, Portland Bureau of Transportation
• James Greenhill, Uber (JUMP)
• Michael Durling, Ellis & Associates
• Thibault Castagne, Vianova
• Michael Schnuerle, Open Mobility Foundation

• 0.4.1 Release Candidate check
  • Clarified that /vehicles is not intended to replace GBFS
  • Clarified review and decision making for beta features
  • Board reviewing 0.4.1, leading to the two clarifying suggestions above. Board should vote final approval on may 13th.
• MDS maturity survey results
  • Link to results: https://docs.google.com/viewer?a=v&pid=forums&srcid=MTY5MjgyNjI5ODM0ODIyMTQ1OTkBMTA1MzExNTkzNTk2NTM0OTgwNTABMjktckRMS3hCZ0FKATAuMQFncm91cHMub3Blbm1vYmlsaXR5Zm91bmRhdGlvbi5vcmcBdjI&authuser=3
• Provider/Agency reconciliation update
  • Spreadsheet
  • Notes
  • State Machine
  • Slide Deck
  • Presentation to board scheduled on May 5th. Drafts for PRs to come shortly after @Mark Maxham.
• Issues and PRs to be discussed for the 1.0.0 version:
  • Please take a look at the issues and PRs from the 1.0.0 and "Future" milestone for subjects you would like to see move forward in the next version of MDS. Add a comment to notify your interest, or bring them up in the WG meetings.
  • 1.0.0 milestone https://github.com/openmobilityfoundation/mobility-data-specification/milestone/9
  • Future milestone : https://github.com/openmobilityfoundation/mobility-data-specification/milestone/4
• New issues and PR
  • https://github.com/openmobilityfoundation/mobility-data-specification/pull/484 Policy Rates PR
    • https://github.com/openmobilityfoundation/mobility-data-specification/issues/472 Addressed issue
    • Question from Mike McDonald on how to handle increasing fees over time. Specific example to be added as comment for detailed discussion.
    • Concerns from Charles Noling about keeping policies understandable enough for the providers receiving them.
    • Webinar presenting Policy API scheduled on May 19th, to be announced on the mailing lists @Jascha.
    • Issue https://github.com/openmobilityfoundation/mobility-data-specification/issues/489 created on how to link specific events to policies to enable retro-analysis
  • https://github.com/openmobilityfoundation/mobility-data-specification/issues/481 Policy rules - order of operation
    • Proposition: prohibit mixing different rule_types in a policy
    • @Neil Goldader to explicit use-cases for multiple rule-type policies.
  • https://github.com/openmobilityfoundation/mobility-data-specification/issues/485 MDS metrics API
    • https://github.com/openmobilityfoundation/mobility-data-specification/pull/487 Definition PR
    • https://github.com/openmobilityfoundation/mobility-data-specification/pull/486 Spec PR
    • API to communicate aggregated metrics, will be discussed in depth during the next meeting.
  • https://github.com/openmobilityfoundation/mobility-data-specification/pull/483 MDS audit spec
    • API to check that data received through MDS corresponds to the reality. Use-cases to be added to the PR for further discussion.
  • https://github.com/openmobilityfoundation/mobility-data-specification/pull/482 Policy speed limit examples
    • Clarify order of operation wording @Mark Maxham
• https://github.com/openmobilityfoundation/mobility-data-specification/pull/469 add optional provider_id to vehicle-register
  • Approved
• Jurisdiction API: PR expected in the following weeks @Mark Maxham