-
Notifications
You must be signed in to change notification settings - Fork 36
Description
Notification Request section has two non-normative examples of a Notification Request.
The second example is inconsistent. The description of the example says:
Below is a non-normative example of a Notification Request when a Credential was deleted by the End-User:
But the example has the following event and event_description parameter values:
"event": "credential_failure",
"event_description": "Could not store the Credential. Out of storage."
The description speaks of a credential_deleted case, but the example is for a credential_failure case where storing the credential fails due to lack of storage space . These are not the same case.
I created a pull request where I propose a fix to this inconsistency by adding a proper credential_deleted example and adding a new description to the credential_failureexample. I also propose changing “was deleted by the End-User” with “was rejected by the End-User”, because the verb “deleted” can be understood to mean a deletion that the user does much later after accepting the issuance of the credential (which might not be supported, see #673), while “rejected” is much more tied to the issuance of the credential.