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

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Mon, 31 Jan 2022 17:01:34 +0000
To: public-credentials@w3.org
Message-Id: <E1nEa3a-0005ps-6I@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+2/-2/💬40)
  2 issues created:
  - example.edu is not a reserved name (by mcr)
    https://github.com/w3c/vc-data-model/issues/867 
  - Make images consistent (by chaals)
    https://github.com/w3c/vc-data-model/issues/865 

  8 issues received 40 new comments:
  - #867 example.edu is not a reserved name (2 by TallTed, mcr)
    https://github.com/w3c/vc-data-model/issues/867 
  - #865 Make images consistent (1 by chaals)
    https://github.com/w3c/vc-data-model/issues/865 
  - #863 [Tracking Issue - Proposed Corrections Feedback] ZKP Section Normative Changes (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/863 [v2.0] 
  - #862 [Tracking Issue - Proposed Corrections Feedback] URL to URI (5 by brentzundel, iherman, kdenhartog)
    https://github.com/w3c/vc-data-model/issues/862 [Errata] [v1.1 (editorial)] 
  - #844 Rename issuanceDate in v2 and reconsider a JWT claim counterpart (1 by alenhorvat)
    https://github.com/w3c/vc-data-model/issues/844 [v2.0] 
  - #843 Remove `@version` from v2 context (7 by OR13, VladimirAlexiev, dlongley)
    https://github.com/w3c/vc-data-model/issues/843 [v2.0] 
  - #820 Question: Using Refresh Service Property to update a credential when Credential Subject has a new field  (4 by TallTed, alenhorvat, msporny)
    https://github.com/w3c/vc-data-model/issues/820 [question] [v2.0] 
  - #753 Default vocab for credentials context v2 (18 by OR13, TallTed, VladimirAlexiev, dlongley, mprorock, msporny, peacekeeper, tplooker)
    https://github.com/w3c/vc-data-model/issues/753 [v2.0] 

  2 issues closed:
  - example.edu is not a reserved name https://github.com/w3c/vc-data-model/issues/867 
  - Missing Referenced   ld-proofs : https://w3c-ccg.github.io/ld-proofs/  https://github.com/w3c/vc-data-model/issues/858 [Editorial] [Errata] [v1.1 (editorial)] 

* w3c/vc-test-suite (+0/-0/💬1)
  1 issues received 1 new comments:
  - #126 [Tracking Issue - Proposed Corrections Feedback] Test suite improvements are needed (1 by iherman)
    https://github.com/w3c/vc-test-suite/issues/126 

* w3c/vc-wg-charter (+12/-1/💬38)
  12 issues created:
  - Data Integrity Crypto Suite Registry (by OR13)
    https://github.com/w3c/vc-wg-charter/issues/62 
  - More narrative description/ background (by samuelweiler)
    https://github.com/w3c/vc-wg-charter/issues/59 [security-needs-resolution] 
  - Success criteria ??? (by samuelweiler)
    https://github.com/w3c/vc-wg-charter/issues/58 
  - Data model or models (by samuelweiler)
    https://github.com/w3c/vc-wg-charter/issues/57 
  - Draft state for Verifiable Credential Data Integrity 1.0? (by samuelweiler)
    https://github.com/w3c/vc-wg-charter/issues/56 
  - Add charter history (by samuelweiler)
    https://github.com/w3c/vc-wg-charter/issues/55 
  - Update the Verifiable Credential Data Integrity 1.0 section (by OR13)
    https://github.com/w3c/vc-wg-charter/issues/54 
  - expand acronyms on first use (by samuelweiler)
    https://github.com/w3c/vc-wg-charter/issues/53 
  - clarify IETF liaison (by samuelweiler)
    https://github.com/w3c/vc-wg-charter/issues/52 
  - Standardizing PGP for Linked Data Integrity (by OR13)
    https://github.com/w3c/vc-wg-charter/issues/48 
  - Standardizing MultiKey2021  (by OR13)
    https://github.com/w3c/vc-wg-charter/issues/46 
  - Standardizing JsonWebSignature2020 / JsonWebKey2020 (by OR13)
    https://github.com/w3c/vc-wg-charter/issues/45 

  13 issues received 38 new comments:
  - #59 More narrative description/ background (1 by brentzundel)
    https://github.com/w3c/vc-wg-charter/issues/59 [security-needs-resolution] 
  - #58 Success criteria ??? (2 by iherman, samuelweiler)
    https://github.com/w3c/vc-wg-charter/issues/58 [security-needs-resolution] 
  - #57 Data model or models (1 by iherman)
    https://github.com/w3c/vc-wg-charter/issues/57 
  - #56 Draft state for Verifiable Credential Data Integrity 1.0? (4 by iherman, samuelweiler)
    https://github.com/w3c/vc-wg-charter/issues/56 
  - #55 Add charter history (3 by iherman, samuelweiler)
    https://github.com/w3c/vc-wg-charter/issues/55 
  - #54 Update the Verifiable Credential Data Integrity 1.0 section (2 by bumblefudge, selfissued)
    https://github.com/w3c/vc-wg-charter/issues/54 
  - #53 expand acronyms on first use (3 by iherman, samuelweiler)
    https://github.com/w3c/vc-wg-charter/issues/53 
  - #52 clarify IETF liaison (1 by iherman)
    https://github.com/w3c/vc-wg-charter/issues/52 
  - #48 Standardizing PGP for Linked Data Integrity (4 by OR13, mprorock, wyc)
    https://github.com/w3c/vc-wg-charter/issues/48 
  - #46 Standardizing MultiKey2021  (5 by OR13, Sakurann, iherman, mprorock, wyc)
    https://github.com/w3c/vc-wg-charter/issues/46 
  - #45 Standardizing JsonWebSignature2020 / JsonWebKey2020 (3 by iherman, mprorock, selfissued)
    https://github.com/w3c/vc-wg-charter/issues/45 
  - #38 Multilingual support for selecting a image file (2 by iherman, shigeya)
    https://github.com/w3c/vc-wg-charter/issues/38 
  - #24 Protocols and APIs should remain out of scope (7 by OR13, Sakurann, iherman)
    https://github.com/w3c/vc-wg-charter/issues/24 

  1 issues closed:
  - Fixing problems identified through using the 1.0 and 1.1 specs must be in scope https://github.com/w3c/vc-wg-charter/issues/22 



