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

Issues
------
* w3c/vc-data-model (+2/-0/💬43)
  2 issues created:
  - Add `revoked` and `expired` to verification method classes (by OR13)
    https://github.com/w3c/vc-data-model/issues/1262 
  - Add cryptographic hashes for vocabulary files (by msporny)
    https://github.com/w3c/vc-data-model/issues/1261 [ready for PR] [before-CR] 

  20 issues received 43 new comments:
  - #1262 Add `revoked` and `expired` to verification method classes (2 by OR13, iherman)
    https://github.com/w3c/vc-data-model/issues/1262 
  - #1254 Section title and contents mismatch on "Complex Language Markup" (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1254 [post-CR] 
  - #1248 signatures should be on quoted graphs (10 by TallTed, bblfish, brentzundel, iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1248 [post-CR] 
  - #1247 Addressing Verifier Stored Data Vulnerabilities and Legal Compliance (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1247 [HorizontalReview] [privacy-needs-resolution] [security-needs-resolution] [before-CR] 
  - #1246 Strengthening Trust Boundaries for Holder Software in Verifiable Credential Processing (3 by iherman, jandrieu, kdenhartog)
    https://github.com/w3c/vc-data-model/issues/1246 [HorizontalReview] [privacy-needs-resolution] [security-needs-resolution] [post-CR] 
  - #1245 Mitigating Location Correlation via Common Issuers (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1245 [HorizontalReview] [privacy-needs-resolution] [post-CR] 
  - #1244 Address Metadata-Driven Correlation (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1244 [HorizontalReview] [privacy-needs-resolution] [post-CR] 
  - #1235 Revert language change on the definition of Subject (2 by brentzundel, iherman)
    https://github.com/w3c/vc-data-model/issues/1235 [ready for PR] [before-CR] 
  - #1231 Minor change to validFrom requested (2 by David-Chadwick, TallTed)
    https://github.com/w3c/vc-data-model/issues/1231 [pr exists] [before-CR] 
  - #1214 Spec does not contain "name" and "description" terms in the context (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1214 [pr exists] [before-CR] 
  - #1206 Allowing expanded `type` values in conforming documents (2 by brentzundel, iherman)
    https://github.com/w3c/vc-data-model/issues/1206 [ready for PR] [before-CR] 
  - #1185 Conformance requirements for normative context (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/1185 [ready for PR] [before-CR] 
  - #1150 Protected term errors when supporting v1 and v2 (2 by dlongley, iherman)
    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 [pending close] [before-CR] 
  - #1027 Add guidance on ignoring optional fields (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1027 [ready for PR] [before-CR] 
  - #991 Clarify credentialStatus (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/991 [pr exists] [status] [before-CR] 
  - #965 'issued' vs. 'validFrom' (formerly 'issuanceDate')  (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/965 [ready for PR] [before-CR] 
  - #938 Indicating Encrypted VCs in VPs (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/938 [ready for PR] [pending close] [discuss] [before-CR] 
  - #870 Evidence extension point (was: Improve tests for Evidence) (7 by OR13, TallTed, iherman, longpd)
    https://github.com/w3c/vc-data-model/issues/870 [evidence] [before-CR] 
  - #860 Determine interoperable way for Holder to make claims directly in VPs (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/860 [pr exists] [discuss] [before-CR] 

* w3c/vc-json-schema (+0/-1/💬1)
  1 issues received 1 new comments:
  - #134 Test suite (1 by decentralgabe)
    https://github.com/w3c/vc-json-schema/issues/134 [testing] [pre-cr] 

  1 issues closed:
  - Encourage usage of OHTTP during schema resolution https://github.com/w3c/vc-json-schema/issues/203 [privacy-needs-resolution] [pre-cr] 

