...
- Welcome and Linux Foundation antitrust policy (André)
- Introduction of new members
- Sandy K (Infoeaze, Vice-Chair of this WG)
- Update on currently identified Utility Projects (Reminder pls update list or submit issue!)
- Sankarshan
- Will update the group further in next meetings
- SSI4DE update
- Naming for the network in decision process (SSI4DE is the project name of project sponsored by BMWi)
- Governance of network itself has progressed, legal entity type has been decided
- Technical requirements of the test network have been specified
- Adrian Doerk will present the project in one of the upcoming WG sessions
- Richard Esplin offered to advise on the level of effort (staffing) required to support a new network
- Sovrin
- Drummond Reed updated the group on the Governance Framework WG of Sovrin
- Sovrin founding story could be fed into a user story to capture process with which Sovrin network was created
- Drummond pointed out that Dan Burnett, formerly with ConsenSys, has now become the Executive Director of the Enterprise Ethereum Alliance. Drummond suggests we reach out to Dan to discuss collaboration on ToIP-compatible DID methods for Ethereum. Drummond will take the action item to reach out to Dan.
- Bedrock: Call for interested companies that may be interested in joining. Send email request to Dan Gisolfi stating company name and contact email address.
- Sankarshan
- Call for user stories to be documented using the GitHub Template
- WG Research
- Horizontal Interop:
- Who feels strongly that interoperability between DID Utilities is required at Layer 1 (horizontal Interop)?
- Those that feel strong, please convene and report back in two weeks with a list of applicable use cases.
- Drummond reported that Credentials WG work under W3C will be rolled into DID method WG
- ToIP Technical Stack WG needs to define what is a ToIP compliant DID method
- If a Utility supports one (or more) ToIP compliant DID method, there is no need for interop between networks themselves
- Is standardisation of DID method a governance component for Layer 1? → That does not apply to Layer 1, no utility will talk to another utility directly.
- Is there a need for private utilities? → Potentially no good use case on Layer 1, on higher layers privacy and access control are strong drivers.
- Public utilities are commonly public read / controlled write. Needs to be explained in TSS.
- Private utilities, if the creators deem this mode necessary, can certainly be ToIP compliant.
- Question tbd: Who "certifies" ToIP compliance? → Will be covered by Governance WG. Trust Assurance TF will perform the related work.
- Compliance certification will be performed by governance authority (GA), i.e. the GA that will determine the compliance of a ToIP Layer One public utility can be at any higher layer (2, 3, or 4).
- ToIP Foundation will not issue certifications. Third parties potentially will be very interested in being eligible to attest ToIP compliance.
- DDNR
- There is work underway in DIF Identity & Discovery WG that is addressing Decentralised DID Namespace Registry (DDNR).
- Creation of a Utility Foundry Sandbox Utility
- The members of the UFWG need to gain experience before writing guidelines and best practices.
- Challenge: Create a Sample Utility comprised of 3-5 nodes for testing purposes using the the Blockchain Automation Framework (BAF)
- Leverage this research exercise as a way to create BAF artifacts for Hyperledger Indy
- Discussion showed that this is a time-consuming and labor-intense exercise that cannot easily be performed by the WG memebers.
- Presentation of BAF process and toolset appreciated by WG.
- Jessica Townsend of Accenture will organize a presentation for one of the next WG sessions.
- Horizontal Interop:
- Education & Awareness
- Bootstrapping Node Hosting - Learn BAF: Request Accenture Presentation Daniel Bachenheimercan organize
- DDNR Awareness: Setup a presentation for a future date: Contact Kapil Singh Dan Gisolfi can organize
- Topics for Future Meetings
...