- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 11 Mar 2024 17:01:14 +0000
- To: public-credentials@w3.org
- Message-Id: <E1rjj1W-003eCs-Ph@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+2/-11/💬31)
2 issues created:
- Should we use `Ed25519Signature2020` in the Examples (by iherman)
https://github.com/w3c/vc-data-model/issues/1457 [editorial]
- Do we need sha3-512 in the vocabulary tables (by iherman)
https://github.com/w3c/vc-data-model/issues/1455
19 issues received 31 new comments:
- #1455 Do we need sha3-512 in the vocabulary tables? (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/issues/1455 [editorial] [before-PR]
- #1445 Proposal: remove ambiguity and asymmetry as it relates to subject identifiers (1 by brentzundel)
https://github.com/w3c/vc-data-model/issues/1445 [pending close] [discuss]
- #1442 What does the hash values in §B.2 mean? (2 by iherman)
https://github.com/w3c/vc-data-model/issues/1442 [editorial]
- #1432 first example contains an http url identifying a credential (2 by decentralgabe, iherman)
https://github.com/w3c/vc-data-model/issues/1432 [editorial] [ready for PR]
- #1431 EnvelopedVerifiablePresentation missing in data model (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/issues/1431 [pr exists] [normative] [CR1]
- #1424 Unnecessary direction attribute? (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/issues/1424 [editorial] [pr exists] [CR2]
- #1410 Does the specification need a normative "Credential Type Specifications" section? (1 by brentzundel)
https://github.com/w3c/vc-data-model/issues/1410 [pending close] [CR2]
- #1388 Specify what kind of processing is safe on a returned document (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/issues/1388 [editorial] [pr exists] [CR1]
- #1359 Authorized Presenters (3 by decentralgabe, iherman, jandrieu)
https://github.com/w3c/vc-data-model/issues/1359 [ready for PR] [discuss] [post-CR]
- #1348 Non-normative changes from Jeffrey Yasskin's review (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1348 [ready for PR] [post-CR]
- #1303 Remove the at risk issue marker for `Evidence` (1 by brentzundel)
https://github.com/w3c/vc-data-model/issues/1303 [pending close] [before-PR]
- #1291 Multiple Credential Status Lists (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/issues/1291 [editorial] [pr exists] [CR1]
- #1274 Tell a bit more about `verificationMethod` type schema (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/issues/1274 [editorial] [pr exists] [CR1]
- #1254 Section title and contents mismatch on "Complex Language Markup" (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1254 [post-CR]
- #1239 `expires` header for https://www.w3.org/2018/credentials/v1 is in the past (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1239 [before-PR]
- #1197 Define `verification material` find replace `public keys` (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1197 [editorial] [post-CR]
- #1192 Explain that natural language examples are illustrative (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/issues/1192 [editorial] [pr exists] [i18n-needs-resolution] [CR1]
- #1176 Define what a credential validity does mean (2 by filip26, iherman)
https://github.com/w3c/vc-data-model/issues/1176 [post-CR]
- #995 [Terminology] claim (1 by brentzundel)
https://github.com/w3c/vc-data-model/issues/995 [pending close] [terminology] [post-CR]
11 issues closed:
- EnvelopedVerifiablePresentation missing in data model https://github.com/w3c/vc-data-model/issues/1431 [pr exists] [normative] [CR1]
- Unnecessary direction attribute? https://github.com/w3c/vc-data-model/issues/1424 [editorial] [pr exists] [CR2]
- Specify what kind of processing is safe on a returned document https://github.com/w3c/vc-data-model/issues/1388 [editorial] [pr exists] [CR1]
- Multiple Credential Status Lists https://github.com/w3c/vc-data-model/issues/1291 [editorial] [pr exists] [CR1]
- Tell a bit more about `verificationMethod` type schema https://github.com/w3c/vc-data-model/issues/1274 [editorial] [pr exists] [CR1]
- Explain that natural language examples are illustrative https://github.com/w3c/vc-data-model/issues/1192 [editorial] [pr exists] [i18n-needs-resolution] [CR1]
- Define what a credential validity does mean https://github.com/w3c/vc-data-model/issues/1176 [post-CR]
- Remove the at risk issue marker for `Evidence` https://github.com/w3c/vc-data-model/issues/1303 [pending close] [before-PR]
- Does the specification need a normative "Credential Type Specifications" section? https://github.com/w3c/vc-data-model/issues/1410 [pending close] [CR2]
- Proposal: remove ambiguity and asymmetry as it relates to subject identifiers https://github.com/w3c/vc-data-model/issues/1445 [pending close] [discuss]
- [Terminology] claim https://github.com/w3c/vc-data-model/issues/995 [pending close] [terminology] [post-CR]
* w3c/vc-data-integrity (+2/-0/💬2)
2 issues created:
- Wrong cryptosuite name in example (by iherman)
https://github.com/w3c/vc-data-integrity/issues/252
- Editorial: add a reference to the cryptosuites in the section on Multikeys (by iherman)
https://github.com/w3c/vc-data-integrity/issues/251 [editorial]
2 issues received 2 new comments:
- #252 Wrong cryptosuite name in example (1 by iherman)
https://github.com/w3c/vc-data-integrity/issues/252 [pr exists] [editorial]
- #245 Editorial: `type` must be a URL (1 by iherman)
https://github.com/w3c/vc-data-integrity/issues/245 [CR1] [editorial]
* w3c/vc-di-bbs (+0/-3/💬9)
5 issues received 9 new comments:
- #139 Proof `created` should be optional (1 by msporny)
https://github.com/w3c/vc-di-bbs/issues/139 [PR-exists]
- #136 Specification should clearly identify BBS+ (not BBS) (1 by msporny)
https://github.com/w3c/vc-di-bbs/issues/136 [editorial]
- #134 Tell implementers to use major type 2 encoding (not tag 64 -- Uint8Array) for CBOR (1 by msporny)
https://github.com/w3c/vc-di-bbs/issues/134 [PR-exists]
- #127 Add at-risk marker and enable passing in `pid` and `verifier ID` for pseudonym support from BBS spec (5 by Wind4Greg, dlongley, msporny)
https://github.com/w3c/vc-di-bbs/issues/127
- #114 "XML Schema formatted date string" not specific enough (1 by msporny)
https://github.com/w3c/vc-di-bbs/issues/114 [pending-close] [i18n-needs-resolution] [PR-exists]
3 issues closed:
- Tell implementers to use major type 2 encoding (not tag 64 -- Uint8Array) for CBOR https://github.com/w3c/vc-di-bbs/issues/134 [PR-exists]
- "XML Schema formatted date string" not specific enough https://github.com/w3c/vc-di-bbs/issues/114 [pending-close] [i18n-needs-resolution] [PR-exists]
- Proof `created` should be optional https://github.com/w3c/vc-di-bbs/issues/139 [PR-exists]
* w3c/vc-jwt (+1/-6/💬4)
1 issues created:
- Example of JWT presentation is incorrect (by OR13)
https://github.com/w3c/vc-jose-cose/issues/255
3 issues received 4 new comments:
- #216 Inconsistent sectioning? (1 by iherman)
https://github.com/w3c/vc-jose-cose/issues/216 [editorial]
- #207 COSE algorithms and examples not specified (1 by decentralgabe)
https://github.com/w3c/vc-jose-cose/issues/207 [before-CR]
- #206 Algorithms are poorly defined / unimplementable (2 by iherman, selfissued)
https://github.com/w3c/vc-jose-cose/issues/206 [before-CR]
6 issues closed:
- Inconsistent sectioning? https://github.com/w3c/vc-jose-cose/issues/216 [editorial]
- Example of JWT presentation is incorrect https://github.com/w3c/vc-jose-cose/issues/255 [editorial] [has-pr] [before-CR]
- Improve language around holder binding https://github.com/w3c/vc-jose-cose/issues/242 [has-pr] [before-CR]
- Question on the SD-JWT-VC normative reference https://github.com/w3c/vc-jose-cose/issues/218 [has-pr] [before-CR]
- Media types are incorrect; usage can't be counted on https://github.com/w3c/vc-jose-cose/issues/204 [has-pr] [before-CR]
- Register COSE Media Type Suffixes https://github.com/w3c/vc-jose-cose/issues/224 [has-pr] [before-CR]
* w3c/vc-status-list-2021 (+9/-0/💬11)
9 issues created:
- describe dummy or decoy entries as a privacy mitigation (by npdoty)
https://github.com/w3c/vc-bitstring-status-list/issues/150 [privacy-needs-resolution]
- status list index randomization requirement (by npdoty)
https://github.com/w3c/vc-bitstring-status-list/issues/149 [privacy-needs-resolution]
- comparison with alternative revocation mechanisms (by npdoty)
https://github.com/w3c/vc-bitstring-status-list/issues/148 [privacy-tracker]
- when revocation status is and isn't appropriate to present (by npdoty)
https://github.com/w3c/vc-bitstring-status-list/issues/147 [privacy-needs-resolution]
- information revealed by status updates (by npdoty)
https://github.com/w3c/vc-bitstring-status-list/issues/146 [privacy-needs-resolution]
- anonymizing proxy rather than CDN as a privacy mitigation (by npdoty)
https://github.com/w3c/vc-bitstring-status-list/issues/145 [privacy-needs-resolution]
- caching status lists as a mitigation for identifying when the holder visited a verifier (by npdoty)
https://github.com/w3c/vc-bitstring-status-list/issues/144 [privacy-needs-resolution]
- mitigations for risk of unique status lists (by npdoty)
https://github.com/w3c/vc-bitstring-status-list/issues/143
- status list index is a persistent cross-origin identifier (by npdoty)
https://github.com/w3c/vc-bitstring-status-list/issues/142 [privacy-needs-resolution]
9 issues received 11 new comments:
- #150 describe dummy or decoy entries as a privacy mitigation (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/150 [privacy-needs-resolution]
- #149 status list index randomization requirement (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/149 [privacy-needs-resolution]
- #148 comparison with alternative revocation mechanisms (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/148 [privacy-tracker]
- #147 when revocation status is and isn't appropriate to present (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/147 [privacy-needs-resolution]
- #146 information revealed by status updates (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/146 [privacy-needs-resolution]
- #145 anonymizing proxy rather than CDN as a privacy mitigation (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/145 [privacy-needs-resolution]
- #144 caching status lists as a mitigation for identifying when the holder visited a verifier (1 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/144 [ready-for-pr] [before-CR] [privacy-needs-resolution] [normative]
- #143 mitigations for risk of unique status lists (2 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/143 [privacy-needs-resolution]
- #142 status list index is a persistent cross-origin identifier (2 by msporny)
https://github.com/w3c/vc-bitstring-status-list/issues/142 [privacy-needs-resolution]
Pull requests
-------------
* w3c/vc-data-model (+2/-5/💬14)
2 pull requests submitted:
- Registered Structured Syntax Suffix (by selfissued)
https://github.com/w3c/vc-data-model/pull/1456
- Updating the text on vocabulary hashes (by iherman)
https://github.com/w3c/vc-data-model/pull/1454
6 pull requests received 14 new comments:
- #1456 Registered Structured Syntax Suffix (1 by OR13)
https://github.com/w3c/vc-data-model/pull/1456
- #1453 Add section on enveloped verifiable presentations. (3 by iherman, msporny)
https://github.com/w3c/vc-data-model/pull/1453 [normative] [CR1]
- #1452 Remove note on verification methods; refactor proof validation section. (4 by TallTed, iherman, msporny)
https://github.com/w3c/vc-data-model/pull/1452 [editorial] [CR1]
- #1451 Add language related to validation expectations. (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/pull/1451 [editorial] [CR1]
- #1450 Clarify that credential status can have multiple entries. (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/pull/1450 [editorial] [CR1]
- #1449 Add warning about English descriptions being illustrative. (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/pull/1449 [editorial] [CR1]
5 pull requests merged:
- Add section on enveloped verifiable presentations.
https://github.com/w3c/vc-data-model/pull/1453 [normative] [CR1]
- Remove note on verification methods; refactor proof validation section.
https://github.com/w3c/vc-data-model/pull/1452 [editorial] [CR1]
- Add language related to validation expectations.
https://github.com/w3c/vc-data-model/pull/1451 [editorial] [CR1]
- Clarify that credential status can have multiple entries.
https://github.com/w3c/vc-data-model/pull/1450 [editorial] [CR1]
- Add warning about English descriptions being illustrative.
https://github.com/w3c/vc-data-model/pull/1449 [editorial] [CR1]
* w3c/vc-data-integrity (+2/-0/💬0)
2 pull requests submitted:
- Added the proposed sentence for verification method type of issue 245 (by iherman)
https://github.com/w3c/vc-data-integrity/pull/254
- Updated the cryptosuite references (by iherman)
https://github.com/w3c/vc-data-integrity/pull/253
* w3c/vc-di-bbs (+2/-3/💬5)
2 pull requests submitted:
- Pseudonyms and Anonymous Holder Binding optional features (by Wind4Greg)
https://github.com/w3c/vc-di-bbs/pull/145
- Update algorithms to align with new cryptosuite interface (by msporny)
https://github.com/w3c/vc-di-bbs/pull/144
4 pull requests received 5 new comments:
- #145 Pseudonyms and Anonymous Holder Binding optional features (2 by TallTed, Wind4Greg)
https://github.com/w3c/vc-di-bbs/pull/145
- #143 Specify HMAC key size (1 by msporny)
https://github.com/w3c/vc-di-bbs/pull/143
- #142 Constrain CBOR encoding to not use tags on components (1 by msporny)
https://github.com/w3c/vc-di-bbs/pull/142
- #141 Update Proof Configuration Procedure to Pass Through Proof options (1 by msporny)
https://github.com/w3c/vc-di-bbs/pull/141
3 pull requests merged:
- Specify HMAC key size
https://github.com/w3c/vc-di-bbs/pull/143
- Constrain CBOR encoding to not use tags on components
https://github.com/w3c/vc-di-bbs/pull/142
- Update Proof Configuration Procedure to Pass Through Proof options
https://github.com/w3c/vc-di-bbs/pull/141
* w3c/vc-jwt (+4/-6/💬3)
4 pull requests submitted:
- fix typos (by TallTed)
https://github.com/w3c/vc-jose-cose/pull/257
- Update JOSE VP example (by decentralgabe)
https://github.com/w3c/vc-jose-cose/pull/256
- Rename Appendix to Examples (by selfissued)
https://github.com/w3c/vc-jose-cose/pull/254
- Fix section numbering (by selfissued)
https://github.com/w3c/vc-jose-cose/pull/253
2 pull requests received 3 new comments:
- #256 Update JOSE VP example (2 by decentralgabe)
https://github.com/w3c/vc-jose-cose/pull/256
- #253 Fix section numbering (1 by decentralgabe)
https://github.com/w3c/vc-jose-cose/pull/253
6 pull requests merged:
- fix typos
https://github.com/w3c/vc-jose-cose/pull/257
- Update JOSE VP example
https://github.com/w3c/vc-jose-cose/pull/256
- Recommend the use of proof of possession
https://github.com/w3c/vc-jose-cose/pull/252
- Mark uses of SD-JWT-VC as being at risk
https://github.com/w3c/vc-jose-cose/pull/251
- Fix section numbering
https://github.com/w3c/vc-jose-cose/pull/253
- Registered structured suffixes
https://github.com/w3c/vc-jose-cose/pull/249
* w3c/vc-status-list-2021 (+0/-0/💬4)
1 pull requests received 4 new comments:
- #138 added human readable/machine readable, changed example to be more clear. (4 by aphillips, mkhraisha, msporny)
https://github.com/w3c/vc-bitstring-status-list/pull/138
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, 11 March 2024 17:01:16 UTC