Weekly github digest (Weekly update on Verifiable Credentials WG activity) from W3C Webmaster via GitHub API on 2024-01-15 (public-credentials@w3.org from January 2024)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Mon, 15 Jan 2024 17:01:43 +0000
To: public-credentials@w3.org
Message-Id: <E1rPQLH-009IoX-NO@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+1/-3/💬11)
  1 issues created:
  - (editorial) "bitstring" vs "bit string" (by TallTed)
    https://github.com/w3c/vc-data-model/issues/1412 

  6 issues received 11 new comments:
  - #1412 (editorial) "bitstring" vs "bit string" (1 by TallTed)
    https://github.com/w3c/vc-data-model/issues/1412 
  - #1408 reconsider `@id` for `mediaType` term (5 by TallTed, gobengo, iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1408 [ready for PR] [post-CR] 
  - #1388 Specify what kind of processing is safe on a returned document (2 by jyasskin, msporny)
    https://github.com/w3c/vc-data-model/issues/1388 [pr exists] [before-CR] 
  - #1377 Rewrite verification algorithm in a way that does not cause layer violations (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1377 [pr exists] [before-CR] 
  - #1254 Section title and contents mismatch on "Complex Language Markup" (1 by seabass-labrax)
    https://github.com/w3c/vc-data-model/issues/1254 [post-CR] 
  - #1135 Add VC-JWT diagrams to core specification (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1135 [ready for PR] [post-CR] 

  3 issues closed:
  - Rewrite verification algorithm in a way that does not cause layer violations https://github.com/w3c/vc-data-model/issues/1377 [pr exists] [before-CR] 
  - Add VC-JWT diagrams to core specification https://github.com/w3c/vc-data-model/issues/1135 [ready for PR] [post-CR] 
  - (editorial) "bitstring" vs "bit string" https://github.com/w3c/vc-data-model/issues/1412 

* w3c/vc-data-integrity (+1/-1/💬2)
  1 issues created:
  - Specify that the `proof` property refers to a named graph (by iherman)
    https://github.com/w3c/vc-data-integrity/issues/238 

  2 issues received 2 new comments:
  - #238 Specify that the `proof` property refers to a named graph (1 by iherman)
    https://github.com/w3c/vc-data-integrity/issues/238 
  - #190 Add explanation about why proof graphs are used (1 by iherman)
    https://github.com/w3c/vc-data-integrity/issues/190 [during CR] 

  1 issues closed:
  - Specify that the `proof` property refers to a named graph https://github.com/w3c/vc-data-integrity/issues/238 

* w3c/vc-di-ecdsa (+1/-0/💬0)
  1 issues created:
  - "Section 4: Retrieving Cryptographic Material" => "Section 4: Retrieve Verification Method" (by dlongley)
    https://github.com/w3c/vc-di-ecdsa/issues/51 

* w3c/vc-di-bbs (+8/-0/💬18)
  8 issues created:
  - Add at-risk marker and enable passing in `pid` and `verifier ID` for pseudonym support from BBS spec (by dlongley)
    https://github.com/w3c/vc-di-bbs/issues/127 
  - Consider including `bbsHeader` in base proof to simplify disclosure / derived proof implementations (by dlongley)
    https://github.com/w3c/vc-di-bbs/issues/126 
  - Include issuer's original public key, `PK` in the base proof (by dlongley)
    https://github.com/w3c/vc-di-bbs/issues/125 
  - Enable `presentationHeader` bytes to be optionally passed when deriving a BBS proof (by dlongley)
    https://github.com/w3c/vc-di-bbs/issues/122 
  - "ECDSA-SD base proof" header should say "BBS base proof" header (by dlongley)
    https://github.com/w3c/vc-di-bbs/issues/121 
  - `serializeBaseProofValue` text mentions 5 elements, but there are just 3 (by dlongley)
    https://github.com/w3c/vc-di-bbs/issues/120 
  - Add note that implementers can reuse `createHmacIdLabelMapFunction` in `createShuffledIdLabelMapFunction` (by dlongley)
    https://github.com/w3c/vc-di-bbs/issues/119 
  - Switch from SHAKE-256 to SHA-256 (by dlongley)
    https://github.com/w3c/vc-di-bbs/issues/118 

  7 issues received 18 new comments:
  - #126 Consider including `bbsHeader` in base proof to simplify disclosure / derived proof implementations (3 by Wind4Greg, dlongley)
    https://github.com/w3c/vc-di-bbs/issues/126 
  - #125 Include issuer's original public key, `PK` in the base proof (2 by Wind4Greg, dlongley)
    https://github.com/w3c/vc-di-bbs/issues/125 
  - #122 Enable `presentationHeader` bytes to be optionally passed when deriving a BBS proof (2 by Wind4Greg, dlongley)
    https://github.com/w3c/vc-di-bbs/issues/122 
  - #121 "ECDSA-SD base proof" header should say "BBS base proof" header (1 by dlongley)
    https://github.com/w3c/vc-di-bbs/issues/121 
  - #120 `serializeBaseProofValue` text mentions 5 elements, but there are just 3 (1 by dlongley)
    https://github.com/w3c/vc-di-bbs/issues/120 
  - #119 Add note that implementers can reuse `createHmacIdLabelMapFunction` in `createShuffledIdLabelMapFunction` (2 by Wind4Greg, dlongley)
    https://github.com/w3c/vc-di-bbs/issues/119 
  - #118 Switch from SHAKE-256 to SHA-256 (7 by ChristopherA, Wind4Greg, dlongley, msporny)
    https://github.com/w3c/vc-di-bbs/issues/118 

