- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 20 Feb 2023 17:01:14 +0000
- To: public-credentials@w3.org
- Message-Id: <E1pU9XO-006IRQ-3C@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+8/-6/💬80)
8 issues created:
- Media types other than credential+ld+json (by Sakurann)
https://github.com/w3c/vc-data-model/issues/1048
- NIST defines "credential" differently (by OR13)
https://github.com/w3c/vc-data-model/issues/1047
- Add a unique version property to the core data model (by decentralgabe)
https://github.com/w3c/vc-data-model/issues/1046
- Do we have to introduce the `Credential` class in the VCDM vocabulary? (by iherman)
https://github.com/w3c/vc-data-model/issues/1044
- Add "Relay Attacks" to security considerations (by OR13)
https://github.com/w3c/vc-data-model/issues/1041
- Guidance on `application/ld+json` (by OR13)
https://github.com/w3c/vc-data-model/issues/1040
- Add at least one unsigned properties (by jandrieu)
https://github.com/w3c/vc-data-model/issues/1039
- Query on HashLinks (by sumanair)
https://github.com/w3c/vc-data-model/issues/1038
36 issues received 80 new comments:
- #1047 NIST defines "credential" differently (2 by PatStLouis, mwherman2000)
https://github.com/w3c/vc-data-model/issues/1047
- #1046 Add a unique version property to the core data model (2 by bumblefudge, decentralgabe)
https://github.com/w3c/vc-data-model/issues/1046
- #1044 Do we have to introduce the `Credential` class in the VCDM vocabulary? (2 by OR13, iherman)
https://github.com/w3c/vc-data-model/issues/1044
- #1041 Add "Relay Attacks" to security considerations (1 by bumblefudge)
https://github.com/w3c/vc-data-model/issues/1041
- #1039 Add at least one unsigned properties (3 by dlongley, jandrieu)
https://github.com/w3c/vc-data-model/issues/1039
- #1037 `nonTransferable` property in v2.0? (1 by David-Chadwick)
https://github.com/w3c/vc-data-model/issues/1037
- #1029 Add examples of JSON-LD Framing (1 by OR13)
https://github.com/w3c/vc-data-model/issues/1029
- #1020 Clarification on when a credentialRefresh service should be used (2 by David-Chadwick, TallTed)
https://github.com/w3c/vc-data-model/issues/1020 [question] [refresh]
- #1016 Specify allowed Verifier interactions with Verifiable Data Registries (2 by Sakurann)
https://github.com/w3c/vc-data-model/issues/1016 [discuss]
- #1012 Need to clarify the nature of the media type in relationship to "credential" vs "verifiable-credential" (1 by paulfdietrich)
https://github.com/w3c/vc-data-model/issues/1012 [discuss]
- #995 [Terminology] claim (5 by David-Chadwick, RieksJ, Sakurann, jandrieu)
https://github.com/w3c/vc-data-model/issues/995 [terminology]
- #989 Section 3.2 Credentials makes confusing statements about what a "credential" is (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/989 [editorial] [terminology]
- #982 W3C VC-LD Specification and Layered VC Specification: = interoperability at the application layer of layered spec (2 by Sakurann, TallTed)
https://github.com/w3c/vc-data-model/issues/982 [conversation]
- #972 Strawman for Increasing Interop (2 by Sakurann, TallTed)
https://github.com/w3c/vc-data-model/issues/972 [discuss]
- #965 'issued' vs. 'validFrom' (formerly 'issuanceDate') (3 by OR13, iherman, msporny)
https://github.com/w3c/vc-data-model/issues/965 [ready for PR]
- #956 Protecting integrity of `@context` (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/issues/956 [ready for PR] [discuss]
- #952 Proposal: Chaining VCs via links and digests (2 by OR13, iherman)
https://github.com/w3c/vc-data-model/issues/952 [discuss]
- #950 Verification of multiple credential schemas (1 by iherman)
https://github.com/w3c/vc-data-model/issues/950 [ready for PR] [schema]
- #948 Limit JSON-LD optionality to enhance developer experience (1 by msporny)
https://github.com/w3c/vc-data-model/issues/948 [discuss]
- #947 Make the usage of `@context` optional (4 by Sakurann, TallTed, iherman)
https://github.com/w3c/vc-data-model/issues/947 [discuss]
- #946 what is attribute ID in the verifiable credential? (3 by OR13, iherman, msporny)
https://github.com/w3c/vc-data-model/issues/946 [ready for PR] [question]
- #937 Presentations SHOULD expire (2 by David-Chadwick, Sakurann)
https://github.com/w3c/vc-data-model/issues/937 [discuss]
- #935 Add "credential boilerplates" as examples (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/issues/935 [ready for PR]
- #919 Evidence as a Related Credential (2 by decentralgabe, iherman)
https://github.com/w3c/vc-data-model/issues/919 [ready for PR] [discuss] [evidence]
- #914 Dereferencing relative to `issuer` (1 by iherman)
https://github.com/w3c/vc-data-model/issues/914 [discuss]
- #909 Define policies for directory of a related work (4 by TallTed, iherman, msporny)
https://github.com/w3c/vc-data-model/issues/909 [pr exists]
- #902 Define "prover" in addition to "holder". (11 by David-Chadwick, RieksJ, agropper, 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 (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/895 [discuss]
- #890 credentialSchema and Selective Disclosure (2 by David-Chadwick, iherman)
https://github.com/w3c/vc-data-model/issues/890 [ready for PR] [schema]
- #887 What is the action associated with issuing/creating a Verifiable Presentation? (3 by PatStLouis, iherman, msporny)
https://github.com/w3c/vc-data-model/issues/887 [ready for PR]
- #882 Add extension mechanism to allow different methods for VP-to-VC / holder binding to next version of standard to allow verification of rightfulness of presentation (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/882 [ready for PR] [holder-binding]
- #860 Determine interoperable way for Holder to make claims directly in VPs (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/860 [discuss]
- #821 "bound"/"binding" terminology is a significantly stronger relationship than is actually present between VCs and their Subjects *or* Holders (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/821 [clarification] [holder-binding] [terminology]
- #789 Explicit reference should be added about binding the VC to the holder (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/789 [ready for PR] [holder-binding]
- #779 Is a verifiable credential in JSON-LD expand form valid? (1 by msporny)
https://github.com/w3c/vc-data-model/issues/779 [ready for PR]
- #758 Fix the vc-data-model namespace with https://www.w3.org/ns/vc/v2 (4 by OR13, TallTed, iherman)
https://github.com/w3c/vc-data-model/issues/758 [discuss]
6 issues closed:
- ACDC (Authentic Chained Data Containers) in VC DM 2.0 https://github.com/w3c/vc-data-model/issues/895 [discuss]
- W3C VC-LD Specification and Layered VC Specification: = interoperability at the application layer of layered spec https://github.com/w3c/vc-data-model/issues/982 [conversation]
- Strawman for Increasing Interop https://github.com/w3c/vc-data-model/issues/972 [discuss]
- Make the usage of `@context` optional https://github.com/w3c/vc-data-model/issues/947 [discuss]
- Evidence as a Related Credential https://github.com/w3c/vc-data-model/issues/919 [ready for PR] [discuss] [evidence]
- Section 3.2 Credentials makes confusing statements about what a "credential" is https://github.com/w3c/vc-data-model/issues/989 [editorial] [terminology]
* w3c/vc-data-integrity (+1/-1/💬10)
1 issues created:
- NIST defines data integrity differently that we do (by OR13)
https://github.com/w3c/vc-data-integrity/issues/83
5 issues received 10 new comments:
- #33 vc:proof scope (5 by bertvannuffelen, dlongley)
https://github.com/w3c/vc-data-integrity/issues/33
- #30 either nonce or challenge is redundant (2 by awoie)
https://github.com/w3c/vc-data-integrity/issues/30
- #26 proofChain property violates VC data model requirement (1 by dlongley)
https://github.com/w3c/vc-data-integrity/issues/26
- #25 Add language about verificationMethod representation (1 by OR13)
https://github.com/w3c/vc-data-integrity/issues/25
- #2 Ambiguity resulting from signature -> proof rename (1 by kimdhamilton)
https://github.com/w3c/vc-data-integrity/issues/2
1 issues closed:
- Add language about verificationMethod representation https://github.com/w3c/vc-data-integrity/issues/25
* w3c/vc-jwt (+2/-0/💬5)
2 issues created:
- F2F mapping converstation (by OR13)
https://github.com/w3c/vc-jwt/issues/53
- Describe how `cnf` is allowed to be used for credential binding (by OR13)
https://github.com/w3c/vc-jwt/issues/52
2 issues received 5 new comments:
- #53 F2F mapping converstation (3 by iherman, mprorock, selfissued)
https://github.com/w3c/vc-jwt/issues/53
- #49 Change spec name? (2 by mprorock)
https://github.com/w3c/vc-jwt/issues/49
* w3c/vc-status-list-2021 (+1/-0/💬0)
1 issues created:
- Encoded list in Base64 or Base64Url? (by amondit)
https://github.com/w3c/vc-status-list-2021/issues/58
Pull requests
-------------
* w3c/vc-data-model (+6/-0/💬33)
6 pull requests submitted:
- Add warning related to protecting integrity of @context (by msporny)
https://github.com/w3c/vc-data-model/pull/1051
- Restrict JSON-LD expression to compact document form. (by msporny)
https://github.com/w3c/vc-data-model/pull/1050
- Setting up a user dependent namespace document (by iherman)
https://github.com/w3c/vc-data-model/pull/1049
- Remove eg and ie (by decentralgabe)
https://github.com/w3c/vc-data-model/pull/1045
- s/`MIME Media Type`/`Media Type`/ (by TallTed)
https://github.com/w3c/vc-data-model/pull/1043
- Replace JsonSchemaValidator2018 (undefined) to CredentialSchema2022 (by decentralgabe)
https://github.com/w3c/vc-data-model/pull/1042
5 pull requests received 33 new comments:
- #1049 Setting up a user dependent namespace document (1 by iherman)
https://github.com/w3c/vc-data-model/pull/1049
- #1045 Remove eg and ie (5 by TallTed, decentralgabe, iherman, peacekeeper)
https://github.com/w3c/vc-data-model/pull/1045
- #1035 Add rendering property to VC Data Model (15 by dlongley, iherman, lemoustachiste, msporny)
https://github.com/w3c/vc-data-model/pull/1035
- #1023 Add language clarifying multiple data schemas (3 by David-Chadwick, decentralgabe, iherman)
https://github.com/w3c/vc-data-model/pull/1023
- #1014 Add normative requirements regarding media type and proof (9 by OR13, TallTed, andresuribe87, iherman, jandrieu, paulfdietrich, selfissued)
https://github.com/w3c/vc-data-model/pull/1014
* w3c/vc-use-cases (+0/-0/💬1)
1 pull requests received 1 new comments:
- #129 Use case for Holder Binding (1 by justAnIdentity)
https://github.com/w3c/vc-use-cases/pull/129
* w3c/vc-jwt (+1/-0/💬12)
1 pull requests submitted:
- Feature: vc-jwt context (by mprorock)
https://github.com/w3c/vc-jwt/pull/54
4 pull requests received 12 new comments:
- #54 Feature: vc-jwt context (8 by OR13, TallTed, bumblefudge, mkhraisha, mprorock)
https://github.com/w3c/vc-jwt/pull/54
- #51 Guidance on securing `application/credential+ld+json` with "authorship that can be cryptographically verified." (2 by iherman)
https://github.com/w3c/vc-jwt/pull/51
- #50 Shorten media type closes #45 (1 by iherman)
https://github.com/w3c/vc-jwt/pull/50
- #48 Refine vp-jwt-1.1 production rules (1 by OR13)
https://github.com/w3c/vc-jwt/pull/48
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, 20 February 2023 17:01:16 UTC