Uploaded image for project: 'OASIS Cloud Application Management for Platforms (CAMP) TC'
  1. OASIS Cloud Application Management for Platforms (CAMP) TC
  2. CAMP-232

9 Conformance - Relationship btw mandatory and RFC2119 not defined

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Applied
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.2
    • Fix Version/s: 1.2
    • Component/s: Spec
    • Labels:
      None
    • Environment:

      Conformance

    • Proposal:
      Hide

      Re-cast the conformance clauses to have meaningful structure and lose the mandatory versus non-mandatory (not defined anyway) distinction. That will result in conformance clauses that set expectations that further interchange.

      Or, remove the SHOULD and MAY material as irrelevant to the implementation of a conformance target.

      Show
      Re-cast the conformance clauses to have meaningful structure and lose the mandatory versus non-mandatory (not defined anyway) distinction. That will result in conformance clauses that set expectations that further interchange. Or, remove the SHOULD and MAY material as irrelevant to the implementation of a conformance target.

      Description

      The conformance target definitions in 9 Conformance share the form:

      "...SHALL comply with all the CAMP ***** or ***** mandatory requirements listed in this specification, as summaried in Appendix C.1, "Mandatory Statements"."

      Despite in invocation of RFC 2119, which provides levels of expectations for interchange in 1.6.2, the only expectation invoked by these conformance targets are with the keyword SHALL.

      That is to say that the conformance requirements defined in Appendix C.2 Non-Mandatory, are discarded and rendered nugatory by this definition of conformance targets. Why SHOULD and MAY requirements are defined only to be ignored isn't clear.

      SHOULD and MAY carry less force than SHALL but for interchange purposes, are not valueless.

        Attachments

          Activity

            People

            • Assignee:
              martin.chapman Martin Chapman (Inactive)
              Reporter:
              chet-oasis Chet Ensign
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: