search

decentralized-identity / credential-manifest

Format that normalizes the definition of requirements for the issuance of a credential
https://identity.foundation/credential-manifest/
Apache License 2.0
29 stars 22 forks source link

Should the CM include a property indicating what issuance protocols the Issuer supports? #7

Closed csuwildcat closed 2 years ago

csuwildcat commented 4 years ago

Do we want to include a property the issuer can use to indicate what credential issuance protocols it supports?

brentzundel commented 4 years ago

I think this could be valuable, but I wonder how that would be done. For example, how does an issuer indicate that it supports "Aries did-comms, version 1.2, with anoncreds 2.0 signatures" Or did I just answer my own question? I also wonder if having the issuer DID is sufficient, at least at first. Or maybe the holder can contact the issuer (maybe using some standard cred-manifest-inquiry message format) and inquire directly?

llorllale commented 4 years ago

The credential manifest should at the very least indicate the formats the issuer supports (jwts, jsonld, etc).

brentzundel commented 2 years ago

this is already done

brentzundel commented 2 years ago

re-opening, because I was wrong

decentralgabe commented 2 years ago

Related to https://github.com/decentralized-identity/credential-manifest/issues/26#issuecomment-1177955271

decentralgabe commented 2 years ago

Discussed on the call today. We believe this is difficult to solve without protocols having a way to make decisions based on any properties we add to CM, specifying which protocols are supported.

Without concrete examples of how this decision making would be done per-protocol we are inclined to leave this up to implementers.

@brentzundel @llorllale looking to you for ideas.

brentzundel commented 2 years ago

I agree with @decentralgabe

brentzundel commented 2 years ago

Based on discussion in credential manifest call, we are closing this.