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

Issues
------
* w3c/vc-data-model (+3/-4/💬40)
  3 issues created:
  - Revert language change on the definition of Subject (by jandrieu)
    https://github.com/w3c/vc-data-model/issues/1235 [before-CR] 
  - [VC-JWT] Reference is wrong (by nikosft)
    https://github.com/w3c/vc-data-model/issues/1233 
  - Revisit validation vs verification (by OR13)
    https://github.com/w3c/vc-data-model/issues/1232 

  10 issues received 40 new comments:
  - #1235 Revert language change on the definition of Subject (7 by RieksJ, TallTed, dlongley)
    https://github.com/w3c/vc-data-model/issues/1235 [before-CR] 
  - #1231 Minor change to validFrom requested (6 by David-Chadwick, TallTed, dlongley)
    https://github.com/w3c/vc-data-model/issues/1231 
  - #1227 Document the value of processing as JSON-LD (1 by OR13)
    https://github.com/w3c/vc-data-model/issues/1227 
  - #1216 Missing term in the vcdm spec (4 by iherman, msporny)
    https://github.com/w3c/vc-data-model/issues/1216 [before-CR] 
  - #1201 Document how VCs are processed as JSON today (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1201 [pr exists] [before-CR] 
  - #1173 Entities and Parties (1 by RieksJ)
    https://github.com/w3c/vc-data-model/issues/1173 [before-CR] 
  - #1048 Media types other than vc+ld+json (1 by msporny)
    https://github.com/w3c/vc-data-model/issues/1048 [pr exists] [media-type] [before-CR] 
  - #1010 `termsOfUse` is insufficiently specified (7 by David-Chadwick, OR13, TallTed, hendersonweb)
    https://github.com/w3c/vc-data-model/issues/1010 [conversation] [directory] [before-CR] 
  - #870 Evidence extension point (was: Improve tests for Evidence) (11 by OR13, TallTed, dmitrizagidulin, 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 msporny)
    https://github.com/w3c/vc-data-model/issues/860 [pr exists] [discuss] [before-CR] 

  4 issues closed:
  - Missing term in the vcdm spec https://github.com/w3c/vc-data-model/issues/1216 [before-CR] 
  - Entities and Parties https://github.com/w3c/vc-data-model/issues/1173 [before-CR] 
  - Media types other than vc+ld+json https://github.com/w3c/vc-data-model/issues/1048 [pr exists] [media-type] [before-CR] 
  - Document how VCs are processed as JSON today https://github.com/w3c/vc-data-model/issues/1201 [pr exists] [before-CR] 

* w3c/vc-json-schema (+2/-1/💬10)
  2 issues created:
  - Clarify the usage of the `id` property in `credentialSubject` when using `JsonSchemaCredential` (by decentralgabe)
    https://github.com/w3c/vc-json-schema/issues/197 
  - JSON schema's `type` and VC.context.JsonSchema.type (by andresuribe87)
    https://github.com/w3c/vc-json-schema/issues/194 

  3 issues received 10 new comments:
  - #197 Clarify the usage of the `id` property in `credentialSubject` when using `JsonSchemaCredential` (7 by TallTed, decentralgabe, dlongley)
    https://github.com/w3c/vc-json-schema/issues/197 [pre-cr] 
  - #194 JSON schema's `type` and VC.context.JsonSchema.type (1 by decentralgabe)
    https://github.com/w3c/vc-json-schema/issues/194 
  - #133 Being able to normatively reference JSON Schema (2 by Relequestual, iherman)
    https://github.com/w3c/vc-json-schema/issues/133 [planning] [process] 

  1 issues closed:
  - Add warning for improperly formed schemes using multiple schemas https://github.com/w3c/vc-json-schema/issues/136 [enhancement] [pre-cr] 

