• ACTION: Chairs will work with Carly and Judith Fleenor to create the Learning Pathway home page. Learning Pathway Drafts

• Walk through the Project Overview
• Discuss work started partnering with the UFWG
• Establish Task Force Scheule and off-line processes
• Goals and objectives for next meeting

Links to documents:  https://docs.google.com/document/d/1uLs-m1Oor7g8GYNNnWtoZ2b9JOrK-xvW2ql__zuSbQg/edit#

Kyle's presentation referred to this wiki: https://github.com/bcgov/bc-vcpedia/wiki

First Scott explained that the next steps to build on the ToIP governance metamodel is to begin developing layer-specific templates.

• The natural place for this to start is with ToIP Layer 1 public utilities. Utility Foundry WG co-chairs Alex Tweeddale and Lynn Gray Bendixsen are here to talk to that today.
• Kyle Robinson will talk about the needs at Layer 3.

Second, Kyle gave a presentation about the governance framework work they are doing in British Columbia.

• He began by showing a view of the 4-layer ToIP stack that fills in all of the requirements for a full operational instance of the stack (see screenshot #1 below).
  • The left side shows the technology stack implementation that BC Gov is using.
  • The right side shows the different governance frameworks involved.
• He then showed a diagram from the ToIP interactive model that fills in the different parties involved in the digital trust ecosystems being developed in British Columbia (see screenshot #2 below).
  • Kyle stressed that an "ecosystem" can be very simple.
  • Also, two ecosystems can intersect with each other and produce synergies without any formal recognition of each other.
  • Nicky Hickman: I love the idea of fuzzy boundaries - I guess this is where the semantics comes in - the same credential might mean something in different ecosystems. Contextual and dynamic policy & governance
• Stephen Curran asked a question about separation and avoiding dependencies. He asked for examples of Layer 3 specific credential governance frameworks (CFGs).
  
  • Drummond said that most CGFs that have been developed in the wild so far have been "packaged" inside of Layer 4 ecosystem governance frameworks (EGFs).
  • A specific example is the CGFs that are part of the GLEIF vLEI EGF. See the documents at the bottom of the page: https://www.gleif.org/en/lei-solutions/gleifs-digital-strategy-for-the-lei/introducing-the-verifiable-lei-vlei. The links for the four CGFs included are:

    • Qualified vLEI Issuer vLEI Credential Governance Framework
      A document that details the requirements to enable this vLEI Credential to be issued by GLEIF to Qualified vLEI Issuers, which allows the Qualified vLEI Issuers to issue, verify and revoke Legal Entity vLEI Credentials, Legal Entity Official Organizational Role vLEI Credentials and Legal Entity Engagement Context Role vLEI Credentials.

    • Legal Entity vLEI Credential Governance Framework
      A document that details the requirements for a vLEI Credential, the entity level vLEI Credential issued by a Qualified vLEI Issuer to a Legal Entity.

    • Legal Entity Official Organizational Role vLEI Credential Governance Framework
      A document that details the requirements for vLEI Role Credentials issued to official representatives of a Legal Entity. These vLEI Credentials are issued by Qualified vLEI Issuers who are responsible for the validation of persons in official roles against one or more public sources.

    • Legal Entity Engagement Context Role vLEI Credential Governance Framework
      A document that details the requirements for vLEI Role Credentials issued to representatives of a Legal Entity in other than official roles but in functional or other context of engagement. These vLEI Role Credentials can be issued and revoked by a Legal Entity itself, or a Qualified vLEI Issuer can provide these value-added services to a Legal Entity.

• Kyle then showed examples from the BC Gov "verifiable credentials wiki" at https://github.com/bcgov/bc-vcpedia/wiki of how educational credentials work in BC Gov governance frameworks that are in development.

Finally, Scott Perry said that he is going to create 8 placeholder documents:

• 4 layer-specific templates
• 4 Companion Guides

He stressed that they will be "messy" for quite a while, however that's where we will start to aggregate all the pieces that will eventually go into the final deliverables.