Merge pull request #517 from w3c/simoneonofri-fedid-success-criteria

[wg/fedid] Update Success Criteria

2024/wg-fedid.html

@@ -298,16 +298,22 @@ <h2>Success Criteria</h2>
           interoperable
           implementations</a> of every feature defined in the specification, where
         interoperability can be verified by passing open test suites, and two or
-        more implementations (distinct browser engines) 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.
+        more implementations (distinct browser engines) interoperating with each other.
+        </p>
+      <p>
+        In order to advance to Proposed Recommendation, each normative specification must have an open test suite of every feature defined in the specification.
+      </p>
+      <p>
+        In order to advance to Proposed Recommendation, the Digital Credential API must demonstrate support for at least two formats (e.g., W3C Verifiable Credentials, ISO mDoc). 
+      </p>
+      <p>
+        Each specification should have testing plans, starting from the earliest drafts.
       </p>
-      <p>There should be testing plans for each specification, starting from the earliest drafts.</p>
       <p>
         To promote interoperability, all changes made to specifications
         in Candidate Recommendation
         or to features that have deployed implementations
-        should have <a href='https://www.w3.org/2019/02/testing-policy.html'>tests</a>.
+        should have <a href="https://www.w3.org/2019/02/testing-policy.html">tests</a>.
         Testing efforts should be conducted via the <a href="https://github.com/web-platform-tests/wpt">Web Platform
           Tests</a> project.</p>