You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please stop spreading the incorrect information that W3C VCDM does not support selective disclosure; this has caused a lot of confusion for a lot of people since the inception of the SD-JWT effort. A related common claim from the SD-JWT community that W3C VCDM only supports selective disclosure via advanced or non-approved crypto, is equally incorrect.
If what you really want to say is that in your opinion selective disclosure in SD-JWT is "simpler" or "better" - perhaps because it's more tightly coupled with the data model rather than supported via an extensible proof mechanism as in W3C VCDM - then please communicate it also that way, instead of drawing a dishonest ❌ symbol in the "Selective Disclosure" row in your "Feature Overview".
The text was updated successfully, but these errors were encountered:
Please stop spreading the incorrect information that W3C VCDM does not support selective disclosure; this has caused a lot of confusion for a lot of people since the inception of the SD-JWT effort. A related common claim from the SD-JWT community that W3C VCDM only supports selective disclosure via advanced or non-approved crypto, is equally incorrect.
See for example: https://www.w3.org/TR/vc-di-ecdsa/#ecdsa-sd-2023
If what you really want to say is that in your opinion selective disclosure in SD-JWT is "simpler" or "better" - perhaps because it's more tightly coupled with the data model rather than supported via an extensible proof mechanism as in W3C VCDM - then please communicate it also that way, instead of drawing a dishonest ❌ symbol in the "Selective Disclosure" row in your "Feature Overview".
The text was updated successfully, but these errors were encountered: