Weekly github digest (Weekly update on Verifiable Credentials WG activity)

Issues
------
* w3c/vc-data-model (+3/-1/💬11)
  3 issues created:
  - Suggest to make explicit reference to the JADES standard (by anthonycamilleri)
    https://github.com/w3c/vc-data-model/issues/1481 
  - Example of Use of renderMethod (by anthonycamilleri)
    https://github.com/w3c/vc-data-model/issues/1480 
  - Consider explicitly allowing/recommending language maps for use in internationalisation. (by anthonycamilleri)
    https://github.com/w3c/vc-data-model/issues/1479 

  7 issues received 11 new comments:
  - #1481 Suggest to make explicit reference to the JADES standard (2 by anthonycamilleri, brentzundel)
    https://github.com/w3c/vc-data-model/issues/1481 [editorial] [CR1] 
  - #1480 Example of Use of renderMethod (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1480 
  - #1479 Consider explicitly allowing/recommending language maps for use in internationalisation. (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1479 
  - #1475 `credential repository` vs `repository`, and definitions in _1.2  Ecosystem Overview_ vs _2. Terminology_ (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1475 [editorial] [CR1] 
  - #1472 Truth (or falsity) is not part of VCDM ecosystem (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1472 [editorial] [CR1] 
  - #1467 Add issuee definition (4 by David-Chadwick, brentzundel)
    https://github.com/w3c/vc-data-model/issues/1467 [future] 
  - #1462 Revisit Verifiable Credential media types (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1462 [normative] [CR1] 

  1 issues closed:
  - Truth (or falsity) is not part of VCDM ecosystem https://github.com/w3c/vc-data-model/issues/1472 [editorial] [CR1] 

* w3c/vc-use-cases (+0/-0/💬1)
  1 issues received 1 new comments:
  - #39 Use case for personal curation in the repository (1 by jandrieu)
    https://github.com/w3c/vc-use-cases/issues/39 [Potential Use Case] [pending-close] 

* w3c/vc-data-integrity (+1/-0/💬0)
  1 issues created:
  - Fix referenced step numbers in verify proof sets and chains algorithm (by dlongley)
    https://github.com/w3c/vc-data-integrity/issues/260 

* w3c/vc-di-bbs (+1/-0/💬2)
  1 issues created:
  - No reference to algorithm (by roblesjoel)
    https://github.com/w3c/vc-di-bbs/issues/157 

  2 issues received 2 new comments:
  - #157 No reference to algorithm (1 by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/issues/157 
  - #154 Typo & missing check in chapter 3.4.4 (1 by aljones15)
    https://github.com/w3c/vc-di-bbs/issues/154 

* w3c/vc-status-list-2021 (+0/-5/💬6)
  4 issues received 6 new comments:
  - #157 Make the generated vocabulary file available for preview (3 by iherman, msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/157 [before-CR] [pr exists] [editorial] 
  - #151 Remove open ended status messages because it is a layer violation (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/151 [before-CR] [pr exists] [normative] 
  - #143 mitigations for risk of unique status lists (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/143 [before-CR] [pr exists] [privacy-needs-resolution] [editorial] 
  - #127 "bitstring" vs "bit string" (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/127 [discuss] [before-CR] [editorial] 

  5 issues closed:
  - "bitstring" vs "bit string" https://github.com/w3c/vc-bitstring-status-list/issues/127 [discuss] [before-CR] [editorial] 
  - Make the generated vocabulary file available for preview https://github.com/w3c/vc-bitstring-status-list/issues/157 [before-CR] [pr exists] [editorial] 
  - Remove open ended status messages because it is a layer violation https://github.com/w3c/vc-bitstring-status-list/issues/151 [before-CR] [pr exists] [normative] 
  - describe dummy or decoy entries as a privacy mitigation https://github.com/w3c/vc-bitstring-status-list/issues/150 [before-CR] [pr exists] [privacy-needs-resolution] [editorial] 
  - mitigations for risk of unique status lists https://github.com/w3c/vc-bitstring-status-list/issues/143 [before-CR] [pr exists] [privacy-needs-resolution] [editorial] 



