From acf92d49a9827685fa6c46dbbdd0d6f1a5fcf779 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sat, 15 Jul 2023 10:32:09 -0400 Subject: [PATCH 01/11] Add section on Ecosystem Compatibility. --- index.html | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+) diff --git a/index.html b/index.html index ca7271b45..5dec77cb5 100644 --- a/index.html +++ b/index.html @@ -3625,6 +3625,58 @@

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 pure JSON Web Tokens (JWTs), CBOR Web Tokens (CWTs), +ISO-18013-5 (mDLs), and Authentic Chained Data Containers (ACDCs). +

+ +

+If conceptually aligned digital credential formats can be transformed to the +data model according to the rules provided in this section, they are considered +"compatible with the Verifiable Credentials ecosystem", and the result +of the transformation, which is a conforming document, is a +verifiable credential. Specifications that contain transformations to the +data model described by this specification: +

+ + + +
+
From 81fdc25d2059855b78543c95e363f117e1da1947 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Tue, 18 Jul 2023 17:58:15 -0400 Subject: [PATCH 02/11] Fix grammar in Ecosystem Compatibility section. Co-authored-by: Ted Thibodeau Jr --- index.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index 5dec77cb5..5a0ae5e2f 100644 --- a/index.html +++ b/index.html @@ -3633,7 +3633,7 @@

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 pure JSON Web Tokens (JWTs), CBOR Web Tokens (CWTs), +credential formats include JSON Web Tokens (JWTs), CBOR Web Tokens (CWTs), ISO-18013-5 (mDLs), and Authentic Chained Data Containers (ACDCs).

@@ -3642,17 +3642,17 @@

Ecosystem Compatibility

data model according to the rules provided in this section, they are considered "compatible with the Verifiable Credentials ecosystem", and the result of the transformation, which is a conforming document, is a -verifiable credential. Specifications that contain transformations to the +verifiable credential. Specifications that include transformations to the data model described by this specification:

  • -MUST identify if the transformation to this data model is uni-directional or -bi-directional. +MUST identify whether the transformation to this data model is one-way-only or +round-trippable.
  • -MUST preserve the `@context` values when performing bi-directional +MUST preserve the `@context` values when performing round-trippable transformation.
  • @@ -3663,8 +3663,8 @@

    Ecosystem Compatibility

    a conforming document.
  • -SHOULD provide a test suite that demonstrates that the transformation algorithm -specified results in a conforming document. +SHOULD provide a test suite that demonstrates that the specified transformation +algorithm results in a conforming document.
  • SHOULD ensure that all semantics utilized in the transformed From e64268738002462b3535532f3452eddfcfaa26ab Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Tue, 18 Jul 2023 20:08:51 -0400 Subject: [PATCH 03/11] Add references to "digital credentials" specifications. --- index.html | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 5a0ae5e2f..2e7e3f874 100644 --- a/index.html +++ b/index.html @@ -3633,8 +3633,19 @@

    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 (mDLs), and Authentic Chained Data Containers (ACDCs). +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).

    From 0202074b696ee211668f230d25a88c0315026956 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Tue, 18 Jul 2023 20:16:14 -0400 Subject: [PATCH 04/11] Update Ecosystem Compatibility based on VCWG Special Topic call. --- index.html | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/index.html b/index.html index 2e7e3f874..4b76143b6 100644 --- a/index.html +++ b/index.html @@ -3649,12 +3649,10 @@

    Ecosystem Compatibility

    -If conceptually aligned digital credential formats can be transformed to the -data model according to the rules provided in this section, they are considered -"compatible with the Verifiable Credentials ecosystem", and the result -of the transformation, which is a conforming document, is a -verifiable credential. Specifications that include transformations to the -data model described by this specification: +If conceptually aligned digital credential formats can be transformed to a +conforming document according to the rules provided in this section, they +are considered "compatible with the Verifiable Credentials ecosystem". +Specifications that are compatible with the Verifiable Credentials ecosystem:

      @@ -3667,15 +3665,16 @@

      Ecosystem Compatibility

      transformation.
    • -MUST result in a conforming document. +MUST result in a conforming document when transforming to the data +model described by this specification.
    • -MUST specify a media type for the input document, which will be transformed into -a conforming document. +MUST specify a registered media type for the input document.
    • SHOULD provide a test suite that demonstrates that the specified transformation -algorithm results in a conforming document. +algorithm to the data model in this specification results in +a conforming document.
    • SHOULD ensure that all semantics utilized in the transformed From 0dc9ca524b8c567a9de727924e9675e8821e6955 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Tue, 18 Jul 2023 20:28:06 -0400 Subject: [PATCH 05/11] Add clarification around when a transformation becomes a VC. --- index.html | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/index.html b/index.html index 4b76143b6..b752a4b9c 100644 --- a/index.html +++ b/index.html @@ -3685,6 +3685,15 @@

      Ecosystem Compatibility

    +

    +Readers are advised that a digital credential is only considered a +verifiable credential or a verifiable presentation if it is +transformed into a conforming document, as described by this +specification. While some communities might call some digital credential +formats "verifiable credentials", doing so does not have consensus in this +community. +

    +
