From 22e373048f96f18db8f7a8b71023dbcb1f28a924 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Wed, 2 Aug 2023 13:21:36 -0400 Subject: [PATCH] Add section on Ecosystem Compatibility. (#1203) 17 approvals, open for more than a week, no objections during the Special topic call on 08-01-2023 * Add section on Ecosystem Compatibility. * Fix grammar in Ecosystem Compatibility section. Co-authored-by: Ted Thibodeau Jr * Add references to "digital credentials" specifications. * Update Ecosystem Compatibility based on VCWG Special Topic call. * Add clarification around when a transformation becomes a VC. * Add note about what constitutes a verifiable credential. * Clarify that a conforming document has two possible media types. * Clarify that JOSE, COSE, wrapped conforming documents are VCs/VPs. * Clarify which specs need to follow the ecosystem guidelines. Co-authored-by: Dave Longley * Remove vague statement about "any securing mechanism" per @jandrieu. Co-authored-by: Joe Andrieu * Apply editorial suggestions from @Sakurann to Ecosystem Compatibility. Co-authored-by: Kristina <52878547+Sakurann@users.noreply.github.com> --------- Co-authored-by: Ted Thibodeau Jr Co-authored-by: Dave Longley Co-authored-by: Joe Andrieu Co-authored-by: Kristina <52878547+Sakurann@users.noreply.github.com> --- index.html | 78 +++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 77 insertions(+), 1 deletion(-) diff --git a/index.html b/index.html index ca7271b45..4274a8071 100644 --- a/index.html +++ b/index.html @@ -2230,7 +2230,7 @@

Data Schemas

If multiple schemas are present, validity is determined according to the -processing rules outlined by each associated credentialSchema +processing rules outlined by each associated credentialSchema type property.

@@ -3625,6 +3625,82 @@

Reserved Extension Points

+ +
+

Ecosystem Compatibility

+ +

+There are a number of digital credential formats that do not natively use the +data model provided in this document, but are aligned with a number of concepts +in this specification. At the time of publication, examples of these digital +credential formats include + +JSON Web Tokens (JWTs), + +CBOR Web Tokens (CWTs), +ISO-18013-5:2021 +(mDLs), + +AnonCreds, + +Gordian Envelopes, and + +Authentic Chained Data Containers (ACDCs). +

+ +

+If conceptually aligned digital credential formats can be transformed into a +conforming document according to the rules provided in this section, they +are considered "compatible with the W3C Verifiable Credentials ecosystem". +A conforming document is either a verifiable credential serialized +as the `application/vc+ld+json` media type or a verifiable presentation +serialized as the `application/vp+ld+json` media type. Specifications that +describe how to perform transformations that enable compatibility with +the Verifiable Credentials ecosystem: +

+ +
    +
  • +MUST identify whether the transformation to this data model is one-way-only or +round-trippable. +
    • +
  • +MUST preserve the `@context` values when performing round-trippable +transformation. +
    • +
  • +MUST result in a conforming document when transforming to the data +model described by this specification. +
    • +
  • +MUST specify a registered media type for the input document. +
    • +
  • +SHOULD provide a test suite that demonstrates that the specified transformation +algorithm to the data model in this specification results in +a conforming document. +
    • +
  • +SHOULD ensure that all semantics utilized in the transformed +conforming document follow best practices for Linked Data. See +Section , Section +, and Linked Data Best Practices [[?LD-BP]] +for additional guidance. +
    • +
+ +

+Readers are advised that a digital credential is only considered +compatible with the W3C Verifiable Credentials ecosystem if it is a +conforming document and it utilizes at least one securing mechanism, as +described by their respective requirements in this specification. While some communities might call some digital +credential formats that are not conforming documents +"verifiable credentials", doing so does NOT make that digital credential +compliant to this specification. +

+ +
+