From a41ce51d8a57360c8015eb2c8b37d66b4169efb5 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Thu, 19 Feb 2026 12:33:32 -0500 Subject: [PATCH 1/6] Add CR exit criteria language. --- index.html | 23 ++++++++++++++++++++--- 1 file changed, 20 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index 016b6eb3..9218d8ab 100644 --- a/index.html +++ b/index.html @@ -306,11 +306,28 @@

-This version of the DID Core specification, version 1.1, is experimental. -DO NOT implement it. If you want to implement DIDs, use the current version 1.0 -specification: [[[DID-CORE]]]. +The W3C Decentralized Identifier Working Group has published this document as a +W3C Candidate Recommendation and is requesting that software developers and DID +Method specification authors provide experimental implementations designed to +test the implementability of all of the features in this document.

+

+To exit the W3C Candidate Recommendation phase, the W3C DID Working Group will +require two things: 1) for normative statements that are machine testable, at +least two interoperable implementations per feature, and 2) for normative +statements that are not machine testable, at least two demonstrations of +implementation per feature. A feature is defined as one or more functionally +related normative statements in the specification. For this specification, +interoperability is defined as normative statements, such as those referring to +data model properties and their values, being interpreted in the same way +between two different DID Methods. +

+ +

+The resolution of a specific DID Method is out of scope for this specification, +and is covered by the [[[DID-RESOLUTION]]] specification. +

From bdb8e5e8c66d19d0c4ac6813e9276869a1596d3b Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Thu, 19 Feb 2026 12:37:40 -0500 Subject: [PATCH 2/6] Make DID Resolution reference non-normative. --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 9218d8ab..d1c3602f 100644 --- a/index.html +++ b/index.html @@ -326,7 +326,7 @@

The resolution of a specific DID Method is out of scope for this specification, -and is covered by the [[[DID-RESOLUTION]]] specification. +and is covered by the [[[?DID-RESOLUTION]]] specification.

From af3ff687d3fe3e0fb386559a39d8bb77c6086145 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sat, 21 Feb 2026 14:43:44 -0500 Subject: [PATCH 3/6] Add test suite URL. --- index.html | 1 + 1 file changed, 1 insertion(+) diff --git a/index.html b/index.html index d1c3602f..98f3a684 100644 --- a/index.html +++ b/index.html @@ -31,6 +31,7 @@ // W3C Candidate Recommendation information crEnd: "2026-03-19", + testSuiteURI: "https://github.com/w3c/did-test-suite/", implementationReportURI: "https://w3c.github.io/did-test-suite/", // Editor's Draft URL From af3f2d352234db661a61409861e5098da613e886 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sat, 21 Feb 2026 14:52:03 -0500 Subject: [PATCH 4/6] Add warning that open issues might result in changes. --- index.html | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/index.html b/index.html index 98f3a684..1b5b5a3a 100644 --- a/index.html +++ b/index.html @@ -313,6 +313,12 @@ test the implementability of all of the features in this document.

+

+Any open class +1, 2, or 3 issues listed in the +issue tracker might result in changes to the specification. +

+

To exit the W3C Candidate Recommendation phase, the W3C DID Working Group will require two things: 1) for normative statements that are machine testable, at From 5135855ee30fd73399dd92edc98db1ee347ef4e8 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sat, 21 Feb 2026 15:19:08 -0500 Subject: [PATCH 5/6] Clarify what implementation of a feature requires. --- index.html | 43 +++++++++++++++++++++++++++++++------------ 1 file changed, 31 insertions(+), 12 deletions(-) diff --git a/index.html b/index.html index 1b5b5a3a..af4c031a 100644 --- a/index.html +++ b/index.html @@ -314,21 +314,40 @@

-Any open class -1, 2, or 3 issues listed in the -issue tracker might result in changes to the specification. +Implementers are cautioned that any open +class 1, 2, or +3 issues listed in the issue +tracker might result in changes to the specification.

-To exit the W3C Candidate Recommendation phase, the W3C DID Working Group will -require two things: 1) for normative statements that are machine testable, at -least two interoperable implementations per feature, and 2) for normative -statements that are not machine testable, at least two demonstrations of -implementation per feature. A feature is defined as one or more functionally -related normative statements in the specification. For this specification, -interoperability is defined as normative statements, such as those referring to -data model properties and their values, being interpreted in the same way -between two different DID Methods. +To exit the W3C Candidate Recommendation phase, the W3C DID Working Group +requires the following: +

+ +
    +
  1. +For normative statements that are machine testable, at least two conforming +implementations per feature; that is, when a [=conforming producer=] implements +a feature, at least two [=conforming consumers=] are able to consume the feature +and for every feature that is consumed, there are at least two [=conforming +producers=] that produce the feature. +
  2. +
  3. +For normative statements that are not machine testable, at least two +demonstrations of implementation per feature. +
  4. +
  5. +The [[[DID-RESOLUTION]]] specification has met its exit criteria for the +W3C Candidate Recommendation phase. +
  6. +
+ +

+A feature is defined as one or more functionally related normative statements in +the specification. For this specification, interoperability is defined as +normative statements, such as those referring to data model properties and their +values, being interpreted in the same way between two different DID Methods.

From b07945077aa427e850be72053ed9e006183a7ba7 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sat, 21 Feb 2026 15:22:47 -0500 Subject: [PATCH 6/6] Update publication date for CR. --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index af4c031a..708d3662 100644 --- a/index.html +++ b/index.html @@ -30,7 +30,7 @@ //prEnd: "2021-08-31", // W3C Candidate Recommendation information - crEnd: "2026-03-19", + crEnd: "2026-04-05", testSuiteURI: "https://github.com/w3c/did-test-suite/", implementationReportURI: "https://w3c.github.io/did-test-suite/", @@ -41,7 +41,7 @@ subtitle: "Core architecture, data model, and representations", // if you wish the publication date to be other than today, set this - publishDate: "2026-02-19", + publishDate: "2026-03-05", // previously published draft, uncomment this and set its // YYYY-MM-DD date and its maturity status