Update the editorial style for normative changes #113
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wareid
approved these changes
Feb 22, 2022
|
@wareid I let you decide when you want to merge this; it affects the PR you are working on after all... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I applied the style and structure necessary for the update of a Recommendation. This should only be applied to normative changes.
The essential point is: the changes should remain in the document, ie, both the old and new, suitably included in
<del>and<ins>elements, and linking to the short description of the changes. The rest (adding buttons to show old or new) is done by a JS magic included by respec.This should only happen with normative changes!
Preview | Diff