Comments (7)
OR13
commented on August 15, 2024
3
discussed on the call, seems fraught with privacy issues, suggest not implementing it.
from vc-bitstring-status-list.
iherman
commented on August 15, 2024
1
The issue was discussed in a meeting on 2023-01-24
- no resolutions were taken
View the transcript
1.6. Add a "reason code" (issue vc-status-list-2021#12)
See github issue vc-status-list-2021#12.
Kristina Yasuda: issue 12.
… Adding reason field. Which sounds useful..
Manu Sporny: I agree it would be useful.
… but I'm concerned about size.
… The whole point is of Status List is to scale well.
… Also, it leaks privacy.
… And is the reason just an open text?.
… The issuer should keep track of why, and they should be able to explain why to the appropriate parties.
… That's between the individual and the issuer, not information that is publicized.
… Presently, I'd be -1 to this.
… Because the use case isn't clear.
… and we don't have enough experience to say what all the codes would be.
Dave Longley: Agree with manu. This seems like something that is very hard to do while preserving the privacy of the holder..
… solving this in a general way that won't be abused is fraught.
Gregory Natran: echoing Manu. At least in Canada, you could run into real problems with privacy law..
… it may not be your concern that its suspended for repeat DUI verses something less serious.
Kristina Yasuda: let's document that there's no consensus on adopting this feature and we can revisit later.
… with two minutes left.
from vc-bitstring-status-list.
lemoustachiste
commented on August 15, 2024
I think it could be useful.
Maybe a naive approach would be to have a second string (optional) the same size as the bit string (so the index is lookable and matches the status index), and the value could go from 0 to 9.
Does someone know why CRL does not make use of 7 but uses 10 instead? I am not sure the codes have to follow CRL's though.
from vc-bitstring-status-list.
msporny
commented on August 15, 2024
This can now be handled with the multi-bit value for a status list that supports that. That said, the privacy concerns remain. So much so that having two different types of status lists might be needed from a privacy standpoint.
This feature is now supported through the multi-bit values, so I'm marking it pending close.
from vc-bitstring-status-list.
lemoustachiste
commented on August 15, 2024
multi-bit value for a status list that supports that
@msporny do you have more resources that reference this solution?
from vc-bitstring-status-list.
msporny
commented on August 15, 2024
See this credentialSubject.size for a hint on how this works. I'll note that there is probably more changes that will need to occur before the data model is frozen: https://w3c.github.io/vc-bitstring-status-list/#bitstringstatuslistcredential
from vc-bitstring-status-list.
msporny
commented on August 15, 2024
Closing this issue as there is a mechanism to do this in the specification today.
from vc-bitstring-status-list.
Related Issues (20)
- Conformance classes need to be defined HOT 2
- Rename "size" to "statusSize" HOT 5
- Rename `reference` to `statusReference` HOT 2
- Remove `ttl` HOT 5
- Matching of VC issuer and Status List VC issuer - MAY vs MUST HOT 5
- Add `@type` to `encodedList` term definition HOT 4
- "bitstring" vs "bit string" HOT 4
- Accessibility self-review of Bitstring Status List v1.0
- Internationalization Self-Review for Bitstring Status List v1.0
- Horizontal Reviews for Bitstring Status List v1.0 HOT 1
- Encoding of `statusListIndex` HOT 3
- `statusPurpose` type `message` unclear HOT 2
- `credentialSubject.statusMessage` localizable? HOT 3
- Processing error `title` and `detail` need lang/dir guidance HOT 5
- Testing with revoked and not-revoked credential HOT 1
- Align bitstring structure and IETF Token Status List structure? HOT 3
- Precise timestamps of status changes HOT 2
- Credential Type Mismatch between the Spec and the Schema HOT 4
- Verification algorithm should say what happens if schema isn't followed HOT 2
- Invalid JSON in Example 1 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vc-bitstring-status-list.