- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 07 Aug 2023 17:01:22 +0000
- To: public-credentials@w3.org
- Message-Id: <E1qT3be-003RYh-Ag@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+1/-0/💬10)
1 issues created:
- Document the value of processing as JSON-LD (by OR13)
https://github.com/w3c/vc-data-model/issues/1227
2 issues received 10 new comments:
- #1227 Document the value of processing as JSON-LD (7 by OR13, awoie, dlongley, mtaimela)
https://github.com/w3c/vc-data-model/issues/1227
- #1201 Document how VCs are processed as JSON today (3 by OR13, msporny)
https://github.com/w3c/vc-data-model/issues/1201 [pr exists] [before-CR]
* w3c/vc-json-schema (+0/-10/💬5)
5 issues received 5 new comments:
- #179 Consider removing versioning from the name (1 by decentralgabe)
https://github.com/w3c/vc-json-schema/issues/179 [enhancement]
- #178 Change VerifiableCredentialSchema2023 to use a new property with the @json type (1 by decentralgabe)
https://github.com/w3c/vc-json-schema/issues/178 [enhancement]
- #167 Security and Privacy Self-Review Questionnaire (1 by decentralgabe)
https://github.com/w3c/vc-json-schema/issues/167 [horizontal-review]
- #122 How can JSON Schemas be used with JSON-LD? Why is this useful? (1 by andresuribe87)
https://github.com/w3c/vc-json-schema/issues/122 [v2] [pre-cr]
- #106 How does using JSON Schemas enable interoperability? (1 by decentralgabe)
https://github.com/w3c/vc-json-schema/issues/106 [enhancement] [v2]
10 issues closed:
- How can JSON Schemas be used with JSON-LD? Why is this useful? https://github.com/w3c/vc-json-schema/issues/122 [v2] [pre-cr]
- Add language for handling implementation mismatches https://github.com/w3c/vc-json-schema/issues/181 [enhancement] [pre-cr]
- How does using JSON Schemas enable interoperability? https://github.com/w3c/vc-json-schema/issues/106 [enhancement] [v2]
- Consider removing versioning from the name https://github.com/w3c/vc-json-schema/issues/179 [enhancement]
- Add text to clarify when to use JsonSchema2023 over CredentialSchema2023 https://github.com/w3c/vc-json-schema/issues/173 [enhancement]
- Section 3.1.1 encourages dereferencable IRIs https://github.com/w3c/vc-json-schema/issues/176 [enhancement] [good first issue]
- Update term definitions to match the VCDM's vocab https://github.com/w3c/vc-json-schema/issues/182 [enhancement]
- Change VerifiableCredentialSchema2023 to use a new property with the @json type https://github.com/w3c/vc-json-schema/issues/178 [enhancement]
- What is the difference between JsonSchema2023 and CredentialSchema2023? https://github.com/w3c/vc-json-schema/issues/172 [question]
- Require all implementers to support at least one common JSON Schema version https://github.com/w3c/vc-json-schema/issues/180 [enhancement]
* w3c/vc-data-integrity (+4/-1/💬17)
4 issues created:
- Add sec:cryptosuite data type to vocabulary (by msporny)
https://github.com/w3c/vc-data-integrity/issues/161
- Clearly define conformance classes (by msporny)
https://github.com/w3c/vc-data-integrity/issues/159
- Do not assume errors can be surfaced (by msporny)
https://github.com/w3c/vc-data-integrity/issues/157 [ready for pr] [before CR]
- Add definition sections for secretKeyJwk and secretKeyMultibase (by msporny)
https://github.com/w3c/vc-data-integrity/issues/151
11 issues received 17 new comments:
- #161 Add sec:cryptosuite data type to vocabulary (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/161 [ready for pr] [before CR]
- #159 Clearly define conformance classes (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/159 [ready for pr]
- #157 Do not assume errors can be surfaced (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/157 [ready for pr] [before CR]
- #151 Add definition sections for secretKeyJwk and secretKeyMultibase (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/151 [ready for pr] [before CR]
- #129 Missing term definitions in the spec (3 by msporny)
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 (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/120 [ready for pr] [before CR]
- #110 relating an agent to their key? (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/110 [question]
- #107 Describe how JSON-LD framing is used with Selective Disclosure (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/107 [after CR]
- #87 Potential attacks on `previousProof` and algorithmic mitigations (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/87 [ready for pr] [before CR]
- #78 Expiration Date (4 by David-Chadwick, msporny)
https://github.com/w3c/vc-data-integrity/issues/78 [pr exists] [before CR]
- #29 domain should be a string or array (2 by msporny)
https://github.com/w3c/vc-data-integrity/issues/29 [ready for pr] [before CR]
1 issues closed:
- Add at least one unsigned properties https://github.com/w3c/vc-data-integrity/issues/90 [pending close (7 days)] [before CR]
* w3c/vc-di-eddsa (+0/-0/💬3)
1 issues received 3 new comments:
- #4 privateKeyMultibase (3 by OR13, dmitrizagidulin, msporny)
https://github.com/w3c/vc-di-eddsa/issues/4 [before CR]
* w3c/vc-di-ecdsa (+1/-0/💬2)
1 issues created:
- Confirming `EcdsaSecp256r1VerificationKey2019` -> `Multibase` transition (by bnewbold)
https://github.com/w3c/vc-di-ecdsa/issues/22
1 issues received 2 new comments:
- #22 Confirming `EcdsaSecp256r1VerificationKey2019` -> `Multikey` transition (2 by OR13, msporny)
https://github.com/w3c/vc-di-ecdsa/issues/22 [question]
* w3c/vc-di-bbs (+1/-0/💬4)
1 issues created:
- Hosted JSON-LD context should expose itself as `ld+json` instead of `json` (by j-steinbach)
https://github.com/w3c/vc-di-bbs/issues/90
1 issues received 4 new comments:
- #90 Hosted JSON-LD context should expose itself as `ld+json` instead of `json` (4 by dlongley, j-steinbach)
https://github.com/w3c/vc-di-bbs/issues/90
* w3c/vc-jwt (+1/-0/💬16)
1 issues created:
- How to test `credentialStatus` and `credentialSchema`? (by OR13)
https://github.com/w3c/vc-jose-cose/issues/134
4 issues received 16 new comments:
- #134 How to test `credentialStatus` and `credentialSchema`? (1 by OR13)
https://github.com/w3c/vc-jose-cose/issues/134
- #133 Clarify relationship between validity times (7 by David-Chadwick, OR13, TallTed)
https://github.com/w3c/vc-jose-cose/issues/133
- #132 JWT - securing mechanism or not? (7 by OR13, TallTed, alenhorvat)
https://github.com/w3c/vc-jose-cose/issues/132
- #128 File PING request once rename is complete (1 by OR13)
https://github.com/w3c/vc-jose-cose/issues/128
Pull requests
-------------
* w3c/vc-data-model (+2/-1/💬31)
2 pull requests submitted:
- Editorial update index.html: use JsonSchema and not JsonSchema2023 — bis (by iherman)
https://github.com/w3c/vc-data-model/pull/1229
- Added reserved confidenceMethod property to the vocabulary — bis (by iherman)
https://github.com/w3c/vc-data-model/pull/1228
12 pull requests received 31 new comments:
- #1226 Added reserved confidenceMethod property to the vocabulary (13 by OR13, TallTed, iherman, msporny)
https://github.com/w3c/vc-data-model/pull/1226 [before-CR]
- #1225 Editorial update index.html: use JsonSchema and not JsonSchema2023 (4 by TallTed, iherman, msporny)
https://github.com/w3c/vc-data-model/pull/1225 [editorial] [before-CR]
- #1223 Add aud registered claim to v2 context (1 by OR13)
https://github.com/w3c/vc-data-model/pull/1223
- #1222 Add exp registered claim to v2 context (1 by OR13)
https://github.com/w3c/vc-data-model/pull/1222
- #1221 Add nbf registered claim to v2 context (1 by OR13)
https://github.com/w3c/vc-data-model/pull/1221
- #1220 Add iat registered claim to v2 context (1 by OR13)
https://github.com/w3c/vc-data-model/pull/1220
- #1219 Add cnf registered claim to v2 context (2 by OR13, davidlehn)
https://github.com/w3c/vc-data-model/pull/1219
- #1218 Added JsonSchemaCredential2023 to the vocabulary (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1218
- #1202 Add section on JSON Processing. (4 by OR13, awoie, msporny)
https://github.com/w3c/vc-data-model/pull/1202
- #1200 Better not set §B as non-normative (minor editorial) (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1200
- #1199 Add validation section regarding holder (1 by OR13)
https://github.com/w3c/vc-data-model/pull/1199
- #1172 Add "author" and "party" to terminology, rewrite "claim" terminology (1 by OR13)
https://github.com/w3c/vc-data-model/pull/1172
1 pull requests merged:
- Better not set §B as non-normative (minor editorial)
https://github.com/w3c/vc-data-model/pull/1200
* w3c/vc-json-schema (+5/-8/💬3)
5 pull requests submitted:
- Remove year as a version (by decentralgabe)
https://github.com/w3c/vc-json-schema/pull/192
- update section on storage, content integrity protection (by decentralgabe)
https://github.com/w3c/vc-json-schema/pull/191
- Add guidance on when to use each type (by decentralgabe)
https://github.com/w3c/vc-json-schema/pull/190
- Add language to address implementation mismatches (by decentralgabe)
https://github.com/w3c/vc-json-schema/pull/189
- Rename IRI to URL and point to RFC (by andresuribe87)
https://github.com/w3c/vc-json-schema/pull/188
3 pull requests received 3 new comments:
- #191 update section on storage, content integrity protection (1 by decentralgabe)
https://github.com/w3c/vc-json-schema/pull/191
- #186 Update language around the defined types and their usages (1 by decentralgabe)
https://github.com/w3c/vc-json-schema/pull/186
- #185 Update term definitions according to the core vocab (1 by iherman)
https://github.com/w3c/vc-json-schema/pull/185
8 pull requests merged:
- Add language to address implementation mismatches
https://github.com/w3c/vc-json-schema/pull/189
- update section on storage, content integrity protection
https://github.com/w3c/vc-json-schema/pull/191
- Add guidance on when to use each type
https://github.com/w3c/vc-json-schema/pull/190
- Remove year as a version
https://github.com/w3c/vc-json-schema/pull/192
- Rename IRI to URL and point to RFC
https://github.com/w3c/vc-json-schema/pull/188
- Update term definitions according to the core vocab
https://github.com/w3c/vc-json-schema/pull/185
- Update language around the defined types and their usages
https://github.com/w3c/vc-json-schema/pull/186
- Require at least one JSON Schema version
https://github.com/w3c/vc-json-schema/pull/184
* w3c/vc-data-integrity (+11/-9/💬20)
11 pull requests submitted:
- Add `cryptosuiteString` subtype for the `cryptosuite` property. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/162
- Add conformance classes to specification. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/160
- Allow errors to be conveyed based on execution environment. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/158
- Update domain to support arrays of domain values. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/156
- Add text on difference between proof and VC validity periods. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/155
- Add revoked definition and anchor for vocabulary. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/154
- Add anchor and definition for proof property. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/153
- Define anchors for secretKeyJwk and secretKeyMultibase (by msporny)
https://github.com/w3c/vc-data-integrity/pull/152
- Add a JsonWebKey context file. (by dmitrizagidulin)
https://github.com/w3c/vc-data-integrity/pull/150
- Add a Multikey context file. (by dmitrizagidulin)
https://github.com/w3c/vc-data-integrity/pull/149
- Add vocab definitions for secretKeyJwk and secretKeyMultibase (by dmitrizagidulin)
https://github.com/w3c/vc-data-integrity/pull/148
14 pull requests received 20 new comments:
- #148 Add vocab definitions for secretKeyJwk and secretKeyMultibase (1 by OR13)
https://github.com/w3c/vc-data-integrity/pull/148
- #146 Fix Mastodon spelling. (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/146
- #144 add missing comma (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/144
- #143 Correcting previously mis-corrected sentence (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/143
- #142 Added final versions of some properties (with anchors) (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/142
- #141 Added the error terms to the vocabulary (3 by iherman, msporny)
https://github.com/w3c/vc-data-integrity/pull/141
- #140 Add errors with anchors to the specification. (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/140
- #139 Add section on Securing Data Losslessly. (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/139
- #138 Add section on context injection. (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/138
- #137 Update range of Multikey and JsonWebKey (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/137
- #135 Add JSON Web Key to specification (3 by OR13, dlongley, msporny)
https://github.com/w3c/vc-data-integrity/pull/135
- #134 Explain use of each verify proof option. (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/134
- #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 (3 by OR13)
https://github.com/w3c/vc-data-integrity/pull/99
9 pull requests merged:
- add missing comma
https://github.com/w3c/vc-data-integrity/pull/144
- Added final versions of some properties (with anchors)
https://github.com/w3c/vc-data-integrity/pull/142
- Added the error terms to the vocabulary
https://github.com/w3c/vc-data-integrity/pull/141
- Fix Mastodon spelling.
https://github.com/w3c/vc-data-integrity/pull/146
- Add errors with anchors to the specification.
https://github.com/w3c/vc-data-integrity/pull/140
- Add section on Securing Data Losslessly.
https://github.com/w3c/vc-data-integrity/pull/139
- Add section on context injection.
https://github.com/w3c/vc-data-integrity/pull/138
- Update range of Multikey and JsonWebKey
https://github.com/w3c/vc-data-integrity/pull/137
- Explain use of each verify proof option.
https://github.com/w3c/vc-data-integrity/pull/134
* w3c/vc-di-eddsa (+3/-0/💬0)
3 pull requests submitted:
- Remove mis-implementation Issue (by Wind4Greg)
https://github.com/w3c/vc-di-eddsa/pull/54
- Update Cryptosuite Names. (by Wind4Greg)
https://github.com/w3c/vc-di-eddsa/pull/53
- Revise cryptosuite names (by Wind4Greg)
https://github.com/w3c/vc-di-eddsa/pull/52
* w3c/vc-di-ecdsa (+2/-2/💬5)
2 pull requests submitted:
- Revert 21 msporny mitigate poison (by msporny)
https://github.com/w3c/vc-di-ecdsa/pull/24
- Update crypto-suite names (by Wind4Greg)
https://github.com/w3c/vc-di-ecdsa/pull/23
4 pull requests received 5 new comments:
- #23 Update crypto-suite names (1 by msporny)
https://github.com/w3c/vc-di-ecdsa/pull/23
- #21 Mitigate poison datasets in ECDSA when canonicalizing. (2 by msporny)
https://github.com/w3c/vc-di-ecdsa/pull/21
- #20 Add ecdsa-sd-2023 cryptosuite to ECDSA Cryptosuites specification (1 by msporny)
https://github.com/w3c/vc-di-ecdsa/pull/20
- #19 Add helper functions for performing selective disclosure (1 by msporny)
https://github.com/w3c/vc-di-ecdsa/pull/19
2 pull requests merged:
- Mitigate poison datasets in ECDSA when canonicalizing.
https://github.com/w3c/vc-di-ecdsa/pull/21
- Add ecdsa-sd-2023 cryptosuite to ECDSA Cryptosuites specification
https://github.com/w3c/vc-di-ecdsa/pull/20
* w3c/vc-jwt (+0/-0/💬6)
2 pull requests received 6 new comments:
- #123 Address Ambiguity Regarding Multiple Structured Suffixes (2 by OR13)
https://github.com/w3c/vc-jose-cose/pull/123
- #88 remove securing json (4 by OR13, TallTed, mprorock)
https://github.com/w3c/vc-jose-cose/pull/88 [tag-needs-resolution]
* w3c/vc-status-list-2021 (+0/-1/💬1)
1 pull requests received 1 new comments:
- #74 update contexts in examples to point to v2 (1 by mprorock)
https://github.com/w3c/vc-status-list-2021/pull/74
1 pull requests merged:
- update contexts in examples to point to v2
https://github.com/w3c/vc-status-list-2021/pull/74
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, 7 August 2023 17:01:25 UTC