Weekly github digest (Weekly update on Verifiable Credentials WG activity) from W3C Webmaster via GitHub API on 2022-08-01 (public-credentials@w3.org from August 2022)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Mon, 01 Aug 2022 17:01:15 +0000
To: public-credentials@w3.org
Message-Id: <E1oIYn5-001O0o-7k@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+3/-3/💬46)
  3 issues created:
  - Add DataIntegritySignature to v2 context? (by msporny)
    https://github.com/w3c/vc-data-model/issues/901 
  - Standardize recording a pre-issuance DID Auth VP as evidence property (by jandrieu)
    https://github.com/w3c/vc-data-model/issues/896 
  - ACDC (Authentic Chained Data Containers) in VC DM 2.0 (by SmithSamuelM)
    https://github.com/w3c/vc-data-model/issues/895 

  26 issues received 46 new comments:
  - #896 Standardize recording a pre-issuance DID Auth VP as evidence property (2 by msporny, peacekeeper)
    https://github.com/w3c/vc-data-model/issues/896 
  - #895 ACDC (Authentic Chained Data Containers) in VC DM 2.0 (6 by SmithSamuelM, TallTed, talltree)
    https://github.com/w3c/vc-data-model/issues/895 
  - #889 Are Persistent URI's with https an implementation of VC? (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/889 [pending close] 
  - #887 What is the action associated with issuing/creating a Verifiable Presentation? (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/887 [discuss] 
  - #885 vc:credentialSubject semantics (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/885 
  - #884 example 2 > sec: prefix (1 by Sakurann)
    https://github.com/w3c/vc-data-model/issues/884 
  - #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 (4 by agropper, alenhorvat, awoie)
    https://github.com/w3c/vc-data-model/issues/882 
  - #880 Migrate Section 6.3.1 JSON Web Token to separate normative specification (1 by Sakurann)
    https://github.com/w3c/vc-data-model/issues/880 [v2.0] [vc-jwt?] 
  - #878 [JWT encoding] JWT claim names `instead of` or `in addition to` their verifiable credential counterparts (2 by David-Chadwick, TallTed)
    https://github.com/w3c/vc-data-model/issues/878 [v2.0] 
  - #873 Diagram issues (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/873 
  - #831 Proposal: Anchored Resources and Hashlinks for VCs (1 by peacekeeper)
    https://github.com/w3c/vc-data-model/issues/831 [v2.0] 
  - #823 nonce property (3 by Sakurann, TallTed, iherman)
    https://github.com/w3c/vc-data-model/issues/823 [question] [vc-jwt] [data-integrity?] 
  - #821 "bound"/"binding" terminology is a significantly stronger relationship than is actually present between VCs and their Subjects *or* Holders (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/821 [Clarification] 
  - #815 VC-DATA-MODEL: adding more examples of non json-ld credentials (1 by Sakurann)
    https://github.com/w3c/vc-data-model/issues/815 [pending close] 
  - #813 [VC-DATA-MODEL] This recommendation has no stated purpose, goals, or intended audience statements. (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/813 [Editorial] [v2.0] 
  - #811 Remove proof property from most examples (1 by Sakurann)
    https://github.com/w3c/vc-data-model/issues/811 [Editorial] [pending close] [v2.0] 
  - #809 JWT encoding (1 by Sakurann)
    https://github.com/w3c/vc-data-model/issues/809 [v2.0] [vc-jwt] 
  - #799 Bound Credentials and Unbound Credentials (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/799 [v2.0] 
  - #796 [PROPOSAL] Spec needs to include a non-JSON/non-JSON-LD example VC binding e.g. JPEG EXIF/XMP (2 by Sakurann, brentzundel)
    https://github.com/w3c/vc-data-model/issues/796 [v2.0] 
  - #792 V1 specification doesn't definitively state that the credentialSubject.id, if specified, is always the id of the Subject of the Credential (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/792 [Editorial] [PR exists] [Errata] [v2.0] 
  - #791 [PROPOSAL] New specification document title: W3C Consensus-based Data Model Specification for Verifiable Credentials (3 by brentzundel, iherman)
    https://github.com/w3c/vc-data-model/issues/791 [pending close] 
  - #790 "Individual claims can be merged together to express a graph of information about a subject." is not a true statement, in general (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/790 [pending close] 
  - #751 Cover "authenticatability" of credential (1 by brentzundel)
    https://github.com/w3c/vc-data-model/issues/751 [Editorial] [Clarification] [Errata] [maintenance] [v1.1 (editorial)] 
  - #421 need MIME type guidance (2 by Sakurann, msporny)
    https://github.com/w3c/vc-data-model/issues/421 [relevant?] 
  - #248 Add a summary text as meta information (5 by RieksJ, TallTed, brentzundel, iherman, jandrieu)
    https://github.com/w3c/vc-data-model/issues/248 
  - #164 Issuers may express a Time to Live on the credential (1 by Sakurann)
    https://github.com/w3c/vc-data-model/issues/164 [relevant?] 

  3 issues closed:
  - [PROPOSAL] New specification document title: W3C Consensus-based Data Model Specification for Verifiable Credentials https://github.com/w3c/vc-data-model/issues/791 [pending close] 
  - Diagram issues https://github.com/w3c/vc-data-model/issues/873 
  - Cover "authenticatability" of credential https://github.com/w3c/vc-data-model/issues/751 [Editorial] [Clarification] [Errata] [maintenance] [v1.1 (editorial)] 



Pull requests
-------------
* w3c/vc-data-model (+4/-1/💬31)
  4 pull requests submitted:
  - Migrate Data Integrity section to dedicated specification. (by msporny)
    https://github.com/w3c/vc-data-model/pull/900 
  - Migrate VC-JWT section to dedicated specification. (by msporny)
    https://github.com/w3c/vc-data-model/pull/899 
  - Update README to reflect v2.0 work. (by msporny)
    https://github.com/w3c/vc-data-model/pull/898 
  - Migrate Subject-Holder Relationships to VC Implementation Guide. (by msporny)
    https://github.com/w3c/vc-data-model/pull/897 

  5 pull requests received 31 new comments:
  - #900 Migrate Data Integrity section to dedicated specification. (2 by iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/900 [substantive] 
  - #899 Migrate VC-JWT section to dedicated specification. (2 by msporny, peacekeeper)
    https://github.com/w3c/vc-data-model/pull/899 [substantive] 
  - #894 Prepare the VC Data Model v2.0 FPWD publication (12 by caribouW3, deniak, iherman, msporny)
    https://github.com/w3c/vc-data-model/pull/894 
  - #759 feat: adds 2020 v1 VC context and v3 security context (9 by brentzundel, iherman, kdenhartog, msporny)
    https://github.com/w3c/vc-data-model/pull/759 
  - #752 feat: add name and description (6 by RieksJ, iherman, msporny, peacekeeper)
    https://github.com/w3c/vc-data-model/pull/752 

  1 pull requests merged:
  - Prepare the VC Data Model v2.0 FPWD publication
    https://github.com/w3c/vc-data-model/pull/894 

* w3c/vc-imp-guide (+1/-0/💬0)
  1 pull requests submitted:
  - Migrate Subject-Holder Relationships to VC Implementation Guide. (by msporny)
    https://github.com/w3c/vc-imp-guide/pull/68 


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-wg-charter


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 1 August 2022 17:01:17 UTC