Summary:
Planned topics
- Work updates (5 mins)
- Grooming (20 mins)
- Design discussion (20 mins)
- Open Discussion (10 mins)
...
(7:30AM Los Angeles, 10:30AM Toronto/New York, 3:30PM London, 17:30H Moscow)
Remember the Hyperledger Code of Conduct
Anti-Trust Policy:
Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.
Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.
...
Announcements
- None
Release status
Work updates (from the previous week)
- Add thread decorator in exchange request #628- (Talwinder Kaur )
- Sign the response using recipient keys #728 - (Talwinder Kaur)
- Add did-communication service convertions conventions to did document #818 (Sandra Vrtikapa)
- Integrate did-communication service conventions #822(Sandra Vrtikapa)
- Implement service behavior according to Client dependency (work in progress) #802 - (Андрій Солук )
- Added dependency interface to Client #724 (on review) - (Андрій Солук )
- Consolidate creator, storage and resolver DID under VDRI #777 - Firas Qutishat
- v0.1.0 release documentation - Rolson Quadras
- DIDComm WebSocket support in-progress - Rolson Quadras
- Error handling for controller REST API, and bug fixes #756, #803 - (Sudesh Shetty )
- Adding REST Endpoint for creating public DIDs (in-progress) - (Sudesh Shetty )
- Adding bddtests for DID Exchange with Public DIDs (in-progress) (Sudesh Shetty )
- ES256K (secp256k1) signature #381 - made PR to go-jose, not accepted, need to find another approach in aries (Dmitriy Kinoshenko)
- Refactor creation of VC which extends the base data model #263 (Dmitriy Kinoshenko)
- Worked on design for Issue Credential protocol (derektrider, Talwinder Kaur, Sandra Vrtikapa)
- Refactored keys structures and introduced metadatastore in kms #596 (Baha A Shaaban )
Grooming updates (from the previous week)
...
- Add requesting state to the introduce service and logic according to that state - (Андрій Солук)
- Support for IndexedDB - Firas Qutishat
- Create agents in wasm - Firas Qutishat
- Support for Javascript WS - Firas Qutishat
- DIDComm WebSocket support - Rolson Quadras
- DIDComm Router Design - Rolson Quadras
- Demo of VC encoding - Dmitriy Kinoshenko
- ES256K (secp256k1) signature for VC - Dmitriy Kinoshenko
- Refactor VC signing - Dmitriy Kinoshenko
- Public DIDs in DID Exchange controller - Sudesh Shetty
- Implicit Invitation - Sandra Vrtikapa
- Finding answers to Issue credential design questions regarding prepare result for request and if schema ID is linked to Verifiable Credential ID Talwinder Kaur
Once Key restrucurting done (and fully merged) - will work on remove KMS out of Packer #635 - Baha A Shaaban
Design discussion
- Discuss design for Issue Credential protocol (derektrider, Talwinder Kaur, Sandra Vrtikapa)
Milestone progress
Other business
- TBD
Future topics
- TBD
Action items
- TBDCriteria language for issue-credential
requestmessage (derektrider)