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

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Mon, 30 Jan 2023 17:01:14 +0000
To: public-credentials@w3.org
Message-Id: <E1pMXWs-008jAq-P4@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+4/-5/💬35)
  4 issues created:
  - Clarification on when a credentialRefresh service should be used (by morgatron)
    https://github.com/w3c/vc-data-model/issues/1020 
  - Support for SD-JWT (by David-Chadwick)
    https://github.com/w3c/vc-data-model/issues/1019 
  - Remove requirement for JWT (etc.) support from VC 2.0 & only support Linked Data (by ChristopherA)
    https://github.com/w3c/vc-data-model/issues/1018 
  - Requesting content type for presentation (by andresuribe87)
    https://github.com/w3c/vc-data-model/issues/1017 

  16 issues received 35 new comments:
  - #1018 Remove requirement for JWT (etc.) support from VC 2.0 & only support Linked Data (6 by ChristopherA, OR13, TallTed, mwherman2000, peacekeeper)
    https://github.com/w3c/vc-data-model/issues/1018 
  - #1008 Remove 3-party Issuer-Holder-Verifier diagram and replace with 2-party Raw Credential Sender-Receiver Model (2 by brentzundel, mwherman2000)
    https://github.com/w3c/vc-data-model/issues/1008 [conversation] 
  - #1002 Change vocabulary base URL for v2 context (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/1002 [ready for PR] [discuss] 
  - #982 W3C VC-LD Specification and Layered VC Specification: = interoperability at the application layer of layered spec (3 by mwherman2000)
    https://github.com/w3c/vc-data-model/issues/982 [conversation] 
  - #967 In Example 1, `value` and `lang` are not aliased to `@value` and `@language` (5 by OR13, msporny, pchampin)
    https://github.com/w3c/vc-data-model/issues/967 [PossibleErratum] [discuss] 
  - #953 Add `@vocab` for `private claims` in `/credentials/v2` `@context` (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/953 [pr exists] 
  - #946 what is attribute ID  in the verifiable credential? (2 by OR13, msporny)
    https://github.com/w3c/vc-data-model/issues/946 [ready for PR] [question] 
  - #945 Some questions about implementation: URIs and verificationMethod (3 by OR13, fabrii)
    https://github.com/w3c/vc-data-model/issues/945 [question] 
  - #913 `issuanceDate/expirationDate` and `validFrom/validUntil` (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/913 [pr exists] 
  - #912 Add normative reference to Data Integrity (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/912 [editorial] [pr exists] 
  - #908 Describe SD-JWT as an alternative for selective disclosure (1 by David-Chadwick)
    https://github.com/w3c/vc-data-model/issues/908 [conversation] 
  - #896 Standardize recording a pre-issuance DID Auth VP as evidence property (2 by OR13, msporny)
    https://github.com/w3c/vc-data-model/issues/896 [evidence] 
  - #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 (4 by TallTed, agropper, awoie)
    https://github.com/w3c/vc-data-model/issues/882 [discuss] [holder-binding] 
  - #870 Improve tests for Evidence (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/870 [evidence] 
  - #862 [Tracking Issue - Proposed Corrections Feedback] URL to URI (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/862 [pr exists] 
  - #848 clarify what an "appropriate VC/VP" is (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/848 [editorial] [pr exists] 

  5 issues closed:
  - `issuanceDate/expirationDate` and `validFrom/validUntil` https://github.com/w3c/vc-data-model/issues/913 [pr exists] 
  - Add normative reference to Data Integrity https://github.com/w3c/vc-data-model/issues/912 [editorial] [pr exists] 
  - [Tracking Issue - Proposed Corrections Feedback] URL to URI https://github.com/w3c/vc-data-model/issues/862 [pr exists] 
  - Add `@vocab` for `private claims` in `/credentials/v2` `@context` https://github.com/w3c/vc-data-model/issues/953 [pr exists] 
  - clarify what an "appropriate VC/VP" is https://github.com/w3c/vc-data-model/issues/848 [editorial] [pr exists] 

* w3c/vc-imp-guide (+1/-0/💬0)
  1 issues created:
  - Verifier perspective needed on subject-holder relationships (by RieksJ)
    https://github.com/w3c/vc-imp-guide/issues/69 

* w3c/vc-use-cases (+0/-0/💬1)
  1 issues received 1 new comments:
  - #128 Define use case(s) that requires holder binding (1 by peppelinux)
    https://github.com/w3c/vc-use-cases/issues/128 

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

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

* w3c/vc-jwt (+2/-0/💬3)
  2 issues created:
  - clearer wording for step 2 (by TallTed)
    https://github.com/w3c/vc-jwt/issues/43 
  - Bikeshedding the name for the `vc-jwt` 1.1 `cty` (by OR13)
    https://github.com/w3c/vc-jwt/issues/42 

  1 issues received 3 new comments:
  - #42 Bikeshedding the name for the `vc-jwt` 1.1 `cty` value. (3 by TallTed, dlongley)
    https://github.com/w3c/vc-jwt/issues/42 

* w3c/vc-status-list-2021 (+7/-2/💬37)
  7 issues created:
  - Is it possible to support multiple purposes? (by echenknox)
    https://github.com/w3c/vc-status-list-2021/issues/47 
  - clarify protocol for retrieval of a status list  (by mprorock)
    https://github.com/w3c/vc-status-list-2021/issues/44 
  - Trusted origins, list issuers vs hosts (by OR13)
    https://github.com/w3c/vc-status-list-2021/issues/43 
  - Would like multiple status to be capable of representation in a status list (by mprorock)
    https://github.com/w3c/vc-status-list-2021/issues/42 
  - Randomization (by OR13)
    https://github.com/w3c/vc-status-list-2021/issues/41 
  - Should "noise" be added during "updates" (by OR13)
    https://github.com/w3c/vc-status-list-2021/issues/40 
  - Verification should fail for revocable credentials for status list that cannot be deferenced (by BenjaminMoe)
    https://github.com/w3c/vc-status-list-2021/issues/39 

  12 issues received 37 new comments:
  - #47 Is it possible to support multiple purposes? (1 by 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 
  - #41 Randomization (1 by dlongley)
    https://github.com/w3c/vc-status-list-2021/issues/41 
  - #40 Should "noise" be added during "updates" (3 by dlongley, msporny)
    https://github.com/w3c/vc-status-list-2021/issues/40 
  - #39 Verification should fail for revocable credentials for status list that cannot be deferenced (7 by OR13, dlongley, iherman, morgatron, msporny)
    https://github.com/w3c/vc-status-list-2021/issues/39 [ready-for-pr] 
  - #38 Define TTL and caching behavior for lists (5 by OR13, Sakurann, dlongley, iherman, longpd)
    https://github.com/w3c/vc-status-list-2021/issues/38 [ready-for-pr] 
  - #37 Define priority for a single credential with multiple statuses (8 by OR13, Sakurann, andresuribe87, dlongley, iherman, msporny)
    https://github.com/w3c/vc-status-list-2021/issues/37 [discuss] 
  - #36 Specify bit order for status list  (4 by Sakurann, TallTed, iherman, msporny)
    https://github.com/w3c/vc-status-list-2021/issues/36 [ready-for-pr] 
  - #23 Handling Right to Erasure in encodedList and Validate Algorithm (1 by iherman)
    https://github.com/w3c/vc-status-list-2021/issues/23 [ready-for-pr] 
  - #12 Add a "reason code" (2 by OR13, iherman)
    https://github.com/w3c/vc-status-list-2021/issues/12 
  - #8 Bitstring endianness (2 by OR13, iherman)
    https://github.com/w3c/vc-status-list-2021/issues/8 
  - #3 Context about how this differs from 2020-rl (2 by Sakurann, msporny)
    https://github.com/w3c/vc-status-list-2021/issues/3 

  2 issues closed:
  - Context about how this differs from 2020-rl https://github.com/w3c/vc-status-list-2021/issues/3 
  - Bitstring endianness https://github.com/w3c/vc-status-list-2021/issues/8 



