issues
search
w3c
/
vc-bitstring-status-list
A privacy-preserving mechanism to publish status information for Verifiable Credentials.
https://w3c.github.io/vc-bitstring-status-list/
Other
22
stars
19
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Status size missing from `BitstringStatusList`
#176
timothee-haudebourg
opened
3 weeks ago
2
The `BitstringStatusList.statusMessages` and `statusSize` properties are still being referenced
#175
timothee-haudebourg
opened
4 weeks ago
6
TTL is mandatory 5 hour period if not specified
#174
msporny
opened
1 month ago
3
Add a MUST statement preventing 2 entries from having the same statusPurpose
#173
PatStLouis
opened
2 months ago
0
Update auto-publish.yml
#172
iherman
closed
3 months ago
2
Add issue marker noting guidance about decoy values will be resolved in CR.
#171
msporny
closed
4 months ago
3
Added a reference to optional features in SOTD
#170
iherman
closed
5 months ago
1
(Editorial) Add border lines (or use different colors) to table rows
#169
iherman
closed
3 months ago
2
add missing 'for'
#168
brentzundel
closed
3 months ago
1
improve language of "Unnecessary Correlation" section
#167
TallTed
closed
5 months ago
1
Tweaks to privacy considerations section about decoy values.
#166
TallTed
closed
5 months ago
1
Create lint-vocab.yml in workflows
#165
iherman
closed
5 months ago
1
Ensure that status messages are committed to at issuance time.
#164
msporny
closed
5 months ago
1
Update index.html
#163
TallTed
closed
6 months ago
1
Add comparison matrix and stapling language.
#162
msporny
closed
6 months ago
1
Add suggestion on how malicious issuers can be detected.
#161
msporny
closed
5 months ago
3
Add Privacy Considerations section on "Unnecessary Correlation".
#160
msporny
closed
6 months ago
2
Added changes to the vocabulary per #158
#159
iherman
closed
6 months ago
6
Proposed improvement to the official vocabulary
#158
iherman
closed
6 months ago
5
Make the generated vocabulary file available for preview
#157
iherman
closed
5 months ago
4
Add privacy considerations about status message updates/alterations.
#156
msporny
closed
6 months ago
1
Add privacy considerations section about decoy values.
#155
msporny
closed
6 months ago
4
Clarify normative text around randomness of list index.
#154
msporny
closed
6 months ago
1
Add normative statements related to caching of status list VCs.
#153
msporny
closed
6 months ago
2
Clarify internationalization mechanism for Processing Errors.
#152
msporny
closed
6 months ago
1
Remove open ended status messages because it is a layer violation
#151
jandrieu
closed
5 months ago
10
Describe decoy entries as a privacy mitigation
#150
npdoty
opened
7 months ago
8
status list index randomization requirement
#149
npdoty
closed
6 months ago
3
comparison with alternative revocation mechanisms
#148
npdoty
closed
6 months ago
3
when revocation status is and isn't appropriate to present
#147
npdoty
closed
6 months ago
3
information revealed by status updates
#146
npdoty
closed
6 months ago
6
anonymizing proxy rather than CDN as a privacy mitigation
#145
npdoty
closed
6 months ago
4
caching status lists as a mitigation for identifying when the holder visited a verifier
#144
npdoty
closed
6 months ago
4
mitigations for risk of unique status lists
#143
npdoty
closed
5 months ago
4
status list index is a persistent cross-origin identifier
#142
npdoty
closed
6 months ago
4
Testing with revoked and not-revoked credential
#141
BigBlueHat
opened
7 months ago
1
Processing error `title` and `detail` need lang/dir guidance
#140
aphillips
closed
6 months ago
5
Update vocabulary and template files
#139
iherman
closed
7 months ago
1
added human readable/machine readable, changed example to be more clear.
#138
mkhraisha
closed
6 months ago
7
add base 10 identifier info
#137
mkhraisha
closed
7 months ago
1
`credentialSubject.statusMessage` localizable?
#136
aphillips
closed
6 months ago
3
`statusPurpose` type `message` unclear
#135
aphillips
closed
6 months ago
2
Encoding of `statusListIndex`
#134
aphillips
closed
7 months ago
3
Horizontal Reviews for Bitstring Status List v1.0
#133
msporny
closed
4 months ago
1
Internationalization Self-Review for Bitstring Status List v1.0
#132
msporny
closed
4 months ago
1
Accessibility self-review of Bitstring Status List v1.0
#131
msporny
closed
4 months ago
1
Ensure better compression for `encodedList` by typing the value.
#130
msporny
closed
8 months ago
2
Explicitly allow `issuer` to be different between VC and BSLC.
#129
msporny
closed
8 months ago
1
Add at risk issue marker for TTL.
#128
msporny
closed
8 months ago
2
"bitstring" vs "bit string"
#127
TallTed
closed
5 months ago
7
Next