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

@@ -316,8 +316,7 @@ <h2>Success Criteria</h2>
 Proposed Recommendation, each normative specification must have an open
 test suite of every feature defined in the specification.</p>
 
-    <p>In order for <a href="#deliverable-did-resolution">DID Resolution</a> to advance to <a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, 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 <a href="#deliverable-did-core">DID Core</a> and <a href="#deliverable-did-resolution">DID Resolution</a>.
+    <p>In order for <a href="#deliverable-did-resolution">DID Resolution</a> to advance to <a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, 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.</p>
     </ul>
 
 	  <p>There should be testing plans for each specification, starting from the earliest drafts.</p>