Skip to content

Commit

Permalink
Merge pull request #43 from martinthomson/mozilla-fo-resolution
Browse files Browse the repository at this point in the history
Mozilla FO resolution
  • Loading branch information
AramZS committed Feb 6, 2023
2 parents e0d0e3c + 68733a8 commit 2b48b80
Showing 1 changed file with 18 additions and 9 deletions.
27 changes: 18 additions & 9 deletions charter.html
Original file line number Diff line number Diff line change
Expand Up @@ -128,15 +128,21 @@ <h1 id="title">PROPOSED Private Advertising Technology Working Group Charter</h1
Chairs
</th>
<td>
<i class="todo">[chair name] (affiliation)</i>
<ul>
<li>Aram Zucker-Scharff (Washington Post)</li>
<li>Sean Turner (sn3rd; Invited Expert)</li>
</ul>
</td>
</tr>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<span class="todo"><a href="mailto:">[team contact name]</a></span> <i class="todo">(0.1 <abbr title="Full-Time Equivalent">FTE</abbr>)</i>
<ul>
<li>Sam Weiler</li>
</ul>
(0.2 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
Expand Down Expand Up @@ -260,16 +266,19 @@ <h2>Success Criteria</h2>
Working Draft</a>,
<a href="https://www.w3.org/2021/Process-20211102/#RecsWD">Working
Draft</a>,
<a href="https://www.w3.org/2021/Process-20211102/#candidate-recommendation-draft">Candidate
Recommendation Draft</a>, and
<a href="https://www.w3.org/2021/Process-20211102/#candidate-recommendation-snapshot">Candidate
Recommendation Snapshot</a>.
It is expected that to reach the Candidate Recommendation Snapshot stage, each normative
specification is expected to have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent implementations</a> of every feature defined in the specification.</p>
Recommendation Snapshot</a>, and <a href="https://www.w3.org/2021/Process-20211102/#candidate-recommendation-draft">Candidate
Recommendation Draft</a>. The WG does not intend to publish specifications as <a href="https://www.w3.org/2021/Process-20211102/#RecsPR">Proposed Recommendations</a>.

<p>To reach the Candidate Recommendation Snapshot stage, each normative
specification is expected to have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at
least two independent implementations</a> of every feature defined in the specification.
Interoperability of implementations will be verified by passing open test suites.

<p>Each normative specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.</p>

<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
<p>There shall be a testing plan and open test suite developed that covers all functional
aspects of normative specifications developed by the WG.

<p>Normative specifications which have user-facing features should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and recommendations for maximizing accessibility in implementations.</p>
</section>
Expand Down

0 comments on commit 2b48b80

Please sign in to comment.