Merge pull request #9 from iherman/issue-7-new-versions

New version to settle open issues

Author: iherman

index.html

@@ -195,13 +195,14 @@ <h2>Motivation and Background</h2>
                 <h2>Scope</h2>
 
                 <p>
-                    For new Recommendations listed <a href="#deliverables">below</a>, the Working
-                    Group will complete them and then will continue to maintain those
-                    specifications. For all published Recommendations, the Working Group will
-                    maintain those specifications, ensuring that no
-                    <a href="https://www.w3.org/policies/process/20231103/#class-4">Class 4
-                        changes</a> are introduced except as needed to address any serious security
-                    issues that arise or to support the new Recommendations produced by the group.
+                    The working group will maintain all Recommendations that were already
+                    published at the start of the charter period by publishing <a href="#maintain">new versions</a>.
+                    However, no new normative features will be introduced for those specifications, except as needed to
+                    address any serious privacy or security issues that arise, or to support the new Recommendations
+                    produced by the group.
+                    The working group will also publish a number of new Recommendations (see the list
+                    <a href="#normative">below</a>), and will consider working on
+                    <a href="#incubation">incubated</a> specifications.
                 </p>
 
                 <section id="section-out-of-scope">
@@ -443,14 +444,14 @@ <h3>
 
                 </section>
 
-                <section>
+                <section id="maintain">
                     <h3>
                         Maintenance Specifications
                     </h3>
                     <p>
-                        The Working Group will maintain the following W3C normative specifications without making any <a
-                            href="https://www.w3.org/policies/process/20231103/#class-4">Class 4 changes</a> except for
-                        serious security issues that arise.
+                        No new normative features will be introduced for the following specifications, except as needed to
+                        address any serious privacy or security issues that arise, or to support the new Recommendations
+                        produced by the group.
                     </p>
 
                     <dl>
@@ -792,14 +793,26 @@ <h3>Timeline</h3>
                 <h2>Success Criteria</h2>
 
                 <!-- Testing and interop -->
-                <p>
+                <!-- <p>
                     In order to advance beyond <a href="https://www.w3.org/policies/process/#RecsCR"
                         title="Candidate Recommendation">Candidate Recommendation</a>, each normative specification is
                     expected to have <a href="https://www.w3.org/policies/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. A feature is a distinct,
                     normatively required, concretely implementable piece of functionality, such as a data model property
                     or algorithm, that provides value by allowing a system to achieve a specific use case.
+                </p> -->
+
+                <p>
+                    In order to advance beyond <a href="https://www.w3.org/policies/process/#RecsCR"
+                        title="Candidate Recommendation">Candidate Recommendation</a>, each normative specification is
+                    expected to have <a href="https://www.w3.org/policies/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. In order to advance beyond
+                    Candidate Recommendation, each normative specification must have an open test suite of every feature
+                    defined in the specification. A feature is a distinct,
+                    normatively required, concretely implementable piece of functionality, such as a data model property
+                    or algorithm, that provides value by allowing a system to achieve a specific use case.
                 </p>
 
                 <p>