Re: [w3ctag/design-reviews] Verifiable Credential Status List 2021 (Issue #874)

@rhiaro There are several kinds of statuses I've seen in the wild... Ones that go into a registry / list, which is expert curated... and ones which are open ended, and where you need to understand what the issuer wanted the status to mean, and each issuer can assign that value a different meaning... for example `0xdeadbeef` might mean "Organic Certification Passed" or "Formal Objection Present", depending on the issuer.

The other case is where a registry defines each status, and the RDF class ensured consistent meaning via term URLs:

- `0x00` - reserved
- `0x01` - "suspended" - https://w3c.github.io/vc-status-list-2021/#bitstringstatuslistentry
- `0x00` - "revoked" - https://w3c.github.io/vc-status-list-2021/#bitstringstatuslistentry
- ...

Or a status list might not support multiple status, in which case, each bit is bound to a single meaning, regardless of where that meaning is defined.... this last category has been most contentious, since people fear that we will see issuer's creating a lot of implementation burden, on verifiers, by using multiple lists, with "custom status" values.

AFAIK, the WG has not defined a way to support the "open world model for status'es", for either the single list case, or the multiple lists cases, but there is ongoing work to provide clarity on this topic.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/874#issuecomment-1714223148
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/874/1714223148@github.com>