* w3c/vc-data-integrity (+2/-14/💬19)
  2 issues created:
  - Conformance classes usage of the word "data model" (by msporny)
    https://github.com/w3c/vc-data-integrity/issues/165 
  - Is a another context required to express JsonWebKey or Multikey? (by msporny)
    https://github.com/w3c/vc-data-integrity/issues/164 

  16 issues received 19 new comments:
  - #164 Is a another context required to express JsonWebKey or Multikey? (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/164 [before CR] 
  - #159 Clearly define conformance classes (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/159 [pr exists] [before CR] 
  - #157 Do not assume errors can be surfaced (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/157 [pr exists] [before CR] 
  - #151 Add definition sections for secretKeyJwk and secretKeyMultibase (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/151 [pr exists] [before CR] 
  - #136 Add table for all error conditions (2 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/136 [pr exists] [before CR] 
  - #131 Ensure that documents that drop data throw errors (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/131 [pr exists] [before CR] 
  - #130 Add JsonWebKey definition in Data Integrity (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/130 [pr exists] [before CR] 
  - #129 Missing term definitions in the spec (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/129 [pr exists] [before CR] 
  - #107 Describe how JSON-LD framing is used with Selective Disclosure (1 by OR13)
    https://github.com/w3c/vc-data-integrity/issues/107 [during CR] 
  - #88 Specify a default context if JSON-LD processing is required (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/88 [pr exists] [before CR] 
  - #78 Expiration Date (2 by David-Chadwick, TallTed)
    https://github.com/w3c/vc-data-integrity/issues/78 [pr exists] [before CR] 
  - #74 Domain and range of sec:publicKey (2 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/74 [pr exists] [before CR] 
  - #73 domain of publicKeyJWK should be rdf:JSON (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/73 [pr exists] [before CR] 
  - #66 Cleanly separate cryptosuite verification and purpose verification algorithms (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/66 [pr exists] [before CR] 
  - #60 Explain how proof types are mapped to URLs (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/60 [pr exists] [before CR] 
  - #29 domain should be a string or array (1 by msporny)
    https://github.com/w3c/vc-data-integrity/issues/29 [pr exists] [before CR] 

  14 issues closed:
  - relating an agent to their key? https://github.com/w3c/vc-data-integrity/issues/110 [question] [pending close (7 days)] 
  - Clearly define conformance classes https://github.com/w3c/vc-data-integrity/issues/159 [pr exists] [before CR] 
  - Do not assume errors can be surfaced https://github.com/w3c/vc-data-integrity/issues/157 [pr exists] [before CR] 
  - Add definition sections for secretKeyJwk and secretKeyMultibase https://github.com/w3c/vc-data-integrity/issues/151 [pr exists] [before CR] 
  - Add table for all error conditions https://github.com/w3c/vc-data-integrity/issues/136 [pr exists] [before CR] 
  - Ensure that documents that drop data throw errors https://github.com/w3c/vc-data-integrity/issues/131 [pr exists] [before CR] 
  - Add JsonWebKey definition in Data Integrity https://github.com/w3c/vc-data-integrity/issues/130 [pr exists] [before CR] 
  - Missing term definitions in the spec https://github.com/w3c/vc-data-integrity/issues/129 [pr exists] [before CR] 
  - Specify a default context if JSON-LD processing is required https://github.com/w3c/vc-data-integrity/issues/88 [pr exists] [before CR] 
  - Domain and range of sec:publicKey https://github.com/w3c/vc-data-integrity/issues/74 [pr exists] [before CR] 
  - domain of publicKeyJWK should be rdf:JSON https://github.com/w3c/vc-data-integrity/issues/73 [pr exists] [before CR] 
  - Cleanly separate cryptosuite verification and purpose verification algorithms https://github.com/w3c/vc-data-integrity/issues/66 [pr exists] [before CR] 
  - Explain how proof types are mapped to URLs https://github.com/w3c/vc-data-integrity/issues/60 [pr exists] [before CR] 
  - domain should be a string or array https://github.com/w3c/vc-data-integrity/issues/29 [pr exists] [before CR] 

* w3c/vc-di-eddsa (+1/-0/💬2)
  1 issues created:
  - Add definition for secretKeyMultibase serialization (by dmitrizagidulin)
    https://github.com/w3c/vc-di-eddsa/issues/56 

  1 issues received 2 new comments:
  - #4 privateKeyMultibase (2 by OR13, dmitrizagidulin)
    https://github.com/w3c/vc-di-eddsa/issues/4 [before CR] [pr exists] 

* w3c/vc-di-ecdsa (+1/-0/💬6)
  1 issues created:
  - Clarifying `publicKeyMultibase` encoding: `did:key` style with multicodec code, or not? (by bnewbold)
    https://github.com/w3c/vc-di-ecdsa/issues/26 

  1 issues received 6 new comments:
  - #22 Confirming `EcdsaSecp256r1VerificationKey2019` -> `Multikey` transition (6 by OR13, bnewbold, dmitrizagidulin, msporny)
    https://github.com/w3c/vc-di-ecdsa/issues/22 [question] [during CR] 

