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

Compare with Current View Page History

« Previous Version 3 Next »

Summary:

  • Aries RFC MkDocs
  • DIDComm v2 Credential protocol updates
  • Basis for common identifiers

Zoom: https://zoom.us/j/93803916577?pwd=UWdLSTJ2b0kvZTRyc1hZTUdQQ3ZFZz09

Recording:

Date

(7AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)



Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Attendees

Welcome / Introductions

Announcements

  • IIW - April 16-18
  • Lots of BC Ledgers, all but BSovrinTest. Genesis now all points to the same ledger.

Release Status and Work Updates

Discussion Topics

  • Aries RFC MkDocs Demo and Feedback - Stephen
  • VCX Update - Patrik Stas
  • DIDComm v2 conversion
    • (Notes from previous weeks)
      • Smaller changes may mean faster adoption
      • negotiation pulled out into a sibling protocol - (nobody using negotation? Subhasis referenced use.)
        • propose message moves to different family.
      • Document the short-circuted use of the protocol that starts at issuance directly, depending on needs of credential type.
      • we need to be careful not to match protocol to UX human steps on a 1 to 1 basis
      • abandoned state - if a user declines to present, what should happen between the holder and verifier?
        • problem report sent (or no message, see below) on decline - should be documented
      • explicit 'no' messages instead of a problem report when it's an explicit no, instead of an error.
      • document use of timeout for offers (didcomm v2 friendly, perhaps a field within the protocol.Credential Protocols for DIDComm v2
    • Any Volunteers?
  • Basis for common identifiers

Other Business

Future Topics

  • Niels Klomp offered a deeper dive into the openid4vc related flows
  • decorator for redirection after proofs. - existing?
  • in the Aug 9 call there was talk about EUDI compatibility. Maybe tracking the progress every now and then in these calls? Has there been any discussion about adding SD-JWT and OID4VC stuff to Aries Interop test suite?

Action items

Call Recording: 

  • No labels