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

Version 1 Next »

Summary:

  • Credential protocol Reversions

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

Release Status and Work Updates

Discussion Topics

  • Credential Protocols for DIDComm v2
    • https://identity.foundation/waci-didcomm/
    • Wishlist / Goals?
      • Features that may not be necessary - patrik
      • reverting .1 and .2
      • abandoned state - if a user declines to present, what should happen between the holder and verifier?
        • problem report sent on decline - should be documented
      • offers that sit for a long time at the holder
        • documenting a timeout for the offer.
        • use of timing in thread decorator
      • Removal of any reference to payments.
      • preview model doesn't work for vc data model creds. could allow an unsigned version of the credential being issued.
      • nobody using negotation? Subhasis referenced use.
      • cred def reference - did:indy and language that makes clear DIDs can (should?) be used.
        • requirements for DID methods that resolve to cred related assets
      • return of supplements
      • make sibling protocols for each credential type instead of being universal?
      • Different protocols for different sections?
        • negotiation
        • offer/request
        • actual issuance
        • ui note
          • we need to be careful not to match protocol to UX on a 1 to 1 basis
    • DIDComm v2 conversion
      • Smaller changes may mean faster adoption
    • After DIDComm v2 conversion

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