* w3c/vc-jwt (+0/-0/💬18)
  9 issues received 18 new comments:
  - #217 Example 24 is invalid (2 by decentralgabe, iherman)
    https://github.com/w3c/vc-jose-cose/issues/217 [before-CR] 
  - #214 Inconsistent versions (1 by iherman)
    https://github.com/w3c/vc-jose-cose/issues/214 [before-CR] 
  - #207 COSE algorithms and examples not specified (1 by selfissued)
    https://github.com/w3c/vc-jose-cose/issues/207 [before-CR] 
  - #206 Algorithms are poorly defined / unimplementable (2 by decentralgabe, iherman)
    https://github.com/w3c/vc-jose-cose/issues/206 [before-CR] 
  - #205 Unclear semantics wrt. JWT claims vs. VC properties (2 by decentralgabe, iherman)
    https://github.com/w3c/vc-jose-cose/issues/205 [before-CR] 
  - #202 Conformance classes are not defined (2 by decentralgabe)
    https://github.com/w3c/vc-jose-cose/issues/202 [before-CR] 
  - #201 Support JWT-secured VCs (2 by decentralgabe, iherman)
    https://github.com/w3c/vc-jose-cose/issues/201 [before-CR] 
  - #195 Horizontal Review Tracking (3 by decentralgabe, iherman)
    https://github.com/w3c/vc-jose-cose/issues/195 [horizontal-review] [before-CR] 
  - #192 Spec should be more specific about implementation details (3 by iherman, kdenhartog, selfissued)
    https://github.com/w3c/vc-jose-cose/issues/192 [before-CR] 

