Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 9 Current »

Summary

  • Closing Game
  • Transition to HTTPS, OOB
  • DIF Presentation Exchange Format overview

This call was recorded: <RECORDING TO BE ADDED>

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 (Org) <email>
  • Troy Ronda (SecureKey) <troy.ronda@securekey.com>
  • Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
  • Baha A Shaaban  (SecureKey) <baha.shaaban@securekey.com>
  • Jim Mason <jim.mason@skywebteam.com>
  • George Aristy (SecureKey) <george.aristy@securekey.com>
  • Daniel Hardman (Evernym) <daniel.hardman@evernym.com>
  • Ajay Jadhav (AyanWorks) <ajay@ayanworks.com>
  • John Callahan (Veridium) <jcallahan@veridiumid.com>

Welcome / Introductions

Announcements

  • Indy Interop-athon Conference - Details and registration
    • Efforts to organize led by Stephen Curran
    • User Story: As a prover, I want to be able to create a proof that includes claims from credentials rooted in different Indy networks that a verifier can verify so that I can easily interact with issuers using different Indy networks.
    • Organizational help welcome.


Related Meetings Review

  • Ursa - 
  • SSI in IoT WG
  • Indy Contributors - Every 2nd Tuesday 8am US/Pacific - Build and deploy help request
  • Identity WG / Identity WG Implementer calls (Wed / Thurs) - July 30, at 9 am US/Mountain (Wiki page:  2020-07-30 Identity WG Implementers Call)
  • DIF DIDComm WG - Monday's at Noon US/Pacific - Sam Curren (Mon) - DID Doc services, etc.

Upcoming Releases and Work Updates

Agenda

  • Closing Game
    • First Issue: Oldest issue 201 (about did:key) and newest 520 (RecipientKeys for encryption and signing)
    • Other issues - Presentation
  • Transition to HTTPS - Transition to Step 2 (PR to be added)
  • Transition to OOB (Presentation) - Merge PR?  Accept Plan?  Set goal date for completion of Step 1?
  • Presentation Exchange Format overview

Next Week

  • Requests?

Future Topics

  • Vince Albanese - future speaker: DirectTrust hack-a-thon Nov 2020 (DIDComm on XMPP)
  • Migrating to new JWE envelope format: https://github.com/hyperledger/aries-rfcs/issues/478
  • 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

  File Modified


  • No labels