- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 18 Sep 2023 17:01:42 +0000
- To: public-credentials@w3.org
- Message-Id: <E1qiHd0-007f9Z-AC@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+3/-2/💬49)
3 issues created:
- Pre-CR review from Jeffrey Yasskin (by msporny)
https://github.com/w3c/vc-data-model/issues/1285 [before-CR]
- Add Security Consideration to avoid key reuse (by msporny)
https://github.com/w3c/vc-data-model/issues/1284
- Normative requirement for securing a VC or VP (by andresuribe87)
https://github.com/w3c/vc-data-model/issues/1282
21 issues received 49 new comments:
- #1282 Normative requirement for securing a VC or VP (2 by Sakurann, decentralgabe)
https://github.com/w3c/vc-data-model/issues/1282 [ready for PR] [clarification]
- #1275 Allow string values in JOSE properties in base JSON-LD context (2 by iherman, selfissued)
https://github.com/w3c/vc-data-model/issues/1275 [ready for PR] [before-CR]
- #1267 Encourage the use of OHTTP (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1267 [privacy-needs-resolution] [security-needs-resolution] [before-CR]
- #1265 Add `relatedResource` to `VerifiablePresentation` (4 by Sakurann, iherman, jandrieu)
https://github.com/w3c/vc-data-model/issues/1265 [before-CR]
- #1264 Recommend that authors don't use `@language` in `@context` (9 by BigBlueHat, aphillips, dlongley, iherman, msporny, shigeya)
https://github.com/w3c/vc-data-model/issues/1264 [pr exists] [i18n-needs-resolution] [before-CR]
- #1263 are `domain` and `range` correct for all properties in data model? (6 by brentzundel, bumblefudge, iherman)
https://github.com/w3c/vc-data-model/issues/1263 [discuss] [before-CR]
- #1262 Add `revoked` and `expired` to verification method classes (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1262 [pending close]
- #1261 Add cryptographic hashes for vocabulary files (1 by msporny)
https://github.com/w3c/vc-data-model/issues/1261 [ready for PR] [before-CR]
- #1247 Addressing Verifier Stored Data Vulnerabilities and Legal Compliance (5 by Sakurann, iherman, kdenhartog)
https://github.com/w3c/vc-data-model/issues/1247 [ready for PR] [HorizontalReview] [privacy-needs-resolution] [security-needs-resolution] [before-CR]
- #1246 Strengthening Trust Boundaries for Holder Software in Verifiable Credential Processing (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1246 [HorizontalReview] [privacy-needs-resolution] [security-needs-resolution] [before-CR]
- #1245 Mitigating Location Correlation via Common Issuers (2 by Sakurann, iherman)
https://github.com/w3c/vc-data-model/issues/1245 [HorizontalReview] [privacy-needs-resolution] [before-CR]
- #1244 Address Metadata-Driven Correlation (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1244 [HorizontalReview] [privacy-needs-resolution] [before-CR]
- #1240 Address normative concept of VerifiableCredentialGraph (1 by msporny)
https://github.com/w3c/vc-data-model/issues/1240 [ready for PR] [before-CR]
- #1232 Revisit validation vs verification (3 by Sakurann, iherman, jandrieu)
https://github.com/w3c/vc-data-model/issues/1232 [ready for PR] [before-CR]
- #1227 Document the value of processing as JSON-LD (1 by msporny)
https://github.com/w3c/vc-data-model/issues/1227 [ready for PR] [before-CR]
- #1185 Conformance requirements for normative context (1 by msporny)
https://github.com/w3c/vc-data-model/issues/1185 [ready for PR] [before-CR]
- #1155 Internationalization Review for VCDM 2.0 (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1155 [HorizontalReview] [i18n-tracker] [before-CR]
- #1150 Protected term errors when supporting v1 and v2 (1 by msporny)
https://github.com/w3c/vc-data-model/issues/1150 [pr exists] [before-CR]
- #1047 NIST defines "credential" differently (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1047 [ready for PR] [terminology] [before-CR]
- #1010 `termsOfUse` is insufficiently specified (3 by David-Chadwick, MizukiSonoko, iherman)
https://github.com/w3c/vc-data-model/issues/1010 [conversation] [directory] [before-CR]
- #870 Evidence extension point (was: Improve tests for Evidence) (2 by OR13, iherman)
https://github.com/w3c/vc-data-model/issues/870 [evidence] [before-CR]
2 issues closed:
- Addressing Verifier Stored Data Vulnerabilities and Legal Compliance https://github.com/w3c/vc-data-model/issues/1247 [ready for PR] [HorizontalReview] [privacy-needs-resolution] [security-needs-resolution] [before-CR]
- Protected term errors when supporting v1 and v2 https://github.com/w3c/vc-data-model/issues/1150 [pr exists] [before-CR]
* w3c/vc-use-cases (+0/-0/💬1)
1 issues received 1 new comments:
- #146 Chain of GS1 credentials to identify a trade item (1 by iherman)
https://github.com/w3c/vc-use-cases/issues/146 [needsPR]
* w3c/vc-json-schema (+0/-3/💬7)
1 issues received 7 new comments:
- #210 Pre-CR normative dependencies will trigger a 2nd CR (7 by decentralgabe, msporny)
https://github.com/w3c/vc-json-schema/issues/210 [pre-cr]
3 issues closed:
- Pre-CR normative dependencies will trigger a 2nd CR https://github.com/w3c/vc-json-schema/issues/210 [pre-cr]
- Add guidance for wallets when using JsonSchemaCredential and selected disclosure https://github.com/w3c/vc-json-schema/issues/202 [privacy-needs-resolution] [pre-cr]
- Pre-CR normative dependencies will trigger a 2nd CR https://github.com/w3c/vc-json-schema/issues/210 [pre-cr]
* w3c/vc-data-integrity (+7/-0/💬13)
7 issues created:
- https://w3id.org/security/data-integrity/v1 is an octet-stream (by jeswr)
https://github.com/w3c/vc-data-integrity/issues/200
- [EDDSA] Highlight security/privacy trade-offs between RDF-CANON and JCS (by msporny)
https://github.com/w3c/vc-data-integrity/issues/195
- [ECDSA] Highlight security/privacy trade-offs between RDF-CANON and JCS (by msporny)
https://github.com/w3c/vc-data-integrity/issues/194
- need resourceIntegrity in vocab and under w3c (by mprorock)
https://github.com/w3c/vc-data-integrity/issues/193
- Correct statements about standardization of multibase and multihash (by selfissued)
https://github.com/w3c/vc-data-integrity/issues/192
- Remove normative dependencies on multibase (by selfissued)
https://github.com/w3c/vc-data-integrity/issues/191
- Add explanation about why proof graphs are used (by msporny)
https://github.com/w3c/vc-data-integrity/issues/190
6 issues received 13 new comments:
- #195 [EDDSA] Highlight security/privacy trade-offs between RDF-CANON and JCS (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/195 [privacy-needs-resolution] [security-needs-resolution] [before CR]
- #194 [ECDSA] Highlight security/privacy trade-offs between RDF-CANON and JCS (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/194 [privacy-needs-resolution] [security-needs-resolution] [before CR]
- #192 Correct statements about standardization of multibase and multihash (3 by OR13, iherman, msporny)
https://github.com/w3c/vc-data-integrity/issues/192 [ready for pr] [before CR]
- #191 Remove normative dependencies on multibase (5 by BigBlueHat, OR13, iherman, msporny)
https://github.com/w3c/vc-data-integrity/issues/191 [ready for pr] [before CR]
- #169 Add Security Consideration to avoid key reuse (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/169 [security-needs-resolution] [ready for pr] [before CR]
- #168 Add Privacy Consideration for previous signers in proof chains (2 by msporny)
https://github.com/w3c/vc-data-integrity/issues/168 [privacy-needs-resolution] [ready for pr] [before CR]
* w3c/vc-di-ecdsa (+0/-0/💬1)
1 issues received 1 new comments:
- #30 Highlight security/privacy trade-offs between RDF-CANON and JCS (1 by msporny)
https://github.com/w3c/vc-di-ecdsa/issues/30 [privacy-needs-resolution] [security-needs-resolution] [during CR]
* w3c/vc-di-bbs (+0/-0/💬13)
1 issues received 13 new comments:
- #84 Hashing (bbs-proof-2023) (13 by Wind4Greg, brianorwhatever, dlongley)
https://github.com/w3c/vc-di-bbs/issues/84
* w3c/vc-jwt (+2/-6/💬36)
2 issues created:
- Add guidance on using JWT-VCs when using the SD-JWT media types (by selfissued)
https://github.com/w3c/vc-jose-cose/issues/157 [before-CR]
- Controller document examples (by OR13)
https://github.com/w3c/vc-jose-cose/issues/154
22 issues received 36 new comments:
- #154 Controller document examples (2 by OR13, selfissued)
https://github.com/w3c/vc-jose-cose/issues/154
- #145 Representing extension validation in tests (1 by decentralgabe)
https://github.com/w3c/vc-jose-cose/issues/145 [testsuite] [blocked-by-test-suite]
- #136 signature profiles (1 by alenhorvat)
https://github.com/w3c/vc-jose-cose/issues/136 [has-pr]
- #135 Can registered JWT claims be used only in the JOSE header?? (1 by iherman)
https://github.com/w3c/vc-jose-cose/issues/135 [has-pr] [before-CR]
- #133 Clarify relationship between validity times (1 by iherman)
https://github.com/w3c/vc-jose-cose/issues/133 [has-pr] [before-CR]
- #132 JWT - securing mechanism or not? (6 by OR13, alenhorvat, selfissued)
https://github.com/w3c/vc-jose-cose/issues/132 [has-pr]
- #128 File PING request once rename is complete (3 by awoie, selfissued)
https://github.com/w3c/vc-jose-cose/issues/128 [horizontal-review] [before-CR]
- #127 Better references to OIDC key discovery (1 by Sakurann)
https://github.com/w3c/vc-jose-cose/issues/127 [has-pr] [before-CR]
- #118 Describe SD-JWT as an alternative for selective disclosure (1 by iherman)
https://github.com/w3c/vc-jose-cose/issues/118 [has-pr] [before-CR]
- #117 how is `kid` to be `useful to distinguish the specific key used`? (1 by iherman)
https://github.com/w3c/vc-jose-cose/issues/117 [has-pr] [before-CR]
- #106 Explain relationship between controller documents and JOSE headers (1 by iherman)
https://github.com/w3c/vc-jose-cose/issues/106 [has-pr] [before-CR]
- #95 Internationalization Review for VC JOSE COSE (1 by awoie)
https://github.com/w3c/vc-jose-cose/issues/95 [horizontal-review] [before-CR]
- #94 Accessibility Self-Review for VC-JWT (1 by awoie)
https://github.com/w3c/vc-jose-cose/issues/94 [horizontal-review] [before-CR]
- #93 Security and Privacy Self-Review Questionnaire (1 by awoie)
https://github.com/w3c/vc-jose-cose/issues/93 [horizontal-review] [before-CR]
- #67 typ for COSE (2 by Sakurann, cghost420)
https://github.com/w3c/vc-jose-cose/issues/67 [has-pr] [before-CR]
- #64 How to include credential metadata in vc + jwt encoding (2 by David-Chadwick)
https://github.com/w3c/vc-jose-cose/issues/64 [pending-close]
- #52 Describe how `cnf` is allowed to be used for "binding" (1 by iherman)
https://github.com/w3c/vc-jose-cose/issues/52 [has-pr] [before-CR]
- #39 JWT exp claim (1 by iherman)
https://github.com/w3c/vc-jose-cose/issues/39 [has-pr] [before-CR]
- #35 Should we comment on "principle"? (2 by iherman, selfissued)
https://github.com/w3c/vc-jose-cose/issues/35 [pending-close] [post-CR]
- #31 About the optionality of the "kid" field in JWT-formatted VCs/VPs (2 by BigBlueHat, iherman)
https://github.com/w3c/vc-jose-cose/issues/31 [has-pr] [before-CR]
- #30 Accept or Dismiss the guidance provided by DIF on `kid` / `iss` (3 by BigBlueHat, Sakurann, iherman)
https://github.com/w3c/vc-jose-cose/issues/30 [discuss] [has-pr] [before-CR]
- #22 Clarify relationship between "iss" and "issuer" (1 by Sakurann)
https://github.com/w3c/vc-jose-cose/issues/22 [has-pr] [before-CR]
6 issues closed:
- Clarify relationship between validity times https://github.com/w3c/vc-jose-cose/issues/133 [has-pr] [before-CR]
- Should we comment on "principle"? https://github.com/w3c/vc-jose-cose/issues/35 [pending-close] [post-CR]
- JWT - securing mechanism or not? https://github.com/w3c/vc-jose-cose/issues/132 [has-pr]
- typ for COSE https://github.com/w3c/vc-jose-cose/issues/67 [has-pr] [before-CR]
- Better references to OIDC key discovery https://github.com/w3c/vc-jose-cose/issues/127 [has-pr] [before-CR]
- Clarify relationship between "iss" and "issuer" https://github.com/w3c/vc-jose-cose/issues/22 [has-pr] [before-CR]
* w3c/vc-status-list-2021 (+3/-2/💬29)
3 issues created:
- Should validation algorithm check size of bitstring? (by andresuribe87)
https://github.com/w3c/vc-status-list-2021/issues/87
- Add privacy considerations for multi-bit correlation (by msporny)
https://github.com/w3c/vc-status-list-2021/issues/86
- Split design space into two different types of status lists (by msporny)
https://github.com/w3c/vc-status-list-2021/issues/85
14 issues received 29 new comments:
- #86 Add privacy considerations for multi-bit correlation (1 by iherman)
https://github.com/w3c/vc-status-list-2021/issues/86 [before-CR]
- #85 Split design space into two different types of status lists (4 by Sakurann, decentralgabe, iherman, msporny)
https://github.com/w3c/vc-status-list-2021/issues/85
- #84 Cascading status updates (7 by KDean-GS1, Sakurann, brianorwhatever, decentralgabe, iherman, msporny, paulfdietrich)
https://github.com/w3c/vc-status-list-2021/issues/84 [pending 7 day close]
- #82 auto-publishing using echidna? (1 by iherman)
https://github.com/w3c/vc-status-list-2021/issues/82 [before-CR]
- #81 Vocabulary definitions (1 by iherman)
https://github.com/w3c/vc-status-list-2021/issues/81 [before-CR]
- #80 Section 4.3 should be improved to suggest utilization of OHTTP to prevent correlation (2 by Sakurann, kdenhartog)
https://github.com/w3c/vc-status-list-2021/issues/80 [during-CR]
- #64 Add section on expected server HTTP status codes (2 by Sakurann, iherman)
https://github.com/w3c/vc-status-list-2021/issues/64 [ready-for-pr] [before-CR]
- #58 Encoded list in Base64 or Base64Url? (1 by iherman)
https://github.com/w3c/vc-status-list-2021/issues/58 [ready-for-pr] [before-CR]
- #51 Clarify that `StatusList2021Credential` must be VC-DATA-MODEL (v1.1) (1 by iherman)
https://github.com/w3c/vc-status-list-2021/issues/51 [before-CR]
- #50 Versioning (1 by msporny)
https://github.com/w3c/vc-status-list-2021/issues/50 [before-CR]
- #44 clarify protocol for retrieval of a status list (3 by andresuribe87, iherman, jandrieu)
https://github.com/w3c/vc-status-list-2021/issues/44 [ready-for-pr] [before-CR]
- #40 Should "noise" be added during "updates" (1 by iherman)
https://github.com/w3c/vc-status-list-2021/issues/40 [during-CR]
- #14 Can the spec relax/remove the requirement on minimal bit length? (3 by iherman, jandrieu, thehenrytsai)
https://github.com/w3c/vc-status-list-2021/issues/14 [before-CR]
- #12 Add a "reason code" (1 by msporny)
https://github.com/w3c/vc-status-list-2021/issues/12 [before-CR] [pending 7 day close]
2 issues closed:
- Split design space into two different types of status lists https://github.com/w3c/vc-status-list-2021/issues/85
- Versioning https://github.com/w3c/vc-status-list-2021/issues/50 [before-CR]
Pull requests
-------------
* w3c/vc-data-model (+8/-3/💬27)
8 pull requests submitted:
- Fix various aspects of privacy.html (by TallTed)
https://github.com/w3c/vc-data-model/pull/1288
- Sync v2 context with data integrity context. (by dlongley)
https://github.com/w3c/vc-data-model/pull/1287
- Privacy considerations around issuer location (by decentralgabe)
https://github.com/w3c/vc-data-model/pull/1286
- Add normative text requiring protecting VCs and VPs (by andresuribe87)
https://github.com/w3c/vc-data-model/pull/1283
- Add normative requirements related to context processing (by msporny)
https://github.com/w3c/vc-data-model/pull/1281
- Add definition of Verifiable Credential Graph and why it exists (by msporny)
https://github.com/w3c/vc-data-model/pull/1280
- Add links to static copies of vocabulary files and hashes (by msporny)
https://github.com/w3c/vc-data-model/pull/1279
- Base classes are defined now in the spec (by iherman)
https://github.com/w3c/vc-data-model/pull/1278
13 pull requests received 27 new comments:
- #1281 Add normative requirements related to context processing (1 by iherman)
https://github.com/w3c/vc-data-model/pull/1281
- #1280 Add definition of Verifiable Credential Graph and why it exists (1 by iherman)
https://github.com/w3c/vc-data-model/pull/1280
- #1279 Add links to static copies of vocabulary files and hashes (2 by BigBlueHat, iherman)
https://github.com/w3c/vc-data-model/pull/1279
- #1278 Base classes are defined now in the spec (1 by iherman)
https://github.com/w3c/vc-data-model/pull/1278
- #1277 Fix markup, typos, and a small fix. (3 by TallTed, davidlehn, iherman)
https://github.com/w3c/vc-data-model/pull/1277
- #1276 Provide guidance to use compact terms/types instead of full URLs (3 by OR13, TallTed, iherman)
https://github.com/w3c/vc-data-model/pull/1276
- #1272 Add base classes and fragment identifiers for vocabulary. (2 by iherman)
https://github.com/w3c/vc-data-model/pull/1272 [on-track-to-be-merged]
- #1271 Add guidance to not use JSON-LD keywords in @context value. (4 by aphillips, iherman, seabass-labrax)
https://github.com/w3c/vc-data-model/pull/1271 [on-track-to-be-merged]
- #1270 Explain JSON-LD further. (4 by BigBlueHat, TallTed, iherman, nadalin)
https://github.com/w3c/vc-data-model/pull/1270
- #1269 updated entity to include abstract nouns (2 by brentzundel, iherman)
https://github.com/w3c/vc-data-model/pull/1269 [on-track-to-be-merged]
- #1268 Adding the jsonSchema property to the vocabulary (1 by decentralgabe)
https://github.com/w3c/vc-data-model/pull/1268 [before-CR]
- #1260 Add Verification Method types to v2 context (2 by Sakurann, iherman)
https://github.com/w3c/vc-data-model/pull/1260
- #1199 Add validation section regarding holder (1 by iherman)
https://github.com/w3c/vc-data-model/pull/1199
3 pull requests merged:
- Base classes are defined now in the spec
https://github.com/w3c/vc-data-model/pull/1278
- Add validation section regarding holder
https://github.com/w3c/vc-data-model/pull/1199
- Adding the jsonSchema property to the vocabulary
https://github.com/w3c/vc-data-model/pull/1268 [before-CR]
* w3c/vc-use-cases (+1/-0/💬2)
1 pull requests submitted:
- updated verify claim and added validate claim. images still need update (by jandrieu)
https://github.com/w3c/vc-use-cases/pull/149
1 pull requests received 2 new comments:
- #149 updated verify claim and added validate claim. images still need update (2 by iherman, philarcher)
https://github.com/w3c/vc-use-cases/pull/149
* w3c/vc-json-schema (+2/-3/💬3)
2 pull requests submitted:
- Prepare for CR (by decentralgabe)
https://github.com/w3c/vc-json-schema/pull/217
- Address normative references issues (by decentralgabe)
https://github.com/w3c/vc-json-schema/pull/216
1 pull requests received 3 new comments:
- #216 Address normative references issues (3 by decentralgabe, iherman)
https://github.com/w3c/vc-json-schema/pull/216
3 pull requests merged:
- Address normative references issues
https://github.com/w3c/vc-json-schema/pull/216
- Add privacy considerations around data minimization
https://github.com/w3c/vc-json-schema/pull/213
- Address part of 210
https://github.com/w3c/vc-json-schema/pull/212
* w3c/vc-data-integrity (+6/-2/💬5)
6 pull requests submitted:
- Add `previousProof` term mapping definition. (by dlongley)
https://github.com/w3c/vc-data-integrity/pull/202
- Fix context media types served by github pages. (by dlongley)
https://github.com/w3c/vc-data-integrity/pull/201
- Add sections on security/privacy and c14n method selection. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/199
- Add section on previous proof privacy consideration. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/198
- Update status of Multibase and Multihash at IETF. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/197
- Remove normative dependency on Multibase and Multihash. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/196
3 pull requests received 5 new comments:
- #201 Fix context media types served by github pages. (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/201
- #196 Remove normative dependency on Multibase and Multihash. (3 by msporny)
https://github.com/w3c/vc-data-integrity/pull/196
- #189 Updated vocabulary and diagram (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/189
2 pull requests merged:
- Fix context media types served by github pages.
https://github.com/w3c/vc-data-integrity/pull/201
- Updated vocabulary and diagram
https://github.com/w3c/vc-data-integrity/pull/189
* w3c/vc-di-bbs (+1/-0/💬1)
1 pull requests submitted:
- Removing myself from the work item (by OR13)
https://github.com/w3c/vc-di-bbs/pull/91
1 pull requests received 1 new comments:
- #91 Removing myself from the work item (1 by OR13)
https://github.com/w3c/vc-di-bbs/pull/91
* w3c/vc-jwt (+2/-6/💬41)
2 pull requests submitted:
- Use Correct Names for Things (by selfissued)
https://github.com/w3c/vc-jose-cose/pull/156
- Tighten "cnf" claim description (by selfissued)
https://github.com/w3c/vc-jose-cose/pull/155
8 pull requests received 41 new comments:
- #156 Use Correct Names for Things (2 by OR13, iherman)
https://github.com/w3c/vc-jose-cose/pull/156 [editorial]
- #155 Tighten "cnf" claim description (1 by iherman)
https://github.com/w3c/vc-jose-cose/pull/155
- #153 add guidance on kid (3 by OR13, cghost420, iherman)
https://github.com/w3c/vc-jose-cose/pull/153
- #152 point to an ietf cose wg adopted draft for a COSE typ header (1 by Sakurann)
https://github.com/w3c/vc-jose-cose/pull/152
- #151 explain the usage of exp and iat jwt claims (2 by Sakurann, iherman)
https://github.com/w3c/vc-jose-cose/pull/151
- #149 Remove JWT references (keep SD-JWT) (20 by BigBlueHat, OR13, Sakurann, alenhorvat, iherman)
https://github.com/w3c/vc-jose-cose/pull/149
- #147 clarify that what is secured is a document conforming to vcdm (1 by Sakurann)
https://github.com/w3c/vc-jose-cose/pull/147
- #144 Add support for DIDs (11 by OR13, cghost420, iherman, msporny)
https://github.com/w3c/vc-jose-cose/pull/144
6 pull requests merged:
- Remove JWT references (keep SD-JWT)
https://github.com/w3c/vc-jose-cose/pull/149
- explain the usage of exp and iat jwt claims
https://github.com/w3c/vc-jose-cose/pull/151
- clarify that what is secured is a document conforming to vcdm
https://github.com/w3c/vc-jose-cose/pull/147
- point to an ietf cose wg adopted draft for a COSE typ header
https://github.com/w3c/vc-jose-cose/pull/152
- replace openid-configuration well-known URI with jwt issuer well-known URI
https://github.com/w3c/vc-jose-cose/pull/148
- Clarify relationship between "iss" and "issuer"
https://github.com/w3c/vc-jose-cose/pull/146
* w3c/vc-status-list-2021 (+0/-1/💬1)
1 pull requests received 1 new comments:
- #83 Example both with revocation and suspension (1 by brentzundel)
https://github.com/w3c/vc-status-list-2021/pull/83
1 pull requests merged:
- Example both with revocation and suspension
https://github.com/w3c/vc-status-list-2021/pull/83
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 September 2023 17:01:46 UTC