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

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Mon, 20 Nov 2023 17:01:30 +0000
To: public-credentials@w3.org
Message-Id: <E1r57eM-009EIj-Rm@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+0/-5/💬30)
  15 issues received 30 new comments:
  - #1352 Add mechanism to embed externally secured VCs in a VP (5 by dlongley, longpd, msporny)
    https://github.com/w3c/vc-data-model/issues/1352 [ready for PR] [before-CR] 
  - #1348 Non-normative changes from Jeffrey Yasskin's review (1 by jyasskin)
    https://github.com/w3c/vc-data-model/issues/1348 [ready for PR] [post-CR] 
  - #1347 Normative changes from Jeffrey Yasskin's review (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1347 [ready for PR] [before-CR] 
  - #1341 credentialSubject doesn't say how to identify the "subjects" of the verifiable credential. (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1341 [pr exists] [before-CR] 
  - #1335 Recommend how authors set default language and direction (2 by aphillips, msporny)
    https://github.com/w3c/vc-data-model/issues/1335 [pr exists] [i18n-needs-resolution] [before-CR] 
  - #1328 Make validation normative (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1328 [before-CR] 
  - #1319 Cross-check the `domain`/`range` statements in the vocabulary with the VCDM spec (5 by TallTed, iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1319 [ready for PR] [before-CR] 
  - #1313 Use a better example for bidirectional text (Editorial) (1 by aphillips)
    https://github.com/w3c/vc-data-model/issues/1313 [editorial] [i18n-tracker] [post-CR] 
  - #1300 Clarify what conformance means to the issuers/verifiers (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1300 [pr exists] [discuss] [before-CR] 
  - #1290 JSON-only processors and VCDM 2.0 conformance (1 by iherman)
    https://github.com/w3c/vc-data-model/issues/1290 [before-CR] 
  - #1266 Recommend that authors don't use `@base` in `@context` (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1266 [pr exists] [before-CR] 
  - #1265 Add `relatedResource` to `VerifiablePresentation` (5 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1265 [pending close] [before-CR] 
  - #1247 Addressing Verifier Stored Data Vulnerabilities and Legal Compliance (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1247 [ready for PR] [HorizontalReview] [privacy-needs-resolution] [security-needs-resolution] [before-CR] 
  - #1244 Address Metadata-Driven Correlation (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1244 [ready for PR] [HorizontalReview] [privacy-needs-resolution] [before-CR] 
  - #1047 NIST defines "credential" differently (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1047 [pr exists] [terminology] [before-CR] 

  5 issues closed:
  - credentialSubject doesn't say how to identify the "subjects" of the verifiable credential. https://github.com/w3c/vc-data-model/issues/1341 [pr exists] [before-CR] 
  - Recommend how authors set default language and direction https://github.com/w3c/vc-data-model/issues/1335 [pr exists] [i18n-needs-resolution] [before-CR] 
  - Clarify what conformance means to the issuers/verifiers https://github.com/w3c/vc-data-model/issues/1300 [pr exists] [discuss] [before-CR] 
  - Recommend that authors don't use `@base` in `@context` https://github.com/w3c/vc-data-model/issues/1266 [pr exists] [before-CR] 
  - NIST defines "credential" differently https://github.com/w3c/vc-data-model/issues/1047 [pr exists] [terminology] [before-CR] 

* w3c/vc-json-schema (+0/-1/💬1)
  1 issues received 1 new comments:
  - #224 Provide for localization of a VC JSON Schema document (1 by aphillips)
    https://github.com/w3c/vc-json-schema/issues/224 [i18n-needs-resolution] 

  1 issues closed:
  - Provide for localization of a VC JSON Schema document https://github.com/w3c/vc-json-schema/issues/224 [i18n-needs-resolution] 

* w3c/vc-data-integrity (+1/-1/💬9)
  1 issues created:
  - Discrepancy Between DataIntegrityProof EdDSA `eddsa-2022` vs Crypto Suite `eddsa-rdfc-2022` Definition (by LuisOsta)
    https://github.com/w3c/vc-data-integrity/issues/221 

  2 issues received 9 new comments:
  - #221 Discrepancy Between DataIntegrityProof EdDSA `eddsa-2022` vs Crypto Suite `eddsa-rdfc-2022` Definition (8 by LuisOsta, Wind4Greg, dlongley, msporny)
    https://github.com/w3c/vc-data-integrity/issues/221 
  - #96 Internationalization Review for VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa) (1 by aphillips)
    https://github.com/w3c/vc-data-integrity/issues/96 [i18n-tracker] 

  1 issues closed:
  - Internationalization Review for VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa) https://github.com/w3c/vc-data-integrity/issues/96 [i18n-tracker] 