* w3c/vc-di-bbs (+0/-0/💬1)
  1 issues received 1 new comments:
  - #90 Hosted JSON-LD context should expose itself as `ld+json` instead of `json` (1 by tmarkovski)
    https://github.com/w3c/vc-di-bbs/issues/90 

* w3c/vc-jwt (+2/-1/💬18)
  2 issues created:
  - signature profiles (by alenhorvat)
    https://github.com/w3c/vc-jose-cose/issues/136 
  - Can registered JWT claims be used only in the JOSE header?? (by Sakurann)
    https://github.com/w3c/vc-jose-cose/issues/135 

  9 issues received 18 new comments:
  - #136 signature profiles (3 by OR13, TallTed)
    https://github.com/w3c/vc-jose-cose/issues/136 
  - #135 Can registered JWT claims be used only in the JOSE header?? (4 by Sakurann, alenhorvat)
    https://github.com/w3c/vc-jose-cose/issues/135 
  - #132 JWT - securing mechanism or not? (2 by OR13)
    https://github.com/w3c/vc-jose-cose/issues/132 
  - #128 File PING request once rename is complete (1 by mprorock)
    https://github.com/w3c/vc-jose-cose/issues/128 
  - #127 Better references to OIDC key discovery (3 by OR13, Sakurann, selfissued)
    https://github.com/w3c/vc-jose-cose/issues/127 
  - #119 Deprecate `vc` & `vp` ? (2 by OR13, Sakurann)
    https://github.com/w3c/vc-jose-cose/issues/119 
  - #95 Internationalization Review for VC JOSE COSE (1 by Sakurann)
    https://github.com/w3c/vc-jose-cose/issues/95 [horizontal-review] 
  - #94 Accessibility Self-Review for VC-JWT (1 by Sakurann)
    https://github.com/w3c/vc-jose-cose/issues/94 [horizontal-review] 
  - #49 Change spec name? (1 by Sakurann)
    https://github.com/w3c/vc-jose-cose/issues/49 

  1 issues closed:
  - Change spec name? https://github.com/w3c/vc-jose-cose/issues/49 



Pull requests
-------------
* w3c/vc-data-model (+2/-10/💬32)
  2 pull requests submitted:
  - Added an SVG diagram of the vocabulary. (by iherman)
    https://github.com/w3c/vc-data-model/pull/1236 
  - Update links from VC-JWT to VC-JOSE-COSE (by andresuribe87)
    https://github.com/w3c/vc-data-model/pull/1234 

  17 pull requests received 32 new comments:
  - #1236 Added an SVG diagram of the vocabulary. (1 by OR13)
    https://github.com/w3c/vc-data-model/pull/1236 
  - #1230 Removing the serviceEndpoint vocabulary item (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1230 
  - #1229 Editorial update index.html: use JsonSchema and not JsonSchema2023 — bis (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1229 [before-CR] 
  - #1228 Added reserved confidenceMethod property to the vocabulary — bis (1 by iherman)
    https://github.com/w3c/vc-data-model/pull/1228 [before-CR] 
  - #1225 Editorial update index.html: use JsonSchema and not JsonSchema2023 (2 by brentzundel, msporny)
    https://github.com/w3c/vc-data-model/pull/1225 [pending close] 
  - #1223 Add aud registered claim to v2 context (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1223 
  - #1222 Add exp registered claim to v2 context  (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1222 
  - #1221 Add nbf registered claim to v2 context  (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1221 
  - #1220 Add iat registered claim to v2 context (1 by msporny)
    https://github.com/w3c/vc-data-model/pull/1220 
  - #1219 Add cnf registered claim to v2 context (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1219 
  - #1218 Added JsonSchemaCredential to the vocabulary, and remove '2023' from JsonSchema2023 (2 by decentralgabe, iherman)
    https://github.com/w3c/vc-data-model/pull/1218 [before-CR] 
  - #1215 Update term definition for vc json schemas as creds (6 by OR13, decentralgabe, iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1215 
  - #1212 Refer to VC-SPECS-DIR for proof types. (1 by iherman)
    https://github.com/w3c/vc-data-model/pull/1212 
  - #1211 Clarify that some abstract concepts are not realized in implementations (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1211 
  - #1202 Add section on JSON Processing. (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/1202 
  - #1199 Add validation section regarding holder (3 by OR13, TallTed, iherman)
    https://github.com/w3c/vc-data-model/pull/1199 
  - #1172 Add "author" and "party" to terminology, rewrite "claim" terminology (4 by OR13, RieksJ, TallTed, iherman)
    https://github.com/w3c/vc-data-model/pull/1172 

  10 pull requests merged:
  - Removing the serviceEndpoint vocabulary item
    https://github.com/w3c/vc-data-model/pull/1230 
  - Editorial update index.html: use JsonSchema and not JsonSchema2023 — bis
    https://github.com/w3c/vc-data-model/pull/1229 [before-CR] 
  - Add aud registered claim to v2 context
    https://github.com/w3c/vc-data-model/pull/1223 
  - Add exp registered claim to v2 context 
    https://github.com/w3c/vc-data-model/pull/1222 
  - Add nbf registered claim to v2 context 
    https://github.com/w3c/vc-data-model/pull/1221 
  - Add iat registered claim to v2 context
    https://github.com/w3c/vc-data-model/pull/1220 
  - Add cnf registered claim to v2 context
    https://github.com/w3c/vc-data-model/pull/1219 
  - Add section on JSON Processing.
    https://github.com/w3c/vc-data-model/pull/1202 
  - Added JsonSchemaCredential to the vocabulary, and remove '2023' from JsonSchema2023
    https://github.com/w3c/vc-data-model/pull/1218 [before-CR] 
  - Update term definition for vc json schemas as creds
    https://github.com/w3c/vc-data-model/pull/1215 

