Weekly github digest (Weekly update on Verifiable Credentials WG activity) from W3C Webmaster via GitHub API on 2024-01-08 (public-credentials@w3.org from January 2024)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Mon, 08 Jan 2024 17:01:39 +0000
To: public-credentials@w3.org
Message-Id: <E1rMt0N-006F2d-C5@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+2/-7/💬29)
  2 issues created:
  - Does the specification need a normative "Credential Specifications" section? (by msporny)
    https://github.com/w3c/vc-data-model/issues/1410 
  - reconsider `@id` for `mediaType` term (by gobengo)
    https://github.com/w3c/vc-data-model/issues/1408 

  11 issues received 29 new comments:
  - #1408 reconsider `@id` for `mediaType` term (6 by dlongley, gobengo, iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1408 
  - #1402 phrasing and/or punctuation for input "inputBytes or inputDocument and inputMediaType" needs work (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1402 [ready for PR] 
  - #1400 Clarify embedded proof extension point (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1400 [pr exists] [before-CR] 
  - #1398 Ensure `credentialStatus` `id` field is optional (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1398 [pr exists] [before-CR] 
  - #1388 Specify what kind of processing is safe on a returned document (12 by dlongley, iherman, jyasskin, msporny)
    https://github.com/w3c/vc-data-model/issues/1388 [pr exists] [before-CR] 
  - #1377 Rewrite verification algorithm in a way that does not cause layer violations (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1377 [pr exists] [before-CR] 
  - #1364 Do VCs still need Media Types with Multiple Suffixes? (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/1364 [pending close] 
  - #1316 Update 4.9 Securing Verifiable Credentials (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1316 [post-CR] 
  - #1312 clarify relationship to the `proof` property and the specifications defining how to secure VCs (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1312 [post-CR] 
  - #1191 Example could include @language (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1191 [editorial] [i18n-needs-resolution] [post-CR] 
  - #1154 Transfer respec-vc to W3C VCWG? (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1154 [question] [post-CR] 

  7 issues closed:
  - clarify relationship to the `proof` property and the specifications defining how to secure VCs https://github.com/w3c/vc-data-model/issues/1312 [post-CR] 
  - Example could include @language https://github.com/w3c/vc-data-model/issues/1191 [editorial] [i18n-needs-resolution] [post-CR] 
  - Transfer respec-vc to W3C VCWG? https://github.com/w3c/vc-data-model/issues/1154 [question] [post-CR] 
  - Clarify embedded proof extension point https://github.com/w3c/vc-data-model/issues/1400 [pr exists] [before-CR] 
  - Ensure `credentialStatus` `id` field is optional https://github.com/w3c/vc-data-model/issues/1398 [pr exists] [before-CR] 
  - Specify what kind of processing is safe on a returned document https://github.com/w3c/vc-data-model/issues/1388 [pr exists] [before-CR] 
  - Do VCs still need Media Types with Multiple Suffixes? https://github.com/w3c/vc-data-model/issues/1364 [pending close] 

* w3c/vc-data-integrity (+2/-0/💬6)
  2 issues created:
  - Fix `vmPurpose` / `vmPurposes` discrepancy in Retrieve Verification Method algorithm  (by dlongley)
    https://github.com/w3c/vc-data-integrity/issues/236 
  - Possible Informative Text on Proof Chains and Sets (by Wind4Greg)
    https://github.com/w3c/vc-data-integrity/issues/234 

  4 issues received 6 new comments:
  - #234 Possible Informative Text on Proof Chains and Sets (1 by TallTed)
    https://github.com/w3c/vc-data-integrity/issues/234 
  - #208 What's a "document"? (1 by jyasskin)
    https://github.com/w3c/vc-data-integrity/issues/208 [during CR] 
  - #206 Verify Proof should take the cryptographic suite as a parameter (1 by jyasskin)
    https://github.com/w3c/vc-data-integrity/issues/206 [during CR] 
  - #107 Describe how JSON-LD framing is used with Selective Disclosure (3 by Wind4Greg, dlongley, msporny)
    https://github.com/w3c/vc-data-integrity/issues/107 [during CR] 

