From befd7563ee285c314b97a4718e495e528bb91be7 Mon Sep 17 00:00:00 2001 From: Jeffrey Yasskin Date: Mon, 8 May 2023 14:59:32 -0700 Subject: [PATCH] Mark single-implementation features "at risk" Instead of distinguishing the CR-draft stage. --- charter.html | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/charter.html b/charter.html index 9a1f2d5..d4f8832 100644 --- a/charter.html +++ b/charter.html @@ -266,15 +266,17 @@

Success Criteria

First Public Working Draft, Working - Draft, - Candidate - Recommendation Snapshot, and Candidate - Recommendation Draft. The WG does not intend to publish specifications as Proposed Recommendations. - -

To reach the Candidate Recommendation Snapshot stage, each normative - specification is expected to have at - least two independent implementations of every feature defined in the specification. - Interoperability of implementations will be verified by passing open test suites. + Draft, and + Candidate + Recommendation. + The WG does not intend to publish specifications as Proposed Recommendations. + +

It is expected that in Candidate Recommendations, + every feature that doesn't have at least two + independent implementations will be clearly marked "at risk". + Interoperability of implementations will be verified by passing open test suites.

Each normative specification should contain separate sections detailing security and privacy implications for implementers, Web authors, and end users.

@@ -282,8 +284,8 @@

Success Criteria

aspects of normative specifications developed by the WG.

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.

- -

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.

+ +

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.