Support BitstringStatusList (was: StatusList2021, was: RevocationStatus2020)

[mkhraisha]

RevocationStatus2020 is no longer supported, we should migrate to use StatusList2021

[msporny]

Agreed.

[peacekeeper]

RevocationStatus2020 is no longer supported

No longer supported by who or what?

we should migrate to use StatusList2021

+1 to using StatusList2021 instead of RevocationStatus2020, but the VC HTTP API is currently not really restricted to a single credential status mechanism anyway, so I'm not sure what exactly you are suggesting in this work here?

[msporny]

We discussed this on the 2022-04-19 telecon. @msporny proposed that the VC API shouldn't favor a status mechanism. @mkhraisha suggested that we shouldn't favor one over the other -- the tests should support both revocation 2020 and status list 2021. The VC API spec should be agnostic wrt. the specific status mechanism.

The group decided that the VC API spec should define endpoints to modify the status of a credential, but be agnostic wrt. the specific status mechanisms. It is expected that test suites will be created for specific status mechanisms.

[msporny]

Note that StatusList2021 has been renamed to BitstringStatusList: https://w3c.github.io/vc-bitstring-status-list/

[msporny]

The group discussed this on the 2023-12-05 telecon and suggested that we should add an example to the specification demonstrating how status information should be changed.