You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Summary

  • Signed Attachments
  • Credential gallery images - SVG
  • DIDComm v2 for binary protocols (gRPC).
  • TBD

This call was recorded:

Date:  (12PM Los Angeles, 3PM New York, Tuesday at 7AM Sydney)

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

  • Sam Curren (Indicio) <sam@indicio.tech>

Welcome / Introductions

Announcements

Related Meetings Review

Upcoming Releases and Work Updates

  • Aries Protocol Test Suite
    • Instructions, docker added - Try It!
    • Issue, credential, and proof tests are merged.
    • esatus backchannel
    • OOB protocol testing added (phase 1)
    • Regular friday meetings, contact Keith Smith for details
  • Aries Agent Test Harness - https://github.com/hyperledger/aries-agent-test-harness - Aries Interop Testing
    • CI Pipeline added – daily execution
    • Visualization of the results - behave output
  • Aries Shared:
  • Aries-CloudAgent-Python (bc.gov)
    • Release 0.5.6 is out.
    • Contributions in progress:
      • Multi-Tenant Agent - from Lukas Müller , SICPA and collaborators
      • Java Clients
      • Mediator configuration
  • Aries-Framework-Go (Troy) #aries-go
    • BBS+ Verifiable Credentials implemented using pure Go. Example.
      • Next tasks: interop testing against Mattr implementation and selective disclosure capabilities.
    • Working on adding remote encrypted storage capability - with a default implementation of DIF Secure Data Storage - Encrypted Data Vaults.
    • Created repo to handle pluggable go framework components such as Indy VDR: https://github.com/hyperledger/aries-framework-go-ext
      • MySQL and CouchDB components moved to ext repo.
  • Aries-SDK-Ruby (Jack)
  • Aries-Framework-DotNet (Tomislav)
  • Aries-Toolbox
  • Aries-SDK-Java
  • Aries-Framework-JavaScript - Framework JS Meetings
    • Current focus is on mediator use case (NodeJS)
    • Plan for 1.0 defined; refactoring to be done
  • Rich Schemas and W3C Verifiable Credentials (Brent & Ken)
    • Some work has been done to support the W3C Verifiable Credentials Data Model specification
    • Modifications to use BBS+ LD sigs as a first step - early exploration.
  • Aries-MobileAgent-Xamarin (Aries MAX) - https://github.com/hyperledger/aries-mobileagent-xamarin
    • Ideas:
      • Automatic offer acceptance/managing credentials
      • Machine readable governance
  • Ursa
    • Go wrapper proceeding nicely
    • Grand refactor in the next few months. Should not affect the external APIs. Will help future additions.

Agenda

  • Issue 560 - RFC 0453 - Support credential gallery images
    • SVG images (Kiva)
  • DIDComm v2 for binary protocols (gRPC) - Tomislav
  • AIP Next?
    • Out Of Band
  • Closing Game
    • PR 558 - Clarify Detached JWS rules
      • Base64URL encode #allthethings? or just signed attachments?
      • Signing the hash of a different format?


Next Week

Future Topics

  • Schema interop - how to reuse a schema across different networks Robert Mitwicki(RFC in progress)
  • Using WebSocket as a way to communicate back to the mobile/desktop wallet (Agent (services or user) as a proxy for communication between service and digital wallet) Robert Mitwicki 

Action items


  • No labels