Status size missing from `BitstringStatusList`

w3c / vc-bitstring-status-list

A privacy-preserving mechanism to publish status information for Verifiable Credentials.

https://w3c.github.io/vc-bitstring-status-list/

Other

22 stars 19 forks source link

Status size missing from `BitstringStatusList` #176

Open timothee-haudebourg opened 1 month ago

timothee-haudebourg commented 1 month ago

Hi, since the Draft 16 April 2024, the status_size property has been moved from BistringStatusList to BistringStatusListEntry. I understand it is sometimes necessary to know the status size from the entry without having to fetch the entire list, but removing it entirely from BitstringStatusList introduces some major issues in my opinion:

It is now impossible to decode a status list without possessing a status list entry.
The status size parameter must be passed around in many places of the implementation, making it error prone.
This differs from IETF Token Status Lists, making it hard to implement a common API.

msporny commented 1 month ago

There is a related comment here for why the spec is in the state that it is in right now: https://github.com/w3c/vc-bitstring-status-list/issues/175#issuecomment-2355676039

iherman commented 1 month ago

The issue was discussed in a meeting on 2024-09-27

no resolutions were taken

View the transcript

#### 4.5. The `BitstringStatusList.statusMessages` and `statusSize` properties are still being referenced (issue vc-bitstring-status-list#175) _See github issue [vc-bitstring-status-list#175](https://github.com/w3c/vc-bitstring-status-list/issues/175)._ **Manu Sporny:** There is maybe only one implementer for this feature at this point. _See github issue [vc-bitstring-status-list#176](https://github.com/w3c/vc-bitstring-status-list/issues/176)._ **Manu Sporny:** Dont think it is currently marked as at risk. … Actually it is already marked at risk. … So we are waiting for implementations. **Brent Zundel:** My understanding is mesur implements these features. **Manu Sporny:** Great. I think Spruce may also be using it, so leaving it in awaiting implementations.

timothee-haudebourg commented 2 weeks ago

I just want to point out that this change is affecting the vc-barcodes CCG where status list entries should be described in a compact way. Adding the statusMessages and statusSize properties would go against that. See https://github.com/w3c-ccg/vc-barcodes/issues/19