Weekly github digest (Weekly update on Verifiable Credentials WG activity) from W3C Webmaster via GitHub API on 2023-02-06 (public-credentials@w3.org from February 2023)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Mon, 06 Feb 2023 17:01:17 +0000
To: public-credentials@w3.org
Message-Id: <E1pP4rl-00DqEc-9Z@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+4/-3/💬52)
  4 issues created:
  - Add guidance on ignoring optional fields (by OR13)
    https://github.com/w3c/vc-data-model/issues/1027 
  - Replace e.g. and i.e. with internationalization friendly text (by decentralgabe)
    https://github.com/w3c/vc-data-model/issues/1025 
  - Forbid expanded JSON-LD in `application/credential+ld+json` (by OR13)
    https://github.com/w3c/vc-data-model/issues/1024 
  - Typos in v.1.1 (by shujikamitsuna)
    https://github.com/w3c/vc-data-model/issues/1021 

  20 issues received 52 new comments:
  - #1027 Add guidance on ignoring optional fields (5 by David-Chadwick, OR13, dlongley)
    https://github.com/w3c/vc-data-model/issues/1027 
  - #1024 Forbid expanded JSON-LD in `application/credential+ld+json` (3 by OR13, bumblefudge)
    https://github.com/w3c/vc-data-model/issues/1024 
  - #1021 Typos in v.1.1 (1 by bumblefudge)
    https://github.com/w3c/vc-data-model/issues/1021 
  - #1002 Change vocabulary base URL for v2 context (1 by OR13)
    https://github.com/w3c/vc-data-model/issues/1002 [ready for PR] [discuss] 
  - #996 Question about verifiable presentations (2 by Sakurann)
    https://github.com/w3c/vc-data-model/issues/996 [conversation] [terminology] 
  - #979 Resolve discrepancies between specifications, vocabularies, schemas (2 by TallTed, decentralgabe)
    https://github.com/w3c/vc-data-model/issues/979 [editorial] [clarification] 
  - #972 Strawman for Increasing Interop (1 by OR13)
    https://github.com/w3c/vc-data-model/issues/972 [discuss] 
  - #967 In Example 1, `value` and `lang` are not aliased to `@value` and `@language` (1 by OR13)
    https://github.com/w3c/vc-data-model/issues/967 [PossibleErratum] [discuss] 
  - #959 Clarification needed on the ease of deducing that a subject is the holder. (1 by awoie)
    https://github.com/w3c/vc-data-model/issues/959 [holder-binding] 
  - #958 Clarification of the type of the "verifiableCredential" field in a VP  (1 by OR13)
    https://github.com/w3c/vc-data-model/issues/958 [question] 
  - #950 Verification of multiple credential schemas (1 by OR13)
    https://github.com/w3c/vc-data-model/issues/950 [schema] 
  - #945 Some questions about implementation: URIs and verificationMethod (1 by OR13)
    https://github.com/w3c/vc-data-model/issues/945 [question] 
  - #933 Define a standard way to use Credential Schemas for Credential Subjects (1 by OR13)
    https://github.com/w3c/vc-data-model/issues/933 [schema] [worked-on-in-ccg] 
  - #932 Representing Multi Issuer Credentials in the VCDM (14 by Sakurann, SmithSamuelM, decentralgabe, dlongley, dwaite, iherman, msporny, peacekeeper)
    https://github.com/w3c/vc-data-model/issues/932 [discuss] 
  - #923 Making explicit the binding of the holder to a VC (1 by OR13)
    https://github.com/w3c/vc-data-model/issues/923 [discuss] [holder-binding] 
  - #919 Evidence as a Related Credential (1 by David-Chadwick)
    https://github.com/w3c/vc-data-model/issues/919 [ready for PR] [discuss] [evidence] 
  - #893 add claims metadata (how the identity claims were assured and how they are maintained) (5 by David-Chadwick, RieksJ, Sakurann, TallTed)
    https://github.com/w3c/vc-data-model/issues/893 [discuss] [evidence] 
  - #890 credentialSchema and Selective Disclosure (4 by OR13, SmithSamuelM, brentzundel, mprorock)
    https://github.com/w3c/vc-data-model/issues/890 [ready for PR] [schema] 
  - #831 Proposal: Anchored Resources and Hashlinks for VCs (4 by OR13, aljones15, brianorwhatever)
    https://github.com/w3c/vc-data-model/issues/831 [discuss] 
  - #421 Define one or more media types for VCs (2 by OR13, StEvUgnIn)
    https://github.com/w3c/vc-data-model/issues/421 [pr exists] 

  3 issues closed:
  - Change vocabulary base URL for v2 context https://github.com/w3c/vc-data-model/issues/1002 [ready for PR] [discuss] 
  - Making explicit the binding of the holder to a VC https://github.com/w3c/vc-data-model/issues/923 [discuss] [holder-binding] 
  - Resolve discrepancies between specifications, vocabularies, schemas https://github.com/w3c/vc-data-model/issues/979 [editorial] [clarification] 

* w3c/vc-use-cases (+0/-0/💬1)
  1 issues received 1 new comments:
  - #124 Section 4 diagram includes "amend claim" (1 by Sakurann)
    https://github.com/w3c/vc-use-cases/issues/124 

* w3c/vc-data-integrity (+0/-0/💬1)
  1 issues received 1 new comments:
  - #81 Review on 2023-01-26 by Greg Bernstein (1 by Wind4Greg)
    https://github.com/w3c/vc-data-integrity/issues/81 

* w3c/vc-jws-2020 (+0/-0/💬1)
  1 issues received 1 new comments:
  - #31 Naming of work (1 by brentzundel)
    https://github.com/w3c/vc-jws-2020/issues/31 

* w3c/vc-jwt (+1/-0/💬0)
  1 issues created:
  - Shorten `verifiable-credential+jwt` to `vc+jwt` (by OR13)
    https://github.com/w3c/vc-jwt/issues/45 

* w3c/vc-status-list-2021 (+6/-1/💬38)
  6 issues created:
  - How to understand herd privacy in using bit string? (by echenknox)
    https://github.com/w3c/vc-status-list-2021/issues/54 
  - Implementation guidelines around how StatusList2021Credential is secured/encoded. (by Sakurann)
    https://github.com/w3c/vc-status-list-2021/issues/52 
  - Clarify that `StatusList2021Credential` must be [[VC-DATA-MODEL](https://w3c.github.io/vc-status-list-2021/#bib-vc-data-model)] (v1.1) (by Sakurann)
    https://github.com/w3c/vc-status-list-2021/issues/51 
  - Versioning (by Sakurann)
    https://github.com/w3c/vc-status-list-2021/issues/50 
  - Document design characteristics why "StatusList2021Entry" is signed. (by Sakurann)
    https://github.com/w3c/vc-status-list-2021/issues/49 
  - Document design characteristics why "StatusList2021Credential" is a VC (by Sakurann)
    https://github.com/w3c/vc-status-list-2021/issues/48 

  11 issues received 38 new comments:
  - #50 Versioning (2 by mprorock, msporny)
    https://github.com/w3c/vc-status-list-2021/issues/50 
  - #48 Document design characteristics why "StatusList2021Credential" is a VC (1 by dlongley)
    https://github.com/w3c/vc-status-list-2021/issues/48 
  - #47 Is it possible to support multiple purposes? (2 by dlongley, echenknox)
    https://github.com/w3c/vc-status-list-2021/issues/47 
  - #42 Would like multiple status to be capable of representation in a status list (1 by dlongley)
    https://github.com/w3c/vc-status-list-2021/issues/42 
  - #40 Should "noise" be added during "updates" (1 by OR13)
    https://github.com/w3c/vc-status-list-2021/issues/40 
  - #37 Define priority for a single credential with multiple statuses (10 by OR13, dlongley, echenknox)
    https://github.com/w3c/vc-status-list-2021/issues/37 [discuss] 
  - #11 RevocationList2021 or RevocationList2021Status (9 by Sakurann, brentzundel, iherman, mprorock, msporny)
    https://github.com/w3c/vc-status-list-2021/issues/11 
  - #9 Bounds checking (4 by dlongley, iherman, mprorock, msporny)
    https://github.com/w3c/vc-status-list-2021/issues/9 [ready-for-pr] 
  - #7 Status list credential issuer validation (6 by Sakurann, iherman, longpd, mprorock)
    https://github.com/w3c/vc-status-list-2021/issues/7 [question] [ready-for-pr] 
  - #6 Preventing multiple single-credential status lists per issuer (1 by iherman)
    https://github.com/w3c/vc-status-list-2021/issues/6 [ready-for-pr] 
  - #4 Status-List-2021 without the VC (1 by iherman)
    https://github.com/w3c/vc-status-list-2021/issues/4 [question] 

  1 issues closed:
  - RevocationList2021 or RevocationList2021Status https://github.com/w3c/vc-status-list-2021/issues/11 



Pull requests
-------------
* w3c/vc-data-model (+4/-0/💬31)
  4 pull requests submitted:
  - ignore gitignore file (by brentzundel)
    https://github.com/w3c/vc-data-model/pull/1028 
  - Add issue to zkp section (by OR13)
    https://github.com/w3c/vc-data-model/pull/1026 
  - Add language clarifying multiple data schemas (by decentralgabe)
    https://github.com/w3c/vc-data-model/pull/1023 
  - Typos pointed out in issue 1021 (by bumblefudge)
    https://github.com/w3c/vc-data-model/pull/1022 

  6 pull requests received 31 new comments:
  - #1026 Add issue to zkp section (3 by OR13, Sakurann, brentzundel)
    https://github.com/w3c/vc-data-model/pull/1026 
  - #1023 Add language clarifying multiple data schemas (2 by OR13, iherman)
    https://github.com/w3c/vc-data-model/pull/1023 
  - #1022 Typos pointed out in issue 1021 (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1022 
  - #1014 Add normative requirements regarding media type and proof  (5 by OR13, dlongley, iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1014 
  - #999 Remove ZKP Section (2 by OR13, iherman)
    https://github.com/w3c/vc-data-model/pull/999 
  - #987 Added presentationSchema (17 by David-Chadwick, OR13, iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/987 

* w3c/vc-imp-guide (+0/-1/💬1)
  1 pull requests received 1 new comments:
  - #60 Fix a broken link to a paper (1 by brentzundel)
    https://github.com/w3c/vc-imp-guide/pull/60 

  1 pull requests merged:
  - Fix a broken link to a paper
    https://github.com/w3c/vc-imp-guide/pull/60 

* w3c/vc-use-cases (+1/-0/💬5)
  1 pull requests submitted:
  - Fix for Issue #128 (by justAnIdentity)
    https://github.com/w3c/vc-use-cases/pull/129 

  1 pull requests received 5 new comments:
  - #129 Use case for Holder Binding (5 by Sakurann, TallTed, awoie, justAnIdentity)
    https://github.com/w3c/vc-use-cases/pull/129 

* w3c/vc-data-integrity (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #79 Attempt to synchronize the security vocabulary with the FPWD spec (1 by 1azteca1)
    https://github.com/w3c/vc-data-integrity/pull/79 

* w3c/vc-jwt (+1/-0/💬10)
  1 pull requests submitted:
  - Add version 2 (by OR13)
    https://github.com/w3c/vc-jwt/pull/44 

  1 pull requests received 10 new comments:
  - #44 Add version 2 (10 by OR13, SmithSamuelM, TallTed, dhh1128, letmaik, quartzjer)
    https://github.com/w3c/vc-jwt/pull/44 

* w3c/vc-status-list-2021 (+1/-0/💬13)
  1 pull requests submitted:
  - Add validity/caching period to status list credentials. (by msporny)
    https://github.com/w3c/vc-status-list-2021/pull/53 

  2 pull requests received 13 new comments:
  - #46 Ensure that statusListCredential can be dereferenced. (4 by dlongley, iherman, msporny)
    https://github.com/w3c/vc-status-list-2021/pull/46 
  - #45 Add section about bitstring encoding. (9 by OR13, dwight-holman, iherman, msporny)
    https://github.com/w3c/vc-status-list-2021/pull/45 


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-data-integrity
* https://github.com/w3c/vc-jws-2020
* 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, 6 February 2023 17:01:19 UTC