W3C home > Mailing lists > Public > public-credentials@w3.org > November 2018

Re: Content-type and/or file extension for Verifiable Credentials and Verifiable Presentations

From: Christopher Allen <ChristopherA@lifewithalacrity.com>
Date: Mon, 19 Nov 2018 15:55:39 -0800
Message-ID: <CACrqygD3XWBoTu8kXL-nyY9SnGL8aEubobWncGu06RH9pkqE5A@mail.gmail.com>
To: David Elie Raymond Christophe Ammouial <david.elie.raymond.christophe.ammouial@everis.com>
Cc: "public-credentials@w3.org" <public-credentials@w3.org>
I have been using .jsonld for DID Objects.

This is out-of-date to current DID spec, but is my DID Object for testing


In the BTCR method, you can append VCs to DID Documents as a default

— Christopher Allen

On Mon, Nov 19, 2018 at 2:58 PM David Elie Raymond Christophe Ammouial <
david.elie.raymond.christophe.ammouial@everis.com> wrote:

> Hello community,
> I wonder what the adequate content type and extension for a Verifiable
> Credential or a Verifiable Presentation using JSON serialisation would be.
> I’m working on software that understands and emits VCs. I looked through
> recent threads but couldn’t find any related discussion – I apologise if
> there is one and I missed it.
> We can always use “application/json” and probably a “.json” extension for
> files, but it might make sense to register something more precise with
> IANA, such as “application/vc+json” and “.credential”.
> Another aspect of the question is whether VCs and VPs should share the
> same content type and only differ from their “@type” property, or use
> separate ones.
> I believe this is one or one of my first emails to the list, so I hope I’m
> not breaking any group rule or best practice. :)
> Regards.
> David
> ------------------------------
> Este correo y la información contenida o adjunta al mismo es privada y
> confidencial y va dirigida exclusivamente a su destinatario. everis informa
> a quien pueda haber recibido este correo por error que contiene información
> confidencial cuyo uso, copia, reproducción o distribución está expresamente
> prohibida. Si no es Vd. el destinatario del mismo y recibe este correo por
> error, le rogamos lo ponga en conocimiento del emisor y proceda a su
> eliminación sin copiarlo, imprimirlo o utilizarlo de ningún modo.
> This message and the information contained in or attached to it are
> private and confidential and intended exclusively for the addressee. everis
> informs to whom it may receive it in error that it contains privileged
> information and its use, copy, reproduction or distribution is prohibited.
> If you are not an intended recipient of this E-mail, please notify the
> sender, delete it and do not read, act upon, print, disclose, copy, retain
> or redistribute any portion of this E-mail.
Received on Monday, 19 November 2018 23:56:14 UTC

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