Joint 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. A count will be posted after the meeting.

18 Attendees

Main Topics

• 1.2.0 Release Review
  • The WGSC reviewed the MDS 1.2 release feature ideas at their Consensus Checkpoint, and used our rubric for evaluation - Michael and WGSC
  • Release feature discussion outcomes and next steps - Michael and WGSC

See our previous Midway Checkpoint meeting notes for details, links, and outcomes from that meeting.

WGSC Meeting Organizers

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

• Thanks to 14 Steering Committee members (across 2 WGs) who did the work to evaluate these features, including the 5 new members just elected.
• We are putting a vote before the OMF Board on Aug 11 to merge the 2 WGs into a new single MDS WG.
• Review of checkpoints per release, and rubric
• Showcase of all features planned to be included before the review

• William Henderson - May need a few weeks to get the details right, make sure to get it in front of more people.

• 1.2 is getting close, welcome feedback, especially technical.

• Summer holidays could be an issue.

• Maybe OMF could host a listening session

• OMF could do an earlier than usual blog post/newsletter to talk about forthcoming features and solicit feedback

• Could host during a WG meeting, and invite targeted groups to review just Requirements, maybe all new features

• Need more comments from technical people

• "Disallowed Fields"

  • This is still an open discussion item
  • May need a special meeting to address/discuss after a write up of the proposal and impact is made
  • Could be a WG topic
  • May be a breaking change if previously required fields are now not required at all in data feeds from Providers

• Keep accuracy as is for now
• New issue for splitting into horizontal and vertical accuracy at a later release and adding to agency
• Add description clarifying that accuracy is horizontal

• 618 distribution by percent
  • Spec can be modified to percent instead of count, but not clear then what it's a percentage of. Fleet count? How to specify?
  • What are the time elements it's measured by? A time of day (how to specify), hourly, continuous?
• 619 clarify min distribution
  • Is it percent of available? Does it include on trip?

• Other features presented to the WG were in alignment to what the WGSC decided and wrote up in the review page.

Action Items

• OMF/WGSC host preview of Requirements and solicit feedback early
• Discussion about Disallowed Fields
• Update to telemetry PR, then approve
• Move the 2 'maybe' policy changes (#618, #619) to next release
• Policy larger discussion around alignment with Metrics methodology and purpose/design goals of Policy rule sharing/enforcement.

New Attendees

None