Pull requests
-------------
* w3c/vc-data-model (+1/-3/💬13)
  1 pull requests submitted:
  - address clarification that the URI can be used to retrieve data (by kdenhartog)
    https://github.com/w3c/vc-data-model/pull/866 [Editorial] [Clarification] [v1.1 (editorial)] 

  6 pull requests received 13 new comments:
  - #866 address clarification that the URI can be used to retrieve data (2 by brentzundel, kdenhartog)
    https://github.com/w3c/vc-data-model/pull/866 [Editorial] [Errata] [v1.1 (editorial)] 
  - #859 Rename "Linked Data Proofs" to "Data Integrity". (1 by kdenhartog)
    https://github.com/w3c/vc-data-model/pull/859 [v1.1 (editorial)] [merge after 14 days] 
  - #857 Edit of Proof Format section (1 by kdenhartog)
    https://github.com/w3c/vc-data-model/pull/857 [v1.1 (editorial)] [merge after 14 days] 
  - #855 Chaals more diagrams (4 by chaals, davidlehn, kdenhartog)
    https://github.com/w3c/vc-data-model/pull/855 [v1.1 (editorial)] [merge after 14 days] 
  - #854 Create SECURITY.md (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/854 [close after 7 days] 
  - #847 add section to differentiate between contexts and credential Schemas (4 by David-Chadwick, TallTed, kdenhartog, kdenhartog-mattr)
    https://github.com/w3c/vc-data-model/pull/847 [v1.1 (editorial)] [merge after 14 days] 

  3 pull requests merged:
  - Edit of Proof Format section
    https://github.com/w3c/vc-data-model/pull/857 [v1.1 (editorial)] [merge after 14 days] 
  - Rename "Linked Data Proofs" to "Data Integrity".
    https://github.com/w3c/vc-data-model/pull/859 [v1.1 (editorial)] [merge after 14 days] 
  - Chaals more diagrams
    https://github.com/w3c/vc-data-model/pull/855 [v1.1 (editorial)] [merge after 14 days] 

* w3c/vc-wg-charter (+7/-1/💬61)
  7 pull requests submitted:
  - [DO NOT MERGE YET] Add ECDSA secpr1 cryptosuite to VCWG input documents. (by msporny)
    https://github.com/w3c/vc-wg-charter/pull/63 
  - Proposed work mode for charter development (by brentzundel)
    https://github.com/w3c/vc-wg-charter/pull/61 
  - Dlarified data model and sub parts (by brentzundel)
    https://github.com/w3c/vc-wg-charter/pull/60 
  - to allow for multibase support in the VCDI spec (by bumblefudge)
    https://github.com/w3c/vc-wg-charter/pull/51 
  - Add a possible reference for pgp as a cryptosuite (by mprorock)
    https://github.com/w3c/vc-wg-charter/pull/50 
  - Align with the latest W3C charter template (by iherman)
    https://github.com/w3c/vc-wg-charter/pull/49 
  - Linked Data Signatures for JWS (by mprorock)
    https://github.com/w3c/vc-wg-charter/pull/47 

  6 pull requests received 61 new comments:
  - #51 to allow for multibase support in the VCDI spec (2 by OR13)
    https://github.com/w3c/vc-wg-charter/pull/51 
  - #50 Add a possible reference for pgp as a cryptosuite (6 by OR13, mprorock, msporny)
    https://github.com/w3c/vc-wg-charter/pull/50 
  - #49 Align with the latest W3C charter template (1 by iherman)
    https://github.com/w3c/vc-wg-charter/pull/49 
  - #47 Linked Data Signatures for JWS (11 by OR13, brentzundel, csuwildcat, iherman, kdenhartog, kdenhartog-mattr, mprorock, msporny)
    https://github.com/w3c/vc-wg-charter/pull/47 
  - #44 Extending support for resources in general (10 by David-Chadwick, Sakurann, iherman, shigeya)
    https://github.com/w3c/vc-wg-charter/pull/44 
  - #43 Specification of APIs or protocols is out of scope (31 by OR13, Sakurann, brentzundel, iherman, kdenhartog, msporny, nadalin, selfissued)
    https://github.com/w3c/vc-wg-charter/pull/43 

  1 pull requests merged:
  - Unambiguously state that fixing problems is in scope
    https://github.com/w3c/vc-wg-charter/pull/42 


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-wg-charter


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 31 January 2022 17:01:37 UTC