On Tue, Mar 01, 2022 at 12:17:24AM +0100, Carsten Bormann wrote: > > A full review should not be necessary. > > I wish that were true... IMO a full review is necessary, not least to ensure that the document remains self-consistent and that any changes applied during editing are uniformly applied to all relevant parts of the document, not just in the subset of places that the editor noticed. This is analogous to a situation that arises when doing code review. If you change an API's semantics, you had better go around and check all the callers of that API to see if they need adjustments, not just the callers of the API that your test suite happens to exercise. With specifications we do not have the rigid rules of function names to identify the places to check, and the safe thing to do is read the whole document with any changes that were made fresh in mind. -Ben