Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

unlinkability: when should it be required and how can it be accomplished #6

Open
npdoty opened this issue Mar 7, 2024 · 0 comments
Open

unlinkability: when should it be required and how can it be accomplished #6

npdoty opened this issue Mar 7, 2024 · 0 comments
Labels
close?

Comments

@npdoty
Copy link
Contributor

npdoty commented Mar 7, 2024

A common topic is how to make presentations of credentials unlinkable, and how to provide any guidance about when presentations might or might not be linkable. This doc should provide some principles (or suggest principles or findings for elsewhere) on those distinctions.

See:
w3c/vc-di-bbs#110
w3ctag/design-reviews#922
npdoty added a commit that referenced this issue Mar 7, 2024
@npdoty
unlinkability #6
c460b4a 
explain a bit the threat that unlinkability protects against
introduce "inherently linkable"
conditions for when web technology must enable unlinkable presentations
what kind of guidance is needed for presentations that still might be linkable
@npdoty npdoty mentioned this issue Mar 7, 2024
Merged
@npdoty npdoty added the close? label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
close?
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@npdoty