Outdated `TerseBitstringStatusListEntry` to `BitstringStatusListEntry` conversion

[timothee-haudebourg]

The new definition of BitstringStatusListEntry includes the statusSize and statusMessages, that cannot be derived from TerseBitstringStatusListEntry.

[msporny]

Yes, statusSize and statusMessages isn't supported in TerseBitstringStatusListEntry because it would bloat the size of the vc-barcode to the point where the VC wouldn't be very compact. We had to make some trade-offs with TerseBitstringStatusListEntry and this was one of them.

Does that create an issue for your use cases, @timothee-haudebourg ?

[timothee-haudebourg]

It does create an issue because in the newest version of Bitstring Status List, statusSize and statusMessages are stored in BitstringStatusListEntry. Here the BitstringStatusListEntry is supposed to be derived from TerseBitstringStatusListEntry, which does not support those properties.

[msporny]

Here the BitstringStatusListEntry is supposed to be derived from TerseBitstringStatusListEntry, which does not support those properties.

Yes, correct, the statusSize and statusMessages properties are not supported.

Would adding text explicitly calling that out address your concern, @timothee-haudebourg? What concrete changes would you like to see made to the specification based on your comments above?

[timothee-haudebourg]

Sorry for the delay, I'm just coming back to this issue. I guess the only way to fix it is to either

• put the statusSize and statusMessages properties back into the BistringStatusList (but that's not the direction taken by the WG it seems); or
• pass them as input of the TerseBitstringStatusListEntry conversion algorithm. But then the verifier needs to know those parameters in advance.