- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 18 Mar 2024 17:01:09 +0000
- To: public-credentials@w3.org
- Message-Id: <E1rmGMH-00448t-R6@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+0/-1/💬13)
7 issues received 13 new comments:
- #1455 Do we need sha3-512 in the vocabulary tables? (2 by iherman)
https://github.com/w3c/vc-data-model/issues/1455 [editorial] [pr exists] [CR1]
- #1442 What does the hash values in §B.2 mean? (2 by iherman)
https://github.com/w3c/vc-data-model/issues/1442 [editorial] [pr exists]
- #1432 first example contains an http url identifying a credential (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1432 [editorial] [ready for PR] [pending close]
- #1359 Authorized Presenters (4 by David-Chadwick, TallTed)
https://github.com/w3c/vc-data-model/issues/1359 [ready for PR] [discuss] [post-CR]
- #1348 Non-normative changes from Jeffrey Yasskin's review (2 by David-Chadwick, iherman)
https://github.com/w3c/vc-data-model/issues/1348 [ready for PR] [post-CR]
- #1254 Section title and contents mismatch on "Complex Language Markup" (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1254 [pending close] [post-CR]
- #1197 Define `verification material` find replace `public keys` (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1197 [editorial] [pending close] [post-CR]
1 issues closed:
- What does the hash values in §B.2 mean? https://github.com/w3c/vc-data-model/issues/1442 [editorial] [pr exists]
* w3c/vc-data-integrity (+1/-1/💬4)
1 issues created:
- Is it o.k. to use the DID context in an example? (by iherman)
https://github.com/w3c/vc-data-integrity/issues/256 [editorial]
2 issues received 4 new comments:
- #256 Is it o.k. to use the DID context in an example? (1 by iherman)
https://github.com/w3c/vc-data-integrity/issues/256 [editorial]
- #248 Discrepancies between the spec and the vocabulary (with bugs in the vocabulary) (3 by TallTed, iherman)
https://github.com/w3c/vc-data-integrity/issues/248 [bug] [CR1] [editorial]
1 issues closed:
- Is it o.k. to use the DID context in an example? https://github.com/w3c/vc-data-integrity/issues/256 [editorial]
* w3c/vc-di-bbs (+1/-2/💬1)
1 issues created:
- Figure titles (by hsano1234)
https://github.com/w3c/vc-di-bbs/issues/146
1 issues received 1 new comments:
- #127 Add at-risk marker and enable passing in `pid` and `verifier ID` for pseudonym support from BBS spec (1 by msporny)
https://github.com/w3c/vc-di-bbs/issues/127 [PR-exists] [normative]
2 issues closed:
- Add at-risk marker and enable passing in `pid` and `verifier ID` for pseudonym support from BBS spec https://github.com/w3c/vc-di-bbs/issues/127 [PR-exists] [normative]
- Specification should clearly identify BBS+ (not BBS) https://github.com/w3c/vc-di-bbs/issues/136 [editorial] [pending-close]
* w3c/vc-status-list-2021 (+1/-0/💬6)
1 issues created:
- Remove open ended status messages because it is a layer violation (by jandrieu)
https://github.com/w3c/vc-bitstring-status-list/issues/151
4 issues received 6 new comments:
- #151 Remove open ended status messages because it is a layer violation (2 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/151 [before-CR] [normative]
- #146 information revealed by status updates (2 by iherman, jandrieu)
https://github.com/w3c/vc-bitstring-status-list/issues/146 [ready-for-pr] [before-CR] [privacy-needs-resolution] [editorial]
- #145 anonymizing proxy rather than CDN as a privacy mitigation (1 by npdoty)
https://github.com/w3c/vc-bitstring-status-list/issues/145 [ready-for-pr] [before-CR] [privacy-needs-resolution] [editorial]
- #144 caching status lists as a mitigation for identifying when the holder visited a verifier (1 by iherman)
https://github.com/w3c/vc-bitstring-status-list/issues/144 [ready-for-pr] [before-CR] [privacy-needs-resolution] [normative]
Pull requests
-------------
* w3c/vc-data-model (+2/-1/💬2)
2 pull requests submitted:
- Removing sha3 reference from the vocabulary table. (by iherman)
https://github.com/w3c/vc-data-model/pull/1459 [editorial] [CR1]
- (Editorial) Created a new version for several diagrams (by iherman)
https://github.com/w3c/vc-data-model/pull/1458 [editorial]
1 pull requests received 2 new comments:
- #1454 Updating the text on vocabulary hashes (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/pull/1454 [editorial] [CR1]
1 pull requests merged:
- Updating the text on vocabulary hashes
https://github.com/w3c/vc-data-model/pull/1454 [editorial] [CR1]
* w3c/vc-data-integrity (+2/-0/💬0)
2 pull requests submitted:
- Updated the section on multikey (by iherman)
https://github.com/w3c/vc-data-integrity/pull/257
- Editorial changes on the vocabulary tables to make it consistent with the VCDM (by iherman)
https://github.com/w3c/vc-data-integrity/pull/255 [CR1] [editorial]
* w3c/vc-di-bbs (+1/-1/💬3)
1 pull requests submitted:
- Use v2 context for the data-integrity (by iherman)
https://github.com/w3c/vc-di-bbs/pull/147
2 pull requests received 3 new comments:
- #145 Pseudonyms and Anonymous Holder Binding optional features (2 by msporny)
https://github.com/w3c/vc-di-bbs/pull/145
- #144 Update algorithms to align with new cryptosuite interface (1 by msporny)
https://github.com/w3c/vc-di-bbs/pull/144
1 pull requests merged:
- Update algorithms to align with new cryptosuite interface
https://github.com/w3c/vc-di-bbs/pull/144
* w3c/vc-jwt (+1/-0/💬0)
1 pull requests submitted:
- Update COSE Examples to use EDN (by decentralgabe)
https://github.com/w3c/vc-jose-cose/pull/258
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, 18 March 2024 17:01:11 UTC