* w3c/vc-jwt (+3/-5/💬10)
  3 issues created:
  - Add COSE Example (by OR13)
    https://github.com/w3c/vc-jose-cose/issues/182 [before-CR] 
  - Update normative guidance for `vc` and `vp` claims (by OR13)
    https://github.com/w3c/vc-jose-cose/issues/180 
  - Change the registration request for SD-JWT (by OR13)
    https://github.com/w3c/vc-jose-cose/issues/179 

  7 issues received 10 new comments:
  - #180 Update normative guidance for `vc` and `vp` claims (1 by decentralgabe)
    https://github.com/w3c/vc-jose-cose/issues/180 
  - #179 Change the registration request for SD-JWT (4 by TallTed, msporny, selfissued)
    https://github.com/w3c/vc-jose-cose/issues/179 [before-CR] 
  - #173 Add a reference to Data Integrity Specification Registries when it exists (1 by decentralgabe)
    https://github.com/w3c/vc-jose-cose/issues/173 [editorial] 
  - #169 Missing word and missing referent in section 2 (1 by decentralgabe)
    https://github.com/w3c/vc-jose-cose/issues/169 [editorial] 
  - #168 Broken links to iss (1 by decentralgabe)
    https://github.com/w3c/vc-jose-cose/issues/168 [editorial] 
  - #167 Example does not correspond to description in section 5.3.1 (1 by decentralgabe)
    https://github.com/w3c/vc-jose-cose/issues/167 [editorial] 
  - #160 Controller Documents vs DID Documents (1 by OR13)
    https://github.com/w3c/vc-jose-cose/issues/160 

  5 issues closed:
  - Example does not correspond to description in section 5.3.1 https://github.com/w3c/vc-jose-cose/issues/167 [editorial] 
  - Broken links to iss https://github.com/w3c/vc-jose-cose/issues/168 [editorial] 
  - Missing word and missing referent in section 2 https://github.com/w3c/vc-jose-cose/issues/169 [editorial] 
  - Add a reference to Data Integrity Specification Registries when it exists https://github.com/w3c/vc-jose-cose/issues/173 [editorial] 
  - Remove internationalization considerations section? https://github.com/w3c/vc-jose-cose/issues/172 [i18n-needs-resolution] 

* w3c/vc-status-list-2021 (+1/-1/💬1)
  1 issues created:
  - Support historical query of status lists (by decentralgabe)
    https://github.com/w3c/vc-bitstring-status-list/issues/94 

  1 issues received 1 new comments:
  - #90 Rename specification to "Herd Privacy Status List" (1 by msporny)
    https://github.com/w3c/vc-bitstring-status-list/issues/90 [before-CR] 

  1 issues closed:
  - Rename specification to "Herd Privacy Status List" https://github.com/w3c/vc-bitstring-status-list/issues/90 [before-CR] 



