Attendees

  • Co-Leads: Marie Wallace (IBM) and Dakota Gruener (ID2020)
  • Participants: 
    • Charlie Walton (Mastercard)
    • Dan Johnson (Mastercard)
    • Rebecca Distler (ID2020)
    • Andy Smith (SITA)
    • Julian Ranger (Digi.me)
    • Dan Bachenheimer (Accenture)
    • Daryl Thomas (Share.ring)
    • Drummond Reed

Agenda Items

TimeItemWho
2 minWelcome & Antitrust Policy NoticeChairs
5 minIntroductionsChair & PM
15 minDiscussion of the objectives of the narrative groupChairs
25 min

Discussion of narrative flow

Chairs

5 minWrap up + next stepsChairs 


Meeting Notes

  1. Welcome and Linux Foundation antitrust policy - http://www.linuxfoundation.org/antitrust-policy
  2. Round of introductions - most of this group now knows each other well
  3. The group discussed the aims of the narrative group and the audience for the proposed document.
    1. Agreement that this must be consumable by a wide audience – policymakers, media, consumers – and cannot be too technical.
    2. Objectives:
        • Be educational and accessible
        • Provide framing/context for the materials that follow
        • Respond to the concerns we see raised in the media and public debate about health passes, vaccine passports
        • Walk people through many of the logical leaps that we’ve made about key design considerations and/or the best approach 
        • Give individuals/organizations trust that GHPC is asking all the key questions and setting the right bar for a “good” health pass.
  4. Marie Wallace] provided an overview of the narrative flow that she has proposed:  https://drive.google.com/file/d/16hwx-CDO07bThZpT5HuaNWZovb7A4UAS/view?usp=sharing
  5. The group workshopped the flow, adding sections and defining action items:
    1. Problem statement: people want to get back to life, get back to traveling.  Dan Johnson
    2. What does the world look like?   Andy Smith 
      • The international air travel ecosystem is messy. A huge # of potential verifiers. 
      • The world is even messier when you expand to other use cases. 
    3. Why is a health pass the right answer to this problem?  [respond to the concerns we’ve heard about inequities, scientific grounding]  Charles Walton
    4. What is a good health pass?  [respond to the concerns we’ve seen about privacy]  Marie Wallace
      • Privacy
      • Peer-to-peer
      • No callback to the issuer
    5. What are the key design considerations? [interoperability, messiness of the ecosystem] Julian Ranger
      • Pragmatic  
      • Decentralized data exchange 
      • Self-sovereign  note: there was an agreement to NOT use the term self-sovereign. 
      • Interoperable
      • Fit for purpose
    6. What are the technical challenges of achieving interoperability?  [point to the rest of the paper and make sure the logical leaps that the drafting groups have made are clear]  Rebecca Distler
    7. What are the recommendations and what is the path ahead for GHPC?  Dakota Gruener
      • Pragmatism: we’re defining what good is, but we’re not expecting perfect immediately. Certification.
    8. Dakota Gruener We are missing the place upfront for "what is the Good Health Pass Collaborative" to clarify why we are creating this paper in the first place. I am wondering if this should maybe come after Andy's "why is this problem so difficult?" piece, before we state our position that a "health pass" is the answer.


Resources