- Release updates
- Next steps in creating shared Aries libraries
- Naming of the Data Registry Interface → Verifiable Data Registry Interface
- Repository organization
- Work plans
Note: This call is Recorded. Recordings posted at the bottom of the page.
(7AM Los Angeles, 10AM New York, 3PM London, 17H Moscow)
Remember the Hyperledger Code of Conduct
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.
- Name (Employer) <email>
- Stephen Curran (Cloud Compass/BC Gov) firstname.lastname@example.org
- John Callahan (Veridium) <email@example.com>
- Nemanja Patrnogic (Evernym) <firstname.lastname@example.org>
- Daniel Hardman (Evernym) <email@example.com>
- Sergey Minaev (Evernym) <firstname.lastname@example.org>
- Richard Esplin (Evernym) <email@example.com>
- Carl DiClementi (Factom Inc) firstname.lastname@example.org
- Troy Ronda (SecureKey) email@example.com
- Steve McCown (Anonyome Labs) <firstname.lastname@example.org>
- Brent Zundel (Evernym) <email@example.com>
Welcome / Introductions
Related Calls and Announcements
- Previous Aries Working Group calls
- Identity Implementors Working Group call
- Main place to get project updates, release status, and announcements.
- Aries-CloudAgent-Python (bc.gov) - Release 0.3.3 has been tagged and is on PyPi
- Aries-Framework-Go (Troy)
- Weekly planning notes (2019-10-22)
- DID Exchange invitations can now include ledger DIDs (in addition to the underlying peer DID support).
- Aries-SDK-Ruby (Jack)
- Aries-Framework-DotNet (Tomislav)
- Aries-StaticAgent-Python - Release 0.4.0
- Aries-SDK-Python - Wrapper from JeromK and SBCA?
- DIF people interested in implementing a Java Script library that might share some of the functionality of the Aries SDK. We need to keep that in mind.
- Rich Schemas and W3C Verifiable Credentials (Ken)
- SDK 2.0 architecture / Indy-Aries split (Sergey)
- 1406 ticket and PR
- Architecture of Aries Verifiable Credentials Proof Formats (Mike Lodder)
- Static Peer DIDs in aries-dri-peer (Richard and Sergey)
- Daniel Python impl that needs to be implemented in Rust
- Rich Schema RFC headed to an APPROVED status, Troy had some comments on how the Link Secrets tie to W3C spec.
- Verifiable Data Registry instead of just Data Registry (vdri instead of dri) for naming of the Aries repos – Stephen Curran
- Removing of the DRI Peer and AMS SQLite? Ignore them for now, maybe add a README and say 'Do Not Use This Right Now' and modify the pull/push privileges for the repos.
- Using SQL In memory mode for the in memory wallet?
- Cam's proposal for an Aries Wallet (Cam)
- Settled differences, and is no longer relevant. We will start from the indy-wallet, waiting for the pull request
- Next step on Aries Core Libraries
- Resolver / Data Registry Interface
- Peer DIDs
- Wallet / Agent Managed Storage / ?
- Verifiable Credentials Proof Formats
- Resolver / Data Registry Interface
- Next call
- Using hardware enclaves (Daniel)
- Hubs vs Agents
- Payments in Aries
- wallet query language
- IOT best practices (Robert Mitwicki, Adam Burdett , Lohan Spies )
- DID Resolution W3C and Sam's concerns: https://github.com/hyperledger/aries-rfcs/issues/130
- Richard: Create repos specified in ARIES-3