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

Jump to bottom

Retire Amended RECs #428

Merged
merged 5 commits into from
Sep 16, 2020
Merged

Retire Amended RECs #428

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a7de755
Retire Amended RECs
frivoal Jul 20, 2020
089c4b6
Remove non-obvious reference to the amended REC process from the defi…
frivoal Aug 6, 2020
a767dad
Clarify involvment of the Team in class 1 and 2 changes
frivoal Aug 13, 2020
0e2e171
Add note indicating the Team cannot make substantive changes to RECs
frivoal Aug 13, 2020
9976b83
Add requirements on Team-maintained candidate corrections
frivoal Aug 13, 2020
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
60 changes: 29 additions & 31 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2527,6 +2527,15 @@ Candidate Changes</h4>
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=] <em class="rfc2119">may</em> maintain its [=errata=]
and associated [=candidate corrections=].
When doing so,
it <em class=rfc2119>must</em> be explicit that those [=errata=] and [=candidate corrections=]
were written by the [=Team=].
The [=Team=] <em class=rfc2119>must</em> solicit [=wide review=]
on [=candidate corrections=] that it produces.

[=Candidate corrections=] and [=candidate additions=] are collectively known as
<dfn lt="candidate change">candidate changes</dfn>.

Expand Down Expand Up @@ -2580,7 +2589,6 @@ The W3C Recommendation Track</h3>
<li>Publication of one or more [=Candidate Recommendations=].
<li>Publication of a [=Proposed Recommendation=].
<li>Publication as a [=W3C Recommendation=].
<li>Possibly, publication as an [=Amended Recommendation=].
</ol>

<div role="region" aria-label="Basic W3C Recommendation Track">
Expand Down Expand Up @@ -2651,8 +2659,6 @@ Maturity Levels on the Recommendation Track</h4>
<dd>
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

Expand Down Expand Up @@ -2757,17 +2763,6 @@ Maturity Levels on the Recommendation Track</h4>
As technology evolves,
a [=W3C Recommendation=] may become:
<dl>
<dt>
An <dfn id="rec-amended" export>Amended Recommendation</dfn>
<dd>
An Amended Recommendation is a [=Recommendation=] that is amended to include
<a href="#correction-classes">substantive changes that do not add new features</a>,
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]].

<dt>
A <dfn export id="RecsSup">Superseded Recommendation</dfn>
<dd>
Expand Down Expand Up @@ -3139,10 +3134,7 @@ Transitioning to Candidate Recommendation</h4>

To publish a [=Candidate Recommendation=],
in addition to meeting the <a href="#transition-reqs">requirements for advancement</a>
a [=Working Group=],
or in the case of a candidate [=Amended Recommendation=]
(a document intended to become an [=Amended Recommendation=]),
W3C:
a [=Working Group=]:

<ul>
<li>
Expand Down Expand Up @@ -3313,8 +3305,7 @@ Transitioning to Proposed Recommendation</h4>
in the W3C Patent Policy [[!PATENT-POLICY]].
</ul>

A Working Group,
or for a proposed [=Amended Recommendation=], W3C:
A Working Group:

<ul>
<li>
Expand Down Expand Up @@ -3388,7 +3379,6 @@ Transitioning to Proposed Recommendation</h4>

<li>
<a href="#transition-rec">Recommendation status</a>,
including [=Amended Recommendation=]
(the expected next step).

<li>
Expand Down Expand Up @@ -3440,11 +3430,11 @@ Transitioning to W3C Recommendation</h4>

<ul>
<li>
republished as a <a href="#revising-rec">revised Recommendation or Amended Recommendation</a>, or
republished as a <a href="#revising-rec">revised Recommendation</a>, or

<li>
republished as a <a href="#transition-cr">Candidate Recommendation</a>
to be developed towards a revised [=Recommendation=] or [=Amended Recommendation=], or
to be developed towards a revised [=Recommendation=], or

<li>
declared <a href="#rec-rescind">superseded or obsolete</a>, or
Expand All @@ -3461,24 +3451,30 @@ Revising a W3C Recommendation</h4>
<h5 id="revised-rec-markup">
Revising a Recommendation: Markup Changes</h5>

A [=Working group=] <em class="rfc2119">may</em> request republication of a [=Recommendation=],
or if there is no [=Working Group=] chartered to maintain a [=Recommendation=]
W3C <em class="rfc2119">may</em> republish the [=Recommendation=],
A [=Working group=] <em class="rfc2119">may</em> request republication of a [=Recommendation=]
to make corrections that do not result
in any changes to the text of the specification.
(See <a href="#correction-classes">class 1 changes</a>.)

If there is no [=Working Group=] chartered to maintain a [=Recommendation=],
the [=Team=] <em class="rfc2119">may</em> republish the [=Recommendation=]
with such changes incorporated.

<h5 id="revised-rec-editorial">
Revising a Recommendation: Editorial Changes</h5>

[=Editorial changes=] to a [=Recommendation=] require no technical review of the intended changes.
A [=Working Group=],
provided there are no votes against the resolution to publish,
<em class="rfc2119">may</em> request publication of a [=Recommendation=]
or W3C <em class="rfc2119">may</em> publish a [=Recommendation=]
to make this class of change without passing through earlier maturity levels.
(See <a href="#correction-classes">class 2 changes</a>.)

If there is no [=Working Group=] chartered to maintain a [=Recommendation=],
the [=Team=] <em class="rfc2119">may</em> republish the [=Recommendation=]
with such changes incorporated,
including [=errata=] and [=candidate corrections=].

<h5 id="revised-rec-substantive">
Revising a Recommendation: Substantive Changes</h5>

Expand All @@ -3496,13 +3492,15 @@ Revising a Recommendation: Substantive Changes</h5>
Alternatively,
a [=Working Group=] <em class="rfc2119">may</em> incorporate the changes
and <a href="#transition-cr">publish as a Candidate Recommendation</a>,
or if no [=Working Group=] is chartered to maintain a [=Recommendation=]
W3C <em class="rfc2119">may</em> publish a <a href="#transition-cr">candidate Amended Recommendation</a>,
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 <a href="#correction-classes">class 3 changes</a>.)

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]].

<h5 id="revised-rec-features">
Revising a Recommendation: New Features</h5>

Expand Down