/
2020-01-14 Framework Go Weekly Planning

2020-01-14 Framework Go Weekly Planning

Jan 14, 2020

Summary:

Planned topics

  • Work updates (5 mins)

  • Grooming (20 mins)

  • Design discussion (20 mins)

  • Open Discussion (10 mins)

Date

Jan 14, 2020 (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.

Attendees

  • @Dmitriy Kinoshenko (Euristiq) <dmytro.kinoshenko@euristiq.com>

  • @Андрій Солук (Euristiq) <andrii.soluk@euristiq.com>

  • @Firas Qutishat (Securekey) <firas.qutishat@scurekey.com>

  • @Rolson Quadras (SecureKey) <rolson.quadras@securekey.com>

  • @Filip Burlacu (SecureKey) <filip.burlacu@securekey.com>

  • @Baha A Shaaban (SecureKey) <baha.shaaban@securekey.com>

  • @Troy Ronda (SecureKey) <troy.ronda@securekey.com>

  • @George Aristy (Securekey) <george.aristy@securekey.com>

  • @derektrider (SecureKey) <derek.trider@securekey.com>

Welcome / Introductions

Announcements

  • None

Release status

  • None

Work updates (from the previous week)

  • Verifiable Credential: Support JSON-LD for Verifiable Credentials #952 @Dmitriy Kinoshenko

  • Verifiable Credential: Support JWT with ES256K (secp256k1) signature #381 - PR is made based on go-jose PR @Dmitriy Kinoshenko  

  • Verifiable Credential (WIP): Linked Data proof of Verifiable Credential #174 @Dmitriy Kinoshenko

  • Verifiable Credential: minor improvements #1041, #1043, #1056 @Dmitriy Kinoshenko

  • Define the Client interface for messenger (on review) #1039 @Андрій Солук

  • Replace DIDCommMsg type with map[string]interface{} (in progress)  #1039 @Андрій Солук

  • Create vc store #1049@Firas Qutishat

  • Add route client  #1031@Firas Qutishat

  • Generic message handler - Registration, Handling  (#970, #1032)- @Sudesh Shetty

  • Connection store refactoring - #1034 - @Sudesh Shetty

  • Generic message handler outbound handler (IN PROGRESS) #1059- @Sudesh Shetty

  • HTTP over DIDComm RFCs (in progress) #924 - @Filip Burlacu

  • Crypto interface service with default Tink implementation added #984 - @Baha A Shaaban

Grooming updates (from the previous week)



Design discussion



Milestone progress

  • TBD

Other business

  • TBD

Upcoming work

  • Javascript Worker Binding #1064

  • Register Key with Router during key generation in DIDExchange #988 - @Rolson Quadras

  • The messenger implementation @Андрій Солук

  • Generic message handler outbound handler, bddtests, REST binding - @Sudesh Shetty

  • HTTP over DIDComm - @Sudesh Shetty

  • Verifiable Credential: Linked Data proof of Verifiable Credential #174 @Dmitriy Kinoshenko

  • Verifiable Credential: Refactoring creation of serialized JWT from Verifiable Credential #339 @Dmitriy Kinoshenko

  • Continue work on Authcrypt/Anoncrypt (Routing Forward needs Anoncrypt) once KMS is ready (Finishing #977) @Baha A Shaaban

Future topics

  • TBD

Action items