Page History

...

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

• Rolson Quadras  (SecureKey) <rolson.quadras@securekey.com>
• Troy Ronda (SecureKey) <troy.ronda@securekey.com>Name (organization) <email>

Welcome / Introductions

Announcements

...

• DIDExchange Rest API - Integrate Action events with webhooks #579 - Rolson Quadras
• DIDExchange Rest API - Support for AcceptExchangeRequest API #549 - Rolson Quadras
• DIDExchange Rest API - Return ConnectionID #537 - Rolson Quadras
• Add/verify signature in exchange response #24 (Sandra Vrtikapa)
• Support for public did in request message(Sandra Vrtikapa)
• Remove transientStore from did exchange service #687  - Firas Qutishat
• DIDExchange - Transient v Permanent Data store #622 - Firas Qutishat
• Allow injectable transient storage #672 - Firas Qutishat
• Concurrency failure in bdd-test #649 - Firas Qutishat
• Fix service endpoint in create invitation response (Complete) #572 (Derek Trider)
• RestAPI - Get label value in CreateInvitation #552 (Derek Trider)
• Grooming stories for issue-credential epic #663 (Derek Trider)
• Compute the sendVerKey for sending response #353 (Talwinder Kaur)
• State Refactoring #677 closed #679 In progress.  (Talwinder Kaur)
  
• Set the Legacy pack/unpack implementation as the default #632 (Filip Burlacu)
• Refactor Keys structure in KMS #596 (Baha A Shaaban )
• Introduce protocol client implementation #657 (work in progress) (@Andrii Soluk)
• Verifiable Credential follow-up issues #586, #514 (Dmytro Kinoshenko)

...

• 0.1.1 Overview
• WebAssembly and C Bindings (Troy Ronda)
  • Folders:
    • cmd/aries-c (generates C callable shared objects and archives).
    • cmd/aries-wasm (generates Web Assembly).
    • pkg/binding/c/didexchange (C exports for DIDExchange Client).
    • pkg/binding/wasm/didexchange (WASM exports for DID Exchange Client).
    • (and so forth).
  • Testing strategy:
    • BDD (
      • WASM in browser
      )
      • . GoLang can drive remote browser: https://github.com/sclevine/agouti (as can similar JS BDD frameworks).
      BDD (C in linux). Load
      • WASM outside browser. Load in GoLang as a wrapper client OR rewrite BDD tests in external language (JS).
      BDD (WASM
      • C outside browser
      )
      • .
       Load
      • Load in GoLang as a wrapper client OR rewrite BDD tests in external language (JS).
    • Unit Test
      • C bindings - should be able to test exported functions directly as normal Go unit tests.
      • WASM bindings - the pre-transformed test functions should be testable as normal Go unit tests. TBD: the J

Milestone progress

• TBD

Other business

• https://didcom.org is now used as the prefix for message types (replaces did:sov:....)
• FYI: https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0289-toip-stack
• FYI: https://github.com/hyperledger/aries-framework-go/issues/694 (latest linter fixes)

Future topics

• TBD

Action items

•  TBDGroom discrepancies in rest api
•