The GSWG currently holds bi-weekly Zoom webmeetings for the NA/EU time zones alternating between plenary meetings reviewing overall Working Group and Task Force progress on deliverables and special topic meetings. In addition it supports a monthly ToIP WG update meeting for APAC timezones. See the specific scheduling details of each meeting in the sections below.

You can get a calendar invite to any meeting via the ToIP Calendar page, and

Thursday, 25 June 2020 — 11:00-12:00 PT / 18:00-19:00 UTC

Send an email to governance-stack-wg@lists.trustoverip.org to request a calendar invite ( you can subscribe to the mailing list at lists.trustoverip.org).

1. Welcome and Linux Foundation antitrust policy
2. Introduction of new members
3. Deciding on chairs, vice chairs, and terms
4. Presentation on machine-readable governance frameworks—Daniel Hardman
   1. https://github.com/hyperledger/aries-rfcs/blob/master/concepts/0430-machine-readable-governance-frameworks/README.md
5. Next steps on Governance Template Task Force
6. Topics for Future Meetings
   
   1. Scott Perry - Trust Assurance 101
   2. <your topic here>

GSWG Meeting Structure

NA/EU Plenary - Every fourth Thursday — 14:00-15:00 EDT

...

/ 18:00 - 19:00 UTC

Agenda and Notes

Meeting recording

1. Status since last meeting (Scott, Tom, Drummond) - 5 minutes
   1. 29 attendees
   2. New Introductions
      1. Scott Whitmire IEEE - Standard for medical Imaging
      2. Gena Morgan - GS1 - Standards in Supply Chain
      3. Will Groah IEEE working with other ToIP groups
      4. AJ Finema - Bangkok, Governance Blockchain Decentralized identity consultant
      5. Gene DiMira - Manulife - AML Compliance Officer
   3. New whitepapers, templates, thought leadership documents should be sent to Scott Perry scott@scottperrycpa.com
2. Templatizing a Utility Governance Framework based on Sovrin Governance Framework (Drummond - 15 min)
   1. Google Slides are here
   2. Sovrin Governance Framework - started in 2016, now at V2 including GDPR conformance in December 2019 - working group of over 50 members
   3. Modular Framework of documents including a Home Page, Master Document, Glossary, Legal Agreements, Controlled Documents and a Trust Assurance Framework
   4. Key best practices
      1. Modular design
      2. Must include legal agreements and legal teams
      3. One glossary for entire framework
      4. Roles and responsibilities
      5. Affiliated trust assurance framework
      6. Non-normative but accessible framework
   5. Tour of the Sovrin Governance Framework - available on web at sovrin.org
   6. Templatize the Sovrin work
      1. Tailored to Layer one but structure can be used as an overarching model for ToIP GSWG
3. Example templates from the Brighthive Repository (Tom - 10 minutes)
   1. BrightHive has focused on Data Trust (aligned to Layer 4)
   2. Governance established through a data trust agreement (DTA) - on web at  github.com/brighthive/data-trust-legal
   3. Roles and responsibilities - Better when there is a strong central authority
   4. Brighthive has examples in gitHub
   5. Framework adopted from the Intelligence Industry, Canada efforts
   6. Good examples from Goodwill Industries and the Commonwealth of Virginia
4. Open Discussion
   1. Don't Boil the Ocean - Tackle progressive steps 
   2. Next Steps - Establish your own task force
   3. Start producing Tools
      1. Standard Specification on Governance Framework Template Model 
      2. Not Layer Specific - At an Architecture Level
      3. email soliciting interest in framework architecture design
      4. email soliciting other areas that members want to tackle
5. Topics for Future Meetings - Contact Scott Perry, Drummond Reed or Tom Plagge
   1. Daniel Hardman - https://github.com/hyperledger/aries-rfcs/blob/master/concepts/0430-machine-readable-governance-frameworks/README.md
   2. Scott Perry - Trust Assurance 101

See the GSWG Meeting Page template for the standard plenary meeting structure.

NA/EU Special Topic - Every second Thursday — 14:00-15:00 EDT

...

/ 18:00 - 19:00 UTC

Agenda

...

See this Google Slides presentation for the full agenda. Summary:

...