From 654d3518403dcabe0f2940da5084983a411baa00 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Tue, 18 Jul 2023 20:29:27 -0400 Subject: [PATCH 06/11] Add note about what constitutes a verifiable credential. --- index.html | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index b752a4b9c..49c5bc576 100644 --- a/index.html +++ b/index.html @@ -3649,7 +3649,7 @@

Ecosystem Compatibility

-If conceptually aligned digital credential formats can be transformed to a +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 Verifiable Credentials ecosystem". Specifications that are compatible with the Verifiable Credentials ecosystem: @@ -3690,8 +3690,9 @@

Ecosystem Compatibility

verifiable credential or a verifiable presentation if it is transformed into a conforming document, as described by this specification. While some communities might call some digital credential -formats "verifiable credentials", doing so does not have consensus in this -community. +formats that are not conforming documents "verifiable credentials", +doing so did not achieve consensus with the Working Group that created this +specification.

From 9648a0d182db324031f21d99ca537e9ad255fee0 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Tue, 18 Jul 2023 20:40:53 -0400 Subject: [PATCH 07/11] Clarify that a conforming document has two possible media types. --- index.html | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/index.html b/index.html index 49c5bc576..20fc0bb88 100644 --- a/index.html +++ b/index.html @@ -3652,7 +3652,10 @@

Ecosystem Compatibility

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 Verifiable Credentials ecosystem". -Specifications that are compatible with the 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 are +compatible with the Verifiable Credentials ecosystem:

    From 8d89cb52de7d61f7943a0d34b65c3d4f0140bb6c Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sun, 23 Jul 2023 10:48:28 -0400 Subject: [PATCH 08/11] Clarify that JOSE, COSE, wrapped conforming documents are VCs/VPs. --- index.html | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index 20fc0bb88..ed7671b2f 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.

    @@ -3690,12 +3690,16 @@

    Ecosystem Compatibility

    Readers are advised that a digital credential is only considered a -verifiable credential or a verifiable presentation if it is -transformed into a conforming document, as described by this -specification. While some communities might call some digital credential -formats that are not conforming documents "verifiable credentials", -doing so did not achieve consensus with the Working Group that created this -specification. +verifiable credential or a verifiable presentation if it is a +conforming document and it utilizes at least one securing mechanism, as +described by this specification. Additionally, any conforming document, +using any securing mechanism, where every claim in the conforming +document is secured, is considered a verifiable credential or a +verifiable presentation. While some communities might call some digital +credential formats that are not conforming documents +"verifiable credentials", doing so does NOT make that digital credential a +verifiable credential or a verifiable presentation as defined by +this specification.

    From 8a449c981e7b8eeed387d253f7957c04a6741fbe Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Mon, 24 Jul 2023 12:55:53 -0400 Subject: [PATCH 09/11] Clarify which specs need to follow the ecosystem guidelines. Co-authored-by: Dave Longley --- index.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index ed7671b2f..8e6ac4604 100644 --- a/index.html +++ b/index.html @@ -3654,8 +3654,9 @@

    Ecosystem Compatibility

    are considered "compatible with the 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 are -compatible with the Verifiable Credentials ecosystem: +serialized as the `application/vp+ld+json` media type. Specifications that +describe how to perform transformations that enable compatibility with +the Verifiable Credentials ecosystem:

      From a56b15a30e39ba996e51594208eee1b9ffc50393 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Mon, 31 Jul 2023 17:55:27 -0400 Subject: [PATCH 10/11] Remove vague statement about "any securing mechanism" per @jandrieu. Co-authored-by: Joe Andrieu --- index.html | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/index.html b/index.html index 8e6ac4604..96bfdc969 100644 --- a/index.html +++ b/index.html @@ -3693,10 +3693,7 @@

      Ecosystem Compatibility

      Readers are advised that a digital credential is only considered a verifiable credential or a verifiable presentation if it is a conforming document and it utilizes at least one securing mechanism, as -described by this specification. Additionally, any conforming document, -using any securing mechanism, where every claim in the conforming -document is secured, is considered a verifiable credential or a -verifiable presentation. While some communities might call some digital +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 a verifiable credential or a verifiable presentation as defined by From 056d2a10c2d630a712e311c3880821e71c118453 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Mon, 31 Jul 2023 21:59:47 -0400 Subject: [PATCH 11/11] Apply editorial suggestions from @Sakurann to Ecosystem Compatibility. Co-authored-by: Kristina <52878547+Sakurann@users.noreply.github.com> --- index.html | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/index.html b/index.html index 96bfdc969..4274a8071 100644 --- a/index.html +++ b/index.html @@ -3651,7 +3651,7 @@

      Ecosystem Compatibility

      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 Verifiable Credentials ecosystem". +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 @@ -3690,14 +3690,13 @@

      Ecosystem Compatibility

    -Readers are advised that a digital credential is only considered a -verifiable credential or a verifiable presentation if it is a +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 a -verifiable credential or a verifiable presentation as defined by -this specification. +"verifiable credentials", doing so does NOT make that digital credential +compliant to this specification.