* w3c/vc-di-eddsa (+2/-0/💬0)
  2 issues created:
  - Ensure additional custom proof options provided via `proof` are included in the proof configuration (by dlongley)
    https://github.com/w3c/vc-di-eddsa/issues/74 
  - Ensure `created` proof option is optional (by dlongley)
    https://github.com/w3c/vc-di-eddsa/issues/73 

* w3c/vc-di-ecdsa (+2/-0/💬4)
  2 issues created:
  - Ensure additional custom proof options provided via `proof` are included in the proof configuration (by dlongley)
    https://github.com/w3c/vc-di-ecdsa/issues/48 
  - Ensure `created` proof option is optional (by dlongley)
    https://github.com/w3c/vc-di-ecdsa/issues/47 

  2 issues received 4 new comments:
  - #48 Ensure additional custom proof options provided via `proof` are included in the proof configuration (2 by Wind4Greg, dlongley)
    https://github.com/w3c/vc-di-ecdsa/issues/48 
  - #47 Ensure `created` proof option is optional (2 by Wind4Greg, msporny)
    https://github.com/w3c/vc-di-ecdsa/issues/47 

* w3c/vc-di-bbs (+6/-0/💬7)
  6 issues created:
  - "XML Schema formatted date string" not specific enough (by aphillips)
    https://github.com/w3c/vc-di-bbs/issues/114 [i18n-needs-resolution] 
  - Specify byte or character value of `u` (by aphillips)
    https://github.com/w3c/vc-di-bbs/issues/113 [i18n-needs-resolution] 
  - Example could use I18N best practices for language (by aphillips)
    https://github.com/w3c/vc-di-bbs/issues/112 [editorial] [i18n-needs-resolution] 
  - Handling/encoding of nonMandatory and bbsMessages (by aphillips)
    https://github.com/w3c/vc-di-bbs/issues/111 [i18n-needs-resolution] 
  - Clarify how holders can detect or prevent privacy problems. (by jyasskin)
    https://github.com/w3c/vc-di-bbs/issues/110 
  - Ensure `created` proof option is optional (by dlongley)
    https://github.com/w3c/vc-di-bbs/issues/108 

  5 issues received 7 new comments:
  - #114 "XML Schema formatted date string" not specific enough (1 by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/issues/114 [i18n-needs-resolution] 
  - #113 Specify byte or character value of `u` (2 by Wind4Greg, aphillips)
    https://github.com/w3c/vc-di-bbs/issues/113 [i18n-needs-resolution] 
  - #111 Handling/encoding of nonMandatory and bbsMessages (1 by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/issues/111 [i18n-needs-resolution] 
  - #110 Clarify how holders can detect or prevent privacy problems. (1 by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/issues/110 
  - #102 Accessibility Self-Review for VC DI BBS (2 by Wind4Greg, matatk)
    https://github.com/w3c/vc-di-bbs/issues/102 [a11y-tracker] 

