Commit d4d40d7

An [=erratum=] <em class="rfc2119">may</em> be accompanied by a non-normative,

<dfn>candidate correction</dfn> approved by [=group decision=].

When annotated inline,

errata--

including their [=candidate corrections=]--

must be marked as such,

are treated as <a href="#correction-classes">class 2 changes</a>,

A <dfn>candidate addition</dfn> is similar to a [=candidate correction=],

except that it proposes a new feature

rather than an error correction.

[=Candidate corrections=] and [=candidate additions=] are collectively known as

<dfn lt="candidate amendment">candidate amendments</dfn>.

<li>[=candidate corrections=],

However, <a href=#class-4>new features</a> can only be added

if the document already identifies itself

as intending to <dfn>allow new features</dfn>.

Adding or removing this allowance is a [=substantive change=].

Such an allowance cannot be added

to a [=technical report=] previously published as a [=Recommendation=]

that did not allow such changes;

this requires a new [=technical report=]

(which could, for example, be similarly named but with an incremented version number).

Additionally,

if the document has previously been published as a [=W3C Recommendation=], the [=Working Group=]

<em class=rfc2119>must not</em> include any <a href="#correction-classes">class 4 change</a>

to that publication

unless it was explicitly marked as [=allowing new features=],

and <em class=rfc2119>must not</em> include any such marking

if not already present.

* the addition or removal of a statement as to whether the document will [=allow new features=]

after its publication as a [=Recommendation=].

Tentative corrections (see <a href="#class-3">class 3 changes</a>)

using [=candidate corrections=].

Note: [=Candidate corrections=] do not normatively modify the document;

A [=candidate correction=] can be made normative

(See <a href="#correction-classes">class 3 changes</a>.)

For [=Recommendations=] explicitly identified as [=allow new features|allowing new features=],

tentative new features (see <a href="#correction-classes">class 4 changes</a>)

<em class=rfc2119>may</em> be added as [=candidate additions=] in annotations,

and <a href="#correction-classes">class 4 changes</a> may be normatively incorporated

in the same fashion as <a href="#correction-classes">class 3 changes</a> in [[#revised-rec-substantive]].

Note: Limiting the addition of new features to [=Recommendations=] that explicitly allow them

enables third parties to depend on a stable feature-set for [=Recommendations=] that do not advertise that ability,

as was the case for all [=Recommendations=] prior to the 2020 revision of this Process.

Note: When a [=Recommendation=] does not [=allow new features=],

new features can be added by creating a new [=technical report=]

and following the full process of advancing that [=technical report=] to [=Recommendation=]--

beginning with a new [=First Public Working Draft=].

Such [=technical reports=] could be written to represent

additional modules building on top of the original [=Recommendation=] of the core technology,

or an expanded replacement of the original [=Recommendation=] of the core technology

(in which case the new [=technical report=] will typically have the same name as the original,

with an incremented version number).

<li>

Identify whether this is a

<dfn>Last Call for Review of Proposed Corrections</dfn>,

<dfn>Last Call for Review of Proposed Additions</dfn>,

or <dfn>Last Call for Review of Proposed Corrections and Additions</dfn>.

as <dfn>proposed amendments</dfn>

(<dfn export>proposed corrections</dfn>/<dfn oldids="proposed-addition" export>proposed additions</dfn>).

Note: [=Last Call for Review of Proposed Additions=] and

[=Last Call for Review of Proposed Corrections and Additions=]

can only be issued for [=Recommendations=] that [=allow new features=].

just as in a [=Last Call for Review of Proposed Corrections=].