GitHub / w3c/vc-bitstring-status-list issues and pull requests
Labelled with: pr exists
#188 - Shouldn’t there be a reference to the vocabulary and context files?
Issue -
State: closed - Opened by iherman about 1 year ago
- 2 comments
Labels: pr exists, normative, CR1
#184 - Clarification on multiple items inside `BitstringStatusListCredential.credentialSubject`
Issue -
State: closed - Opened by antonio-ivanovski about 1 year ago
- 8 comments
Labels: pr exists, editorial, CR1
#183 - New status purpose proposal
Issue -
State: closed - Opened by PatStLouis about 1 year ago
- 4 comments
Labels: pr exists, normative, CR1
#182 - Hosting of the bitstring status list context
Issue -
State: closed - Opened by chumbert about 1 year ago
- 6 comments
Labels: question, pr exists, CR1
#178 - Inconsistent algorithm and data model for encodedList
Issue -
State: closed - Opened by PatStLouis about 1 year ago
- 1 comment
Labels: pr exists, editorial, CR1
#174 - TTL is mandatory 5 minute period if not specified
Issue -
State: closed - Opened by msporny over 1 year ago
- 5 comments
Labels: pr exists, normative, CR1
#158 - Proposed improvement to the official vocabulary
Issue -
State: closed - Opened by iherman over 1 year ago
- 5 comments
Labels: before-CR, pr exists
#157 - Make the generated vocabulary file available for preview
Issue -
State: closed - Opened by iherman over 1 year ago
- 4 comments
Labels: before-CR, pr exists, editorial
#151 - Remove open ended status messages because it is a layer violation
Issue -
State: closed - Opened by jandrieu almost 2 years ago
- 10 comments
Labels: before-CR, pr exists, normative
#150 - Describe decoy entries as a privacy mitigation
Issue -
State: closed - Opened by npdoty almost 2 years ago
- 10 comments
Labels: during-CR, pr exists, privacy-needs-resolution, editorial
#149 - status list index randomization requirement
Issue -
State: closed - Opened by npdoty almost 2 years ago
- 3 comments
Labels: before-CR, pr exists, privacy-needs-resolution, editorial
#148 - comparison with alternative revocation mechanisms
Issue -
State: closed - Opened by npdoty almost 2 years ago
- 3 comments
Labels: before-CR, pr exists, privacy-tracker, editorial
#147 - when revocation status is and isn't appropriate to present
Issue -
State: closed - Opened by npdoty almost 2 years ago
- 3 comments
Labels: before-CR, pr exists, privacy-needs-resolution, editorial
#146 - information revealed by status updates
Issue -
State: closed - Opened by npdoty almost 2 years ago
- 6 comments
Labels: before-CR, pr exists, privacy-needs-resolution, editorial
#145 - anonymizing proxy rather than CDN as a privacy mitigation
Issue -
State: closed - Opened by npdoty almost 2 years ago
- 4 comments
Labels: before-CR, pr exists, privacy-needs-resolution, editorial
#144 - caching status lists as a mitigation for identifying when the holder visited a verifier
Issue -
State: closed - Opened by npdoty almost 2 years ago
- 4 comments
Labels: before-CR, pr exists, privacy-needs-resolution, normative
#143 - mitigations for risk of unique status lists
Issue -
State: closed - Opened by npdoty almost 2 years ago
- 4 comments
Labels: before-CR, pr exists, privacy-needs-resolution, editorial
#142 - status list index is a persistent cross-origin identifier
Issue -
State: closed - Opened by npdoty almost 2 years ago
- 4 comments
Labels: before-CR, pr exists, privacy-needs-resolution, editorial
#140 - Processing error `title` and `detail` need lang/dir guidance
Issue -
State: closed - Opened by aphillips almost 2 years ago
- 5 comments
Labels: before-CR, pr exists, i18n-needs-resolution, editorial
#125 - Add `@type` to `encodedList` term definition
Issue -
State: closed - Opened by dlongley almost 2 years ago
- 4 comments
Labels: before-CR, pr exists
#124 - Matching of VC issuer and Status List VC issuer - MAY vs MUST
Issue -
State: closed - Opened by dmitrizagidulin almost 2 years ago
- 5 comments
Labels: before-CR, pr exists
#120 - Remove `ttl`
Issue -
State: closed - Opened by dlongley almost 2 years ago
- 5 comments
Labels: before-CR, pr exists
#114 - Rename `reference` to `statusReference`
Issue -
State: closed - Opened by dlongley almost 2 years ago
- 2 comments
Labels: before-CR, pr exists
#113 - Rename "size" to "statusSize"
Issue -
State: closed - Opened by dlongley almost 2 years ago
- 5 comments
Labels: before-CR, pr exists
#101 - Conformance classes need to be defined
Issue -
State: closed - Opened by msporny almost 2 years ago
- 2 comments
Labels: before-CR, pr exists
#97 - Verification algorithm should say what happens if schema isn't followed
Issue -
State: closed - Opened by jyasskin about 2 years ago
- 2 comments
Labels: before-CR, pr exists
#96 - Credential Type Mismatch between the Spec and the Schema
Issue -
State: closed - Opened by hkny about 2 years ago
- 3 comments
Labels: before-CR, pr exists
#87 - Should validation algorithm check size of bitstring?
Issue -
State: closed - Opened by andresuribe87 over 2 years ago
- 2 comments
Labels: before-CR, pr exists
#86 - Add privacy considerations for multi-bit correlation
Issue -
State: closed - Opened by msporny over 2 years ago
- 3 comments
Labels: before-CR, pr exists
#80 - Section 4.3 should be improved to suggest utilization of OHTTP to prevent correlation
Issue -
State: closed - Opened by kdenhartog over 2 years ago
- 5 comments
Labels: during-CR, pr exists
#78 - Media type pairings
Issue -
State: closed - Opened by OR13 over 2 years ago
- 2 comments
Labels: before-CR, pr exists
#73 - Unify design of status lists to support multi-bit values
Issue -
State: closed - Opened by msporny over 2 years ago
- 14 comments
Labels: before-CR, pr exists
#70 - update core context
Issue -
State: closed - Opened by mprorock over 2 years ago
- 2 comments
Labels: before-CR, pr exists
#64 - Add section on expected server HTTP status codes
Issue -
State: closed - Opened by msporny over 2 years ago
- 5 comments
Labels: before-CR, pr exists
#58 - Encoded list in Base64 or Base64Url?
Issue -
State: closed - Opened by amondit almost 3 years ago
- 4 comments
Labels: before-CR, pr exists
#52 - Implementation guidelines around how StatusList2021Credential is secured/encoded.
Issue -
State: closed - Opened by Sakurann almost 3 years ago
- 3 comments
Labels: before-CR, pr exists
#51 - Clarify that `StatusList2021Credential` must be VC-DATA-MODEL (v1.1)
Issue -
State: closed - Opened by Sakurann almost 3 years ago
- 3 comments
Labels: before-CR, pr exists
#49 - Document design characteristics why "StatusList2021Entry" is signed.
Issue -
State: closed - Opened by Sakurann almost 3 years ago
- 2 comments
Labels: during-CR, pr exists
#48 - Document design characteristics why "StatusList2021Credential" is a VC
Issue -
State: closed - Opened by Sakurann almost 3 years ago
- 5 comments
Labels: during-CR, pr exists, editorial
#44 - clarify protocol for retrieval of a status list
Issue -
State: closed - Opened by mprorock almost 3 years ago
- 5 comments
Labels: before-CR, pr exists
#41 - Randomization
Issue -
State: closed - Opened by OR13 almost 3 years ago
- 2 comments
Labels: before-CR, pr exists
#36 - Specify bit order for status list
Issue -
State: closed - Opened by msporny almost 3 years ago
- 6 comments
Labels: before-CR, pr exists
#35 - Status of what?
Issue -
State: closed - Opened by David-Chadwick about 3 years ago
- 3 comments
Labels: before-CR, pr exists
#17 - Add vocabulary document
Issue -
State: closed - Opened by msporny almost 4 years ago
- 2 comments
Labels: before-CR, pr exists
#9 - Bounds checking
Issue -
State: closed - Opened by clehner about 4 years ago
- 6 comments
Labels: before-CR, pr exists
#7 - Status list credential issuer validation
Issue -
State: closed - Opened by clehner over 4 years ago
- 8 comments
Labels: before-CR, pr exists