Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attendees: (Please add your name here)

Agenda:

Johannes; UNICEF work on Youth Agency in Africa.  Convener of Yoma

Iain Barclay Cardiff University, UK;  PhD studying - Applications of tech, SSI for last ~2 years, for UN SDG related impact.  Some work in IoT, used Evernym stack for birth registration trial in Kenya, but paper written about application.  Recently been looking at blockchain and tokenised value flows, recently transport - token used for incentives for behaviour change.  Also work on making AI scrutable

Zeljko:  S/W engineer, Hyperledger & ToIP member, SSI enthusiast

Lohan Spies:  DIDx SA -focus on Cyber Security, recently focus on SSI applications, acting as CTO for Yoma project

Kalin Niclov; Previously in Linux as SW Engineer, Head of Digital Currency at SICPA, ToIP founding members, recently also joined DIF, 2 foundations in identity and currency, SICPA secures all but 4 major fiat currencies and for most PP and ID Cards.  

Thiru: CTO - blockchain enthusiast, recently implemented 3 blockchain projects, SSI recent interest starting with tokens.  Experienced implementer.

Aamir Abdullah 

Agenda:

  1. Introductions
  2. Introductions, Ambiguity and Pace
  3. Review Timeplan, deliverables & approach
  4. Purpose & Principles review
    1. Vision, Mission, Values (Johannes) 
      1. Still working through Values with youth participants
    2. Purpose & Principles discussion
      1. Q4 we will start on SE / Legal entity established.  Both discussions on GF and future Yoma SE need to work in parallel.  Arrange specific sessions w/ SE team, bridging mechanism or interim solution for GA may be required  
      2. All to take time to review this document, add comments and suggested text before our next meeting.
      3. Make use of the Use Case Documents 
  5. AOB
  • Start Glossary document to define our language
  • Specify Layer 1 requirements rather than selecting specific Layer 1 utilities. (current investigation e.g. based on token requirements)
  • Token:  separate component related to token itself but the governance specifies rules, policies under which it will operate.