Reconciling MAY/can vs. SHOULD #101
Closed
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
Client MAY (2.2) vs. SHOULD (2.4) use alternatives they're aware of; clients "can" (2.4) vs. SHOULD (5) include the Alt-Used header. Reconciling these both to SHOULDs.
|
LGTM |
|
Discussed in Yokohama; this pull request seems reasonable. |
reschke
added a commit
that referenced
this pull request
Nov 4, 2015
|
There are unfortunately 2 change request here, one of which I partly agree with, the other I disagree with. The first one is caused by having normative language spread over 2.2 and 2.4; I tried to address this in acc3ae3. The second one is about adding a duplicate requirement; I continue to believe we shouldn't do that. We can mention requirements multiple times, but only one place should have the magic keyword (otherwise we risk ending up with exactly the kind of inconsistencies this pull request is about). @MikeBishop are you ok with the change? |
|
I think this is resolved, but if you disagree, please open a new issue ASAP. |
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.
Client MAY (2.2) vs. SHOULD (2.4) use alternatives they're aware of; clients "can" (2.4) vs. SHOULD (5) include the Alt-Used header. Reconciling these both to SHOULDs.