You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<ahref="https://www.w3.org/2019/did-wg/">Decentralized Identifier Working Group</a>
81
81
is two-fold. First, it will maintain the <ahref="https://www.w3.org/TR/did-core/">Decentralized Identifiers (DIDs)</a>
82
82
specification and related Working Group Notes.
83
-
Second, it will define common requirements, algorithms, architectural options, and various considerations for the DID resolution and DID URL dereferencing processes.
83
+
Second, it will seek consensus around the best way to achieve effective interoperability through common requirements, algorithms, architectural options, and various considerations for the DID resolution and DID URL dereferencing processes.
<p>WebDriver is a remote control interface that enables introspection and control of user agents. It provides a platform- and language-neutral wire protocol as a way for out-of-process programs to remotely instruct the behavior of web browsers.</p>
<p>The WebDriver Bidirectional Protocol extends WebDriver by introducing a bidirectional communication mechanism; in place of the strict command/response format of WebDriver, that bidirectional communication mechanism permits events to stream from the user agent to the controlling software, better matching the evented nature of the browser DOM.</p>
<p>AT Driver defines a protocol for introspection and remote control of assistive technology (AT) such as screen readers, using a bidirectional communication channel.</p>
<p>In order to advance to <ahref="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each normative specification is expected to have <ahref="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent 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 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.</p>
217
223
218
224
<p>To promote interoperability, all changes made to specifications in Candidate Recommendation or to features that have deployed implementations will have <ahref='https://www.w3.org/2019/02/testing-policy.html'>tests</a>. Testing efforts will be conducted via the <ahref="https://github.com/web-platform-tests/wpt">Web Platform Tests</a> project.</p>
<dd>Coordination on mechanisms for automating tests that cannot be written purely using web-platform APIs.</dd>
262
+
</dl>
263
+
<dl>
264
+
<dt><ahref="https://whatwg.org/">WHATWG</a></dt>
265
+
<dd>Coordination on the <ahref="https://testutils.spec.whatwg.org/">Test Utils</a> specification, which defines a set of APIs for use in tests but not suitable to enable for end users — and the primary client for which is the <ahref="https://web-platform-tests.org">Web Platform Tests</a> project’s <ahref="https://github.com/web-platform-tests/wpt/">web-platform-tests</a> testsuite.</dd>
266
+
</dl>
267
+
</section>
268
+
251
269
<sectionclass="participation">
252
270
<h2id="participation">
253
271
Participation
@@ -262,7 +280,7 @@ <h2 id="participation">
262
280
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <ahref="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>.
263
281
</p>
264
282
<p>Participants in the group are required (by the <ahref="https://www.w3.org/Consortium/Process/#ParticipationCriteria">W3C Process</a>) to follow the
265
-
W3C <ahref="https://www.w3.org/Consortium/cepc/">Code of Ethics and Professional Conduct</a>.</p>
283
+
W3C <ahref="https://www.w3.org/policies/code-of-conduct/">Code of Conduct</a>.</p>
0 commit comments