diff --git a/index.bs b/index.bs
index 0ff165b3..38386d6b 100644
--- a/index.bs
+++ b/index.bs
@@ -2527,6 +2527,15 @@ Candidate Changes
except that it proposes a new feature
rather than an error correction.
+ If there is no group chartered to maintain a [=technical report=],
+ the [=Team=] may maintain its [=errata=]
+ and associated [=candidate corrections=].
+ When doing so,
+ it must be explicit that those [=errata=] and [=candidate corrections=]
+ were written by the [=Team=].
+ The [=Team=] must solicit [=wide review=]
+ on [=candidate corrections=] that it produces.
+
[=Candidate corrections=] and [=candidate additions=] are collectively known as
candidate changes.
@@ -2580,7 +2589,6 @@ The W3C Recommendation Track
Publication of one or more [=Candidate Recommendations=].
Publication of a [=Proposed Recommendation=].
Publication as a [=W3C Recommendation=].
- Possibly, publication as an [=Amended Recommendation=].
@@ -2651,8 +2659,6 @@ Maturity Levels on the Recommendation Track
A Candidate Recommendation is a document that satisfies the technical
requirements of the Working Group that produced it and their dependencies,
- or makes substantive corrections
- to a [=Recommendation=] that is not maintained by a [=Working Group=],
and has already received wide review.
W3C publishes a Candidate Recommendation to
@@ -2757,17 +2763,6 @@ Maturity Levels on the Recommendation Track
As technology evolves,
a [=W3C Recommendation=] may become:
- -
- An Amended Recommendation
-
-
- An Amended Recommendation is a [=Recommendation=] that is amended to include
- substantive changes that do not add new features,
- and is produced by W3C
- at a time when the [=Recommendation=] does not fit within the charter of any active Working Group.
- Since the [=W3C team=] rather than a [=Working Group=] moves it through the Process,
- there are implications regarding the scope of Royalty-Free IPR licenses
- granted under the W3C Patent Policy [[PATENT-POLICY]].
-
-
A Superseded Recommendation
-
@@ -3139,10 +3134,7 @@ Transitioning to Candidate Recommendation
To publish a [=Candidate Recommendation=],
in addition to meeting the requirements for advancement
- a [=Working Group=],
- or in the case of a candidate [=Amended Recommendation=]
- (a document intended to become an [=Amended Recommendation=]),
- W3C:
+ a [=Working Group=]:
-
@@ -3313,8 +3305,7 @@ Transitioning to Proposed Recommendation
in the W3C Patent Policy [[!PATENT-POLICY]].
- A Working Group,
- or for a proposed [=Amended Recommendation=], W3C:
+ A Working Group:
-
@@ -3388,7 +3379,6 @@ Transitioning to Proposed Recommendation
-
Recommendation status,
- including [=Amended Recommendation=]
(the expected next step).
-
@@ -3440,11 +3430,11 @@ Transitioning to W3C Recommendation
-
- republished as a revised Recommendation or Amended Recommendation, or
+ republished as a revised Recommendation, or
-
republished as a Candidate Recommendation
- to be developed towards a revised [=Recommendation=] or [=Amended Recommendation=], or
+ to be developed towards a revised [=Recommendation=], or
-
declared superseded or obsolete, or
@@ -3461,13 +3451,15 @@ Revising a W3C Recommendation
Revising a Recommendation: Markup Changes
- A [=Working group=] may request republication of a [=Recommendation=],
- or if there is no [=Working Group=] chartered to maintain a [=Recommendation=]
- W3C may republish the [=Recommendation=],
+ A [=Working group=] may request republication of a [=Recommendation=]
to make corrections that do not result
in any changes to the text of the specification.
(See class 1 changes.)
+ If there is no [=Working Group=] chartered to maintain a [=Recommendation=],
+ the [=Team=] may republish the [=Recommendation=]
+ with such changes incorporated.
+
Revising a Recommendation: Editorial Changes
@@ -3475,10 +3467,14 @@ Revising a Recommendation: Editorial Changes
A [=Working Group=],
provided there are no votes against the resolution to publish,
may request publication of a [=Recommendation=]
- or W3C may publish a [=Recommendation=]
to make this class of change without passing through earlier maturity levels.
(See class 2 changes.)
+ If there is no [=Working Group=] chartered to maintain a [=Recommendation=],
+ the [=Team=] may republish the [=Recommendation=]
+ with such changes incorporated,
+ including [=errata=] and [=candidate corrections=].
+
Revising a Recommendation: Substantive Changes
@@ -3496,13 +3492,15 @@ Revising a Recommendation: Substantive Changes
Alternatively,
a [=Working Group=] may incorporate the changes
and publish as a Candidate Recommendation,
- or if no [=Working Group=] is chartered to maintain a [=Recommendation=]
- W3C may publish a candidate Amended Recommendation,
and advance the specification from that state.
- If the publication was requested by the [=W3C team=] in the absence of a [=Working Group=],
- the resulting [=Recommendation=] will be called an [=Amended Recommendation=].
(See class 3 changes.)
+ Note: If there is no [=Working Group=] chartered to maintain a [=Recommendation=]
+ the [=Team=] cannot make substantive changes and republish the [=Recommendation=].
+ It can, however, informatively highlight problems and desirable changes
+ using [=errata=] and [=candidate corrections=]
+ and republish as described in [[#revised-rec-editorial|the previous section]].
+
Revising a Recommendation: New Features