Page History

...

NA/EU Meeting Thursday, 17 September 2020 — 11:00-12:00 PT / 18:00-19:00 UTC

Recording: 

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
   1. The objective of this WG meeting is to enable the participants to meet and discuss the roadmap of deliverables
2. Introduction of new members - 5 minutes (Please use the format: Name / Affiliation / Location / any other detail you would like to share)
   
3. Guides and Processes - introduction to the topic by Dan Gisolfi
   1. https://github.com/trustoverip/deliverables/issues/4 - call-to-action is to build on the guides already existing as exemplars and across the Foundation come up with templates relevant to the work underway
   2. You will need to join the ToIP organization on GitHub (however, that is not a barrier to the contributions); additionally you will likely need a Linux Foundation account (membership) as per Drummond
4. GSWG Leadership Updates
   1. See slides from the All Members meeting
      
5. Activities since our last NA/EU call
1. Recap of GSWG APAC Call  - sankarshan
   
   1. Notes can be found here (hat tip to Scott Perry for his scribe role)
   2. Summary
      1. Introduction to the Governance Architecture TF with some extensive conversation around how it all fits in
      2. Encouraging the group to think deeply over the Critical Success Factors - as how it can help shape future growth of the group
      3. A high level introduction to the Health ID plan proposed by the Union Government of India - there have been sporadic discussions on various channels about it. The group also encourages participating members to share any proposal/policy document so that there is an increase in level of awareness and a structured approach to unpacking the proposals along the mission, values and vision of the Foundation.
6. Presentation Topics - Key Deliverables from our Group
   1. GSWG Status Slides to ToIP All-Member Member Meeting - An in-depth discussion - All
      1. Dan Gisolfi - Some of the work going on in the industry across various groups (Sovrin, Bedrock, etc.) - How is this group going to leverage frameworks from these groups for the benefit of ToIP?
      2. Scott Perry - We are very much open and looking forward to these inputs. Taking it even further at a next level - we are also looking for more such inputs from across regions like APAC.
      3. Scott Whitmire - We need to look at what kind of standards are required - at each layer - so that someone who is willing to develop something, should be able to see what and how to utilise from these standards.
      4. Karl Kneis - One of the challenges with the stack and governance is it is too large to scope. We need to categorise the governance and how that operates at scale and at various layers
   2. Roadmap of GSWG Deliverables (Drummond)
      1. Drummond Reed - Purpose: is not to say “Hey we have got the roadmap here” This is rather a conversation starter. We are really just focusing on next 3,6,9,12 months of roadmap. Six deliverable types - Specifications, Templates, Definitions, Recommendations, Implementation Plan, White papers. Deliverables will be organised in accordance with the stack.
      2. Specifications - TOIP Governance Architecture TSS and ToIP M/C readable GF TSS.
         1. Dan Gisolfi - TSWG has plan to spread the specs across layers, is that also going to be the case in GSWG? Drummond Reed- All these specs will be full stack - not layer specific
      3. Templates - At least 4 core templates we see to be delivered, one each for the layers - ToIP Layer 1 Governance Framework Template, ToIP Layer 2 and so on.
         1. Dan Gisolfi - From priority stand point, this is good, because it helps to understand what is needed at respective layer to start with.
         2. Scott Perry - GSWG - Processes & Roles TF is focusing on defining processes and their alignment with evolving specifications and templates.

      4. Definitions - Definitions and Glossary are very much needed - these save hours if you have the definitions in place. We can't make definitions in absence of technology terminologies - so there will be a joint work with the TSWG as well.

         1. Dan Gisolfi - We need to settle on how do we bring the terminology. We need to kind of look at each term at a very granular level. Is the GSWG going to have glossary as a corpus of the group?
         2. Drummond Reed - We will be the consumer of lots of terms/definitions from other groups as well.
         3. Scott Perry - Now that we have the Concepts and Terminology group in place - they should be the owner of the terminologies and definitions while all the groups can provide inputs.
      5. Recommendations - Design principles for ToIP GF. 4 Policy Recommendations (1 per layer) | 4 Best Practices Recommendations (1 per layer)
         1. Dan Gisolfi - There has to be alignment while we recommend best practices. We should assume that C&T will be required to minimally produce 4 glossaries (1 per WG)
      6. White Papers - White paper - one per quarter starting Q4-2020.
         1. Scott Whitmire - What about a white paper that describes a prototype ecosystem from top to bottom presented in narrative story form?
         2. Drummond Reed - That sounds like a good deliverable for the Ecosystem Foundry WG that we and the TSWG could contribute to.
         3. Suggestion from Dan Gisolfi- We should leverage outlines from Sovrin and BBU and you have a starter.
   3. First Look - Class Definitions of Verifiable Credentials (Scott Perry)
      1. Scott Perry - There are lot of communities, groups that have done lot of vetting on standards to do with identity services.
      2. Drummond Reed - LoA could be defined for any type of verifiable credential if it’s needed—but it’s highly contextual
      3. Dan Gisolfi - We need to use Scott's example content to make a point. How do we classify this Trust Assurance content - Is it in a template? Recommendation? Other? 
In my opinion, it is a Recommendation.

      4. Kalyan Kulkarni - It certainly is more a recommendation in its current form - but has a great potential to be transformed into templates - one for each class.
      5. Scott Whitmire - Another recommendation would be which class is best for a given type of credential.
      6. Preview of Credentials Policy Template
         1. Scott Perry - It is going to provide lot of education and information which is needed at the current stage
         2. Dan Gisolfi - All good comments BUT we must strive for CONSUMABILITY of our workproducts. If ToIP is too complex it will be a hit against us. EFWG and UFWG will have more consumers - If there is lot of granularity in the work products, it becomes harder to consume.
7. Open Discussion -
   1. Purpose of Bi-Weekly Meetings and Topics for future meetings
   2. Critical Success Factors in the adoption of ToIP deliverables (the items listed below are intended to be a starter set) - 
      
      1. CSF 1: Agree on what is an ecosystem?
      2. CSF2: Define the criteria to prove possession of a private key used to sign VCs

      3. CSF 3: The set of due diligence required to sign a VC with a stated level of assurance

      4. CSF 4: Agree on the Stack diagram

      5. CSF 4:Define the role of a governance authority over an ecosystem
   3. Outreach and engagement from ToIP members

...