* w3c/vc-jwt (+3/-0/💬23)
  3 issues created:
  - Question on the SD-JWT-VC normative reference (by iherman)
    https://github.com/w3c/vc-jose-cose/issues/218 [before-CR] 
  - Example 24 is invalid (by iherman)
    https://github.com/w3c/vc-jose-cose/issues/217 
  - Inconsistent sectioning? (by iherman)
    https://github.com/w3c/vc-jose-cose/issues/216 

  13 issues received 23 new comments:
  - #214 Inconsistent versions (2 by iherman, selfissued)
    https://github.com/w3c/vc-jose-cose/issues/214 [before-CR] 
  - #211 Remove mentions of "proof" from Section 6.1 (1 by selfissued)
    https://github.com/w3c/vc-jose-cose/issues/211 [post-CR] 
  - #210 Example 13 description is wrong (1 by selfissued)
    https://github.com/w3c/vc-jose-cose/issues/210 [post-CR] 
  - #209 Explicitly allow key format conversion (2 by msporny, selfissued)
    https://github.com/w3c/vc-jose-cose/issues/209 [before-CR] 
  - #208 Data format for COSE_Key expression in Controller Document is undefined (2 by msporny, selfissued)
    https://github.com/w3c/vc-jose-cose/issues/208 [before-CR] 
  - #207 COSE algorithms and examples not specified (2 by msporny, selfissued)
    https://github.com/w3c/vc-jose-cose/issues/207 [before-CR] 
  - #206 Algorithms are poorly defined / unimplementable (2 by msporny, selfissued)
    https://github.com/w3c/vc-jose-cose/issues/206 [before-CR] 
  - #205 Unclear semantics wrt. JWT claims vs. VC properties (2 by msporny, selfissued)
    https://github.com/w3c/vc-jose-cose/issues/205 [before-CR] 
  - #204 Media types are incorrect; usage can't be counted on (3 by TallTed, msporny, selfissued)
    https://github.com/w3c/vc-jose-cose/issues/204 [before-CR] 
  - #202 Conformance classes are not defined (2 by msporny, selfissued)
    https://github.com/w3c/vc-jose-cose/issues/202 [before-CR] 
  - #201 Support JWT-secured VCs (2 by msporny, selfissued)
    https://github.com/w3c/vc-jose-cose/issues/201 [before-CR] 
  - #199 Add an example for selective disclosure (1 by David-Chadwick)
    https://github.com/w3c/vc-jose-cose/issues/199 [post-CR] 
  - #188 Should JOSE/COSE verification strip out or inline @context values? (1 by jyasskin)
    https://github.com/w3c/vc-jose-cose/issues/188 [pending-close] 

* w3c/vc-status-list-2021 (+2/-1/💬9)
  2 issues created:
  - Add `@type` to `encodedList` term definition (by dlongley)
    https://github.com/w3c/vc-bitstring-status-list/issues/125 
  - Matching of VC issuer and Status List VC issuer - MAY vs MUST (by dmitrizagidulin)
    https://github.com/w3c/vc-bitstring-status-list/issues/124 

  6 issues received 9 new comments:
  - #124 Matching of VC issuer and Status List VC issuer - MAY vs MUST (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/124 [before-CR] 
  - #114 Rename `reference` to `statusReference` (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/114 [ready-for-pr] [before-CR] 
  - #113 Rename "size" to "statusSize" (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/113 [ready-for-pr] [before-CR] 
  - #84 Cascading status updates (1 by KDean-GS1)
    https://github.com/w3c/vc-bitstring-status-list/issues/84 [pending 7 day close] 
  - #82 auto-publishing using echidna? (3 by deniak, iherman, msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/82 [before-CR] 
  - #73 Unify design of status lists to support multi-bit values (2 by TallTed, msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/73 [before-CR] [pr exists] 

  1 issues closed:
  - auto-publishing using echidna? https://github.com/w3c/vc-bitstring-status-list/issues/82 [before-CR] 



Pull requests
-------------
* w3c/vc-data-model (+1/-5/💬26)
  1 pull requests submitted:
  - Update status list terms to match spec. (by BigBlueHat)
    https://github.com/w3c/vc-data-model/pull/1409 

  10 pull requests received 26 new comments:
  - #1409 Update status list terms to match spec. (4 by dlongley, iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1409 
  - #1407 Example diagrams multiple credentials (3 by iherman, selfissued)
    https://github.com/w3c/vc-data-model/pull/1407 [editorial] 
  - #1406 Update context to include latest BitstringStatusList changes. (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1406 [before-CR] 
  - #1405 Add RANGE_ERROR to list of potential errors. (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1405 [before-CR] 
  - #1404 Jwt example diagrams (3 by iherman, selfissued)
    https://github.com/w3c/vc-data-model/pull/1404 [editorial] 
  - #1403 Add embedded securing mechanism specification requirements (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1403 [before-CR] 
  - #1401 Refine status language and make credential status `id` optional. (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1401 [before-CR] 
  - #1397 Correct layering violations related to the proof property (2 by iherman, selfissued)
    https://github.com/w3c/vc-data-model/pull/1397 [before-CR] 
  - #1396 Rename "Controller Document" to "Entity Document". (5 by iherman, jandrieu, msporny)
    https://github.com/w3c/vc-data-model/pull/1396 [before-CR] 
  - #1392 Add requirement for securing mechanisms to have post-verification documentation. (1 by iherman)
    https://github.com/w3c/vc-data-model/pull/1392 [pending close] [before-CR] 

  5 pull requests merged:
  - Update context to include latest BitstringStatusList changes.
    https://github.com/w3c/vc-data-model/pull/1406 [before-CR] 
  - Add RANGE_ERROR to list of potential errors.
    https://github.com/w3c/vc-data-model/pull/1405 [before-CR] 
  - Add embedded securing mechanism specification requirements
    https://github.com/w3c/vc-data-model/pull/1403 [before-CR] 
  - Refine status language and make credential status `id` optional.
    https://github.com/w3c/vc-data-model/pull/1401 [before-CR] 
  - Rename "Controller Document" to "Entity Document".
    https://github.com/w3c/vc-data-model/pull/1396 [before-CR] 