* w3c/vc-status-list-2021 (+1/-25/💬32)
  1 issues created:
  - (editorial) "bitstring" vs "bit string" (by TallTed)
    https://github.com/w3c/vc-bitstring-status-list/issues/127 

  26 issues received 32 new comments:
  - #127 (editorial?) "bitstring" vs "bit string" (2 by TallTed, msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/127 [before-CR] 
  - #125 Add `@type` to `encodedList` term definition (2 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/125 [ready-for-pr] [before-CR] 
  - #124 Matching of VC issuer and Status List VC issuer - MAY vs MUST (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/124 [ready-for-pr] [before-CR] 
  - #120 Remove `ttl` (3 by dlongley, msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/120 [ready-for-pr] [before-CR] 
  - #114 Rename `reference` to `statusReference` (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/114 [before-CR] [pr exists] 
  - #113 Rename "size" to "statusSize" (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/113 [before-CR] [pr exists] 
  - #101 Conformance classes need to be defined (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/101 [before-CR] [pr exists] 
  - #97 Verification algorithm should say what happens if schema isn't followed (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/97 [before-CR] [pr exists] 
  - #96 Credential Type Mismatch between the Spec and the Schema (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/96 [before-CR] [pr exists] 
  - #94 Precise timestamps of status changes (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/94 [before-CR] [pr exists] 
  - #93 Bytestring structure and ietf status list (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/93 [before-CR] [pr exists] 
  - #87 Should validation algorithm check size of bitstring? (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/87 [before-CR] [pr exists] 
  - #86 Add privacy considerations for multi-bit correlation (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/86 [before-CR] [pr exists] 
  - #80 Section 4.3 should be improved to suggest utilization of OHTTP to prevent correlation (2 by OR13, msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/80 [during-CR] [pr exists] 
  - #73 Unify design of status lists to support multi-bit values (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/73 [before-CR] [pr exists] 
  - #70 update core context (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/70 [before-CR] [pr exists] 
  - #64 Add section on expected server HTTP status codes (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/64 [before-CR] [pr exists] 
  - #58 Encoded list in Base64 or Base64Url? (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/58 [before-CR] [pr exists] 
  - #56 Implementation Considerations (2 by msporny, shigeya)
    https://github.com/w3c/vc-bitstring-status-list/issues/56 [question] [before-CR] [pending 7 day close] 
  - #52 Implementation guidelines around how StatusList2021Credential is secured/encoded. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/52 [before-CR] [pr exists] 
  - #51 Clarify that `StatusList2021Credential` must be VC-DATA-MODEL (v1.1) (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/51 [before-CR] [pr exists] 
  - #44 clarify protocol for retrieval of a status list  (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/44 [before-CR] [pr exists] 
  - #35 Status of what? (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/35 [before-CR] [pr exists] 
  - #17 Add vocabulary document (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/17 [before-CR] [pr exists] 
  - #9 Bounds checking (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/9 [before-CR] [pr exists] 
  - #7 Status list credential issuer validation (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/7 [before-CR] [pr exists] 

  25 issues closed:
  - Cascading status updates https://github.com/w3c/vc-bitstring-status-list/issues/84 [pending 7 day close] 
  - Implementation Considerations https://github.com/w3c/vc-bitstring-status-list/issues/56 [question] [before-CR] [pending 7 day close] 
  - Is it possible to support multiple purposes? https://github.com/w3c/vc-bitstring-status-list/issues/47 [question] [before-CR] [pending 7 day close] 
  - Revocation or Suspension Date https://github.com/w3c/vc-bitstring-status-list/issues/25 [before-CR] [pending 7 day close] 
  - Handling Right to Erasure in encodedList and Validate Algorithm https://github.com/w3c/vc-bitstring-status-list/issues/23 [before-CR] [pending 7 day close] 
  - Rename `reference` to `statusReference` https://github.com/w3c/vc-bitstring-status-list/issues/114 [before-CR] [pr exists] 
  - Rename "size" to "statusSize" https://github.com/w3c/vc-bitstring-status-list/issues/113 [before-CR] [pr exists] 
  - Conformance classes need to be defined https://github.com/w3c/vc-bitstring-status-list/issues/101 [before-CR] [pr exists] 
  - Verification algorithm should say what happens if schema isn't followed https://github.com/w3c/vc-bitstring-status-list/issues/97 [before-CR] [pr exists] 
  - Credential Type Mismatch between the Spec and the Schema https://github.com/w3c/vc-bitstring-status-list/issues/96 [before-CR] [pr exists] 
  - Precise timestamps of status changes https://github.com/w3c/vc-bitstring-status-list/issues/94 [before-CR] [pr exists] 
  - Should validation algorithm check size of bitstring? https://github.com/w3c/vc-bitstring-status-list/issues/87 [before-CR] [pr exists] 
  - Add privacy considerations for multi-bit correlation https://github.com/w3c/vc-bitstring-status-list/issues/86 [before-CR] [pr exists] 
  - Section 4.3 should be improved to suggest utilization of OHTTP to prevent correlation https://github.com/w3c/vc-bitstring-status-list/issues/80 [during-CR] [pr exists] 
  - Unify design of status lists to support multi-bit values https://github.com/w3c/vc-bitstring-status-list/issues/73 [before-CR] [pr exists] 
  - update core context https://github.com/w3c/vc-bitstring-status-list/issues/70 [before-CR] [pr exists] 
  - Add section on expected server HTTP status codes https://github.com/w3c/vc-bitstring-status-list/issues/64 [before-CR] [pr exists] 
  - Encoded list in Base64 or Base64Url? https://github.com/w3c/vc-bitstring-status-list/issues/58 [before-CR] [pr exists] 
  - Implementation guidelines around how StatusList2021Credential is secured/encoded. https://github.com/w3c/vc-bitstring-status-list/issues/52 [before-CR] [pr exists] 
  - Clarify that `StatusList2021Credential` must be VC-DATA-MODEL (v1.1) https://github.com/w3c/vc-bitstring-status-list/issues/51 [before-CR] [pr exists] 
  - clarify protocol for retrieval of a status list  https://github.com/w3c/vc-bitstring-status-list/issues/44 [before-CR] [pr exists] 
  - Status of what? https://github.com/w3c/vc-bitstring-status-list/issues/35 [before-CR] [pr exists] 
  - Add vocabulary document https://github.com/w3c/vc-bitstring-status-list/issues/17 [before-CR] [pr exists] 
  - Bounds checking https://github.com/w3c/vc-bitstring-status-list/issues/9 [before-CR] [pr exists] 
  - Status list credential issuer validation https://github.com/w3c/vc-bitstring-status-list/issues/7 [before-CR] [pr exists] 



