Remove the incorrect paragraph about request() and revoke() having been removed from the spec. #79
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
…en removed from the spec.
|
Is the controversy over? |
|
Consistency could equally be reached by removing the |
|
Controversy isn't an excuse for having a self-inconsistent specification. Removing non-normative text is the quickest way to consistency, and even if a subsequent discussion concludes that we should remove both request() and revoke() too, I don't think we'll wind up re-adding this paragraph. |
|
LGTM |
This was referenced Apr 16, 2016
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.
This paragraph keeps confusing people, since these functions are in fact specified. Removing the paragraph doesn't guarantee we'll keep the functions: it just makes the spec self-consistent.