From bf1570311d434ef13061693b4cf492db8d2054d7 Mon Sep 17 00:00:00 2001 From: Pierre-Antoine Champin Date: Sun, 24 Sep 2023 22:45:37 +0200 Subject: [PATCH 1/9] address #447 --- 2023/did-wg.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2023/did-wg.html b/2023/did-wg.html index f7ef1fc4..bf922637 100644 --- a/2023/did-wg.html +++ b/2023/did-wg.html @@ -361,7 +361,7 @@

Success Criteria

-

All new features should be supported by at least two intents to implement before being incorporated in the specification.

+

All new features should be supported by at least two independent interoperable implementations before being incorporated in the specification.

From aacf57d4815121e3946c0edef0c3ad8d894d0547 Mon Sep 17 00:00:00 2001 From: Pierre-Antoine Champin Date: Sun, 24 Sep 2023 23:16:38 +0200 Subject: [PATCH 2/9] remove DID methods, and make DID resolution a REC track deliverable addresses - #427 (DID resolution on REC track) - #431 (remove DID methods) - #434 (now moot, as DID methods have been removed) --- 2023/did-wg.html | 44 +++++++++++--------------------------------- 1 file changed, 11 insertions(+), 33 deletions(-) diff --git a/2023/did-wg.html b/2023/did-wg.html index bf922637..31127243 100644 --- a/2023/did-wg.html +++ b/2023/did-wg.html @@ -78,10 +78,9 @@

PROPOSED Decentralized Identifier Working Gro

The mission of the Decentralized Identifier Working Group -is to maintain the Decentralized Identifiers (DIDs) -specification and related Working Group Notes. The WG will also seek consensus -around the best way to achieve effective interoperability, possibly through the -specification of DID Resolution and/or DID methods. +is two-fold. First, it will maintain the Decentralized Identifiers (DIDs) +specification and related Working Group Notes. +Second, it will define common requirements, algorithms, architectural options, and various considerations for the DID resolution and DID URL dereferencing processes.

@@ -151,12 +150,10 @@

Motivation and Background

level changes on the Recommendation.

-The Working Group will also seek consensus around DID Method specifications, and -may produce related documents. +The Working Group will also take over the work started by the Credenials Community Group around DID Resolution, to define common requirements, algorithms including their inputs and results, architectural options, and various considerations for the DID resolution and DID URL dereferencing processes.

-The Working Group will begin working toward a specification for DID Resolution -and DID URL Dereferencing. +It is expected that these two goals will be taken by distinct task forces in the WG.

@@ -182,10 +179,7 @@

Scope

-The Working Group may also publish new Working Group Notes, Editors Drafts, or -Working Drafts for DID Resolution or DID URL Dereferencing, or of DID Method -Specifications. Any new documents intended for Recommendation will be -limited to the Working Draft maturity level. +The Working Group may also publish new Working Group Notes.

@@ -224,7 +218,7 @@

The Working Group will maintain the following W3C normative specification:

-
+
Decentralized Identifiers (DIDs) v1.0

This specification defines new type of identifier that enables verifiable, decentralized digital identity. @@ -240,26 +234,10 @@

Exclusion Draft Charter: https://www.w3.org/2020/12/did-wg-charter.html.

-
-

- The Working Group may begin work on the following W3C normative specifications: -

- -
-
Decentralized Identifier (DID) Method Specification
-
-

- DID Method Specifications may be produced by the working group. -

-

- Expected Completion: It is not intended that any DID Method Specification developed by the working group will advance beyond Working Draft status. -

-

- Adopted Draft: The DID Specification Registries contains many links to examples of DID Method Specifications, some of which may be selected by the working group for development into a Recommendation. The group might also choose a similar starting document not listed in the Registry. -

-
+
+
Decentralized Identifier (DID) Resolution and DID URL Dereferencing v1.0
-
+

This document specifies the algorithms and guidelines for resolving DIDs and dereferencing DID URLs.

@@ -267,7 +245,7 @@

Draft State: Draft Community Group Report

Expected completion: - It is not intended that DID Resolution and DID URL Dereferencing will advance beyond Working Draft status. + START+24M.

