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

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Mon, 26 Jun 2023 17:01:09 +0000
To: public-credentials@w3.org
Message-Id: <E1qDpaP-00DXGH-TW@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+3/-3/💬56)
  3 issues created:
  - Add language that there is generally no relationship between a VP and their VCs other than integrity protection (by awoie)
    https://github.com/w3c/vc-data-model/issues/1165 
  - consider changing all mentions of misnamed `holder binding` to something like `authorized presenter list` (by TallTed)
    https://github.com/w3c/vc-data-model/issues/1162 
  - (tracking issue) apparent copy-paste error in #1144 needs fixing (by TallTed)
    https://github.com/w3c/vc-data-model/issues/1161 

  23 issues received 56 new comments:
  - #1162 consider changing all mentions of misnamed `holder binding` to something like `authorized presenter list` (4 by TallTed, awoie, brentzundel)
    https://github.com/w3c/vc-data-model/issues/1162 
  - #1147 Depreciation of "Evidence" (3 by TallTed, brentzundel, decentralgabe)
    https://github.com/w3c/vc-data-model/issues/1147 [pending close] [evidence] 
  - #1138 Missing security considerations on MITM, cloning etc. (1 by decentralgabe)
    https://github.com/w3c/vc-data-model/issues/1138 
  - #1133 Make `validFrom` optional (2 by Sakurann, brentzundel)
    https://github.com/w3c/vc-data-model/issues/1133 [ready for PR] 
  - #1124 Remove reference to 20DocumentVerification2018 (3 by Sakurann, TallTed, brentzundel)
    https://github.com/w3c/vc-data-model/issues/1124 
  - #1118 Media Types and HTTP (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/1118 
  - #1080 (Editorial) systematically adding an anchor to each property (3 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1080 [editorial] [before-CR] 
  - #1077 Remove normative statements from vocab (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1077 [before-CR] 
  - #1047 NIST defines "credential" differently (2 by shigeya)
    https://github.com/w3c/vc-data-model/issues/1047 [terminology] 
  - #1031 Make `verifiable-credential.id` & `verifiable-presentation.id` REQUIRED. (2 by Sakurann, iherman)
    https://github.com/w3c/vc-data-model/issues/1031 [pending close] [discuss] 
  - #1017 Requesting content type for presentation (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/1017 [ready for PR] [media-type] 
  - #996 Question about verifiable presentations (7 by Sakurann, awoie, brentzundel, dlongley)
    https://github.com/w3c/vc-data-model/issues/996 [ready for PR] [conversation] [terminology] 
  - #995 [Terminology] claim (4 by RieksJ, Sakurann, TallTed, iherman)
    https://github.com/w3c/vc-data-model/issues/995 [pending close] [terminology] 
  - #988 Holder-Binding: Needs Privacy & Correlation, Centralization/Lock-in Considerations (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/988 [discuss] [holder-binding] [blocked] 
  - #984 Verifier Role Confusion (2 by Sakurann, iherman)
    https://github.com/w3c/vc-data-model/issues/984 [question] [pending close] [terminology] 
  - #950 Verification of multiple credential schemas (3 by brentzundel, decentralgabe, dlongley)
    https://github.com/w3c/vc-data-model/issues/950 [discuss] [schema] 
  - #946 what is attribute ID  in the verifiable credential? (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/946 [pr exists] [question] 
  - #942 Create the new role of issuee (2 by Sakurann, iherman)
    https://github.com/w3c/vc-data-model/issues/942 [pending close] [discuss] [terminology] 
  - #928 Add `render` property to a core VC data model (2 by Sakurann, brentzundel)
    https://github.com/w3c/vc-data-model/issues/928 [pending close] [discuss] 
  - #902 Define "prover" in addition to "holder". (5 by RieksJ, Sakurann, TallTed, iherman)
    https://github.com/w3c/vc-data-model/issues/902 [pending close] [discuss] [terminology] 
  - #882 Add extension mechanism to allow different methods for VP-to-VC / holder binding to next version of standard to allow verification of rightfulness of presentation (2 by OR13, brentzundel)
    https://github.com/w3c/vc-data-model/issues/882 [pr exists] [holder-binding] 
  - #860 Determine interoperable way for Holder to make claims directly in VPs (2 by agropper, brentzundel)
    https://github.com/w3c/vc-data-model/issues/860 [discuss] 
  - #821 "bound"/"binding" terminology is a significantly stronger relationship than is actually present between VCs and their Subjects *or* Holders (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/821 [clarification] [pending close] [holder-binding] [terminology] 

  3 issues closed:
  - Add extension mechanism to allow different methods for VP-to-VC / holder binding to next version of standard to allow verification of rightfulness of presentation https://github.com/w3c/vc-data-model/issues/882 [pr exists] [holder-binding] 
  - what is attribute ID  in the verifiable credential? https://github.com/w3c/vc-data-model/issues/946 [pr exists] [question] 
  - Requesting content type for presentation https://github.com/w3c/vc-data-model/issues/1017 [ready for PR] [media-type] 

