New user/issuer task - Provide Claim

[RieksJ]

Requirement: issuers MUST be able to (sovereignly, autonomously) determine what kinds of claims they will issue to what holders, under what conditions this is done, and specify constraints regarding the contents of the claims they issue to such holders.

Motivation: there are many real-world situations in which this requirement applies, and we need to be able to mimic this for claims as well. For example,

• a government will only issue citizen claims to citizens;
• a ticket that provides entry to an event is only issued after payment is received;
• the contents of an identity claim (e.g., provided to a citizen), will only contain data about that citizen, and/or family in the first degree

[jandrieu]

@RieksJ First, apologies for the delay responding.

It's not clear that provide claim is any different than issue claim. "It MUST be possible for any entity to issue a verifiable credential."

To the editors' reading, issuance is clearly an action that happens under the issuer's authority. The issuing entity gets to issue; there is nothing implying that they lose the ability to decide when to issue what to whom.

[KDean-Dolphin]

I think this is well outside the scope of the use case document. Every VC is issued according to a business process determined by the issuer; the result should be a VC that the holder has confidence meets their requirements.

Marking as pending close if no further feedback.