- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 13 Feb 2023 17:01:17 +0000
- To: public-credentials@w3.org
- Message-Id: <E1pRcCb-001Yux-Bg@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+3/-3/💬60)
3 issues created:
- Broken link in 1.0 (by vongohren)
https://github.com/w3c/vc-data-model/issues/1036
- Make `credential.id` & `presentation.id` REQUIRED. (by OR13)
https://github.com/w3c/vc-data-model/issues/1031
- Add examples of JSON-LD Framing (by OR13)
https://github.com/w3c/vc-data-model/issues/1029
22 issues received 60 new comments:
- #1031 Make `verifiable-credential.id` & `verifiable-presentation.id` REQUIRED. (6 by David-Chadwick, OR13, vongohren)
https://github.com/w3c/vc-data-model/issues/1031
- #1029 Add examples of JSON-LD Framing (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/1029
- #1027 Add guidance on ignoring optional fields (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/1027
- #1021 Typos in v.1.1 (1 by shujikamitsuna)
https://github.com/w3c/vc-data-model/issues/1021
- #1020 Clarification on when a credentialRefresh service should be used (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/1020 [question]
- #1015 Provide guidance when media type is incorrect (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/1015 [discuss] [media-type]
- #1008 Remove 3-party Issuer-Holder-Verifier diagram and replace with 2-party Raw Credential Sender-Receiver Model (1 by mwherman2000)
https://github.com/w3c/vc-data-model/issues/1008 [conversation]
- #997 Add spec text around utilizing JSON Schemas for VCDM objects (1 by decentralgabe)
https://github.com/w3c/vc-data-model/issues/997 [discuss] [schema]
- #996 Question about verifiable presentations (1 by RieksJ)
https://github.com/w3c/vc-data-model/issues/996 [conversation] [terminology]
- #986 Separation of Cryptographic Verification from Business Process (and Semantic) Validation (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/986 [conversation]
- #985 Enable CBOR Representation(s) of Verifiable Credentials (2 by OR13, iherman)
https://github.com/w3c/vc-data-model/issues/985 [discuss]
- #983 Terminology needs to be revised (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/983 [editorial] [terminology]
- #958 Clarification of the type of the "verifiableCredential" field in a VP (1 by brentzundel)
https://github.com/w3c/vc-data-model/issues/958 [question] [pending close]
- #957 Clarification needed regarding "the subject of a VC" (1 by OR13)
https://github.com/w3c/vc-data-model/issues/957 [holder-binding] [terminology]
- #935 Add "credential boilerplates" as examples (13 by OR13, TallTed, iherman, pchampin)
https://github.com/w3c/vc-data-model/issues/935 [ready for PR]
- #932 Representing Multi Issuer Credentials in the VCDM (8 by OR13, agropper, decentralgabe, dlongley)
https://github.com/w3c/vc-data-model/issues/932 [discuss]
- #902 Define "prover" in addition to "holder". (5 by OR13, RieksJ, Sakurann, iherman, mwherman2000)
https://github.com/w3c/vc-data-model/issues/902 [discuss] [holder-binding] [terminology]
- #895 ACDC (Authentic Chained Data Containers) in VC DM 2.0 (3 by bumblefudge, iherman, jandrieu)
https://github.com/w3c/vc-data-model/issues/895 [discuss]
- #860 Determine interoperable way for Holder to make claims directly in VPs (2 by TallTed, iherman)
https://github.com/w3c/vc-data-model/issues/860 [discuss]
- #831 Proposal: Anchored Resources and Hashlinks for VCs (6 by OR13, TallTed, dlongley)
https://github.com/w3c/vc-data-model/issues/831 [discuss]
- #789 Explicit reference should be added about binding the VC to the holder (2 by RieksJ)
https://github.com/w3c/vc-data-model/issues/789 [discuss] [holder-binding]
- #421 Define one or more media types for VCs (1 by msporny)
https://github.com/w3c/vc-data-model/issues/421 [pr exists]
3 issues closed:
- Terminology needs to be revised https://github.com/w3c/vc-data-model/issues/983 [editorial] [terminology]
- Typos in v.1.1 https://github.com/w3c/vc-data-model/issues/1021
- Clarification of the type of the "verifiableCredential" field in a VP https://github.com/w3c/vc-data-model/issues/958 [question] [pending close]
* w3c/vc-imp-guide (+1/-0/💬10)
1 issues created:
- Clarification needed regarding "the subject of a VC" (by RieksJ)
https://github.com/w3c/vc-imp-guide/issues/70
4 issues received 10 new comments:
- #70 Clarification needed regarding "the subject of a VC" (1 by awoie)
https://github.com/w3c/vc-imp-guide/issues/70
- #67 Be suspicious of QR Code flows that don't also check digital signatures at some point (2 by Sakurann, iherman)
https://github.com/w3c/vc-imp-guide/issues/67
- #66 Verifiers MUST NOT trust visual indicators on apps they do not control (6 by OR13, TallTed, agropper, iherman)
https://github.com/w3c/vc-imp-guide/issues/66
- #65 Ensure that credential storage should be encrypted using strong entropy sources (1 by iherman)
https://github.com/w3c/vc-imp-guide/issues/65
* w3c/vc-use-cases (+3/-0/💬16)
3 issues created:
- Consider "dispute" as an action (by jandrieu)
https://github.com/w3c/vc-use-cases/issues/134
- Add language around "Amend" actions (by msporny)
https://github.com/w3c/vc-use-cases/issues/133
- Repo needs CODEOWNERs (by OR13)
https://github.com/w3c/vc-use-cases/issues/132
7 issues received 16 new comments:
- #132 Repo needs CODEOWNERs (5 by iherman, jandrieu)
https://github.com/w3c/vc-use-cases/issues/132
- #128 Define use case(s) that requires holder binding (1 by iherman)
https://github.com/w3c/vc-use-cases/issues/128
- #126 Expand on Use Cases for Multi Party Credentials (3 by decentralgabe, iherman, jandrieu)
https://github.com/w3c/vc-use-cases/issues/126 [needsPR]
- #124 Section 4 diagram includes "amend claim" (2 by OR13, iherman)
https://github.com/w3c/vc-use-cases/issues/124 [needsPR]
- #122 User Agent not defined (1 by iherman)
https://github.com/w3c/vc-use-cases/issues/122
- #109 update diagrams (3 by Sakurann, iherman, msporny)
https://github.com/w3c/vc-use-cases/issues/109 [pending-close]
- #107 Review Editor/Author section (1 by iherman)
https://github.com/w3c/vc-use-cases/issues/107 [editorial]
* w3c/vc-data-integrity (+1/-13/💬35)
1 issues created:
- Apply guidance from RCH WG on processing poisoned graphs (by OR13)
https://github.com/w3c/vc-data-integrity/issues/82
24 issues received 35 new comments:
- #82 Apply guidance from RCH WG on processing poisoned graphs (5 by OR13, dlongley, quartzjer)
https://github.com/w3c/vc-data-integrity/issues/82
- #37 URLs in current editors draft all seem to be invalid (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/37
- #34 nonce property (2 by Sakurann, msporny)
https://github.com/w3c/vc-data-integrity/issues/34 [question]
- #33 vc:proof scope (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/33
- #31 Link of ZCAP is 404 (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/31
- #30 either nonce or challenge is redundant (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/30
- #28 Proof Type (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/28
- #27 What attributes are included in proof options? (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/27
- #25 Add language about verificationMethod representation (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/25
- #23 Missing "created" invalidates signature? (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/23
- #22 Storing information on whether a child object is referenced by id or included recursively (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/22
- #21 Should the verification algorithm recursively check embedded objects? (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/21
- #20 Specifying that input document must be framed or compacted in algorithm? (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/20
- #19 Example that demonstrates input(s) and what gets fed to the signature algorithms? (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/19
- #18 How order of signatures is ensured using ld-signatures? (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/18
- #17 Use cases for RsaSignatureAuthentication2018 / authentication suites (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/17
- #15 Examples of the "domain" field in use? (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/15
- #14 [EXAMPLE 1] Is Example 1 technically a Linked Data document or just a Simple Document? (6 by msporny, mwherman2000)
https://github.com/w3c/vc-data-integrity/issues/14
- #13 [Terminology] Definition of a linked data document is not discernable (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/13
- #12 Need a way to specify multi-factor key/proof relationships (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/12
- #11 serialization, canonicalized values and normalized datasets (2 by gkellogg, msporny)
https://github.com/w3c/vc-data-integrity/issues/11
- #9 Mark as Deprecated or Move to CCG (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/9
- #5 LD-Proofs v LD-Signatures (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/5
- #2 Ambiguity resulting from signature -> proof rename (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/2
13 issues closed:
- Link of ZCAP is 404 https://github.com/w3c/vc-data-integrity/issues/31
- either nonce or challenge is redundant https://github.com/w3c/vc-data-integrity/issues/30
- Proof Type https://github.com/w3c/vc-data-integrity/issues/28
- Need a way to specify multi-factor key/proof relationships https://github.com/w3c/vc-data-integrity/issues/12
- [Terminology] Definition of a linked data document is not discernable https://github.com/w3c/vc-data-integrity/issues/13
- [EXAMPLE 1] Is Example 1 technically a Linked Data document or just a Simple Document? https://github.com/w3c/vc-data-integrity/issues/14
- LD-Proofs v LD-Signatures https://github.com/w3c/vc-data-integrity/issues/5
- Examples of the "domain" field in use? https://github.com/w3c/vc-data-integrity/issues/15
- Use cases for RsaSignatureAuthentication2018 / authentication suites https://github.com/w3c/vc-data-integrity/issues/17
- Specifying that input document must be framed or compacted in algorithm? https://github.com/w3c/vc-data-integrity/issues/20
- Should the verification algorithm recursively check embedded objects? https://github.com/w3c/vc-data-integrity/issues/21
- Storing information on whether a child object is referenced by id or included recursively https://github.com/w3c/vc-data-integrity/issues/22
- Mark as Deprecated or Move to CCG https://github.com/w3c/vc-data-integrity/issues/9
* w3c/vc-jwt (+3/-1/💬22)
3 issues created:
- Change spec name? (by OR13)
https://github.com/w3c/vc-jwt/issues/49
- Provide guidance on use of `cty` in JOSE / COSE (by OR13)
https://github.com/w3c/vc-jwt/issues/47
- Replace reference to jwt.io with embedded example (by OR13)
https://github.com/w3c/vc-jwt/issues/46
5 issues received 22 new comments:
- #47 Provide guidance on use of `cty` in JOSE / COSE (7 by OR13, dlongley)
https://github.com/w3c/vc-jwt/issues/47
- #45 Shorten `verifiable-credential+jwt` to `vc+jwt` (12 by OR13, TallTed, dlongley, selfissued)
https://github.com/w3c/vc-jwt/issues/45
- #22 Clarify relationship between "iss" and "issuer" (1 by alenhorvat)
https://github.com/w3c/vc-jwt/issues/22
- #9 Represent issuance time with "iat" rather than "nbf" (1 by alenhorvat)
https://github.com/w3c/vc-jwt/issues/9
- #5 Looser restrictions on the JOSE header `typ` (1 by OR13)
https://github.com/w3c/vc-jwt/issues/5
1 issues closed:
- Looser restrictions on the JOSE header `typ` https://github.com/w3c/vc-jwt/issues/5
* w3c/vc-status-list-2021 (+2/-0/💬5)
2 issues created:
- Implementation Considerations (by shigeya)
https://github.com/w3c/vc-status-list-2021/issues/56
- Add guidance on rfc3642 (by OR13)
https://github.com/w3c/vc-status-list-2021/issues/55
3 issues received 5 new comments:
- #55 Add guidance on rfc3642 (1 by OR13)
https://github.com/w3c/vc-status-list-2021/issues/55
- #50 Versioning (1 by msporny)
https://github.com/w3c/vc-status-list-2021/issues/50
- #37 Define priority for a single credential with multiple statuses (3 by OR13, dlongley)
https://github.com/w3c/vc-status-list-2021/issues/37 [discuss]
Pull requests
-------------
* w3c/vc-data-model (+5/-3/💬22)
5 pull requests submitted:
- Add rendering property to VC Data Model (by msporny)
https://github.com/w3c/vc-data-model/pull/1035
- Propose `verifiable-credential+ld+json` media type (by OR13)
https://github.com/w3c/vc-data-model/pull/1034
- Add guidance for `credential+ld+json` for `external`proof (by OR13)
https://github.com/w3c/vc-data-model/pull/1033
- Add presentation media type (by OR13)
https://github.com/w3c/vc-data-model/pull/1032
- change ZKP section (by brentzundel)
https://github.com/w3c/vc-data-model/pull/1030
7 pull requests received 22 new comments:
- #1033 Add guidance for `credential+ld+json` for `external`proof (3 by dlongley, mprorock)
https://github.com/w3c/vc-data-model/pull/1033
- #1030 change ZKP section (2 by brentzundel, iherman)
https://github.com/w3c/vc-data-model/pull/1030
- #1028 ignore gitignore file (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1028
- #1026 Add issue to zkp section (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/pull/1026
- #1022 Typos pointed out in issue 1021 (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1022
- #1014 Add normative requirements regarding media type and proof (11 by OR13, dlongley, mprorock, msporny, mwherman2000)
https://github.com/w3c/vc-data-model/pull/1014
- #1000 Add media type registration request (2 by mwherman2000)
https://github.com/w3c/vc-data-model/pull/1000
3 pull requests merged:
- ignore gitignore file
https://github.com/w3c/vc-data-model/pull/1028
- Add issue to zkp section
https://github.com/w3c/vc-data-model/pull/1026
- Typos pointed out in issue 1021
https://github.com/w3c/vc-data-model/pull/1022
* w3c/vc-imp-guide (+0/-0/💬1)
1 pull requests received 1 new comments:
- #17 [WIP] added example schema.json for vc (resolves #1) (1 by brentzundel)
https://github.com/w3c/vc-imp-guide/pull/17
* w3c/vc-use-cases (+0/-0/💬2)
1 pull requests received 2 new comments:
- #129 Use case for Holder Binding (2 by justAnIdentity, vongohren)
https://github.com/w3c/vc-use-cases/pull/129
* w3c/vc-jwt (+3/-1/💬15)
3 pull requests submitted:
- Guidance on securing `application/credential+ld+json` with "authorship that can be cryptographically verified."". (by OR13)
https://github.com/w3c/vc-jwt/pull/51
- Shorten media type closes #45 (by OR13)
https://github.com/w3c/vc-jwt/pull/50
- Refine vp-jwt-1.1 production rules (by OR13)
https://github.com/w3c/vc-jwt/pull/48
3 pull requests received 15 new comments:
- #51 Guidance on securing `application/credential+ld+json` with "authorship that can be cryptographically verified." (1 by mprorock)
https://github.com/w3c/vc-jwt/pull/51
- #50 Shorten media type closes #45 (2 by TallTed, dlongley)
https://github.com/w3c/vc-jwt/pull/50
- #44 Add version 2 (12 by OR13, SmithSamuelM, TallTed, dlongley, iherman, msporny)
https://github.com/w3c/vc-jwt/pull/44
1 pull requests merged:
- Add version 2
https://github.com/w3c/vc-jwt/pull/44
* w3c/vc-status-list-2021 (+1/-0/💬10)
1 pull requests submitted:
- Propose text for malicious issuers (by OR13)
https://github.com/w3c/vc-status-list-2021/pull/57
3 pull requests received 10 new comments:
- #53 Add validity/caching period to status list credentials. (1 by iherman)
https://github.com/w3c/vc-status-list-2021/pull/53
- #46 Ensure that statusListCredential can be dereferenced. (1 by iherman)
https://github.com/w3c/vc-status-list-2021/pull/46
- #45 Add section about bitstring encoding. (8 by OR13, dlongley, dwight-holman, iherman, msporny)
https://github.com/w3c/vc-status-list-2021/pull/45
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, 13 February 2023 17:01:20 UTC