- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Thu, 20 Oct 2022 18:42:24 -0400
- To: W3C Credentials CG <public-credentials@w3.org>
On Thu, Oct 20, 2022 at 12:41 PM Kristina Yasuda <Kristina.Yasuda@microsoft.com> wrote: > And JSON-JWT should probably be separated into JSON-encoding (not usign @context - section 6.1 of vc-data-model) and JSON-LD encoding (full use of @context - Section 6.2 of vc-data-mode), these two do not exactly interoperate and survey results will be incomplete without this distinction. Let's be clear... not using `@context` in a Verifiable Credential is called "an invalid Verifiable Credential". :) They don't interoperate because some people are not conformant to the specification today. Folks in the CCG should be paying attention to these conversations as the outcome could drastically affect interop for Verifiable Credentials. It is being suggested that we make this backwards-incompatible/breaking change for VC 2.0. For those interested in this conversation, there is an issue for it: Make the usage of @context optional https://github.com/w3c/vc-data-model/issues/947 and related conversations here: Limit JSON-LD optionality to enhance developer experience https://github.com/w3c/vc-data-model/issues/948 adding @vocab to /credentials/v2 https://github.com/w3c/vc-data-model/issues/953 -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. News: Digital Bazaar Announces New Case Studies (2021) https://www.digitalbazaar.com/
Received on Thursday, 20 October 2022 22:43:12 UTC