* w3c/vc-data-integrity (+6/-3/💬33)
  6 issues created:
  - Ensure proper capitalization of "context" and "vocabulary" (by msporny)
    https://github.com/w3c/vc-data-integrity/issues/183 [during CR] 
  - Adjustments to the `revoked` property (by OR13)
    https://github.com/w3c/vc-data-integrity/issues/182 
  - When converting to RDF, ensure that BASE URL is null. (by msporny)
    https://github.com/w3c/vc-data-integrity/issues/180 
  - Should this suite normatively require integrity checking of the context files? (by kdenhartog)
    https://github.com/w3c/vc-data-integrity/issues/179 
  - Inconsistencies in our URLs (by iherman)
    https://github.com/w3c/vc-data-integrity/issues/177 [before CR] 
  - Apply diagram changes (by iherman)
    https://github.com/w3c/vc-data-integrity/issues/175 [during CR] 

  9 issues received 33 new comments:
  - #183 Ensure proper capitalization of "context" and "vocabulary" (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/183 [ready for pr] [during CR] 
  - #182 Adjustments to the `revoked` property (2 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/182 [ready for pr] [before CR] 
  - #180 When converting to RDF, ensure that BASE URL is null. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/180 [ready for pr] [before CR] 
  - #179 Should this suite normatively require integrity checking of the context files? (2 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/179 [ready for pr] [before CR] 
  - #177 Inconsistencies in our URLs (6 by iherman, msporny)
    https://github.com/w3c/vc-data-integrity/issues/177 [pr exists] [before CR] 
  - #175 Apply diagram changes (18 by TallTed, dlongley, iherman, msporny)
    https://github.com/w3c/vc-data-integrity/issues/175 [during CR] 
  - #170 Add normative guidance that @context files SHOULD be cached (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/170 [privacy-needs-resolution] [security-needs-resolution] [pr exists] [before CR] 
  - #169 Add Security Consideration to avoid key reuse (1 by kdenhartog)
    https://github.com/w3c/vc-data-integrity/issues/169 [security-needs-resolution] [during CR] 
  - #164 Is another context required to express JsonWebKey or Multikey? (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/164 [pending close (7 days)] [before CR] 

  3 issues closed:
  - Add normative guidance that @context files SHOULD be cached https://github.com/w3c/vc-data-integrity/issues/170 [privacy-needs-resolution] [security-needs-resolution] [pr exists] [before CR] 
  - Should this suite normatively require integrity checking of the context files? https://github.com/w3c/vc-data-integrity/issues/179 [ready for pr] [before CR] 
  - Is another context required to express JsonWebKey or Multikey? https://github.com/w3c/vc-data-integrity/issues/164 [pending close (7 days)] [before CR] 

* w3c/vc-di-eddsa (+0/-1/💬2)
  2 issues received 2 new comments:
  - #57 Point Privacy and Security Considerations section back to Data Integrity (1 by msporny)
    https://github.com/w3c/vc-di-eddsa/issues/57 [privacy-needs-resolution] [security-needs-resolution] [before CR] [ready for pr] 
  - #4 privateKeyMultibase (1 by msporny)
    https://github.com/w3c/vc-di-eddsa/issues/4 [before CR] [pr exists] 

  1 issues closed:
  - privateKeyMultibase https://github.com/w3c/vc-di-eddsa/issues/4 [before CR] [pr exists] 

* w3c/vc-di-ecdsa (+1/-0/💬2)
  1 issues created:
  - Add definition for secretKeyMultibase serialization (by msporny)
    https://github.com/w3c/vc-di-ecdsa/issues/35 [before CR] [ready for pr] 

  2 issues received 2 new comments:
  - #32 Ensure to pass SHA-384 param and fetch verification method early to get key size (1 by msporny)
    https://github.com/w3c/vc-di-ecdsa/issues/32 [before CR] [pr exists] 
  - #28 Add normative guidance that Deterministic signatures SHOULD be used (1 by msporny)
    https://github.com/w3c/vc-di-ecdsa/issues/28 [security-needs-resolution] [before CR] [pr exists] 

* w3c/vc-jwt (+1/-0/💬3)
  1 issues created:
  - Withdraw `application/vc+ld+json+jwt` and `application/vp+ld+json+jwt` (by OR13)
    https://github.com/w3c/vc-jose-cose/issues/141 

  2 issues received 3 new comments:
  - #141 Withdraw `application/vc+ld+json+jwt` and `application/vp+ld+json+jwt` (2 by brentzundel, mprorock)
    https://github.com/w3c/vc-jose-cose/issues/141 
  - #117 how is `kid` to be `useful to distinguish the specific key used`? (1 by vdods)
    https://github.com/w3c/vc-jose-cose/issues/117 



