Versions Compared

Old Version 2

changes.mady.by.user Sam Curren

Saved on

compared with

New Version Current

changes.mady.by.user Stephen Curran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary:

Excerpt
  • Credential protocol Reversions

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

Recording: :
Widget Connector
urlhttp://youtube.com/watch?v=n4KxrFJJQ4o

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

Release Status and Work Updates

Discussion Topics

  • Fabric Ecosystem Diagram / Document - David Boswell
    • Fabric Ecosystem ecosystem
    • We need one for Aries
      • Sam will make a wiki page.
  • Credential Protocols for DIDComm v2
    • https://identity.foundation/waci-didcomm/
    • Wishlist / Goals?
      • (all assigned)
    • Done / Almost Done
      • Features that may not be necessary - patrik
      • reverting .1 and .2
      • Removal of any reference to payments.
    • DIDComm v2 conversion
      • 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
      • 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.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.
    • After DIDComm v2 conversion
      • return of supplements
        • credential chains
        • OCA / ux
        • needs a re-think
          • hashlinks
          • signatures?
      • different protocols for different credential types? (needs discussion)
        • make sibling protocols for each credential type instead of being universal?
      • 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?
    • Deferred / Maybe NeverAfter DIDComm v2 conversion
      • 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

Other Business

Future Topics

...

  • 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?

...