w3c/vc-bitstring-status-list

Issues

• (Editorial) Add border lines (or use different colors) to table rows

  #169 opened 3 months ago by iherman
  2

• Horizontal Reviews for Bitstring Status List v1.0

  #133 opened 3 months ago by msporny
  1

• Internationalization Self-Review for Bitstring Status List v1.0

  #132 opened 3 months ago by msporny
  1

• Accessibility self-review of Bitstring Status List v1.0

  #131 opened 3 months ago by msporny
  1

• Security and Privacy Questionnaire

  #77 opened 3 months ago by mkhraisha
  2

• TAG Review Request -- Submitted

  #72 opened 3 months ago by mkhraisha
  3

• Describe decoy entries as a privacy mitigation

  #150 opened 6 months ago by npdoty
  7

• Make the generated vocabulary file available for preview

  #157 opened 5 months ago by iherman
  4

• "bitstring" vs "bit string"

  #127 opened 5 months ago by TallTed
  7

• Remove open ended status messages because it is a layer violation

  #151 opened 5 months ago by jandrieu
  10

• mitigations for risk of unique status lists

  #143 opened 5 months ago by npdoty
  4

• Proposed improvement to the official vocabulary

  #158 opened 5 months ago by iherman
  5

• `statusPurpose` type `message` unclear

  #135 opened 5 months ago by aphillips
  2

• `credentialSubject.statusMessage` localizable?

  #136 opened 5 months ago by aphillips
  3

• comparison with alternative revocation mechanisms

  #148 opened 5 months ago by npdoty
  3

• when revocation status is and isn't appropriate to present

  #147 opened 5 months ago by npdoty
  3

• status list index is a persistent cross-origin identifier

  #142 opened 5 months ago by npdoty
  4

• Processing error `title` and `detail` need lang/dir guidance

  #140 opened 5 months ago by aphillips
  5

• status list index randomization requirement

  #149 opened 5 months ago by npdoty
  3

• information revealed by status updates

  #146 opened 5 months ago by npdoty
  6

• anonymizing proxy rather than CDN as a privacy mitigation

  #145 opened 5 months ago by npdoty
  4

• caching status lists as a mitigation for identifying when the holder visited a verifier

  #144 opened 5 months ago by npdoty
  4

• Testing with revoked and not-revoked credential

  #141 opened 7 months ago by BigBlueHat
  1

• Encoding of `statusListIndex`

  #134 opened 6 months ago by aphillips
  3

• Credential Type Mismatch between the Spec and the Schema

  #96 opened 8 months ago by hkny
  4

• Add `@type` to `encodedList` term definition

  #125 opened 8 months ago by dlongley
  4

• Matching of VC issuer and Status List VC issuer - MAY vs MUST

  #124 opened 8 months ago by dmitrizagidulin
  5

• Remove `ttl`

  #120 opened 8 months ago by dlongley
  5

• Align bitstring structure and IETF Token Status List structure?

  #93 opened 10 months ago by brentzundel
  3

• Cascading status updates

  #84 opened 8 months ago by OR13
  13

• Rename `reference` to `statusReference`

  #114 opened 8 months ago by dlongley
  2

• Rename "size" to "statusSize"

  #113 opened 8 months ago by dlongley
  5

• Conformance classes need to be defined

  #101 opened 8 months ago by msporny
  2

• Verification algorithm should say what happens if schema isn't followed

  #97 opened 8 months ago by jyasskin
  2

• Precise timestamps of status changes

  #94 opened 8 months ago by decentralgabe
  2

• Should validation algorithm check size of bitstring?

  #87 opened 8 months ago by andresuribe87
  2

• Add privacy considerations for multi-bit correlation

  #86 opened 8 months ago by msporny
  3

• Section 4.3 should be improved to suggest utilization of OHTTP to prevent correlation

  #80 opened 8 months ago by kdenhartog
  5

• Unify design of status lists to support multi-bit values

  #73 opened 8 months ago by msporny
  14

• update core context

  #70 opened 8 months ago by mprorock
  2

• auto-publishing using echidna?

  #82 opened 8 months ago by brentzundel
  14

• Vocabulary definitions

  #81 opened 8 months ago by iherman
  6

• Media type pairings

  #78 opened 9 months ago by OR13
  2

• Invalid JSON in Example 1

  #98 opened 9 months ago by samuelmr
  1

• Rename specification to "Herd Privacy Status List"

  #90 opened 10 months ago by msporny
  1

• Status-List-2021 LD-Context broken

  #91 opened a year ago by F-Node-Karlsruhe
  5

• Queries regarding the Specification

  #88 opened a year ago by arnabghose997
  1

• Split design space into two different types of status lists

  #85 opened a year ago by msporny
  4

• Statuslist2021entry example inaccurate?

  #71 opened a year ago by fkim7
  1

• Are index gaps allowed?

  #68 opened a year ago by fabrii
  1