1. Natarajan (Nat) Chandrasekhar – Cambridge, UK – individual contributor
2. Dan Bachenheimer – Washington, DC – Accenture Digital Identity group
3. Stu Vaeth – Boston, MA – Mastercard
4. Bryn Robinson-Morgan – UK – Mastercard
5. Arjun Govind – Philadelphia, PA (Bangalore for the moment) – Digital identity at R3
6. Catherine Nabbala – Bangkok – Finema
7. Dan Gisolfi – New York, NY – IBM
8. Elizabeth Cronan – Washington, DC – Geoguard
9. Eric Welton – Northern Thailand – Individual contributor
10. Gregor Jehle – Stuttgart, Germany – P3KI
11. Jim StClair – Mississippi – Dinocates
12. Jan Lindquist – Stockholm – Hyperledger
13. John Jordan – British Columbia – Province of British Columbia
14. Mark Lizar – Toronto, Canada / UK – Open Consent
15. Mark Scott – San Diego, CA – Individual contributor
16. Mary Lacity – Fayetteville, AK – Sam Walton College of Business
17. Matt Davies – Salt Lake City, UT – Finicity
18. Paul Knowles – Switzerland – Human Colossus Foundation
19. Robin Alexander – Vancouver, BC – Geoguard
20. Steve Magennis – Seattle, WA – Polywug
21. Steven Milstein – Montreal, CA – Collab Ventures
22. Sankarshan Mukhopadhyay – Bengaluru, India – Dhiway
23. Vinod Panicker – Kochi, India – Wipro
24. Vipin Bharathan – New York, NY – dlt.nyc
25. Wenjing Chu – Santa Clara, CA – Futureway Technologies
26. Will Groah
27. Xinxin Fan – San Francisco Bay Area, US – IoTeX
28. Chris Ingrao – Seattle, WA, US – LUMEDIC

...

1. British Columbia government challenges include digital identity of individuals, corporations, legal entities, etc. Many times, when an online service is offered, the identity field is simply treated as a freeform text field, creating serious issues with misidentification, fraud, and others. 
2. BC may lay out a set of policies at the Layer 4 level to make it clear who the recognized authorities are, in BC and elsewhere, for issuing identities (like drivers licenses). 
3. At Level 3, BC could also recognize registries for verified person credentials, permits, licenses, etc.
4.  BC might also recognize software solutions for citizens at Levels 2 and 1.

...

1. Survey of existing governance framework models
   1. E.g., FATF, Pan-Canadian Trust Framework
2. Classes of use cases and boundaries required for governance
   1. Levels of assurance that drive decisions along the stack. For example, government clearance may require high quantity and quality of sources, while employment confirmation may require less-strong assurance. Scott suggests:
      1. Untrusted class – no governance at all, status quo for the internet
      2. Internet Grade – a minimum standard of assurance with governance, a key missing piece
      3. Asset Grade
      4. Classified Grade 
   2. Need to understand use cases that government bodies might be asking of organizations such as ours. FATF example: is the digital ID system authorized by the government for use in customer due diligence (CDD)?
3. Architectural Model for ToIP governance frameworks
   1. Required, recommended, and optional components at each layer
   2. Templates at each layer
4. ToIP stack and verifiable credentials risk model
   1. See Confluence page that Scott has set up: Identity and Verifiable Credential Risks
5. Contributions to ToIP glossary

...

focused on in-depth discussion of a topic or issue affecting the GSWG community

• Emerging Trends Affecting GSWG
• Highlight of Emerging Player - Impact on GSWG Deliverables
• Future GSWG Topic or Deliverable
• GSWG Process or Tool

APAC Special Topic - To be scheduled as needed

Agenda focused on emerging topic or in-depth issue affecting the GSWG APAC community

• Emerging Trends Affecting GSWG APAC
• Highlight of APAC Emerging Player - Impact on GSWG Deliverables
• Recruiting / Aligning APAC into GSWG efforts

Index of Meeting Notes and Recordings

...

1. See organizational proposal from Dan Gisolfi

...

1. Lightweight collaboration mechanism. Can spin up at any time and last as long as necessary.
2. Minimum requirement: a wiki page.
3. Can also have mailing list, github, etc.

...

1. We elect our own. At least one, up to three (at least 2 recommended), can rotate.
2. Volunteers? (Conveners volunteer; no additional volunteers on the call, but welcome over mailing list)

...