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

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Mon, 31 Jul 2023 17:01:14 +0000
To: public-credentials@w3.org
Message-Id: <E1qQWGg-0002Hm-OQ@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+3/-2/💬21)
  3 issues created:
  - Add link to Linked Data Best Practices  (by msporny)
    https://github.com/w3c/vc-data-model/issues/1217 
  - Missing term in the credentials vocabulary (by iherman)
    https://github.com/w3c/vc-data-model/issues/1216 [before-CR] 
  - Spec does not contain terms in the context (by aljones15)
    https://github.com/w3c/vc-data-model/issues/1214 

  16 issues received 21 new comments:
  - #1217 Add link to Linked Data Best Practices  (1 by awoie)
    https://github.com/w3c/vc-data-model/issues/1217 
  - #1214 Spec does not contain "name" and "description" terms in the context (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1214 [before-CR] 
  - #1210 Document issuer defined vocabulary and use of @vocab (1 by dlongley)
    https://github.com/w3c/vc-data-model/issues/1210 [editorial] [ready for PR] [post-CR] 
  - #1206 Allowing expanded `type` values in conforming documents (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1206 [before-CR] 
  - #1205 Define Controller Documents in the Core Data Model (3 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1205 [before-CR] 
  - #1196 Move Data Schemas to Basic Concepts section (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1196 [pr exists] [before-CR] 
  - #1193 `validFrom` and `validUntil` fields need better specification of `dateTime` (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1193 [ready for PR] [i18n-needs-resolution] [before-CR] 
  - #1176 Define what a credential validity does mean (1 by filip26)
    https://github.com/w3c/vc-data-model/issues/1176 [post-CR] 
  - #1175 Ensure the base context doesn't constrain lower-maturity specifications (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1175 [ready for PR] [before-CR] 
  - #1156 Accessibility Self-Review for VCDM 2.0 (2 by awoie)
    https://github.com/w3c/vc-data-model/issues/1156 [HorizontalReview] [a11y-tracker] [before-CR] 
  - #1150 Protected term errors when supporting v1 and v2 (1 by dlongley)
    https://github.com/w3c/vc-data-model/issues/1150 [before-CR] 
  - #1089 Why does the Data Model context file define a DataIntegrityProof RDF class? (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1089 [before-CR] 
  - #1080 (Editorial) systematically adding an anchor to each property (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1080 [editorial] [before-CR] 
  - #1061 Add references in vocabulary that link back to the VCDM document (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1061 [ready for PR] [before-CR] 
  - #1010 `termsOfUse` is insufficiently specified (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1010 [conversation] [directory] [before-CR] 
  - #870 Evidence extension point (was: Improve tests for Evidence) (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/870 [evidence] [before-CR] 

  2 issues closed:
  - Accessibility Self-Review for VCDM 2.0 https://github.com/w3c/vc-data-model/issues/1156 [HorizontalReview] [a11y-tracker] [before-CR] 
  - Move Data Schemas to Basic Concepts section https://github.com/w3c/vc-data-model/issues/1196 [pr exists] [before-CR] 

