From a41ce51d8a57360c8015eb2c8b37d66b4169efb5 Mon Sep 17 00:00:00 2001
From: Manu Sporny
-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.
+
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.
+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
-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: +
+ ++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