Pull requests
-------------
* w3c/vc-data-model (+0/-2/💬15)
  5 pull requests received 15 new comments:
  - #1014 Add normative requirements regarding media type and proof  (1 by iherman)
    https://github.com/w3c/vc-data-model/pull/1014 
  - #1013 Added Presentation as a possible domain for termsOfUse to the formal vocabulary (5 by TallTed, iherman, jandrieu, msporny)
    https://github.com/w3c/vc-data-model/pull/1013 
  - #1011 Change the reference URL in the vocabulary template file (5 by dlongley, iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1011 
  - #999 Remove ZKP Section (2 by decentralgabe, iherman)
    https://github.com/w3c/vc-data-model/pull/999 
  - #987 Added presentationSchema (2 by David-Chadwick, iherman)
    https://github.com/w3c/vc-data-model/pull/987 

  2 pull requests merged:
  - Added Presentation as a possible domain for termsOfUse to the formal vocabulary
    https://github.com/w3c/vc-data-model/pull/1013 
  - Change the reference URL in the vocabulary template file
    https://github.com/w3c/vc-data-model/pull/1011 

* w3c/vc-data-integrity (+0/-4/💬12)
  4 pull requests received 12 new comments:
  - #80 Add section on Proof Purpose Validation. (2 by iherman, msporny)
    https://github.com/w3c/vc-data-integrity/pull/80 
  - #79 Attempt to synchronize the security vocabulary with the FPWD spec (6 by TallTed, iherman, msporny)
    https://github.com/w3c/vc-data-integrity/pull/79 
  - #76 Add section on Canonicalization Method Correctness. (2 by iherman, msporny)
    https://github.com/w3c/vc-data-integrity/pull/76 
  - #75 Add note on verification relationships to Security Considerations. (2 by iherman, msporny)
    https://github.com/w3c/vc-data-integrity/pull/75 

  4 pull requests merged:
  - Attempt to synchronize the security vocabulary with the FPWD spec
    https://github.com/w3c/vc-data-integrity/pull/79 
  - Add section on Proof Purpose Validation.
    https://github.com/w3c/vc-data-integrity/pull/80 
  - Add section on Canonicalization Method Correctness.
    https://github.com/w3c/vc-data-integrity/pull/76 
  - Add note on verification relationships to Security Considerations.
    https://github.com/w3c/vc-data-integrity/pull/75 

* w3c/vc-jws-2020 (+0/-1/💬1)
  1 pull requests received 1 new comments:
  - #32 Change spec title (1 by brentzundel)
    https://github.com/w3c/vc-jws-2020/pull/32 

  1 pull requests merged:
  - Change spec title
    https://github.com/w3c/vc-jws-2020/pull/32 

* w3c/vc-jwt (+0/-2/💬12)
  1 pull requests received 12 new comments:
  - #40 Request media type for 1.1 vc-jwt claim set (12 by OR13, TallTed, brentzundel, decentralgabe, dlongley, iherman, jandrieu, mprorock, msporny, quartzjer)
    https://github.com/w3c/vc-jwt/pull/40 

  2 pull requests merged:
  - Propose "instead of" in terms of media type
    https://github.com/w3c/vc-jwt/pull/41 
  - Request media type for 1.1 vc-jwt claim set
    https://github.com/w3c/vc-jwt/pull/40 

* w3c/vc-status-list-2021 (+2/-0/💬0)
  2 pull requests submitted:
  - Ensure that statusListCredential can be dereferenced. (by msporny)
    https://github.com/w3c/vc-status-list-2021/pull/46 
  - Add section about bitstring encoding. (by 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, 30 January 2023 17:01:17 UTC