Credential status purpose (Conformity Credential)

[PatStLouis]

Impacted sections

No need to alter any of the specification for now as it already deals with status

• https://uncefact.github.io/spec-untp/docs/specification/VerifiableCredentials#vcdm-profile

Issue Description

When implementing BitstringStatusList, we uncovered a use case where we have an issued conformity credential which needs to be updated, meaning a new credential would be issued. In this update, we don't want to revoke the previous credential as this is not the purpose, however we want to signal consumers (holders/verifiers) of that credential that an updated version is available to update in their system, if they so chose. Both credentials are valid and can be used for business processing.

The current status purposes involved in BitstringStatusList are revocation, suspension and message. We do not feel like message is a good approach for this as it involves other normative statements for use. Our use case is very specific and we believe it warrants a status purpose for its end. Therefore, I'm proposing a supersession status purpose, which intent is to signal whether the credential is the latest version or has been superseded, at which point the consumer can request the latest version.

If you feel this is a useful feature, please voice your opinion on the BitstringStatusList specification: