- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 22 Jan 2024 17:01:25 +0000
- To: public-credentials@w3.org
- Message-Id: <E1rRxfp-00CKcw-My@uranus.w3.org>
Issues ------ * w3c/vc-data-model (+1/-1/💬13) 1 issues created: - `Type-Specific Credential Processing` is better phrasing than `Credential Type-Specific Processing` (by TallTed) https://github.com/w3c/vc-data-model/issues/1415 8 issues received 13 new comments: - #1410 Does the specification need a normative "Credential Specifications" section? (1 by iherman) https://github.com/w3c/vc-data-model/issues/1410 [CR2] - #1316 Update 4.9 Securing Verifiable Credentials (1 by brentzundel) https://github.com/w3c/vc-data-model/issues/1316 [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] [post-CR] - #1098 Clarify what "reserved properties might be more formally defined in future versions" means (2 by brentzundel, iherman) https://github.com/w3c/vc-data-model/issues/1098 [editorial] [post-CR] - #981 ManualRefreshService2018 - what exactly is it? (1 by iherman) https://github.com/w3c/vc-data-model/issues/981 [editorial] [ready for PR] [question] [refresh] [post-CR] - #942 Clarify role of Holder (was: Create the new role of issuee) (5 by TallTed, agropper, iherman, jandrieu) https://github.com/w3c/vc-data-model/issues/942 [pending close] [discuss] [terminology] [post-CR] - #926 Definition of evidence should align with NIST (1 by iherman) https://github.com/w3c/vc-data-model/issues/926 [ready for PR] [pending close] [evidence] [post-CR] - #887 What is the action associated with issuing/creating a Verifiable Presentation? (1 by iherman) https://github.com/w3c/vc-data-model/issues/887 [ready for PR] [post-CR] 1 issues closed: - Update 4.9 Securing Verifiable Credentials https://github.com/w3c/vc-data-model/issues/1316 [pending close] [post-CR] * w3c/vc-use-cases (+1/-0/💬0) 1 issues created: - Check existing examples against VC2.0 spec (by jandrieu) https://github.com/w3c/vc-use-cases/issues/152 * w3c/vc-data-integrity (+1/-0/💬1) 1 issues created: - Replace jcs-eddsa-2022 with eddsa-jcs-2022 in examples (by silverpill) https://github.com/w3c/vc-data-integrity/issues/239 1 issues received 1 new comments: - #239 Replace jcs-eddsa-2022 with eddsa-jcs-2022 in examples (1 by Wind4Greg) https://github.com/w3c/vc-data-integrity/issues/239 * w3c/vc-di-eddsa (+1/-0/💬0) 1 issues created: - Some examples have the wrong / old context version (by dlongley) https://github.com/w3c/vc-di-eddsa/issues/75 * w3c/vc-di-ecdsa (+2/-0/💬2) 2 issues created: - Update contexts in examples (by dlongley) https://github.com/w3c/vc-di-ecdsa/issues/53 - Tell implementers to use major type 2 encoding (not tag 64 -- Uint8Array) for CBOR (by dlongley) https://github.com/w3c/vc-di-ecdsa/issues/52 1 issues received 2 new comments: - #53 Update contexts in examples (2 by Wind4Greg, dlongley) https://github.com/w3c/vc-di-ecdsa/issues/53 * w3c/vc-di-bbs (+2/-0/💬5) 2 issues created: - Tell implementers to use major type 2 encoding (not tag 64 -- Uint8Array) for CBOR (by dlongley) https://github.com/w3c/vc-di-bbs/issues/134 - Outdated reference in the spec (by iherman) https://github.com/w3c/vc-di-bbs/issues/132 3 issues received 5 new comments: - #134 Tell implementers to use major type 2 encoding (not tag 64 -- Uint8Array) for CBOR (3 by Wind4Greg, dlongley) https://github.com/w3c/vc-di-bbs/issues/134 - #114 "XML Schema formatted date string" not specific enough (1 by aphillips) https://github.com/w3c/vc-di-bbs/issues/114 [i18n-needs-resolution] - #102 Accessibility Self-Review for VC DI BBS (1 by matatk) https://github.com/w3c/vc-di-bbs/issues/102 [a11y-tracker] * w3c/vc-jwt (+1/-0/💬2) 1 issues created: - Potential problem with Example 2 (by iherman) https://github.com/w3c/vc-jose-cose/issues/222 [before-CR] 1 issues received 2 new comments: - #222 Potential problem with Example 2 (2 by TallTed, iherman) https://github.com/w3c/vc-jose-cose/issues/222 [before-CR] * w3c/vc-status-list-2021 (+3/-3/💬14) 3 issues created: - Horizontal Reviews for Bitstring Status List v1.0 (by msporny) https://github.com/w3c/vc-bitstring-status-list/issues/133 [before-CR] - Internationalization Self-Review for Bitstring Status List v1.0 (by msporny) https://github.com/w3c/vc-bitstring-status-list/issues/132 [i18n-tracker] - Accessibility self-review of Bitstring Status List v1.0 (by msporny) https://github.com/w3c/vc-bitstring-status-list/issues/131 8 issues received 14 new comments: - #127 "bitstring" vs "bit string" (2 by TallTed, iherman) https://github.com/w3c/vc-bitstring-status-list/issues/127 [discuss] [before-CR] - #125 Add `@type` to `encodedList` term definition (2 by iherman, msporny) https://github.com/w3c/vc-bitstring-status-list/issues/125 [before-CR] [pr exists] - #124 Matching of VC issuer and Status List VC issuer - MAY vs MUST (3 by dmitrizagidulin, iherman, msporny) https://github.com/w3c/vc-bitstring-status-list/issues/124 [before-CR] [pr exists] - #120 Remove `ttl` (2 by iherman, msporny) https://github.com/w3c/vc-bitstring-status-list/issues/120 [before-CR] [pr exists] - #93 Align bitstring structure and IETF Token Status List structure? (1 by TallTed) https://github.com/w3c/vc-bitstring-status-list/issues/93 [during-CR] - #77 Security and Privacy Questionnaire (1 by iherman) https://github.com/w3c/vc-bitstring-status-list/issues/77 [before-CR] [privacy-review] [security-review] - #72 TAG Review Request -- Submitted (2 by iherman, msporny) https://github.com/w3c/vc-bitstring-status-list/issues/72 [before-CR] - #23 Handling Right to Erasure in encodedList and Validate Algorithm (1 by TallTed) https://github.com/w3c/vc-bitstring-status-list/issues/23 [before-CR] [pending 7 day close] 3 issues closed: - Add `@type` to `encodedList` term definition https://github.com/w3c/vc-bitstring-status-list/issues/125 [before-CR] [pr exists] - Matching of VC issuer and Status List VC issuer - MAY vs MUST https://github.com/w3c/vc-bitstring-status-list/issues/124 [before-CR] [pr exists] - Remove `ttl` https://github.com/w3c/vc-bitstring-status-list/issues/120 [before-CR] [pr exists] Pull requests ------------- * w3c/vc-data-model (+2/-0/💬6) 2 pull requests submitted: - update references to public key with verification material (by nicksteele) https://github.com/w3c/vc-data-model/pull/1414 - Add intro to Credential Type-Specific Processing. (by BigBlueHat) https://github.com/w3c/vc-data-model/pull/1413 4 pull requests received 6 new comments: - #1414 update references to public key with verification material (1 by nicksteele) https://github.com/w3c/vc-data-model/pull/1414 - #1397 Correct layering violations related to the proof property (2 by TallTed) https://github.com/w3c/vc-data-model/pull/1397 [before-CR] - #1320 Add definition of well formed (1 by brentzundel) https://github.com/w3c/vc-data-model/pull/1320 [post-CR] - #1302 Propose better JSON-LD processing text (2 by BigBlueHat, brentzundel) https://github.com/w3c/vc-data-model/pull/1302 [pending close] [post-CR] * w3c/vc-data-integrity (+1/-0/💬0) 1 pull requests submitted: - i18n Improvements (by Wind4Greg) https://github.com/w3c/vc-data-integrity/pull/240 * w3c/vc-di-ecdsa (+1/-0/💬0) 1 pull requests submitted: - Update context in Multikey example (by Wind4Greg) https://github.com/w3c/vc-di-ecdsa/pull/54 * w3c/vc-di-bbs (+4/-0/💬4) 4 pull requests submitted: - Two different references to the same document.. (by iherman) https://github.com/w3c/vc-di-bbs/pull/135 - Remove reference to RDF Normalization (by Wind4Greg) https://github.com/w3c/vc-di-bbs/pull/133 - Enhance base proof with bbsHeader and PK (by Wind4Greg) https://github.com/w3c/vc-di-bbs/pull/131 - Add informative note about code reuse (by Wind4Greg) https://github.com/w3c/vc-di-bbs/pull/130 2 pull requests received 4 new comments: - #117 Update test vectors for BBS Signature Scheme version 05 (2 by Wind4Greg, dlongley) https://github.com/w3c/vc-di-bbs/pull/117 - #115 i18n improvements (2 by Wind4Greg, aphillips) https://github.com/w3c/vc-di-bbs/pull/115 * w3c/vc-jwt (+4/-0/💬0) 4 pull requests submitted: - update COSE media types (by decentralgabe) https://github.com/w3c/vc-jose-cose/pull/223 - remove some language around proof (by decentralgabe) https://github.com/w3c/vc-jose-cose/pull/221 - adjust language in example 13 (by decentralgabe) https://github.com/w3c/vc-jose-cose/pull/220 - Fix example 24 with enveloped credential (by decentralgabe) https://github.com/w3c/vc-jose-cose/pull/219 * w3c/vc-status-list-2021 (+0/-3/💬5) 3 pull requests received 5 new comments: - #130 Ensure better compression for `encodedList` by typing the value. (2 by msporny) https://github.com/w3c/vc-bitstring-status-list/pull/130 - #129 Explicitly allow `issuer` to be different between VC and BSLC. (1 by msporny) https://github.com/w3c/vc-bitstring-status-list/pull/129 - #128 Add at risk issue marker for TTL. (2 by iherman, msporny) https://github.com/w3c/vc-bitstring-status-list/pull/128 3 pull requests merged: - Ensure better compression for `encodedList` by typing the value. https://github.com/w3c/vc-bitstring-status-list/pull/130 - Explicitly allow `issuer` to be different between VC and BSLC. https://github.com/w3c/vc-bitstring-status-list/pull/129 - Add at risk issue marker for TTL. https://github.com/w3c/vc-bitstring-status-list/pull/128 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, 22 January 2024 17:01:28 UTC