2020-01-21 Framework Go Weekly Planning

2020-01-21 Framework Go Weekly Planning

Summary:

Planned topics

  • Work updates (5 mins)

  • Grooming (20 mins)

  • Design discussion (20 mins)

  • Open Discussion (10 mins)

Date

Jan 21, 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>

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

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

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

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

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

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

Welcome / Introductions

Announcements

  • None

Release status

  • None

Work updates (from the previous week)

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

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

  • Integrate Outbound SendToDID function with Route Service #1061 - @Rolson Quadras

  • Client - Register agent with Router #1072 and Add Key to the router #1073 - @Rolson Quadras

  • Message Service REST Binding - #1090, #973@Sudesh Shetty

  • Message Service SDK Binding BDD tests - #1079, #1059, #970@Sudesh Shetty

  • Message Service REST Binding BDD tests (IN PROGRESS) #974@Sudesh Shetty

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

  • Crypto interface service with default Tink implementation #984 (creating POC) - @Baha A Shaaban

  • Aries RFCs are under community review: RFC 0335RFC 0351 - @Filip Burlacu

Grooming updates (from the previous week)

 

Design discussion

 

Milestone progress

  • TBD

Other business

  • TBD

Upcoming work

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

  • Route Coordination - Integrate Service with Framework #948 - @Rolson Quadras

  • Support "jws" Linked Data proof #1094@Dmitriy Kinoshenko

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

  • HTTP over DIDComm - @Sudesh Shetty

Future topics

  • Generic WASM

  • Need a generic operation between REST API and WASM API plus build JS API for WASM

  • Add API in REST/JS (Basically APIs required to make WASM generic) - Access VC Store, VC functionality like encode/decode, DID functionality

  • From WASM, when should we use Promise Resolution vs  Async Event messages ?

    • Event message - multiple session

    • Promise Resolution - map request to response (local memory)

  • Generic abstract for of Credential Issuance and Presentation

    • local API mode (see 3rd bullet point)

    • A2A mode (protocol)

  • AuthZ mechanism 

Action items