* w3c/vc-data-integrity (+5/-11/💬45)
  5 issues created:
  - Add table for all error conditions (by msporny)
    https://github.com/w3c/vc-data-integrity/issues/136 
  - Add diagrams and test vectors for `previousProof` (by msporny)
    https://github.com/w3c/vc-data-integrity/issues/132 
  - Ensure that documents that drop data throw errors (by msporny)
    https://github.com/w3c/vc-data-integrity/issues/131 [ready for pr] [before CR] 
  - Add JsonWebKey definition in Data Integrity (by msporny)
    https://github.com/w3c/vc-data-integrity/issues/130 
  - Missing term definitions in the spec (by iherman)
    https://github.com/w3c/vc-data-integrity/issues/129 [before CR] 

  25 issues received 45 new comments:
  - #136 Add table for all error conditions (7 by iherman, msporny)
    https://github.com/w3c/vc-data-integrity/issues/136 [pr exists] [before CR] 
  - #132 Add diagrams and test vectors for `previousProof` (2 by Wind4Greg, msporny)
    https://github.com/w3c/vc-data-integrity/issues/132 [ready for pr] [after CR] 
  - #131 Ensure that documents that drop data throw errors (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/131 [ready for pr] [before CR] 
  - #130 Add JsonWebKey definition in Data Integrity (2 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/130 [ready for pr] [before CR] 
  - #129 Missing term definitions in the spec (1 by iherman)
    https://github.com/w3c/vc-data-integrity/issues/129 [ready for pr] [before CR] 
  - #120 Expand use of `previousProof` to allow an array, define in security vocabulary (9 by TallTed, Wind4Greg, dlongley, iherman, msporny)
    https://github.com/w3c/vc-data-integrity/issues/120 [ready for pr] [before CR] 
  - #115 Add guidance on perma-caching contexts to align with VCDM (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/115 [pr exists] [before CR] 
  - #114 Add optional prover-generated nonce value to increase privacy (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/114 [ready for pr] [before CR] 
  - #108 Add clarification for `verificationMethod`  property being optional. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/108 [ready for pr] [before CR] 
  - #97 Accessibility Self-Review for VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa)  (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/97 [a11y-tracker] 
  - #90 Add at least one unsigned properties (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/90 [before CR] 
  - #88 Specify a default context if JSON-LD processing is required (2 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/88 [ready for pr] [before CR] 
  - #84 How to use cryptographic suites (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/84 [pr exists] [before CR] 
  - #82 Apply guidance from RCH WG on processing poisoned graphs (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/82 [pr exists] [before CR] 
  - #78 Expiration Date (3 by David-Chadwick, msporny)
    https://github.com/w3c/vc-data-integrity/issues/78 [pending close (7 days)] [before CR] 
  - #77 Specify how relative URLs should be processed (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/77 [pr exists] [before CR] 
  - #74 Domain and range of sec:publicKey (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/74 [ready for pr] [before CR] 
  - #73 domain of publicKeyJWK should be rdf:JSON (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/73 [ready for pr] [before CR] 
  - #66 Cleanly separate cryptosuite verification and purpose verification algorithms (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/66 [ready for pr] [before CR] 
  - #60 Explain how proof types are mapped to URLs (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/60 [ready for pr] [before CR] 
  - #48 Add requirements on cryptosuite contexts such as `@protected` (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/48 [ready for pr] [before CR] 
  - #38 Determine how cryptographic suites are named and versioned (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/38 [pr exists] [before CR] 
  - #29 domain should be a string or array (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/29 [before CR] 
  - #23 Missing "created" invalidates signature?  (2 by David-Chadwick, msporny)
    https://github.com/w3c/vc-data-integrity/issues/23 [ready for pr] [before CR] 
  - #18 How order of signatures is ensured using ld-signatures? (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/18 [ready for pr] [before CR] 

  11 issues closed:
  - Accessibility Self-Review for VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa)  https://github.com/w3c/vc-data-integrity/issues/97 [a11y-tracker] 
  - Apply guidance from RCH WG on processing poisoned graphs https://github.com/w3c/vc-data-integrity/issues/82 [pr exists] [before CR] 
  - Add guidance on perma-caching contexts to align with VCDM https://github.com/w3c/vc-data-integrity/issues/115 [pr exists] [before CR] 
  - Specify how relative URLs should be processed https://github.com/w3c/vc-data-integrity/issues/77 [pr exists] [before CR] 
  - How to use cryptographic suites https://github.com/w3c/vc-data-integrity/issues/84 [pr exists] [before CR] 
  - Add optional prover-generated nonce value to increase privacy https://github.com/w3c/vc-data-integrity/issues/114 [ready for pr] [before CR] 
  - Add clarification for `verificationMethod`  property being optional. https://github.com/w3c/vc-data-integrity/issues/108 [ready for pr] [before CR] 
  - Add requirements on cryptosuite contexts such as `@protected` https://github.com/w3c/vc-data-integrity/issues/48 [ready for pr] [before CR] 
  - Determine how cryptographic suites are named and versioned https://github.com/w3c/vc-data-integrity/issues/38 [pr exists] [before CR] 
  - How order of signatures is ensured using ld-signatures? https://github.com/w3c/vc-data-integrity/issues/18 [ready for pr] [before CR] 
  - Missing "created" invalidates signature?  https://github.com/w3c/vc-data-integrity/issues/23 [ready for pr] [before CR] 

* w3c/vc-status-list-2021 (+1/-0/💬3)
  1 issues created:
  - Vocabulary definitions (by iherman)
    https://github.com/w3c/vc-status-list-2021/issues/81 

  1 issues received 3 new comments:
  - #81 Vocabulary definitions (3 by iherman, msporny)
    https://github.com/w3c/vc-status-list-2021/issues/81 [pre-CR] 