Pull requests
-------------
* w3c/vc-data-model (+1/-4/💬21)
  1 pull requests submitted:
  - Update media types to `application/vc` and `application/vp` (by msporny)
    https://github.com/w3c/vc-data-model/pull/1478 

  9 pull requests received 21 new comments:
  - #1478 Update media types to `application/vc` and `application/vp` (6 by TallTed, iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1478 [normative] [CR1] 
  - #1476 Move lifecycle section to Use Cases. (8 by David-Chadwick, TallTed, brentzundel)
    https://github.com/w3c/vc-data-model/pull/1476 
  - #1474 Massage "Trust Model" into "Expectations" (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1474 
  - #1473 add lost hyphen (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1473 
  - #1471 Update v2 context (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1471 
  - #1470 Update ecosystem.svg (fix Holder's verb tense) (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1470 [editorial] [CR1] 
  - #1468 Add definition of Issuee (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1468 [pending close] 
  - #1464 Address Jeffrey Yasskin's review comments that are Editorial (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1464 [editorial] [CR1] 
  - #1416 Adding SHACL as a credential schema language (1 by anthonycamilleri)
    https://github.com/w3c/vc-data-model/pull/1416 

  4 pull requests merged:
  - Massage "Trust Model" into "Expectations"
    https://github.com/w3c/vc-data-model/pull/1474 [editorial] [CR1] 
  - add lost hyphen
    https://github.com/w3c/vc-data-model/pull/1473 [editorial] [CR1] 
  - Update v2 context
    https://github.com/w3c/vc-data-model/pull/1471 [normative] [CR1] 
  - Update ecosystem.svg (fix Holder's verb tense)
    https://github.com/w3c/vc-data-model/pull/1470 [editorial] [CR1] 

* w3c/vc-use-cases (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #154 add credential lifecycle example from vc data model (1 by TallTed)
    https://github.com/w3c/vc-use-cases/pull/154 

* w3c/vc-di-bbs (+3/-0/💬2)
  3 pull requests submitted:
  - Optional Feature Test Vectors (by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/pull/160 
  - Correct small typo DataIntegrityProof not DataIntegirtyProof. (by aljones15)
    https://github.com/w3c/vc-di-bbs/pull/159 
  - Procedures update for optional features (by Wind4Greg)
    https://github.com/w3c/vc-di-bbs/pull/158 

  1 pull requests received 2 new comments:
  - #160 Optional Feature Test Vectors (2 by TallTed, Wind4Greg)
    https://github.com/w3c/vc-di-bbs/pull/160 

* w3c/vc-jwt (+2/-2/💬2)
  2 pull requests submitted:
  - change cr date to April 25 (by decentralgabe)
    https://github.com/w3c/vc-jose-cose/pull/267 
  - Update edn plugin to fix COSE render issue (by decentralgabe)
    https://github.com/w3c/vc-jose-cose/pull/266 

  2 pull requests received 2 new comments:
  - #267 change cr date to April 25 (1 by decentralgabe)
    https://github.com/w3c/vc-jose-cose/pull/267 
  - #266 Update edn plugin to fix COSE render issue (1 by decentralgabe)
    https://github.com/w3c/vc-jose-cose/pull/266 

  2 pull requests merged:
  - change cr date to April 25
    https://github.com/w3c/vc-jose-cose/pull/267 
  - Update edn plugin to fix COSE render issue
    https://github.com/w3c/vc-jose-cose/pull/266 

* w3c/vc-status-list-2021 (+0/-5/💬5)
  5 pull requests received 5 new comments:
  - #167 improve language of "Unnecessary Correlation" section (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/167 
  - #166 Tweaks to privacy considerations section about decoy values. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/166 
  - #165 Create lint-vocab.yml in workflows (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/165 
  - #164 Ensure that status messages are committed to at issuance time. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/164 
  - #161 Add suggestion on how malicious issuers can be detected. (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/pull/161 

  5 pull requests merged:
  - improve language of "Unnecessary Correlation" section
    https://github.com/w3c/vc-bitstring-status-list/pull/167 
  - Tweaks to privacy considerations section about decoy values.
    https://github.com/w3c/vc-bitstring-status-list/pull/166 
  - Create lint-vocab.yml in workflows
    https://github.com/w3c/vc-bitstring-status-list/pull/165 
  - Ensure that status messages are committed to at issuance time.
    https://github.com/w3c/vc-bitstring-status-list/pull/164 
  - Add suggestion on how malicious issuers can be detected.
    https://github.com/w3c/vc-bitstring-status-list/pull/161 


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 April 2024 17:00:59 UTC