2019-08-07-B Aries Working Group Call (US afternoon)
Summary:
- RFC Progression
- Demo: Predefined Identities in Protocol Test Suite
- DIDComm message delivery expectations
Note: This call is Recorded. Recordings posted at the bottom of the page.
Date
(12PM Los Angeles, 3PM New York, Tuesday at 5AM 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>
- Sam Curren (Sovrin Foundation) <sam@sovrin.org>
- George Aristy (SecureKey) <george.aristy@securekey.com>
- Matt Raffel (Kiva) <mattr@kiva.org>
- Daniel Bluhm (Sovrin Foundation) <daniel.bluhm@sovrin.org>
- Adam Burdett (Sovrin Foundation)<adam@sovrin.org>
- John Callahan (Veridium) <jcallahan@veridiumid.com>
- Sam Smith (ProSapien) sam@samuelsmith.org
- Brent Zundel (Evernym) brent.zundel@evernym.com
- Daniel Hardman (Evernym)
- Richard Esplin (Evernym)
Welcome / Introductions
Announcements
- BC Gov is interested in formally collaborating with groups with working Mobile Agents. Expected signing of MOU by August 6, 2019
- From the #aries channel: The folks from the BC gov VON ( https://vonx.io ) team, would like to share an opportunity with members of open communities to work with us to do some focused collaboration around mobile agent, Aries agents and aries-cloudagent-python interoperability. We have a pilot production service planned for a significant professional accreditation organization within our province coming up in the fall. This pilot has a requirement for mobile agents to be able to hold and offer verifiable credentials issued and verified by services operating instances of aries-cloudagent-python. Details are in this Open Collaboration MOU: https://drive.google.com/open?id=1GPZ4p4zM36AN3DcHJ13s_IisSrT4F3S0
- Other Announcements
Related Meetings Review
- Ursa -
- Indy Maintainers -
- Implementers Call - GitLab CI/CD Migration demo on 2019-08-01 Identity Implementers WG Call (Recording to be uploaded soon)
Upcoming Releases and Work Updates
- Aries-CloudAgent-Python ( bc.gov )
- Indy SDK
- Migration of components to Aries: Error rendering macro 'jira' : null
- Migration of components to Aries:
- Aries-SDK-Ruby
- PR waiting
- Lower bar to allow self merging if no other obvious maintainer? (Check with Nathan)
- Aries Protocol Test Suite
- Will show in demo later in meeting.
Agenda
- RFCs Under Status Change Review
- RFC 0036: Issue Credential Protocol and RFC0037: Present Proof Protocol
- Issue to explain our reasons for externalizing the payload formats: #168
- Semver: https://github.com/hyperledger/aries-rfcs/blob/master/concepts/0003-protocols/semver.md
- RFC 0095: BasicMessage - Status DEMONSTRATED to ACCEPTED
- RFC 0036: Issue Credential Protocol and RFC0037: Present Proof Protocol
- Demo: Using Predefined Identities in the Aries Protocol Test Suite (Daniel Bluhm)
- DIDComm Delivery Expectations (Sam)
- Next Week's Call
- Open Discussion
- Sam's concerns with diverging from W3C DID Resolution: https://github.com/hyperledger/aries-rfcs/issues/130
- Concerns that ephemeral DIDs are not supported in the W3C resolution spec
- Sam's concerns with diverging from W3C DID Resolution: https://github.com/hyperledger/aries-rfcs/issues/130
Next Week
- Aries Community DID (and method) - How to make a base DID for protocols. (Daniel Hardman)
- Sam's concerns with diverging from W3C DID Resolution: https://github.com/hyperledger/aries-rfcs/issues/130
- Concerns that ephemeral DIDs are not supported in the W3C resolution spec
Future Topics
- DIF Interop Project - Who?
Status of language specific SDKs - Who?- RFCs Moving forward - Make your case
IOT - Summary (Robert M.)- DKMS status
- Signature Envelope (Kyle)
- DID Resolution (Sam Smith)
Action items
Call Recording