* w3c/vc-json-schema (+5/-2/💬7)
  5 pull requests submitted:
  - Add OpenAPI/YAML Representation (by decentralgabe)
    https://github.com/w3c/vc-json-schema/pull/200 
  - Media types for plain json schema, JWT, and SD-JWT (by decentralgabe)
    https://github.com/w3c/vc-json-schema/pull/198 
  - Change plugin to one that supports vc-jose-cose with VCDM 2.0 (by andresuribe87)
    https://github.com/w3c/vc-json-schema/pull/196 
  - Added validation examples. (by andresuribe87)
    https://github.com/w3c/vc-json-schema/pull/195 
  - Added warning to avoid composition problems. (by andresuribe87)
    https://github.com/w3c/vc-json-schema/pull/193 

  2 pull requests received 7 new comments:
  - #196 Change plugin to one that supports vc-jose-cose with VCDM 2.0 (5 by OR13, TallTed, decentralgabe)
    https://github.com/w3c/vc-json-schema/pull/196 
  - #195 Added validation examples. (2 by andresuribe87, decentralgabe)
    https://github.com/w3c/vc-json-schema/pull/195 

  2 pull requests merged:
  - Added warning to avoid composition problems.
    https://github.com/w3c/vc-json-schema/pull/193 
  - Added validation examples.
    https://github.com/w3c/vc-json-schema/pull/195 

