2020-02-04 Framework Go Weekly Planning

2020-02-04 Framework Go Weekly Planning

Summary:

Planned topics

  • Work updates (5 mins)

  • Grooming (20 mins)

  • Design discussion (20 mins)

  • Open Discussion (10 mins)

Date

Feb 4, 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

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

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

  • @Sudesh Shetty (SecureKey) <sudesh.shetty@securekey.com>

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

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

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

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

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

  • @Sandra Vrtikapa (SecureKey)

Welcome / Introductions

Announcements

  • Aries Framework Go v0.1.1 Release 

Release status

  • None

Work updates (from the previous week)

  • Add Metadata field to the thread decorator (on review) #1164 @Андрій Солук

  • Messenger - simple implementation #1132 @Андрій Солук

  • Add docs for introduce protocol #1114 @Андрій Солук

  • DIDComm Router BDD tests #950@Rolson Quadras

  • Support for Multiple Inbound Transport #1124 - @Rolson Quadras

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

  • Support "jws" Linked Data proof #1093 (PR review) - @Dmitriy Kinoshenko

  • verificationMethod for proof verification #1156 (in progress) - @Dmitriy Kinoshenko

  • VC With DID Resolution #1155 (in progress) - @Dmitriy Kinoshenko

  • Basic messaging protocol #959@Sudesh Shetty

  • JS worker to use controller API  #1070 (IN PROGRESS) - @Sudesh Shetty

  • Add SecretLock API service #1144, #1145 and #1146 - @Baha A Shaaban

Grooming updates (from the previous week)

 

Design discussion

 

Milestone progress

  • TBD

Other business

  • TBD

Upcoming work

  • Introduce - the protocol should not depend on thread decorator #1157

  • DIDComm Router/Mediator - REST API Binding #989 - @Rolson Quadras

  • DIDComm Router/Mediator - BDD tests for REST binding #1169 -  @Rolson Quadras

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

  • VC With DID Resolution #1155 - implement for Linked Data Proofs - @Dmitriy Kinoshenko

  • JS worker to use controller API  #1070  - @Sudesh Shetty

  • Create a new Storage type with Delete() function #1147 @Baha A Shaaban

  • Add a new KMS API and mock #1148 @Baha A Shaaban

  • Add a default (local) KMS implementation with SecretLock as option #1149 @Baha A Shaaban

  • Hook the new KMS in framework and context #1150 @Baha A Shaaban

  • Update Crypto unit tests to load a KMS with the new key formats #1151 @Baha A Shaaban

Future topics

  • TBD

Action items

 

VC client API and REST/WASM bindings

VDRI client API and REST/WASM bindings
JS API service for WASM