Pull requests
-------------
* w3c/vc-data-model (+0/-3/💬10)
  4 pull requests received 10 new comments:
  - #1407 Example diagrams multiple credentials (3 by TallTed, iherman)
    https://github.com/w3c/vc-data-model/pull/1407 [editorial] 
  - #1404 Jwt example diagrams (4 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1404 [editorial] 
  - #1397 Correct layering violations related to the proof property (2 by msporny, selfissued)
    https://github.com/w3c/vc-data-model/pull/1397 [before-CR] 
  - #1392 Add requirement for securing mechanisms to have post-verification documentation. (1 by jyasskin)
    https://github.com/w3c/vc-data-model/pull/1392 [pending close] [before-CR] 

  3 pull requests merged:
  - Correct layering violations related to the proof property
    https://github.com/w3c/vc-data-model/pull/1397 [before-CR] 
  - Jwt example diagrams
    https://github.com/w3c/vc-data-model/pull/1404 [editorial] 
  - Example diagrams multiple credentials
    https://github.com/w3c/vc-data-model/pull/1407 [editorial] 

* w3c/vc-data-integrity (+1/-0/💬0)
  1 pull requests submitted:
  - Informative appendix explaining proof sets and chains (by Wind4Greg)
    https://github.com/w3c/vc-data-integrity/pull/237 