* w3c/vc-data-integrity (+1/-13/💬26)
  1 pull requests submitted:
  - Adding domain and defined_by to revoked (by iherman)
    https://github.com/w3c/vc-data-integrity/pull/163 

  16 pull requests received 26 new comments:
  - #160 Add conformance classes to specification. (2 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/160 
  - #158 Allow errors to be conveyed based on execution environment. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/158 
  - #156 Update domain to support arrays of domain values. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/156 
  - #155 Add text on difference between proof and VC validity periods. (3 by David-Chadwick, TallTed)
    https://github.com/w3c/vc-data-integrity/pull/155 
  - #154 Add revoked definition and anchor for vocabulary. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/154 
  - #153 Add anchor and definition for proof property. (2 by iherman, msporny)
    https://github.com/w3c/vc-data-integrity/pull/153 
  - #152 Define anchors for secretKeyJwk and secretKeyMultibase (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/152 
  - #150 Add a JsonWebKey context file. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/150 
  - #149 Add a Multikey context file. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/149 
  - #148 Add vocab definitions for secretKeyJwk and secretKeyMultibase (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/148 
  - #147 Add Dmitri to codeowners and editors. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/147 
  - #145 Extended proof chain algorithms (2 by Wind4Greg, msporny)
    https://github.com/w3c/vc-data-integrity/pull/145 
  - #143 Correcting previously mis-corrected sentence (3 by TallTed, msporny)
    https://github.com/w3c/vc-data-integrity/pull/143 
  - #135 Add JSON Web Key to specification (3 by OR13, msporny)
    https://github.com/w3c/vc-data-integrity/pull/135 
  - #133 Clarify how proof types (and terms) are mapped to URLs. (1 by msporny)
    https://github.com/w3c/vc-data-integrity/pull/133 
  - #99 Update controller document reference (2 by OR13, dmitrizagidulin)
    https://github.com/w3c/vc-data-integrity/pull/99 

  13 pull requests merged:
  - Add conformance classes to specification.
    https://github.com/w3c/vc-data-integrity/pull/160 
  - Allow errors to be conveyed based on execution environment.
    https://github.com/w3c/vc-data-integrity/pull/158 
  - Update domain to support arrays of domain values.
    https://github.com/w3c/vc-data-integrity/pull/156 
  - Add revoked definition and anchor for vocabulary.
    https://github.com/w3c/vc-data-integrity/pull/154 
  - Add anchor and definition for proof property.
    https://github.com/w3c/vc-data-integrity/pull/153 
  - Correcting previously mis-corrected sentence
    https://github.com/w3c/vc-data-integrity/pull/143 
  - Add JSON Web Key to specification
    https://github.com/w3c/vc-data-integrity/pull/135 
  - Define anchors for secretKeyJwk and secretKeyMultibase
    https://github.com/w3c/vc-data-integrity/pull/152 
  - Add a JsonWebKey context file.
    https://github.com/w3c/vc-data-integrity/pull/150 
  - Add a Multikey context file.
    https://github.com/w3c/vc-data-integrity/pull/149 
  - Add vocab definitions for secretKeyJwk and secretKeyMultibase
    https://github.com/w3c/vc-data-integrity/pull/148 
  - Add Dmitri to codeowners and editors.
    https://github.com/w3c/vc-data-integrity/pull/147 
  - Clarify how proof types (and terms) are mapped to URLs.
    https://github.com/w3c/vc-data-integrity/pull/133 

* w3c/vc-di-eddsa (+0/-3/💬5)
  3 pull requests received 5 new comments:
  - #54 Remove mis-implementation Issue (1 by msporny)
    https://github.com/w3c/vc-di-eddsa/pull/54 
  - #53 Update Cryptosuite Names. (2 by msporny)
    https://github.com/w3c/vc-di-eddsa/pull/53 
  - #51 Add EdDSA mitigation for dataset poisoning. (2 by msporny)
    https://github.com/w3c/vc-di-eddsa/pull/51 

  3 pull requests merged:
  - Remove mis-implementation Issue
    https://github.com/w3c/vc-di-eddsa/pull/54 
  - Update Cryptosuite Names.
    https://github.com/w3c/vc-di-eddsa/pull/53 
  - Add EdDSA mitigation for dataset poisoning.
    https://github.com/w3c/vc-di-eddsa/pull/51 

* w3c/vc-di-ecdsa (+1/-1/💬5)
  1 pull requests submitted:
  - Cryptosuite Naming: Update example 4 and test vectors (by Wind4Greg)
    https://github.com/w3c/vc-di-ecdsa/pull/25 

  2 pull requests received 5 new comments:
  - #23 Update crypto-suite names (3 by Wind4Greg, msporny)
    https://github.com/w3c/vc-di-ecdsa/pull/23 
  - #21 Mitigate poison datasets in ECDSA when canonicalizing. (2 by OR13, msporny)
    https://github.com/w3c/vc-di-ecdsa/pull/21 

  1 pull requests merged:
  - Update crypto-suite names
    https://github.com/w3c/vc-di-ecdsa/pull/23 

* w3c/vc-jwt (+0/-1/💬13)
  1 pull requests received 13 new comments:
  - #123 Address Ambiguity Regarding Multiple Structured Suffixes (13 by OR13, TallTed, alenhorvat, andresuribe87)
    https://github.com/w3c/vc-jose-cose/pull/123 

  1 pull requests merged:
  - remove securing json
    https://github.com/w3c/vc-jose-cose/pull/88 [tag-needs-resolution] 

* w3c/vc-status-list-2021 (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #69 chore: update title and urls to contexts (1 by 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-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, 14 August 2023 17:01:21 UTC