/
2019-11-06-B Aries Working Group Call (US afternoon)

2019-11-06-B Aries Working Group Call (US afternoon)

Nov 07, 2019

Summary:

  • Stable/Next work organization

  • RFC 0001

  • Unified DIDComm Deep Linking

  • Open Discussion / Next Week Topics

Note: This call is being recorded.

Date

Nov 6, 2019 (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

  •  

    • Name (Organization) <email>

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

    • Stephen Curran (Cloud Compass/BC Gov) <swcurran@cloudcompass.ca>

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

    • @Steve McCown (Anonyome Labs) <smccown@anonyome.com>

    • @Daniel Bluhm (Sovrin Foundation) <daniel.bluhm@sovrin.org>

    • @Camilo Parra (KIVA) <camilop@kiva.org>

    • @John Callahan (Veridium) <jcallahan@veridiumid.com>

    • @Zac Delventhal (Unveil.social) <zac.delventhal-3rdparty@unveil.social>

    • @Tobias Looker (Mattr) <tobias.looker@mattr.global>

    • @Brent Zundel (Evernym) <brent.zundel@evernym.com>

    • @John Jordan (Province of British Columbia) <john.jordan@gov.bc.ca>

    • @Oskar van Deventer (TNO) <oskar. vanDeventer@tno.nl>

    • @Alain Neyroud (IBM) <neyroud@us.ibm.com>

    • @Paul Knowles (Dativa) <paul.knowles@dativa.com>

    • @Will Abramson (truu) <will@truu.id>

Welcome / Introductions

Announcements

  • Aries Workshop/Connectathon December 3-5 in Provo, Utah - Dates Confirmed, Food Sponsors welcome!

  • Webinar on peer DIDs Nov 21 at 1 PM MST, ssimeetup.org

  • Proposal to renumber RFC 0289

Related Meetings Review

  • Ursa - Progress on packages and Plenum work.

  • Semantics - ODCA pilots underway - The agenda, video, notes, etc. from the HL Indy Semantics WG call: 

  • DID UX Call - Slack/Mailing list - details in the shared document as well minutes and additional information, currently bootstrapping discussion about UX for defined personas

  • Indy Contributors - @Richard Esplin (Mon) - Discussed future of Indy Ledger (View Change, Aardvark BFT, bug fixes, future of Plenum)

  • Identity WG / Identity WG Implementer calls (Wed / Thurs)

Upcoming Releases and Work Updates

  • Aries Protocol Test Suite

    • Works, and ready for test contributions

  • Aries Core Libraries (agent storage, ledger interface, comms)

    • Planning a move for the Indy Wallet crate into hyperledger/aries-kms

      • SQLite as the default KMS plugin.

      • aries-kms-sqlite is archived

    • Need to migrate Postgres capability to aries-kms-postgres

    • Future:

      • Verifiable Data Registry Interface library

      • Static Peer DIDs in aries-vdri as the default implementation

      • aries-vdri-peer is archived

  • Aries-CloudAgent-Python (bc.gov) - Release 0.3.5 Released - mainly cache handling updates. 0.4.0 in works - attachment/signature changes.

    • Continuing to learn about performance/storage impacts of using Aries protocols and non-secrets (metadata) interface.

    • Lessons learned:

      • Latest - adding instrumentation into the agent for metrics - where is time spent? Generating cool graphs

      • Found that latest bottleneck seems be processing/messaging, so focusing on that.

      • Discovered that the "tag-policy" is effectively useless - searching vs. accessing.  Removing, despite space savings, probably pulling from indy-sdk.

  • Aries-Framework-Go (Troy)

    • Weekly planning notes (2019-11-05)

    • Wrapping up 0.1.0 release and starting on 0.1.1.

    • https://didcomm.org is now used as the prefix for message types (replaces did:sov:....)

    • Successful experimentation on the possibility of exposing additional bindings (C, WASM).

      • (We currently have Go and REST.)

    • You can play with the framework by running BDD tests (make bdd-test) or with the OpenAPI (swagger) interface (See README).

  • Aries-SDK-Ruby (Jack)

  • Aries-Framework-DotNet (Tomislav) Transaction Authors/Endorser support for Indy.

  • Aries-SDK-Python - PR from JeromeK - weigh-in from those interested in Python wrapper would be appreciated.

  • Aries-SDK-Java - Usually Wed Evenings

    • Javier => asking help to move forward. Any agenda on what is being developed on other SDKs?

  • Aries-SDK-JavaScript - Contributors are now meeting on every Fridays - 

    • Need to create a new repo - "aries-framework-javascript" and add following contributors to get started.

      • @Jakub Koci , @Matt Raffel , @Ajay Jadhav , @Keith Smith

    • Meeting details are here - Framework JS Meetings 

    • See current plan here - FAQs

  • Indy

  • Ursa

Agenda

Next Week

Future Topics

Action items

Call Recording