Additional language for conformance statement#373
Closed
stephenrwalli wants to merge 3 commits intoopencontainers:masterfrom
Closed
Additional language for conformance statement#373stephenrwalli wants to merge 3 commits intoopencontainers:masterfrom
stephenrwalli wants to merge 3 commits intoopencontainers:masterfrom
Conversation
Proposed additional conformance language to support future certification work (cribbed from https://tools.ietf.org/html/rfc2616). Signed-off-by: Stephen R. Walli <stephen.walli@gmail.com>
Cleaned up one sentence per line (sorry), and removed the word "level" to clear up the grammar. I agree it is not particularly helpful and there is no additional semantics to "level" in RFC 2119.
Contributor
|
On Thu, Apr 07, 2016 at 10:15:47AM -0700, Stephen Walli wrote:
Sounds good to me (although these commits look like they're missing |
README.md
Outdated
|
|
||
| An implementation is not compliant if it fails to satisfy one or more of the MUST or REQUIRED level requirements for the protocols it implements. An implementation that satisfies all the MUST or REQUIRED level and all the SHOULD level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the MUST level requirements but not all the SHOULD level requirements for its protocols is said to be "conditionally compliant." | ||
| An implementation is not compliant if it fails to satisfy one or more of the MUST or REQUIRED requirements for the protocols it implements. | ||
| An implementation that satisfies all the MUST or REQUIRED and all the SHOULD requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the MUST requirements but not all the SHOULD requirements for its protocols is said to be "conditionally compliant." |
Contributor
There was a problem hiding this comment.
Contributor
|
Could you clean up the commits? (or maybe just squash them). Thanks! |
Contributor
|
I have carried this PR in #374 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Proposed additional conformance language to support future certification work (cribbed from https://tools.ietf.org/html/rfc2616). It introduces the additional concept of compliance. (Some standards use the term "conformance.")
Signed-off-by: Stephen R. Walli stephen.walli@gmail.com