Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark single-implementation features "at risk" #62

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Mark single-implementation features "at risk" #62

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 13 additions & 11 deletions charter.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -266,24 +266,26 @@ <h2>Success Criteria</h2>
<a href="https://www.w3.org/2021/Process-20211102/#RecsWD">First Public
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-snapshot">Candidate
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.
Draft</a>, and
<a href="https://www.w3.org/2021/Process-20211102/#RecsCR">Candidate
Recommendation</a>.
The WG does not intend to publish specifications as <a href="https://www.w3.org/2021/Process-20211102/#RecsPR">Proposed Recommendations</a>.

<p>It is expected that in <a
href="https://www.w3.org/2021/Process-20211102/#RecsCR">Candidate Recommendations</a>,
every feature that doesn't have <a
href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two
independent implementations</a> will be clearly marked "at risk".
Interoperability of implementations will be verified by passing open test suites.

<p>Each normative specification should contain separate sections detailing security and privacy implications for implementers, Web authors, and end users.</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>
<p>In considering features, the group will state, during the development of those features or in the text of the document, privacy implications. Proposals should clearly state privacy issues, how they intend to address those issues, and the advertising use cases addressed in each deliverable.</p>

<p>In considering features, the group will state, during the development of those features or in the text of the document, privacy implications. Proposals should clearly state privacy issues, how they intend to address those issues, and the advertising use cases addressed in each deliverable.</p>
</section>

<section id="coordination">
Expand Down