Pull requests
-------------
* w3c/vc-data-model (+6/-4/💬20)
  6 pull requests submitted:
  - Add Verification Method types to v2 context (by OR13)
    https://github.com/w3c/vc-data-model/pull/1260 
  - Sync and fix bugs in v2 context. (by msporny)
    https://github.com/w3c/vc-data-model/pull/1259 
  - Guidance around arrays (by brentzundel)
    https://github.com/w3c/vc-data-model/pull/1258 
  - Issue 1118 (by brentzundel)
    https://github.com/w3c/vc-data-model/pull/1257 
  - Address optionality of fields (by brentzundel)
    https://github.com/w3c/vc-data-model/pull/1256 
  - updates ACDC link to non-expired version (by m00sey)
    https://github.com/w3c/vc-data-model/pull/1255 

  11 pull requests received 20 new comments:
  - #1260 Add Verification Method types to v2 context (1 by OR13)
    https://github.com/w3c/vc-data-model/pull/1260 
  - #1259 Sync and fix bugs in v2 context. (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1259 
  - #1253 Vocabulary fixes — replacement of #1241 (2 by msporny, seabass-labrax)
    https://github.com/w3c/vc-data-model/pull/1253 
  - #1252 Add section about Names and Descriptions of credentials. (4 by David-Chadwick, OR13, msporny)
    https://github.com/w3c/vc-data-model/pull/1252 
  - #1251 Outline plan to mitigate normative context risk when transitioning to Proposed Recommendation (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1251 
  - #1250 Apply range requirements to validFrom/validUntil. (3 by longpd, msporny)
    https://github.com/w3c/vc-data-model/pull/1250 
  - #1249 Provide actionable guidance related to base context hash value. (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1249 
  - #1242 Add sd-jwt registered claim names to v2 context (1 by TallTed)
    https://github.com/w3c/vc-data-model/pull/1242 
  - #1238 Add language on mitm, replay, spoofing attacks (1 by decentralgabe)
    https://github.com/w3c/vc-data-model/pull/1238 
  - #1199 Add validation section regarding holder (2 by OR13)
    https://github.com/w3c/vc-data-model/pull/1199 
  - #1172 Add "author" and "party" to terminology, rewrite "claim" terminology (3 by brentzundel, decentralgabe)
    https://github.com/w3c/vc-data-model/pull/1172 

  4 pull requests merged:
  - Vocabulary fixes — replacement of #1241
    https://github.com/w3c/vc-data-model/pull/1253 
  - Outline plan to mitigate normative context risk when transitioning to Proposed Recommendation
    https://github.com/w3c/vc-data-model/pull/1251 
  - Apply range requirements to validFrom/validUntil.
    https://github.com/w3c/vc-data-model/pull/1250 
  - Provide actionable guidance related to base context hash value.
    https://github.com/w3c/vc-data-model/pull/1249 

* w3c/vc-use-cases (+1/-0/💬0)
  1 pull requests submitted:
  - Miscellaneous cleanup (by KDean-GS1)
    https://github.com/w3c/vc-use-cases/pull/148 

* w3c/vc-json-schema (+1/-1/💬1)
  1 pull requests submitted:
  - Change hard to test must to recommended (by decentralgabe)
    https://github.com/w3c/vc-json-schema/pull/208 

  1 pull requests received 1 new comments:
  - #205 Updated the respec plugin version (1 by andresuribe87)
    https://github.com/w3c/vc-json-schema/pull/205 

  1 pull requests merged:
  - Encourage OHTTP to prevent linking schema requests
    https://github.com/w3c/vc-json-schema/pull/207 

