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

Issues
------
* w3c/vc-wg-charter (+0/-11/💬24)
  12 issues received 24 new comments:
  - #97 Definition of all key formats are left out of scope of the VC data model and crypto suites (3 by brentzundel, iherman, kdenhartog)
    https://github.com/w3c/vc-wg-charter/issues/97 [future VCWG conversation] 
  - #89 Environmental, Ethical and Social Implications of the Work (3 by OR13, iherman, msporny)
    https://github.com/w3c/vc-wg-charter/issues/89 [future VCWG conversation] 
  - #88 algorithms-related input documents for all proofs of integrity types (4 by OR13, Sakurann, iherman, msporny)
    https://github.com/w3c/vc-wg-charter/issues/88 
  - #87 rename a deliverable to "Verifiable Credential Proofs of Integrity 1.0" (1 by brentzundel)
    https://github.com/w3c/vc-wg-charter/issues/87 
  - #84 Add JwtProof2020 to the charter (2 by OR13, iherman)
    https://github.com/w3c/vc-wg-charter/issues/84 [future VCWG conversation] 
  - #83 New PR needed if did:key/multibase is going to be in scope (2 by brentzundel, iherman)
    https://github.com/w3c/vc-wg-charter/issues/83 
  - #82 Normatively defined crypto suites MUST fully define both public and private key representations (2 by OR13, iherman)
    https://github.com/w3c/vc-wg-charter/issues/82 
  - #78 Clarification on supported proof types (1 by brentzundel)
    https://github.com/w3c/vc-wg-charter/issues/78 [has-pr] 
  - #72 Some of the "other deliverables" raise patent concerns (2 by brentzundel, iherman)
    https://github.com/w3c/vc-wg-charter/issues/72 [future VCWG conversation] 
  - #68 Be clear that defining some fields means defining the ceremonies they point to (1 by brentzundel)
    https://github.com/w3c/vc-wg-charter/issues/68 
  - #67 Each registry should include at least one standardized entry (2 by brentzundel, iherman)
    https://github.com/w3c/vc-wg-charter/issues/67 [has-pr] 
  - #62 Data Integrity Crypto Suite Registry (1 by brentzundel)
    https://github.com/w3c/vc-wg-charter/issues/62 [has-pr] 

  11 issues closed:
  - New PR needed if did:key/multibase is going to be in scope https://github.com/w3c/vc-wg-charter/issues/83 
  - Definition of all key formats are left out of scope of the VC data model and crypto suites https://github.com/w3c/vc-wg-charter/issues/97 
  - Each registry should include at least one standardized entry https://github.com/w3c/vc-wg-charter/issues/67 [has-pr] 
  - Normatively defined crypto suites MUST fully define both public and private key representations https://github.com/w3c/vc-wg-charter/issues/82 
  - Some of the "other deliverables" raise patent concerns https://github.com/w3c/vc-wg-charter/issues/72 
  - Environmental, Ethical and Social Implications of the Work https://github.com/w3c/vc-wg-charter/issues/89 
  - Add JwtProof2020 to the charter https://github.com/w3c/vc-wg-charter/issues/84 
  - Be clear that defining some fields means defining the ceremonies they point to https://github.com/w3c/vc-wg-charter/issues/68 
  - Clarification on supported proof types https://github.com/w3c/vc-wg-charter/issues/78 [has-pr] 
  - rename a deliverable to "Verifiable Credential Proofs of Integrity 1.0" https://github.com/w3c/vc-wg-charter/issues/87 
  - Data Integrity Crypto Suite Registry https://github.com/w3c/vc-wg-charter/issues/62 [has-pr] 



Pull requests
-------------
* w3c/vc-wg-charter (+3/-3/💬10)
  3 pull requests submitted:
  - Editorial fix: Remove an unnecessary period (by shigeya)
    https://github.com/w3c/vc-wg-charter/pull/106 
  - Add Koblitz ECDSA Recovery Cryptosuite (by clehner)
    https://github.com/w3c/vc-wg-charter/pull/105 
  - Clean up capitalization. (by msporny)
    https://github.com/w3c/vc-wg-charter/pull/104 

  6 pull requests received 10 new comments:
  - #106 Editorial fix: Remove an unnecessary period (1 by iherman)
    https://github.com/w3c/vc-wg-charter/pull/106 
  - #105 Add Koblitz ECDSA Recovery Cryptosuite (4 by OR13, brianorwhatever, mirceanis, mprorock)
    https://github.com/w3c/vc-wg-charter/pull/105 
  - #104 Clean up capitalization. (2 by brentzundel, iherman)
    https://github.com/w3c/vc-wg-charter/pull/104 
  - #100 A non-exhaustive set of possible input documents for registries (1 by brentzundel)
    https://github.com/w3c/vc-wg-charter/pull/100 
  - #96 Clarify that DI should focus on VCs but ensure generality. (1 by brentzundel)
    https://github.com/w3c/vc-wg-charter/pull/96 
  - #85 Add Deliverables section on Registries (1 by brentzundel)
    https://github.com/w3c/vc-wg-charter/pull/85 

  3 pull requests merged:
  - Clean up capitalization.
    https://github.com/w3c/vc-wg-charter/pull/104 
  - Editorial fix: Remove an unnecessary period
    https://github.com/w3c/vc-wg-charter/pull/106 
  - Clarify that DI should focus on VCs but ensure generality.
    https://github.com/w3c/vc-wg-charter/pull/96 


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