Pull requests
-------------
* w3c/vc-data-model (+6/-10/💬24)
  6 pull requests submitted:
  - Add mechanism to embed enveloped VCs in VPs. (by msporny)
    https://github.com/w3c/vc-data-model/pull/1358 
  - Address @jyasskin's pre-Candidate Recommendation review comments (by msporny)
    https://github.com/w3c/vc-data-model/pull/1357 
  - Add section on Data Theft to Privacy Considerations. (by msporny)
    https://github.com/w3c/vc-data-model/pull/1356 
  - Add section on metadata-based correlation. (by msporny)
    https://github.com/w3c/vc-data-model/pull/1355 
  - Update Editors to reflect contributions. (by msporny)
    https://github.com/w3c/vc-data-model/pull/1354 
  - Massaging text for default language and direction (by TallTed)
    https://github.com/w3c/vc-data-model/pull/1353 

  14 pull requests received 24 new comments:
  - #1358 Add mechanism to embed enveloped VCs in VPs. (3 by longpd, msporny)
    https://github.com/w3c/vc-data-model/pull/1358 [before-CR] 
  - #1354 Update Editors to reflect contributions. (1 by iherman)
    https://github.com/w3c/vc-data-model/pull/1354 [post-CR] 
  - #1351 Update JSON Processing section to Credential-Type-Specific Processing. (1 by iherman)
    https://github.com/w3c/vc-data-model/pull/1351 
  - #1350 (editorial) Assorted grammar, markup, source formatting, etc. (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1350 [before-CR] 
  - #1346 Clarify credentialSubject requirements to improve testability. (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1346 [before-CR] 
  - #1345 catching omissions from change requests on #1295 (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1345 [post-CR] 
  - #1344 Clarify normative statement related to timezone offsets. (5 by TallTed, dlongley, msporny)
    https://github.com/w3c/vc-data-model/pull/1344 [before-CR] 
  - #1340 Use JSON-LD keywords for languages. (3 by BigBlueHat, msporny)
    https://github.com/w3c/vc-data-model/pull/1340 [post-CR] 
  - #1339 Explain default language expression. (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1339 [before-CR] 
  - #1338 Add verification algorithm to specification. (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1338 [before-CR] 
  - #1336 Add conformance classes for issuers and verifiers. (2 by msporny)
    https://github.com/w3c/vc-data-model/pull/1336 [before-CR] 
  - #1332 Add comparison to NIST definition (1 by brentzundel)
    https://github.com/w3c/vc-data-model/pull/1332 [before-CR] 
  - #1276 Warn that using dynamic processor features might lead to less interoperability (2 by msporny)
    https://github.com/w3c/vc-data-model/pull/1276 [post-CR] 
  - #1271 Warn authors that usage of global JSON-LD keywords might harm interoperability (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1271 [before-CR] 

  10 pull requests merged:
  - Use JSON-LD keywords for languages.
    https://github.com/w3c/vc-data-model/pull/1340 [post-CR] 
  - Clarify normative statement related to timezone offsets.
    https://github.com/w3c/vc-data-model/pull/1344 [before-CR] 
  - (editorial) Assorted grammar, markup, source formatting, etc.
    https://github.com/w3c/vc-data-model/pull/1350 [before-CR] 
  - Clarify credentialSubject requirements to improve testability.
    https://github.com/w3c/vc-data-model/pull/1346 [before-CR] 
  - catching omissions from change requests on #1295
    https://github.com/w3c/vc-data-model/pull/1345 [post-CR] 
  - Explain default language expression.
    https://github.com/w3c/vc-data-model/pull/1339 [before-CR] 
  - Add conformance classes for issuers and verifiers.
    https://github.com/w3c/vc-data-model/pull/1336 [before-CR] 
  - Warn that using dynamic processor features might lead to less interoperability
    https://github.com/w3c/vc-data-model/pull/1276 [post-CR] 
  - Warn authors that usage of global JSON-LD keywords might harm interoperability
    https://github.com/w3c/vc-data-model/pull/1271 [before-CR] 
  - Add comparison to NIST definition
    https://github.com/w3c/vc-data-model/pull/1332 [before-CR] 

* w3c/vc-use-cases (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #151 GS1 identification use case (1 by paulfdietrich)
    https://github.com/w3c/vc-use-cases/pull/151 

* w3c/vc-json-schema (+2/-3/💬0)
  2 pull requests submitted:
  - Added the final CR version (by iherman)
    https://github.com/w3c/vc-json-schema/pull/229 
  - Including commits that were missed (by andresuribe87)
    https://github.com/w3c/vc-json-schema/pull/228 

  3 pull requests merged:
  - Added the final CR version
    https://github.com/w3c/vc-json-schema/pull/229 
  - Including commits that were missed
    https://github.com/w3c/vc-json-schema/pull/228 
  - Renamed `name` to `title` and added `lang` & `dir`.
    https://github.com/w3c/vc-json-schema/pull/225 

* w3c/vc-data-integrity (+1/-0/💬0)
  1 pull requests submitted:
  - Added the final CR Version (by iherman)
    https://github.com/w3c/vc-data-integrity/pull/220 

* w3c/vc-di-eddsa (+1/-0/💬0)
  1 pull requests submitted:
  - Added the final CR Version (by iherman)
    https://github.com/w3c/vc-di-eddsa/pull/68 

* w3c/vc-di-ecdsa (+1/-0/💬0)
  1 pull requests submitted:
  - Added the final CR Version (by iherman)
    https://github.com/w3c/vc-di-ecdsa/pull/44 

* w3c/vc-jwt (+1/-3/💬0)
  1 pull requests submitted:
  - Disallow vc and vp claims in head or payloads (by decentralgabe)
    https://github.com/w3c/vc-jose-cose/pull/181 

  3 pull requests merged:
  - (editorial) improve language by inverting a couple of parentheticals
    https://github.com/w3c/vc-jose-cose/pull/178 
  - (editorial) fix some typos, markup, and punctuation
    https://github.com/w3c/vc-jose-cose/pull/177 
  - Fix a few issues, formatting, issue tagging
    https://github.com/w3c/vc-jose-cose/pull/176 


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, 20 November 2023 17:01:33 UTC