Adopted Draft: DID Resolution v0.3, https://w3c-ccg.github.io/did-resolution/, published 2023-01-18, may serve as a starting point. From a34539ebc53da15435e80285efeb80193fcbe6df Mon Sep 17 00:00:00 2001 From: Pierre-Antoine Champin Date: Sun, 24 Sep 2023 23:42:52 +0200 Subject: [PATCH 3/9] add specific exit criteria discussed during TPAC --- 2023/did-wg.html | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/2023/did-wg.html b/2023/did-wg.html index 31127243..f10b5dde 100644 --- a/2023/did-wg.html +++ b/2023/did-wg.html @@ -315,13 +315,18 @@

Success Criteria

more implementations interoperating with each other. In order to advance to Proposed Recommendation, each normative specification must have an open test suite of every feature defined in the specification.

+ +

In order for DID Resolution to advance to Proposed Recommendation, it is expected to define a dummy DID method meant only for demonstrating interoperability across independent implementations. While required for all complying implementations, this method will be explicitly described as unfit for use in production. + It is also expected that the Working Group can exhibit that at least two independant open specification of DID methods relying on DID Core and DID Resolution. + +

There should be testing plans for each specification, starting from the earliest drafts.

To promote interoperability, all changes made to specifications in Candidate Recommendation or to features that have deployed implementations should have tests. - Testing efforts should be conducted via the Web Platform Tests project.

+

@@ -338,9 +343,6 @@

Success Criteria

TAG Web Platform Design Principles.

- -

All new features should be supported by at least two independent interoperable implementations before being incorporated in the specification.

-

From 9630c30d089b62812899386198dce8b690fc94cc Mon Sep 17 00:00:00 2001 From: Pierre-Antoine Champin Date: Tue, 3 Oct 2023 12:37:26 +0200 Subject: [PATCH 4/9] Update 2023/did-wg.html Co-authored-by: Ivan Herman --- 2023/did-wg.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2023/did-wg.html b/2023/did-wg.html index f10b5dde..482cb613 100644 --- a/2023/did-wg.html +++ b/2023/did-wg.html @@ -150,7 +150,7 @@

Motivation and Background

level changes on the Recommendation.

-The Working Group will also take over the work started by the Credenials Community Group around DID Resolution, to define common requirements, algorithms including their inputs and results, architectural options, and various considerations for the DID resolution and DID URL dereferencing processes. +The Working Group will also take over the work started by the Credentials Community Group around DID Resolution, to define common requirements, algorithms including their inputs and results, architectural options, and various considerations for the DID resolution and DID URL dereferencing processes.

It is expected that these two goals will be taken by distinct task forces in the WG. From ca925c489cb3d92acf4d79676e1954043b2d827c Mon Sep 17 00:00:00 2001 From: Pierre-Antoine Champin Date: Tue, 3 Oct 2023 12:37:42 +0200 Subject: [PATCH 5/9] Update 2023/did-wg.html Co-authored-by: Ivan Herman --- 2023/did-wg.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2023/did-wg.html b/2023/did-wg.html index 482cb613..e310eadf 100644 --- a/2023/did-wg.html +++ b/2023/did-wg.html @@ -317,7 +317,7 @@

Success Criteria

test suite of every feature defined in the specification.

In order for DID Resolution to advance to Proposed Recommendation, it is expected to define a dummy DID method meant only for demonstrating interoperability across independent implementations. While required for all complying implementations, this method will be explicitly described as unfit for use in production. - It is also expected that the Working Group can exhibit that at least two independant open specification of DID methods relying on DID Core and DID Resolution. + It is also expected that the Working Group can exhibit that at least two independent open specifications of DID methods relying on DID Core and DID Resolution.

There should be testing plans for each specification, starting from the earliest drafts.

From 1ecaa354c6987ce39eeed8bacb5c3e07dd0106dd Mon Sep 17 00:00:00 2001 From: Pierre-Antoine Champin Date: Wed, 18 Oct 2023 09:49:34 +0200 Subject: [PATCH 6/9] rephrase the requirement for two independant DID methods --- 2023/did-wg.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2023/did-wg.html b/2023/did-wg.html index e310eadf..6c090825 100644 --- a/2023/did-wg.html +++ b/2023/did-wg.html @@ -317,7 +317,7 @@

