WZDx Specification Update Subgroup Kickoff Meeting Notes, 2020 10 30 - usdot-jpo-ode/wzdx GitHub Wiki

Virtual Attendees

  • Austin Department of Transportation – Luke Urie
  • Bentley Systems – Lee Jackson
  • Booz Allen Hamilton – Eric Ricciardi
  • Booz Allen Hamilton – Mahsa Ettefagh
  • Bureau of Transportation Statistics (BTS – USDOT) – Derald Dudley
  • General Motor – David Craig
  • GEWI North America – Eli Sherer
  • HERE Technologies – Jingwei Xu
  • IBI Group – Jacob Brady
  • Iowa DOT – Daniel Sprengeler
  • Iowa DOT – Sinclair Stolle
  • Iowa State University – Skylar Knickerbocker
  • Kentucky Transportation Cabinet – Drew Clark
  • Kodiak Robotics – Daniel Goff
  • Los Angeles County Metropolitan Transportation Authority – Kali Fogel
  • Massachusetts DOT – Neil Boudreau
  • Missouri DOT – Dan Oesch
  • Metropolitan Transportation Commission (Bay Area) – Nisar Ahmed
  • Oregon DOT – Chad Mann
  • Panasonic – Lauren Cordova
  • San Francisco Municipal Transportation Agency – Muyi Zhou
  • Seattle DOT – Craig Moore
  • Southwest Research Institute (SwRI) – Lynne Randolph
  • Southwest Research Institute (SwRI) – Sabrina Mosher
  • Texas Department of Transportation – Jianming Ma
  • TomTom – Rob Hoyler
  • Trihydro – Shane Zumpf
  • Uber ATG – Marysa Myers
  • University of Wisconsin – Steven Parker
  • University of Wisconsin – Yang Chang
  • Utah DOT - Chuck Felice
  • Ver-Mac – Pier Castonguay
  • Volpe – Mark Mockett
  • Volpe – Nate Deshmukh-Towery
  • Volpe – Wesley Alford
  • Washington State DOT – Steve Haapala
  • Washington State DOT – Tom Stidham
  • Woolpert – Michael Hanowsky
  • Qassim Abdullah – Woolpert

Purpose and Intended Outcomes:

  • Formalize the launch of the WZDx Specification Update Subgroup and introduce Co-Chairs
  • Discuss the subgroup’s charter, activities, and meeting cadence
  • Clarify member roles and responsibilities

Agenda

  • Introduce Subgroup Co-Chairs and review roles, responsibilities, and objectives
  • Review issue/pull request creation and best practices on GitHub
  • Conduct backlog grooming and prioritization of potential changes
  • Conclude with action items and next steps

Discussion Summary

  • Subgroup Purpose and Scope

    • Derald Dudley introduced Subgroup Co-Chairs and the value proposition of the Subgroup/WZDx Specification.
    • David Craig reviewed the Subgroup’s role, responsibilities, and objectives.

  • Using GitHub

    • Jacob Brady detailed GitHub’s purpose, usage as it relates to developing the WZDx Specification, and best practices.
    • Craig Moore detailed the 13 current issues on the WZDx Specification’s GitHub repository kicking off this development cycle.
    • Skylar Knickerbocker detailed the prioritization criteria to consider when evaluating issues.

  • Discussion Around Current Issues on GitHub Heading into this Development Cycle

    • Craig Moore talked through the topics (issues) that have been under discussion since beginning development of version 3.0.
      • Craig Moore requested subgroup member feedback on the ‘Recurring Events’ issue – a perennial challenge to address within the specification that the group will attempt to reconcile this development cycle.
      • Craig opened up the discussion to the room for comments:
        • A subgroup member voiced how their organization would like to see the group tackle ‘recurring events’, having some sort of JSON calendar.
        • How those updates are communicated, especially when you address just one part of an event, are things to consider.
        • Another subgroup member – “The focus so far has been on, and rightly so, work zone. There was some interest in making the spec. more inclusive of events like accidents on roadways. Would that be considered?
          • Jacob – event type was added in version 3.0 to address this in the future
            • The subgroup member expressed they’d review the specification again and propose changes that might help making the event type more inclusive.
            • For recurring events, the Open511 specification has information to be considered.
          • Recurring events is issue #6 on GitHub, as a reminder.

  • Next Steps and Action Items

    • David Craig detailed next steps for the subgroup, importantly, for subgroup members to go and comment on the presented issue on the GitHub repository