* w3c/vc-data-integrity (+2/-3/💬8)
  2 pull requests submitted:
  - Editorial: describe isProofVerified's type more accurately. (by jyasskin)
    https://github.com/w3c/vc-data-integrity/pull/235 
  - Editorial: Remove extra quotes like |suite|'s'. (by jyasskin)
    https://github.com/w3c/vc-data-integrity/pull/233 

  3 pull requests received 8 new comments:
  - #233 Editorial: Remove extra quotes like |suite|'s'. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/233 [editorial] 
  - #227 Make Verify Proof match the interface used by JOSE/COSE proof verification (4 by jyasskin, msporny)
    https://github.com/w3c/vc-data-integrity/pull/227 [normative] 
  - #226 Define algorithm input and output types. (3 by jyasskin, msporny)
    https://github.com/w3c/vc-data-integrity/pull/226 [normative] 

  3 pull requests merged:
  - Editorial: Remove extra quotes like |suite|'s'.
    https://github.com/w3c/vc-data-integrity/pull/233 [editorial] 
  - Make Verify Proof match the interface used by JOSE/COSE proof verification
    https://github.com/w3c/vc-data-integrity/pull/227 [normative] 
  - Define algorithm input and output types.
    https://github.com/w3c/vc-data-integrity/pull/226 [normative] 

* w3c/vc-di-ecdsa (+2/-0/💬0)
  2 pull requests submitted:
  - Base proof properties on Data Integrity spec with restrictions (by Wind4Greg)
    https://github.com/w3c/vc-di-ecdsa/pull/50 
  - Edit algorithms to permit more general proof configuration options (by Wind4Greg)
    https://github.com/w3c/vc-di-ecdsa/pull/49 

* w3c/vc-di-bbs (+2/-0/💬2)
  2 pull requests submitted:
  - i18n improvements  (by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/pull/115 
  - Add informative text on linkage via JSON-LD node ids. (by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/pull/109 

  1 pull requests received 2 new comments:
  - #115 i18n improvements  (2 by Wind4Greg, aphillips)
    https://github.com/w3c/vc-di-bbs/pull/115 

* w3c/vc-jwt (+0/-0/💬7)
  3 pull requests received 7 new comments:
  - #215 Improving explanation of SD-JWT (2 by David-Chadwick, selfissued)
    https://github.com/w3c/vc-jose-cose/pull/215 [pending-close] 
  - #213 Update Abstract (2 by David-Chadwick, selfissued)
    https://github.com/w3c/vc-jose-cose/pull/213 [pending-close] 
  - #212 Update Title (3 by David-Chadwick, iherman, selfissued)
    https://github.com/w3c/vc-jose-cose/pull/212 [pending-close] 

* w3c/vc-status-list-2021 (+1/-0/💬4)
  1 pull requests submitted:
  - Update context terms to match spec. (by BigBlueHat)
    https://github.com/w3c/vc-bitstring-status-list/pull/126 

  4 pull requests received 4 new comments:
  - #126 Update context terms to match spec. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/126 
  - #122 Add examples for multiple status lists and multiple entries in a single status list (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/122 
  - #118 Add guidance on how to secure status lists. (1 by TallTed)
    https://github.com/w3c/vc-bitstring-status-list/pull/118 
  - #105 Add formal vocabulary definitions. (1 by iherman)
    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, 8 January 2024 17:01:43 UTC