- From: W3C Webmaster via GitHub API <noreply@w3.org>
- Date: Mon, 06 Jul 2026 17:01:51 +0000
- To: public-credentials@w3.org
- Message-ID: <178335731134.3526609.16046352877451548198@janus.w3.internal>
Issues
------
* w3c/cid (+0/-0/💬6)
1 issues received 6 new comments:
- #166 checksum of vocabulary do not match (6 by BigBlueHat, iherman, pchampin)
https://github.com/w3c/cid/issues/166 [ready for pr] [PossibleErratum] [class 2]
* w3c/vc-data-model (+0/-0/💬2)
2 issues received 2 new comments:
- #1632 remove confidence and render methods from the VCDM spec (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1632 [editorial] [allowed class 4]
- #1628 Deprecate `digestSRI` in v2.1 (1 by msporny)
https://github.com/w3c/vc-data-model/issues/1628 [pr exists] [class 2]
* w3c/vc-confidence-method (+2/-0/💬6)
2 issues created:
- Evaluate constraints that verifiers might request for biometrics (by jandrieu)
https://github.com/w3c/vc-confidence-method/issues/41
- Add VPRs (by jandrieu)
https://github.com/w3c/vc-confidence-method/issues/40
2 issues received 6 new comments:
- #41 Evaluate constraints that verifiers might request for biometrics (4 by amir-hameed-mir, dlongley)
https://github.com/w3c/vc-confidence-method/issues/41
- #39 Another possible biometric example. (2 by iherman, jandrieu)
https://github.com/w3c/vc-confidence-method/issues/39
* w3c/vcalm (+2/-2/💬7)
2 issues created:
- Define a query type for confidence methods in general (by dlongley)
https://github.com/w3c/vcalm/issues/660 [v1.0]
- `acceptedIssuers` examples incorrect (need to be updated to match definition) (by dlongley)
https://github.com/w3c/vcalm/issues/658 [bug] [v1.0]
5 issues received 7 new comments:
- #649 Allow multiple presentations to be sent in a response via an array value for `verifiablePresentation` (1 by kezike)
https://github.com/w3c/vcalm/issues/649 [ready for PR] [effort: low] [v1.0]
- #637 Expand error handling to workflows (1 by kezike)
https://github.com/w3c/vcalm/issues/637 [v1.0]
- #635 Align examples and schemas with VC Data Model 2.0 (context + validFrom/validUntil) (1 by kezike)
https://github.com/w3c/vcalm/issues/635 [pr exists] [v1.0]
- #629 Add clarity around `acceptedEnvelopes` vs. `acceptedCryptosuites` usage (1 by kezike)
https://github.com/w3c/vcalm/issues/629 [pr exists] [effort: low] [v1.0]
- #621 Scope definition of "domain" to "verifiable presentation request"? (3 by kezike, tidoust)
https://github.com/w3c/vcalm/issues/621 [pr exists] [effort: low] [v1.0]
2 issues closed:
- Align examples and schemas with VC Data Model 2.0 (context + validFrom/validUntil) https://github.com/w3c/vcalm/issues/635 [pr exists] [v1.0]
- Add clarity around `acceptedEnvelopes` vs. `acceptedCryptosuites` usage https://github.com/w3c/vcalm/issues/629 [pr exists] [effort: low] [v1.0]
* w3c/vc-recognition (+6/-7/💬15)
6 issues created:
- Internationalization Self-Review Questionnaire for VC Recognized Entities v1.0 (by msporny)
https://github.com/w3c/vc-recognized-entities/issues/98
- Accessibility Self-Review Questionnaire for VC Recognized Entities v1.0 (by msporny)
https://github.com/w3c/vc-recognized-entities/issues/97
- Security and Privacy Self-Review Questionnaire for VC Recognized Entities v1.0 (by msporny)
https://github.com/w3c/vc-recognized-entities/issues/96
- Horizontal Reviews for VC Recognized Entities v1.0 (by msporny)
https://github.com/w3c/vc-recognized-entities/issues/95
- Proper vocabulary term definitions (by iherman)
https://github.com/w3c/vc-recognized-entities/issues/92
- Deprecate/remove `use-cases.html` replace with inline use cases section. (by BigBlueHat)
https://github.com/w3c/vc-recognized-entities/issues/91
11 issues received 15 new comments:
- #90 validation rules for chained credentials (1 by iherman)
https://github.com/w3c/vc-recognized-entities/issues/90
- #89 Discovery model for recognised entity VCs (3 by BigBlueHat, iherman, swcurran)
https://github.com/w3c/vc-recognized-entities/issues/89
- #84 Reorder forward references (1 by msporny)
https://github.com/w3c/vc-recognized-entities/issues/84 [editorial] [pr exists]
- #66 UNTP / UNGRID / DIA Identity Anchor use case (2 by BigBlueHat, iherman)
https://github.com/w3c/vc-recognized-entities/issues/66 [use cases]
- #63 How do you state a historical recognized action is valid between two dates? (2 by BigBlueHat, iherman)
https://github.com/w3c/vc-recognized-entities/issues/63 [discuss] [use cases]
- #44 Is it `the value MUST be a URL`, or `URL or image data`? (1 by msporny)
https://github.com/w3c/vc-recognized-entities/issues/44 [editorial] [pr exists]
- #43 Comic-style images are misleading and inappropriate for a spec (1 by msporny)
https://github.com/w3c/vc-recognized-entities/issues/43 [editorial] [pr exists]
- #41 Explain that `outputValidation` requires governance (1 by msporny)
https://github.com/w3c/vc-recognized-entities/issues/41 [security considerations] [pr exists]
- #4 Outline considerations that are out of scope (1 by msporny)
https://github.com/w3c/vc-recognized-entities/issues/4 [pr exists]
- #3 Document risk surface of peer sharing (1 by msporny)
https://github.com/w3c/vc-recognized-entities/issues/3 [security considerations] [pr exists]
- #2 Document danger of first mover advantages (1 by msporny)
https://github.com/w3c/vc-recognized-entities/issues/2 [security considerations] [pr exists]
7 issues closed:
- Reorder forward references https://github.com/w3c/vc-recognized-entities/issues/84 [editorial] [pr exists]
- Is it `the value MUST be a URL`, or `URL or image data`? https://github.com/w3c/vc-recognized-entities/issues/44 [editorial] [pr exists]
- Comic-style images are misleading and inappropriate for a spec https://github.com/w3c/vc-recognized-entities/issues/43 [editorial] [pr exists]
- Explain that `outputValidation` requires governance https://github.com/w3c/vc-recognized-entities/issues/41 [security considerations] [pr exists]
- Outline considerations that are out of scope https://github.com/w3c/vc-recognized-entities/issues/4 [pr exists]
- Document risk surface of peer sharing https://github.com/w3c/vc-recognized-entities/issues/3 [security considerations] [pr exists]
- Document danger of first mover advantages https://github.com/w3c/vc-recognized-entities/issues/2 [security considerations] [pr exists]
* w3c/vc-barcodes (+2/-1/💬1)
2 issues created:
- Proper class and property specifications, please (by iherman)
https://github.com/w3c/vc-barcodes/issues/61
- Terse bitstringStatusListEntry only in barcode? (by iherman)
https://github.com/w3c/vc-barcodes/issues/60
1 issues received 1 new comments:
- #33 Add mechanism to protect VC Barcodes from insider threats and quantum computers (1 by wes-smith)
https://github.com/w3c/vc-barcodes/issues/33 [ready for pr]
1 issues closed:
- Add mechanism to protect VC Barcodes from insider threats and quantum computers https://github.com/w3c/vc-barcodes/issues/33 [ready for pr]
* w3c/vc-data-integrity (+1/-0/💬2)
1 issues created:
- Potential internal contradiction around verificationMethod (by rmlearney-digicatapult)
https://github.com/w3c/vc-data-integrity/issues/349
1 issues received 2 new comments:
- #348 Move Common Algorthms from vc-di-quantum-resistant to vc-data-integrity and update vc-di-ecdsa and vc-di-eddsa (2 by Wind4Greg)
https://github.com/w3c/vc-data-integrity/issues/348
* w3c/vc-di-ecdsa (+1/-0/💬1)
1 issues created:
- Incorrect C14N in test vectors (A.4) (by filip26)
https://github.com/w3c/vc-di-ecdsa/issues/105
1 issues received 1 new comments:
- #105 Incorrect C14N in test vectors (A.4) (1 by dlongley)
https://github.com/w3c/vc-di-ecdsa/issues/105
Pull requests
-------------
* w3c/cid (+0/-0/💬1)
1 pull requests received 1 new comments:
- #168 Allow for fragment identifier in document.id (1 by pchampin)
https://github.com/w3c/cid/pull/168 [class 3]
* w3c/vcalm (+5/-0/💬1)
5 pull requests submitted:
- 662 (by kezike)
https://github.com/w3c/vcalm/pull/662
- 661 (by PatStLouis)
https://github.com/w3c/vcalm/pull/661
- 659 (by BigBlueHat)
https://github.com/w3c/vcalm/pull/659
- 657 (by kezike)
https://github.com/w3c/vcalm/pull/657
- 656 (by kezike)
https://github.com/w3c/vcalm/pull/656
1 pull requests received 1 new comments:
- #655 Adding VCALM Threat Model (1 by jandrieu)
https://github.com/w3c/vcalm/pull/655
* w3c/vc-recognition (+3/-0/💬1)
3 pull requests submitted:
- 99 (by msporny)
https://github.com/w3c/vc-recognized-entities/pull/99
- 94 (by msporny)
https://github.com/w3c/vc-recognized-entities/pull/94
- 93 (by msporny)
https://github.com/w3c/vc-recognized-entities/pull/93
1 pull requests received 1 new comments:
- #82 Add initial attempt at threat model. (1 by msporny)
https://github.com/w3c/vc-recognized-entities/pull/82
* w3c/vc-barcodes (+1/-0/💬2)
1 pull requests submitted:
- 59 (by wes-smith)
https://github.com/w3c/vc-barcodes/pull/59
1 pull requests received 2 new comments:
- #59 Generalize "augment an existing barcode" feature, refactor algorithms, clean up cruft. (2 by iherman)
https://github.com/w3c/vc-barcodes/pull/59
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/vc-overview
* https://github.com/w3c/vc-use-cases
* https://github.com/w3c/cid
* https://github.com/w3c/vc-data-model
* https://github.com/w3c/vc-bitstring-status-list
* https://github.com/w3c/vc-render-method
* https://github.com/w3c/vc-confidence-method
* https://github.com/w3c/vcalm
* https://github.com/w3c/vc-recognition
* https://github.com/w3c/vc-barcodes
* https://github.com/w3c/vc-data-integrity
* https://github.com/w3c/vc-di-ecdsa
* https://github.com/w3c/vc-di-eddsa
* https://github.com/w3c/vc-di-bbs
* https://github.com/w3c/vc-jose-cose
* https://github.com/w3c/vc-json-schema
* https://github.com/w3c/vc-specs-dir
* https://github.com/w3c/vc-imp-guide
* https://github.com/w3c/vc-test-suite-implementations
* https://github.com/w3c/vc-data-model-2.0-test-suite
* https://github.com/w3c/vc-bitstring-status-list-test-suite
* https://github.com/w3c/vc-di-ecdsa-test-suite
* https://github.com/w3c/vc-di-eddsa-test-suite
* https://github.com/w3c/vc-di-ed25519signature2020-test-suite
* https://github.com/w3c/vc-di-bbs-test-suite
* https://github.com/w3c/vc-jose-cose-test-suite
* https://github.com/w3c/vc-json-schema-test-suite
* https://github.com/w3c/respec-vc
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 July 2026 17:01:52 UTC