Joint MDS Working Group

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

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)

Note: We are now collecting attendees upon entry into the Zoom meeting. An attendee count will be posted here after the meeting:

18 Attendees

Main Topics

• Discussion on Board vote on merger of MDS WGs
• Tiered dwell time rates - #658
  • Created by Neil under the guidance of Marie related to support of duration-based fees in MDS Policy
  • This might solve #631 and #633 for 1.2.0 which Populus created for Policy improvements
• Modes in MDS scheduled for Aug 19

WGSC Meeting Organizers

• Host: Steve Brining
• Facilitator: Michael Schnuerle
• Outreach: Michael Schnuerle
• Note taker: Matt Davis

Action Items

• Neil to refine #658 with necessary clarifications based on notes and feedback
• Community to review "mode" discussion in #652
• OMF to broadcast working group merger

Notes

• Board approved the merger of the City and Provider Working Groups into a single MDS Working Group.

  • Consolidating mailing lists, wiki pages
  • Making a new charter

• Neil presenting about "Tiered Dwell Time with Rates" pull request adding policy examples of parking fees that vary over the duration of the parking event

  • https://github.com/openmobilityfoundation/mobility-data-specification/pull/658
  • In response to this question posted as an issue: https://github.com/openmobilityfoundation/mobility-data-specification/issues/631
  • Matt Davis asked a clarifying question about rate amount: rate amount is always per time unit, so to represent a $2 fee per 30 minutes you'd divide 200 cents / 30 minutes = ~7 cents per minute
  • Emmett asked about whether rates apply as soon as they match a time unit (e.g. at the start of an hour), or after the completion of the time unit. Policy lets you specify either option via different rate_recurrence options.
  • Sebastien Berthaud asked whether the examples in the PR are based on real use cases. Answer is yes, Jean's original post in #631 was motivated by real world use cases. One example is this from Omaha, NE (page 27): https://cityclerk.cityofomaha.org/images/agenda/ID_20_07_14/RES-2020-0583.pdf
  • Neil continues to discussion of Matt's suggestions in #666 and #677
  • #666 suggests adding a flag of whether a rate applies when an event matches a rule or when it does not
    • Implementing #666 doesn't block #658, but we do need to clarify whether rates apply to rules when events match or when they do not
  • Matt raises the question of how one knows whether a rule applies to individual units or an entire group of things (whether that's vehicles or units of time)
    • This will probably require additional clarification
  • Regarding whether rule minimum and maximum are inclusive (#677), Neil suggests that that may need to be configurable to support all rule types

OMF Announcements

• Angela noted this new OMF blog post on MDS: https://www.openmobilityfoundation.org/whats-next-for-mds-previewing-upcoming-versions/

• Michael Schnuerle announces that in the next meeting (2021-08-19) the group will be discussing adding "mode" concepts to MDS

  • Attendees to review and discuss on https://github.com/openmobilityfoundation/mobility-data-specification/discussions/652

New Attendees

N/A