- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 01 Jan 2024 17:01:15 +0000
- To: public-credentials@w3.org
- Message-Id: <E1rKLf9-003Go6-S2@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+2/-5/💬12)
2 issues created:
- phrasing and/or punctuation for input "inputBytes or inputDocument and inputMediaType" needs work (by TallTed)
https://github.com/w3c/vc-data-model/issues/1402
- Clarify embedded proof extension point (by msporny)
https://github.com/w3c/vc-data-model/issues/1400 [before-CR]
10 issues received 12 new comments:
- #1402 phrasing and/or punctuation for input "inputBytes or inputDocument and inputMediaType" needs work (2 by TallTed, msporny)
https://github.com/w3c/vc-data-model/issues/1402 [ready for PR]
- #1400 Clarify embedded proof extension point (1 by msporny)
https://github.com/w3c/vc-data-model/issues/1400 [ready for PR] [before-CR]
- #1399 Verifying a VC should return the same credential regardless of the verification method (1 by msporny)
https://github.com/w3c/vc-data-model/issues/1399 [pr exists] [before-CR]
- #1398 Ensure `credentialStatus` `id` field is optional (1 by msporny)
https://github.com/w3c/vc-data-model/issues/1398 [ready for PR] [before-CR]
- #1386 Specify that it is important to validate the `issuer` value (1 by msporny)
https://github.com/w3c/vc-data-model/issues/1386 [pr exists] [before-CR]
- #1384 Allow extensions to ProblemDetails object (1 by msporny)
https://github.com/w3c/vc-data-model/issues/1384 [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]
- #1365 Clarify section on verifiable credential graph (1 by msporny)
https://github.com/w3c/vc-data-model/issues/1365 [pr exists] [before-CR]
- #1316 Update 4.9 Securing Verifiable Credentials (2 by TallTed, msporny)
https://github.com/w3c/vc-data-model/issues/1316 [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]
5 issues closed:
- Verifying a VC should return the same credential regardless of the verification method https://github.com/w3c/vc-data-model/issues/1399 [pr exists] [before-CR]
- Specify that it is important to validate the `issuer` value https://github.com/w3c/vc-data-model/issues/1386 [pr exists] [before-CR]
- Allow extensions to ProblemDetails object https://github.com/w3c/vc-data-model/issues/1384 [pr exists] [before-CR]
- Clarify section on verifiable credential graph https://github.com/w3c/vc-data-model/issues/1365 [pr exists] [before-CR]
- Define algorithm for verification https://github.com/w3c/vc-data-model/issues/1337 [pr exists] [pending close] [before-CR]
* w3c/vc-data-integrity (+1/-0/💬2)
1 issues created:
- cryptosuite missing from property list in 2.1 Proofs (by HelgeKrueger)
https://github.com/w3c/vc-data-integrity/issues/232
2 issues received 2 new comments:
- #232 cryptosuite missing from property list in 2.1 Proofs (1 by dlongley)
https://github.com/w3c/vc-data-integrity/issues/232
- #190 Add explanation about why proof graphs are used (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/190 [during CR]
* w3c/vc-di-eddsa (+0/-2/💬2)
2 issues received 2 new comments:
- #66 Fix byte length of `publickKeyMultibase` to 34 (1 by msporny)
https://github.com/w3c/vc-di-eddsa/issues/66
- #38 Is Example 15 / 16 correct? (1 by msporny)
https://github.com/w3c/vc-di-eddsa/issues/38 [during CR]
2 issues closed:
- Is Example 15 / 16 correct? https://github.com/w3c/vc-di-eddsa/issues/38 [during CR]
- Fix byte length of `publickKeyMultibase` to 34 https://github.com/w3c/vc-di-eddsa/issues/66
* w3c/vc-di-ecdsa (+0/-2/💬2)
2 issues received 2 new comments:
- #26 Clarifying `publicKeyMultibase` encoding: `did:key` style with multicodec code, or not? (1 by msporny)
https://github.com/w3c/vc-di-ecdsa/issues/26 [question] [during CR]
- #22 Confirming `EcdsaSecp256r1VerificationKey2019` -> `Multikey` transition (1 by msporny)
https://github.com/w3c/vc-di-ecdsa/issues/22 [question] [during CR]
2 issues closed:
- Clarifying `publicKeyMultibase` encoding: `did:key` style with multicodec code, or not? https://github.com/w3c/vc-di-ecdsa/issues/26 [question] [during CR]
- Confirming `EcdsaSecp256r1VerificationKey2019` -> `Multikey` transition https://github.com/w3c/vc-di-ecdsa/issues/22 [question] [during CR]
* w3c/vc-jwt (+12/-1/💬8)
12 issues created:
- Inconsistent versions (by David-Chadwick)
https://github.com/w3c/vc-jose-cose/issues/214
- Remove mentions of "proof" from Section 6.1 (by msporny)
https://github.com/w3c/vc-jose-cose/issues/211 [post-CR]
- Example 13 description is wrong (by msporny)
https://github.com/w3c/vc-jose-cose/issues/210 [before-CR]
- Allow key format conversion (by msporny)
https://github.com/w3c/vc-jose-cose/issues/209 [before-CR]
- Data format for COSE_Key expression in Controller Document is undefined (by msporny)
https://github.com/w3c/vc-jose-cose/issues/208 [before-CR]
- COSE algorithms and examples not specified (by msporny)
https://github.com/w3c/vc-jose-cose/issues/207 [before-CR]
- Algorithms are poorly defined / unimplementable (by msporny)
https://github.com/w3c/vc-jose-cose/issues/206
- Unclear semantics wrt. JWT claims vs. VC properties (by msporny)
https://github.com/w3c/vc-jose-cose/issues/205 [before-CR]
- Media types are incorrect (by msporny)
https://github.com/w3c/vc-jose-cose/issues/204 [before-CR]
- Section on Wallets is not necessary (by msporny)
https://github.com/w3c/vc-jose-cose/issues/203 [post-CR]
- Conformance classes are not defined (by msporny)
https://github.com/w3c/vc-jose-cose/issues/202 [before-CR]
- Support JWT-secured VCs (by msporny)
https://github.com/w3c/vc-jose-cose/issues/201 [before-CR]
8 issues received 8 new comments:
- #214 Inconsistent versions (1 by David-Chadwick)
https://github.com/w3c/vc-jose-cose/issues/214
- #201 Support JWT-secured VCs (1 by David-Chadwick)
https://github.com/w3c/vc-jose-cose/issues/201 [before-CR]
- #199 Add an example for selective disclosure (1 by TallTed)
https://github.com/w3c/vc-jose-cose/issues/199 [post-CR]
- #195 Horizontal Review Tracking (1 by TallTed)
https://github.com/w3c/vc-jose-cose/issues/195 [horizontal-review]
- #191 Do we need an SD-JWT profile for W3C VCs? (1 by David-Chadwick)
https://github.com/w3c/vc-jose-cose/issues/191
- #184 Adjust Explicit Typing Guidance regarding `typ` (1 by TallTed)
https://github.com/w3c/vc-jose-cose/issues/184 [post-CR]
- #179 Change the registration request for SD-JWT (1 by TallTed)
https://github.com/w3c/vc-jose-cose/issues/179 [post-CR]
- #160 Controller Documents vs DID Documents (1 by TallTed)
https://github.com/w3c/vc-jose-cose/issues/160 [post-CR]
1 issues closed:
- Text about obtaining the right verification key https://github.com/w3c/vc-jose-cose/issues/194
* w3c/vc-status-list-2021 (+3/-5/💬39)
3 issues created:
- Remove `ttl` (by dlongley)
https://github.com/w3c/vc-bitstring-status-list/issues/120
- Rename `reference` to `statusReference` (by dlongley)
https://github.com/w3c/vc-bitstring-status-list/issues/114
- Rename "size" to "statusSize" (by dlongley)
https://github.com/w3c/vc-bitstring-status-list/issues/113
27 issues received 39 new comments:
- #113 Rename "size" to "statusSize" (3 by dlongley, msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/113 [ready-for-pr] [before-CR]
- #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 [ready-for-pr] [before-CR]
- #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]
- #94 Precise timestamps of status changes (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/94 [ready-for-pr] [before-CR]
- #93 Bytestring structure and ietf status list (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/93 [before-CR]
- #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]
- #82 auto-publishing using echidna? (3 by iherman, msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/82 [before-CR]
- #81 Vocabulary definitions (2 by iherman, msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/81 [before-CR]
- #80 Section 4.3 should be improved to suggest utilization of OHTTP to prevent correlation (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/80 [during-CR]
- #78 Media type pairings (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/78 [before-CR] [pr exists]
- #73 Unify design of status lists to support multi-bit values (5 by msporny, samuelmr)
https://github.com/w3c/vc-bitstring-status-list/issues/73 [wontfix] [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 [ready-for-pr] [before-CR]
- #58 Encoded list in Base64 or Base64Url? (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/58 [ready-for-pr] [before-CR]
- #56 Implementation Considerations (2 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/56 [before-CR]
- #54 How to understand herd privacy in using bit string? (2 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/54 [question] [before-CR]
- #52 Implementation guidelines around how StatusList2021Credential is secured/encoded. (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/52 [before-CR]
- #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]
- #47 Is it possible to support multiple purposes? (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/47 [question] [before-CR]
- #44 clarify protocol for retrieval of a status list (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/44 [ready-for-pr] [before-CR]
- #42 Would like multiple status to be capable of representation in a status list (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/42 [before-CR]
- #36 Specify bit order for status list (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/36 [before-CR] [pr exists]
- #35 Status of what? (2 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/35 [ready-for-pr] [before-CR]
- #25 Revocation or Suspension Date (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/25 [before-CR]
- #23 Handling Right to Erasure in encodedList and Validate Algorithm (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/23 [before-CR]
- #17 Add vocabulary document (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/17 [before-CR]
5 issues closed:
- How to understand herd privacy in using bit string? https://github.com/w3c/vc-bitstring-status-list/issues/54 [question] [before-CR]
- Vocabulary definitions https://github.com/w3c/vc-bitstring-status-list/issues/81 [before-CR]
- Would like multiple status to be capable of representation in a status list https://github.com/w3c/vc-bitstring-status-list/issues/42 [before-CR]
- Specify bit order for status list https://github.com/w3c/vc-bitstring-status-list/issues/36 [before-CR] [pr exists]
- Media type pairings https://github.com/w3c/vc-bitstring-status-list/issues/78 [before-CR] [pr exists]
Pull requests
-------------
* w3c/vc-data-model (+6/-7/💬15)
6 pull requests submitted:
- Example diagrams multiple credentials (by iherman)
https://github.com/w3c/vc-data-model/pull/1407 [editorial]
- Update context to include latest BitstringStatusList changes. (by msporny)
https://github.com/w3c/vc-data-model/pull/1406
- Add RANGE_ERROR to list of potential errors. (by msporny)
https://github.com/w3c/vc-data-model/pull/1405 [before-CR]
- Jwt example diagrams (by iherman)
https://github.com/w3c/vc-data-model/pull/1404 [editorial]
- Add embedded securing mechanism specification requirements (by msporny)
https://github.com/w3c/vc-data-model/pull/1403
- Refine status language and make credential status `id` optional. (by msporny)
https://github.com/w3c/vc-data-model/pull/1401
10 pull requests received 15 new comments:
- #1406 Update context to include latest BitstringStatusList changes. (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1406 [before-CR]
- #1404 Jwt example diagrams (3 by iherman)
https://github.com/w3c/vc-data-model/pull/1404 [editorial]
- #1403 Add embedded securing mechanism specification requirements (2 by msporny)
https://github.com/w3c/vc-data-model/pull/1403 [before-CR]
- #1395 Add missing digestMultibase value in base context. (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1395 [post-CR]
- #1394 Use new Securing Mechanism Verify Proof interface (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1394 [before-CR]
- #1393 Clarify how issuer validation occurs. (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1393 [before-CR]
- #1391 Clarify that ProblemDetails can be extended for any reason. (2 by TallTed, msporny)
https://github.com/w3c/vc-data-model/pull/1391 [before-CR]
- #1390 Clarify that non-objects aren't allowed as VC graphs. (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1390 [before-CR]
- #1389 Clarify that "proof" is an extension point (2 by msporny)
https://github.com/w3c/vc-data-model/pull/1389 [before-CR]
- #1387 Updating the vocab diagram (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1387 [before-CR]
7 pull requests merged:
- Use new Securing Mechanism Verify Proof interface
https://github.com/w3c/vc-data-model/pull/1394 [before-CR]
- Clarify how issuer validation occurs.
https://github.com/w3c/vc-data-model/pull/1393 [before-CR]
- Clarify that "proof" is an extension point
https://github.com/w3c/vc-data-model/pull/1389 [before-CR]
- Add missing digestMultibase value in base context.
https://github.com/w3c/vc-data-model/pull/1395 [post-CR]
- Clarify that ProblemDetails can be extended for any reason.
https://github.com/w3c/vc-data-model/pull/1391 [before-CR]
- Clarify that non-objects aren't allowed as VC graphs.
https://github.com/w3c/vc-data-model/pull/1390 [before-CR]
- Updating the vocab diagram
https://github.com/w3c/vc-data-model/pull/1387 [before-CR]
* w3c/vc-data-integrity (+0/-2/💬2)
2 pull requests received 2 new comments:
- #230 Define proof properties no longer defined in VCDM (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/230
- #224 Binding Proof Chains Together (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/224 [normative]
2 pull requests merged:
- Define proof properties no longer defined in VCDM
https://github.com/w3c/vc-data-integrity/pull/230
- Binding Proof Chains Together
https://github.com/w3c/vc-data-integrity/pull/224 [normative]
* w3c/vc-di-eddsa (+0/-2/💬3)
2 pull requests received 3 new comments:
- #70 Proof Set and Chain Test Vectors (1 by msporny)
https://github.com/w3c/vc-di-eddsa/pull/70 [editorial]
- #67 Fix byte length of `publickKeyMultibase`. (2 by msporny)
https://github.com/w3c/vc-di-eddsa/pull/67 [normative]
2 pull requests merged:
- Proof Set and Chain Test Vectors
https://github.com/w3c/vc-di-eddsa/pull/70 [editorial]
- Fix byte length of `publickKeyMultibase`.
https://github.com/w3c/vc-di-eddsa/pull/67 [normative]
* w3c/vc-di-ecdsa (+0/-1/💬1)
1 pull requests received 1 new comments:
- #46 Fix skolemize existing blank node identifier bug. (1 by msporny)
https://github.com/w3c/vc-di-ecdsa/pull/46 [normative]
1 pull requests merged:
- Fix skolemize existing blank node identifier bug.
https://github.com/w3c/vc-di-ecdsa/pull/46 [normative]
* w3c/vc-jwt (+3/-1/💬1)
3 pull requests submitted:
- Improving explanation of SD-JWT (by David-Chadwick)
https://github.com/w3c/vc-jose-cose/pull/215
- Update Abstract (by David-Chadwick)
https://github.com/w3c/vc-jose-cose/pull/213
- Update Title (by David-Chadwick)
https://github.com/w3c/vc-jose-cose/pull/212
1 pull requests received 1 new comments:
- #186 Remove requests for multiple suffixes (1 by TallTed)
https://github.com/w3c/vc-jose-cose/pull/186
1 pull requests merged:
- Reference Key Discovery section
https://github.com/w3c/vc-jose-cose/pull/200
* w3c/vc-status-list-2021 (+16/-0/💬10)
16 pull requests submitted:
- Add at risk issue marker regarding multibit status entries. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/123
- Add examples for multiple status lists and multiple entries in a single status list (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/122
- Rename "herd" to "group" privacy. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/121
- Add "at risk" marker noting bitstring format might change in CR. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/119
- Add guidance on how to secure status lists. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/118
- Add privacy consideration section about Multistatus Correlation. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/117
- Raise malformed value error on malformed values. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/116
- Raise error when status list size does not meet minimum threshold. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/115
- Add mechanism to retrieve historical status list information. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/112
- Add section on Processing Errors. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/111
- Clarify base64 encoding as base64url encoding. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/110
- Update BitstringStatusList context to align with latest spec. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/109
- Update VCDM dependency to VCDM v2.0. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/108
- Add protocol statements related to pub/sub of status lists. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/107
- Clarify what credential status information is about. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/106
- Add formal vocabulary definitions. (by msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/105
2 pull requests received 10 new comments:
- #121 Rename "herd privacy" to "group privacy". (2 by kimdhamilton, msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/121
- #105 Add formal vocabulary definitions. (8 by iherman, msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/105
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, 1 January 2024 17:01:19 UTC