Skip to content

Issues: w3c/vc-bitstring-status-list

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

10 Open 96 Closed
10 Open 96 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Clarification on multiple items inside BitstringStatusListCredential.credentialSubject
#184 opened Nov 20, 2024 by antonio-ivanovski
New status purpose proposal CR1 This item was processed during the first Candidate Recommendation phase. normative The item is normative in nature. ready-for-pr
#183 opened Nov 15, 2024 by PatStLouis
@PatStLouis
2
Hosting of the bistring status list context CR1 This item was processed during the first Candidate Recommendation phase. question Further information is requested
#182 opened Nov 7, 2024 by chumbert
@msporny
2
Status size missing from BitstringStatusList CR1 This item was processed during the first Candidate Recommendation phase. normative The item is normative in nature.
#176 opened Sep 13, 2024 by timothee-haudebourg
3
The BitstringStatusList.statusMessages and statusSize properties are still being referenced CR1 This item was processed during the first Candidate Recommendation phase. discuss This issue is a discussion with no clear change requested normative The item is normative in nature.
#175 opened Sep 5, 2024 by timothee-haudebourg
@msporny
7
TTL is mandatory 5 minute period if not specified CR1 This item was processed during the first Candidate Recommendation phase. normative The item is normative in nature. ready-for-pr
#174 opened Aug 29, 2024 by msporny
@msporny
3
Add a MUST statement preventing 2 entries from having the same statusPurpose CR1 This item was processed during the first Candidate Recommendation phase. discuss This issue is a discussion with no clear change requested normative The item is normative in nature.
#173 opened Jul 24, 2024 by PatStLouis
Describe decoy entries as a privacy mitigation during-CR This issue needs to be resolved during the Candidate Recommendation phase. editorial pr exists privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on.
#150 opened Mar 6, 2024 by npdoty
@msporny
8
Testing with revoked and not-revoked credential during-CR This issue needs to be resolved during the Candidate Recommendation phase.
#141 opened Feb 26, 2024 by BigBlueHat
@BigBlueHat
1
Document design characteristics why "StatusList2021Credential" is a VC during-CR This issue needs to be resolved during the Candidate Recommendation phase. ready-for-pr
#48 opened Jan 31, 2023 by Sakurann
@msporny
3
ProTip! no:milestone will show everything without a milestone.