From 36013df81aa68de91e1ce2428f032e3e076799ca Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Wed, 15 Mar 2017 23:24:33 -0700 Subject: [PATCH] runtime: Drop "not supported by the base OS" loophole All of these operations should be supported on all of our compliance-tested platforms. If there are cases where a given OS cannot support one of these operations, it should be discussed in that operation's section, and the "Unless otherwise stated" qualifier makes space for that. But leaving the reader to decide on whether a host OS supports a given operation seems too unstable for a specification. I've also dropped the "OCI compliant" qualifier, because the (not) compliant language in spec.md already ties OCI compliance to the RFC 2119 language. There's no point in mentioning "OCI compliant" outside of that section, because the "MUST" already brings in all of the compliance associations we need. Signed-off-by: W. Trevor King --- runtime.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/runtime.md b/runtime.md index 4786848..8a90605 100644 --- a/runtime.md +++ b/runtime.md @@ -82,7 +82,7 @@ Unless otherwise stated, logging a warning does not change the flow of the opera ## Operations -OCI compliant runtimes MUST support the following operations, unless the operation is not supported by the base operating system. +Unless otherwise stated, runtimes MUST support the following operations. Note: these operations are not specifying any command-line APIs, and the parameters are inputs for general operations.