Success Criteria

test suite of every feature defined in the specification.

In order for DID Resolution to advance to Proposed Recommendation, it is expected to define a dummy DID method meant only for demonstrating interoperability across independent implementations. While required for all complying implementations, this method will be explicitly described as unfit for use in production. - It is also expected that the Working Group can exhibit that at least two independent open specifications of DID methods relying on DID Core and DID Resolution. + It is also expected that the Working Group can provide evidence of at least two independent open specifications of DID methods begin developed outside of the Working Group, and relying on DID Core and DID Resolution.

There should be testing plans for each specification, starting from the earliest drafts.

From 70a1458d968a0922fce1118aacf7f8fa4a882c71 Mon Sep 17 00:00:00 2001 From: Pierre-Antoine Champin Date: Thu, 19 Oct 2023 14:50:11 +0200 Subject: [PATCH 7/9] typo --- 2023/did-wg.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2023/did-wg.html b/2023/did-wg.html index 6c090825..94f1b371 100644 --- a/2023/did-wg.html +++ b/2023/did-wg.html @@ -317,7 +317,7 @@

Success Criteria

test suite of every feature defined in the specification.

In order for DID Resolution to advance to Proposed Recommendation, it is expected to define a dummy DID method meant only for demonstrating interoperability across independent implementations. While required for all complying implementations, this method will be explicitly described as unfit for use in production. - It is also expected that the Working Group can provide evidence of at least two independent open specifications of DID methods begin developed outside of the Working Group, and relying on DID Core and DID Resolution. + It is also expected that the Working Group can provide evidence of at least two independent open specifications of DID methods being developed outside of the Working Group, and relying on DID Core and DID Resolution.

There should be testing plans for each specification, starting from the earliest drafts.

From d8df0476a32f2ea4331c4f589f4593cf6bcba468 Mon Sep 17 00:00:00 2001 From: Pierre-Antoine Champin Date: Mon, 30 Oct 2023 16:05:55 +0100 Subject: [PATCH 8/9] Change DID Resolution success criteria removed the "dummy DID method" and the "provide evidence of existing DID methods" instead, the "evidence of existing DID methods" is deferred to DID Resolver implementations. Interoperability will be demonstrated by ensuring that resolvers support DID methods in common. --- 2023/did-wg.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/2023/did-wg.html b/2023/did-wg.html index 94f1b371..5b75efef 100644 --- a/2023/did-wg.html +++ b/2023/did-wg.html @@ -316,8 +316,7 @@

Success Criteria

Proposed Recommendation, each normative specification must have an open test suite of every feature defined in the specification.

-

In order for DID Resolution to advance to Proposed Recommendation, it is expected to define a dummy DID method meant only for demonstrating interoperability across independent implementations. While required for all complying implementations, this method will be explicitly described as unfit for use in production. - It is also expected that the Working Group can provide evidence of at least two independent open specifications of DID methods being developed outside of the Working Group, and relying on DID Core and DID Resolution. +

In order for DID Resolution to advance to Proposed Recommendation, it is expected that each of the independant implementations mentioned above support at least two DID methods with an open specification (i.e. a specification that is accessible to all for implementation and deployment). It is also expected that each pair of the independant implementations mentioned above support at least one common DID method with an open specification.

There should be testing plans for each specification, starting from the earliest drafts.

From 8cc49a2c9ae3b31698c11bf60fa96491996f60ef Mon Sep 17 00:00:00 2001 From: Pierre-Antoine Champin Date: Thu, 30 Nov 2023 11:24:37 +0100 Subject: [PATCH 9/9] Brent Zundel is now an IE --- 2023/did-wg.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2023/did-wg.html b/2023/did-wg.html index 5b75efef..99a9c16a 100644 --- a/2023/did-wg.html +++ b/2023/did-wg.html @@ -116,7 +116,7 @@

PROPOSED Decentralized Identifier Working Gro Chairs - Brent Zundel (Gen), Dan Burnett (Invited Expert) + Brent Zundel (Invited Expert), Dan Burnett (Invited Expert)