W3C home > Mailing lists > Public > public-credentials@w3.org > December 2021

RE: Verifiable Credentials v1.1 released for public review

From: Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net>
Date: Wed, 1 Dec 2021 16:09:44 +0000
To: David Chadwick <d.w.chadwick@verifiablecredentials.info>, "public-credentials@w3.org" <public-credentials@w3.org>
Message-ID: <MWHPR1301MB20946FDA299952547C66878CC3689@MWHPR1301MB2094.namprd13.prod.outlook.com>
I assume you can embed an (arbitrary) VC inside the credentialSubject of a second VC? …for the Trusted Digital Web, this is an imperative.

Michael Herman
Trusted Digital Web

From: David Chadwick <d.w.chadwick@verifiablecredentials.info>
Sent: Wednesday, November 10, 2021 10:58 AM
To: public-credentials@w3.org
Subject: Re: Verifiable Credentials v1.1 released for public review

On 10/11/2021 15:45, Manu Sporny wrote:

On 11/10/21 10:37 AM, David Chadwick wrote:

This is not correct. You can embed anything in a VC. All you need to do is

define the property name and value and specify this in the schema for the


You are talking about something that is completely unspecified. There is no

standard way to do what you are implying.

Correct. There is no standard way of doing most things with VCs e.g. issue a credit card, a university degree, a passport or perform delegation etc. So it is not surprising to me that the current data model specification does not standardise all the different things that user groups can do with VCs.

Yes, anything is possible... but the point of standards is to (ideally) agree

on ONE way to do something. Your proposal proposes adding something to the VC

Data Model that is driven by a deficiency in JWTs and is a bit of the tail

wagging the dog.
Lets be clear. I am not proposing anything. I was simply stating that embedding JWT VCs in JWT VCs is possible. It just needs one group of interested people to specify this. If that is the CCG EDU group then they can do it themselves. If the group think it is of global interest then they can ask the VC WG to do it.

You should feel free to propose that new normative feature in the VC-JWT

specification in the VC 2.0 work, but let's be very clear here -- that is a

new normative feature (that has negative effects on the ecosystem), so I

expect people (like me) to disagree with it.

I am not going to propose it because I have not encountered a need for it yet. But I would be happy to help people who have a need to specify how to do it

Kind regards


-- manu

Received on Wednesday, 1 December 2021 16:10:00 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:25:25 UTC