Summary:
Planned Topics:
Note: This call is being 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
- Name (Organization) <email>
Welcome / Introductions
Announcements
- New Indy/Aries/Ursa edX course, now online - enroll now!
- Updated Hyperledger Calendar: Calendar of Public Meetings
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:
- Read more: https://odca.online and https://tool.odca.online
- Fully functional parser: https://github.com/THCLab/odca-ruby
- DID UX Call - Slack/Mailing list - details in the shared document as well minutes and additional information, currently focus on Purpose Based Services
- SSI in IoT WG
- Indy Contributors - Richard Esplin (Mon) -
- Identity WG / Identity WG Implementer calls (Wed / Thurs)
Upcoming Releases and Work Updates
- Aries Protocol Test Suite
- Aries Shared:
- Aries KMS
- Verifiable Data Registry Interface (VDRI) library
- Other Core Libraries (pack / unpack)
- Aries-CloudAgent-Python (bc.gov) - Latest is Release 0.4.0 on PyPi - some internal breaking changes regarding plugins
- Aries-Framework-Go (Troy) #aries-go
- 2019-12-17 Framework Go Weekly Planning
- RFC implementation status and Wishlist
- Continuing efforts on routing & relays, crypto/kms, WebAssembly, generic JSON messages, JWE envelopes, verifiable credential Go package.
- WASM is working for DID Exchange from a browser (running the WASM) to a routing agent. Next we want to show DID Exchange between browsers.
- Aries-SDK-Ruby (Jack)
- Aries-Framework-DotNet (Tomislav)
- Aries-StaticAgent-Python - Now up to 0.6.1; more details
- Aries-Toolbox
- Aries-SDK-Python - Wrapper from JeromK and SBCA?
- Aries-SDK-Java
- Aries-Framework-JavaScript / Aries-SDK-JavaScript
- As agreed in the connect-a-thon, planning efforts on merging the aries-sdk-javascript codebase into a single framework repo - aries-framework-javascript
- Starting with the efforts on the React-Native Mobile Agent.
- Rich Schemas and W3C Verifiable Credentials (Brent & Ken)
- HIPEs/RFCs
- Next HIPEs/RFCs for
- encoding
- mapping
- credential definition
- Node implementation of
- context (merged)
- schema PR in progress https://github.com/hyperledger/indy-node/pull/1513
- Migration from LibIndy
- LibVCX 0.5.0 with Aries protocol support released today.
- Ursa 0.3.0 release in November
- Updated BLS signature (multi-signatures, small-BLS)
- Compilation optimization for specific hardware
- Rest of predicates for Anoncreds 2.0 and delegatable credentials
- ZMix 0.1.0 expected in January
- Ursa and ZMix will be separate releases. ZMix is the proving code, and Ursa is everything else.
Agenda
- Issue Game: Can we close this? (15 min -) - issues (as time permits):
- HTTP over DIDComm
- Concern with including Trust Ping and Feature Discovery in RFC 302 Richard Esplin
- Non-interactive protocols require more thought.
- These are important dev tools which we need in our ecosystem.
- But we need to be careful with the UX. Responding to every ping or feature discovery request could compromise the privacy of end users.
- In their current form, they should not be part of the interop profile.
- I should be able to respond to these from the mediator (my cloud agent should be my butler and I should be able to configure it to screen my calls)
- Open Discussion / Next Week Topics
Next Week
Future Topics
- RFC 351 (Generic JSON communication protocol). Use cases for RFC 335 (HTTP over DIDComm).
- DIF Interop Project - Project is proceeding, connect the communities at IIW
- DKMS status
- Independent agent upgrades
- Signature Envelope (Kyle)
- Credential Fraud: Example how in ACA-Py to verify same link secret across multiple credentials in presentation
- Schema interop - how to reused 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
- Update message type and protocol identifier to https. (and protocol documentation hosting.)
Action items
Call Recording