* w3c/vc-use-cases (+0/-0/💬3)
  1 issues received 3 new comments:
  - #146 Chain of GS1 credentials to identify a trade item (3 by brentzundel, jandrieu)
    https://github.com/w3c/vc-use-cases/issues/146 

* w3c/vc-jwt (+1/-0/💬0)
  1 issues created:
  - Address VP Token interop (by OR13)
    https://github.com/w3c/vc-jwt/issues/110 

* w3c/vc-status-list-2021 (+1/-0/💬4)
  1 issues created:
  - Unify design of status lists to support bitfields (by msporny)
    https://github.com/w3c/vc-status-list-2021/issues/73 

  1 issues received 4 new comments:
  - #73 Unify design of status lists to support multi-bit values (4 by OR13, mprorock, msporny)
    https://github.com/w3c/vc-status-list-2021/issues/73 



Pull requests
-------------
* w3c/vc-data-model (+4/-1/💬26)
  4 pull requests submitted:
  - Issue 996 (by brentzundel)
    https://github.com/w3c/vc-data-model/pull/1167 
  - Clean up use-cases summary (by brentzundel)
    https://github.com/w3c/vc-data-model/pull/1166 
  - Add language clarifying VP is short-lived (by brentzundel)
    https://github.com/w3c/vc-data-model/pull/1164 
  - Rationalize and clarify IANA Considerations (by TallTed)
    https://github.com/w3c/vc-data-model/pull/1163 

  9 pull requests received 26 new comments:
  - #1166 Clean up use-cases summary (3 by TallTed, brentzundel)
    https://github.com/w3c/vc-data-model/pull/1166 
  - #1164 Add language clarifying VP is short-lived (1 by brentzundel)
    https://github.com/w3c/vc-data-model/pull/1164 
  - #1163 Rationalize and clarify IANA Considerations (4 by OR13, TallTed)
    https://github.com/w3c/vc-data-model/pull/1163 
  - #1159 Make the vocabulary URLs and values normative (6 by OR13, iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1159 
  - #1158 Make the value of the base context normative. (2 by brentzundel, msporny)
    https://github.com/w3c/vc-data-model/pull/1158 
  - #1149 Add graph node identifiers for registered claims (4 by OR13, brentzundel, dlongley, msporny)
    https://github.com/w3c/vc-data-model/pull/1149 
  - #1142 Update reservation table (2 by OR13, awoie)
    https://github.com/w3c/vc-data-model/pull/1142 
  - #1141 Add issue marker for extension point reservation discussion (2 by OR13, msporny)
    https://github.com/w3c/vc-data-model/pull/1141 
  - #1140 add context integrity capabilities to the core data model (2 by dmitrizagidulin, iherman)
    https://github.com/w3c/vc-data-model/pull/1140 

  1 pull requests merged:
  - Add issue marker for extension point reservation discussion
    https://github.com/w3c/vc-data-model/pull/1141 

* w3c/vc-jwt (+1/-1/💬2)
  1 pull requests submitted:
  - Add comments on key discovery (by OR13)
    https://github.com/w3c/vc-jwt/pull/111 

  2 pull requests received 2 new comments:
  - #109 Add guidance on header parameters (1 by OR13)
    https://github.com/w3c/vc-jwt/pull/109 
  - #88 remove securing json (1 by iherman)
    https://github.com/w3c/vc-jwt/pull/88 [tag-needs-resolution] [pending-wg-review] 

  1 pull requests merged:
  - Add guidance on header parameters
    https://github.com/w3c/vc-jwt/pull/109 

* w3c/vc-status-list-2021 (+0/-0/💬3)
  1 pull requests received 3 new comments:
  - #65 Support for multiple status codes (3 by iherman, mprorock, msporny)
    https://github.com/w3c/vc-status-list-2021/pull/65 


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, 26 June 2023 17:01:12 UTC