Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Meeting Schedule

Attendees

  • Steve Magennis
  • Eric Drury
  • Carly 
  • P Subrahmanyam
  • Dave Hoffman
  • Drummond Reed
  • Francesco Vetrano
  • Atul Mahajan
  • Dominykas Valutis
  • Filipe Pinto
  • George Tang
  • Jacques Bikoundou
  • Jason Colbourne
  • Jason Sherman
  • Jorges Flores
  • Judith Fleenor
  • Karla McKenna
  • Khalid Maliki
  • Lyn Brooks
  • Neil Thomson
  • Philipp Etschel
  • Steven Milstein
  • Trinh
  • Vlad Zubenko

Presentation Files

  • Presentation slides  

Recording

Agenda Items & Meeting Notes 

  • Welcome & Introductions
  • EFWG Community Topics & Announcements
  • Presentation from Philipp Etschel from Bosch: "SSI from a developer's perspective"
  • Q&A / Discussion


  • Philipp Etschel presentation: SSI from a Developers Perspective
  • Philipp - solution developer at Bosch - mostly research team and IDUnion project affiliation (publicly funded by EU).
  • Acknowledgement of personal bias (as everyone has)
  • How can we give all the devices an identity? came into the concept of SSI, adding SSI into devices.
  • Master data - difficult to manage all the data
  • Agent (aries cloud agent) wallet
  • Profile of your organization
  • wallet with credentials
  • Can issue credentials and also verify them (issuer side and verifier side)
  • Schemas configured for your agent
  • Organizational profile - public information, helps to solve master data problem
  • SSI design is made for individuals (peer-to-peer) and this presents challenges for organizations/companies
    • E.g. want details available for companies in credential exchange (like bank account info etc.)
  • Consider if SSI is solution or is there other technologies that are better
  • Public profiles are also helpful because DIDs are not human readable and a profile helps with human trust.
  • What are some of the challenges in creating the project?
    • 2 challenges - 1 set, related to what you are doing - the whole SSI stack. It is developing. Business use cases do not always perfectly fit SSI (access management is an example that fits very well), but the need for a public profile takes effort to add to SSI.
    • 2nd set of problems - specific to BPA - how do we build systems that are scalable and how do we make it work for the enterprise. How does the software manage the wallets. Need lots of wallets and DIDs and this needs to be scalable and efficient. Missing lots of API features to create new wallets and DIDs for example.
      • May need to stop prototype and start from scratch.
    • Architectural side and Ecosystem side
  • Third issue - how to introduce and onboard people into SSI.
    • The world doesn't always match up with the nice picture/general model
    • Ecosystem is very fragmented (e.g. hundreds of DID methods).
    • There is no stack that covers all parts of the ecosystem
    • By design it is interoperable (DID methods, resolver, documents) but in function it is not because of the fragmentation.
    • Talking the same language but not interoperable
  • Current answer: look at your ecosystem and who you want to interact with and then pick your stack so you can work with them.
  • Drummond: trying to move towards interoperable stack a goal of ToIP. Rebooting web of trust - a subgroup creating a tool to analyze interoperability and help people make decisions.
  • Long run - should work itself out, but in the current time it is the challenge.
  • Few people fully understand at the lowest levels (container format, DIDcomm) and the cryptography (limited understanding here) - note this is perception
  • Long run what is needed - more robust stack and companies to put more resources into implementation.
  • Too much entanglement between modules and packages - too many dependencies
  • How do we get others on board
  • Challenges for scaling the solution - need more money and people, dedicate a team to get standardization right (like the EFWG and other WGs). Rebuild crypto and protocol level to make code more structured so it is easier to use. Lower level code restructure will let end results be more scalable. More modular level and not a service level. (but it doesn't seem like it will happen). Therefore take what works in the community - bigger companies don't contribute but wait and see and watch what start-ups are doing and use that work.
  • Get some of the more clear use cases work (e.g. access management) and then reinvest the money into further development.



Admin Reminder : remember to re-subscribe to new meeting calendar

If you want your name on the invite, reach out to Elisa Trevino (on slack), she will put your name in the calendar invite to make sure that the invite is sent out each time.

Coming up 

  • Resuming regular schedule Sept 15 
  • Next presenter, Sept 29: Trinsic Trust Registry solution



  • No labels