Additional language for conformance statement #374
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
|
@vbatts @crosbymichael PTAL |
| @@ -21,6 +21,9 @@ Table of Contents | |||
|
|
|||
| In the specifications in the above table of contents, the keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in [RFC 2119](http://tools.ietf.org/html/rfc2119) (Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997). | |||
|
|
|||
| 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." | |||
|
LGTM except for #374 (comment) |
|
LGTM save Jon's comment On Thu, Apr 7, 2016, 18:51 Vish Kannan [email protected] wrote:
|
Proposed additional conformance language to support future certification work (cribbed from https://tools.ietf.org/html/rfc2616). Signed-off-by: Stephen R. Walli <[email protected]>
|
Fixed. |
wking
added a commit
to wking/opencontainer-runtime-spec
that referenced
this pull request
Apr 12, 2016
With: $ sed -i 's/[[:space:]]*$//' README.md fixing some trailing whitespace that snuck in with ca0803d (Additional language for conformance statement, 2016-04-06, opencontainers#374). Future occurrences should be caught by git-validation, which checks for whitespace issues since [1,2]. [1]: vbatts/git-validation#7 [2]: vbatts/git-validation#9 Signed-off-by: W. Trevor King <[email protected]>
Mashimiao
pushed a commit
to Mashimiao/specs
that referenced
this pull request
Aug 19, 2016
With: $ sed -i 's/[[:space:]]*$//' README.md fixing some trailing whitespace that snuck in with ca0803d (Additional language for conformance statement, 2016-04-06, opencontainers#374). Future occurrences should be caught by git-validation, which checks for whitespace issues since [1,2]. [1]: vbatts/git-validation#7 [2]: vbatts/git-validation#9 Signed-off-by: W. Trevor King <[email protected]>
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.
Proposed additional conformance language to support future certification work (cribbed from https://tools.ietf.org/html/rfc2616).
Closes #373
Signed-off-by: Stephen R. Walli [email protected]