* w3c/vc-di-bbs (+6/-0/💬5)
  6 pull requests submitted:
  - Enable Pass Through of BBS Presentation header (by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/pull/129 
  - Update all text to specify the SHA-256 hash  function rather than SHAKE-256 (by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/pull/128 
  - Informative change to fix incorrect count of number of elements. (by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/pull/124 
  - Remove copy and paste errors wrt ECDSA-SD header values. (by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/pull/123 
  - Update test vectors for BBS Signature Scheme version 05 (by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/pull/117 
  - Base Proof Options on Data Integrity with Restrictions (by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/pull/116 

  2 pull requests received 5 new comments:
  - #129 Enable Pass Through of BBS Presentation header (4 by dlongley, dwaite)
    https://github.com/w3c/vc-di-bbs/pull/129 
  - #115 i18n improvements  (1 by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/pull/115 

* w3c/vc-jwt (+0/-0/💬4)
  2 pull requests received 4 new comments:
  - #213 Update Abstract (1 by decentralgabe)
    https://github.com/w3c/vc-jose-cose/pull/213 [pending-close] 
  - #212 Update Title (3 by David-Chadwick, TallTed, decentralgabe)
    https://github.com/w3c/vc-jose-cose/pull/212 [pending-close] 

* w3c/vc-status-list-2021 (+3/-20/💬32)
  3 pull requests submitted:
  - Ensure better compression for `encodedList` by typing the value. (by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/130 
  - Explicitly allow `issuer` to be different between VC and BSLC. (by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/129 
  - Add at risk issue marker for TTL. (by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/128 

  20 pull requests received 32 new comments:
  - #123 Add at risk issue marker regarding multibit status entries. (2 by iherman, msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/123 
  - #122 Add examples for multiple status lists and multiple entries in a single status list (4 by KDean-GS1, TallTed, msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/122 
  - #121 Rename "herd privacy" to "group privacy". (2 by iherman, msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/121 
  - #119 Add "at risk" marker noting bitstring format might change in CR. (2 by iherman, msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/119 
  - #118 Add guidance on how to secure status lists. (2 by iherman, msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/118 
  - #117 Add privacy consideration section about Multistatus Correlation. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/117 
  - #116 Raise malformed value error on malformed values. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/116 
  - #115 Raise error when status list size does not meet minimum threshold. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/115 
  - #112 Add mechanism to retrieve historical status list information. (2 by iherman, msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/112 
  - #111 Add section on Processing Errors. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/111 
  - #110 Clarify base64 encoding as base64url encoding. (2 by iherman, msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/110 
  - #109 Update BitstringStatusList context to align with latest spec. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/109 
  - #108 Update VCDM dependency to VCDM v2.0. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/108 
  - #107 Add protocol statements related to pub/sub of status lists. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/107 
  - #106 Clarify what credential status information is about. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/106 
  - #105 Add formal vocabulary definitions. (3 by iherman, msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/105 
  - #104 Throw RANGE_ERROR for indexes outside the length of a bitstring. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/104 
  - #103 Add note specifying that issuer might be different for status lists. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/103 
  - #102 Add conformance classes to specification. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/102 
  - #100 Rename "status" to "message" for `statusPurpose` feature. (2 by iherman, msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/100 

  20 pull requests merged:
  - Add at risk issue marker regarding multibit status entries.
    https://github.com/w3c/vc-bitstring-status-list/pull/123 
  - Add examples for multiple status lists and multiple entries in a single status list
    https://github.com/w3c/vc-bitstring-status-list/pull/122 
  - Rename "herd privacy" to "group privacy".
    https://github.com/w3c/vc-bitstring-status-list/pull/121 
  - Add "at risk" marker noting bitstring format might change in CR.
    https://github.com/w3c/vc-bitstring-status-list/pull/119 
  - Add guidance on how to secure status lists.
    https://github.com/w3c/vc-bitstring-status-list/pull/118 
  - Add privacy consideration section about Multistatus Correlation.
    https://github.com/w3c/vc-bitstring-status-list/pull/117 
  - Raise malformed value error on malformed values.
    https://github.com/w3c/vc-bitstring-status-list/pull/116 
  - Raise error when status list size does not meet minimum threshold.
    https://github.com/w3c/vc-bitstring-status-list/pull/115 
  - Add mechanism to retrieve historical status list information.
    https://github.com/w3c/vc-bitstring-status-list/pull/112 
  - Add section on Processing Errors.
    https://github.com/w3c/vc-bitstring-status-list/pull/111 
  - Clarify base64 encoding as base64url encoding.
    https://github.com/w3c/vc-bitstring-status-list/pull/110 
  - Update BitstringStatusList context to align with latest spec.
    https://github.com/w3c/vc-bitstring-status-list/pull/109 
  - Update VCDM dependency to VCDM v2.0.
    https://github.com/w3c/vc-bitstring-status-list/pull/108 
  - Add protocol statements related to pub/sub of status lists.
    https://github.com/w3c/vc-bitstring-status-list/pull/107 
  - Clarify what credential status information is about.
    https://github.com/w3c/vc-bitstring-status-list/pull/106 
  - Add formal vocabulary definitions.
    https://github.com/w3c/vc-bitstring-status-list/pull/105 
  - Throw RANGE_ERROR for indexes outside the length of a bitstring.
    https://github.com/w3c/vc-bitstring-status-list/pull/104 
  - Add note specifying that issuer might be different for status lists.
    https://github.com/w3c/vc-bitstring-status-list/pull/103 
  - Add conformance classes to specification.
    https://github.com/w3c/vc-bitstring-status-list/pull/102 
  - Rename "status" to "message" for `statusPurpose` feature.
    https://github.com/w3c/vc-bitstring-status-list/pull/100 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/vc-data-model
* https://github.com/w3c/vc-test-suite
* https://github.com/w3c/vc-imp-guide
* https://github.com/w3c/vc-use-cases
* https://github.com/w3c/vc-json-schema
* https://github.com/w3c/vc-data-integrity
* https://github.com/w3c/vc-di-eddsa
* https://github.com/w3c/vc-di-ecdsa
* https://github.com/w3c/vc-di-bbs
* https://github.com/w3c/vc-jwt
* https://github.com/w3c/vc-status-list-2021


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 15 January 2024 17:01:47 UTC