Pull requests
-------------
* w3c/vc-data-model (+2/-4/💬34)
  2 pull requests submitted:
  - Update term definition for vc json schemas as creds (by decentralgabe)
    https://github.com/w3c/vc-data-model/pull/1215 
  - Minor correction to viewBox so that all text becomes visible. (by fabienpe)
    https://github.com/w3c/vc-data-model/pull/1213 

  12 pull requests received 34 new comments:
  - #1215 Update term definition for vc json schemas as creds (1 by decentralgabe)
    https://github.com/w3c/vc-data-model/pull/1215 
  - #1213 Minor correction to viewBox so that all text becomes visible. (2 by msporny, w3cbot)
    https://github.com/w3c/vc-data-model/pull/1213 
  - #1212 Refer to VC-SPECS-DIR for proof types. (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1212 
  - #1211 Clarify that some abstract concepts are not realized in implementations (1 by David-Chadwick)
    https://github.com/w3c/vc-data-model/pull/1211 
  - #1209 Vocabulary improvement Phase 1 (4 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1209 
  - #1208 minor language fix (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1208 
  - #1207 Move data schemas to basic concepts section (2 by decentralgabe, iherman)
    https://github.com/w3c/vc-data-model/pull/1207 
  - #1203 Add section on Ecosystem Compatibility. (12 by OR13, TallTed, alenhorvat, iherman, jandrieu, msporny)
    https://github.com/w3c/vc-data-model/pull/1203 
  - #1202 Add section on JSON Processing. (3 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1202 
  - #1199 Add validation section regarding holder (1 by iherman)
    https://github.com/w3c/vc-data-model/pull/1199 
  - #1172 Add "author" and "party" to terminology, rewrite "claim" terminology (3 by iherman, jandrieu)
    https://github.com/w3c/vc-data-model/pull/1172 
  - #1142 Add confidenceMethod to table of reserved terms and v2 `@context` (3 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1142 

  4 pull requests merged:
  - Minor correction to viewBox so that all text becomes visible.
    https://github.com/w3c/vc-data-model/pull/1213 
  - Vocabulary improvement Phase 1
    https://github.com/w3c/vc-data-model/pull/1209 
  - minor language fix
    https://github.com/w3c/vc-data-model/pull/1208 
  - Move data schemas to basic concepts section
    https://github.com/w3c/vc-data-model/pull/1207 

* w3c/vc-use-cases (+0/-0/💬2)
  2 pull requests received 2 new comments:
  - #145 Bona fide shopper (1 by David-Chadwick)
    https://github.com/w3c/vc-use-cases/pull/145 
  - #127 Non-transferable use case (1 by KDean-GS1)
    https://github.com/w3c/vc-use-cases/pull/127 

* w3c/vc-data-integrity (+9/-12/💬16)
  9 pull requests submitted:
  - Added final versions of some properties (with anchors) (by iherman)
    https://github.com/w3c/vc-data-integrity/pull/142 
  - Added the error terms to the vocabulary (by iherman)
    https://github.com/w3c/vc-data-integrity/pull/141 
  - Add errors with anchors to the specification.  (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/140 
  - Add section on Security Data Losslessly. (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/139 
  - Add section on context injection. (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/138 
  - Update range of Multikey and JsonWebKey (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/137 
  - Add JSON Web Key to specification (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/135 
  - Explain use of each verify proof option. (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/134 
  - Clarify how proof types (and terms) are mapped to URLs. (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/133 

  12 pull requests received 16 new comments:
  - #140 Add errors with anchors to the specification.  (2 by iherman, msporny)
    https://github.com/w3c/vc-data-integrity/pull/140 
  - #134 Explain use of each verify proof option. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/134 
  - #128 Require cryptosuite specifications to mitigate against poison graphs. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/128 
  - #127 Vocabulary pruning and improvement phase 1 (2 by iherman, msporny)
    https://github.com/w3c/vc-data-integrity/pull/127 
  - #126 Data Integrity Cryptosuites naming convention update (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/126 
  - #125 Add requirement for protection of terms (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/125 
  - #124 Add expires proof attribute (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/124 
  - #122 Add creator generated nonce to proof. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/122 
  - #121 Added algorithms related to proof sets and chains. (3 by TallTed, Wind4Greg, msporny)
    https://github.com/w3c/vc-data-integrity/pull/121 
  - #119 Add section on relationship to Verifiable Credentials (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/119 
  - #118 Make "created" proof attribute optional. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/118 
  - #116 Add hashes for context and vocab files. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/116 

  12 pull requests merged:
  - Require cryptosuite specifications to mitigate against poison graphs.
    https://github.com/w3c/vc-data-integrity/pull/128 
  - Vocabulary pruning and improvement phase 1
    https://github.com/w3c/vc-data-integrity/pull/127 
  - Data Integrity Cryptosuites naming convention update
    https://github.com/w3c/vc-data-integrity/pull/126 
  - Add requirement for protection of terms
    https://github.com/w3c/vc-data-integrity/pull/125 
  - Add expires proof attribute
    https://github.com/w3c/vc-data-integrity/pull/124 
  - Clarify verificationMethod for controller document
    https://github.com/w3c/vc-data-integrity/pull/123 
  - Add creator generated nonce to proof.
    https://github.com/w3c/vc-data-integrity/pull/122 
  - Added algorithms related to proof sets and chains.
    https://github.com/w3c/vc-data-integrity/pull/121 
  - Add section on relationship to Verifiable Credentials
    https://github.com/w3c/vc-data-integrity/pull/119 
  - Make "created" proof attribute optional.
    https://github.com/w3c/vc-data-integrity/pull/118 
  - Add guidance to recommend usage of DataIntegrityProof pattern.
    https://github.com/w3c/vc-data-integrity/pull/117 
  - Add hashes for context and vocab files.
    https://github.com/w3c/vc-data-integrity/pull/116 

* w3c/vc-status-list-2021 (+0/-0/💬4)
  1 pull requests received 4 new comments:
  - #69 chore: update title and urls to contexts (4 by iherman, msporny)
    https://github.com/w3c/vc-status-list-2021/pull/69 


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, 31 July 2023 17:01:17 UTC