* w3c/vc-data-integrity (+6/-5/💬19)
  6 pull requests submitted:
  - Align context URLs with vocabulary URLs. (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/186 
  - Ensure that base URL is set to null when processing as RDF. (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/185 
  - Add `revoked` and `expires` properties to JsonWebKey context. (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/184 
  - Add cryptosuiteString to v2 context, preserving older v1 context. (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/181 
  - Align `datetimes` to `dateTimeStamp` values to ensure timezone. (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/178 
  - Add multibase datatype definition (by msporny)
    https://github.com/w3c/vc-data-integrity/pull/176 

  8 pull requests received 19 new comments:
  - #185 Ensure that base URL is set to null when processing as RDF. (2 by iherman, msporny)
    https://github.com/w3c/vc-data-integrity/pull/185 
  - #178 Align `datetimes` to `dateTimeStamp` values to ensure timezone. (1 by brianorwhatever)
    https://github.com/w3c/vc-data-integrity/pull/178 
  - #176 Add multibase datatype definition (4 by iherman, msporny)
    https://github.com/w3c/vc-data-integrity/pull/176 
  - #174 Add section on Resource Integrity and `digestMultibase`. (3 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/174 
  - #173 Add section on "Other" Security and Privacy Considerations (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/173 
  - #172 Add guidance on context and URL caching in general (2 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/172 
  - #171 Updated the vocabulary and added a diagram (5 by TallTed, iherman, msporny)
    https://github.com/w3c/vc-data-integrity/pull/171 [before CR] 
  - #99 Update controller document reference (1 by iherman)
    https://github.com/w3c/vc-data-integrity/pull/99 

  5 pull requests merged:
  - Add section on Resource Integrity and `digestMultibase`.
    https://github.com/w3c/vc-data-integrity/pull/174 
  - Add section on "Other" Security and Privacy Considerations
    https://github.com/w3c/vc-data-integrity/pull/173 
  - Add guidance on context and URL caching in general
    https://github.com/w3c/vc-data-integrity/pull/172 
  - Updated the vocabulary and added a diagram
    https://github.com/w3c/vc-data-integrity/pull/171 [before CR] 
  - Fix basic requirements of `proof`
    https://github.com/w3c/vc-data-integrity/pull/166 

* w3c/vc-di-eddsa (+2/-1/💬1)
  2 pull requests submitted:
  - Add secretKeyMultibase definition. (by dmitrizagidulin)
    https://github.com/w3c/vc-di-eddsa/pull/61 
  - Add advisements to read Data Integrity considerations sections. (by msporny)
    https://github.com/w3c/vc-di-eddsa/pull/60 

  1 pull requests received 1 new comments:
  - #59 Simplify language that warns of invalid examples (1 by msporny)
    https://github.com/w3c/vc-di-eddsa/pull/59 

  1 pull requests merged:
  - Simplify language that warns of invalid examples
    https://github.com/w3c/vc-di-eddsa/pull/59 

* w3c/vc-di-ecdsa (+2/-3/💬10)
  2 pull requests submitted:
  - Add secretKeyMultibase representation. (by dmitrizagidulin)
    https://github.com/w3c/vc-di-ecdsa/pull/37 
  - Add which cryptographic hash function to use for RDF-CANON. (by msporny)
    https://github.com/w3c/vc-di-ecdsa/pull/36 

  6 pull requests received 10 new comments:
  - #36 Add which cryptographic hash function to use for RDF-CANON. (3 by Wind4Greg, msporny)
    https://github.com/w3c/vc-di-ecdsa/pull/36 
  - #34 deterministic ECDSA SHOULD be used (1 by Wind4Greg)
    https://github.com/w3c/vc-di-ecdsa/pull/34 
  - #33 Add pointers back to Data Integrity Privacy and Security Considerations sections (2 by msporny)
    https://github.com/w3c/vc-di-ecdsa/pull/33 
  - #31 Simplify language that warns of invalid examples (2 by TallTed, seabass-labrax)
    https://github.com/w3c/vc-di-ecdsa/pull/31 
  - #27 Update selective disclosure functions and their use in ecdsa-sd sign, derive, verify. (1 by msporny)
    https://github.com/w3c/vc-di-ecdsa/pull/27 
  - #25 Cryptosuite Naming: Update example 4 and test vectors (1 by msporny)
    https://github.com/w3c/vc-di-ecdsa/pull/25 

  3 pull requests merged:
  - Add pointers back to Data Integrity Privacy and Security Considerations sections
    https://github.com/w3c/vc-di-ecdsa/pull/33 
  - Cryptosuite Naming: Update example 4 and test vectors
    https://github.com/w3c/vc-di-ecdsa/pull/25 
  - Update selective disclosure functions and their use in ecdsa-sd sign, derive, verify.
    https://github.com/w3c/vc-di-ecdsa/pull/27 

* w3c/vc-jwt (+3/-3/💬3)
  3 pull requests submitted:
  - Add support for DIDs (by OR13)
    https://github.com/w3c/vc-jose-cose/pull/144 
  - Changes to normative statements (by OR13)
    https://github.com/w3c/vc-jose-cose/pull/143 
  - Fix example plugin (by OR13)
    https://github.com/w3c/vc-jose-cose/pull/142 

  3 pull requests received 3 new comments:
  - #144 Add support for DIDs (1 by OR13)
    https://github.com/w3c/vc-jose-cose/pull/144 
  - #142 Fix example plugin (1 by OR13)
    https://github.com/w3c/vc-jose-cose/pull/142 
  - #139 Update examples (1 by OR13)
    https://github.com/w3c/vc-jose-cose/pull/139 

  3 pull requests merged:
  - Fix example plugin
    https://github.com/w3c/vc-jose-cose/pull/142 
  - Update examples
    https://github.com/w3c/vc-jose-cose/pull/139 
  - Add section on wallets / clients
    https://github.com/w3c/vc-jose-cose/pull/137 


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-json-schema
* https://github.com/w3c/vc-data-integrity
* https://github.com/w3c/vc-di-eddsa
* https://github.com/w3c/vc-di-ecdsa
* https://github.com/w3c/vc-di-bbs
* 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, 28 August 2023 17:01:23 UTC