8 Conformance - 8.1, 8.2, 8.3 - General comment

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: Public Review
    • None
    • Hide

      Change:

      8.1 CAMP Provider
      An implementation claiming to conform to the requirements of a CAMP Provider defined in this specification SHALL comply with all of the mandatory statements listed in Appendix C.1, "Mandatory Statements", related to CAMP Provider or Provider.

      to:

      8.1 CAMP Provider
      An implementation claiming to conform to the requirements of a CAMP Provider defined in this specification SHALL comply with all of the CAMP Provider or Provider mandatory requirements listed in this specification, as summarized in Appendix C.1, "Mandatory Statements".

      Us similar wording for Consumer and Plan.

      In addition in 5.6 change:

      Because of the unique function of this resource, future versions of the CAMP specification SHALL NOT make non-backwards compatible changes to this resource. [RE-16]

      to:

      Note: Because of the unique function of this resource, future versions of the CAMP specification are cautioned against making non-backwards compatible changes to this resource.

      Show
      Change: 8.1 CAMP Provider An implementation claiming to conform to the requirements of a CAMP Provider defined in this specification SHALL comply with all of the mandatory statements listed in Appendix C.1, "Mandatory Statements", related to CAMP Provider or Provider. to: 8.1 CAMP Provider An implementation claiming to conform to the requirements of a CAMP Provider defined in this specification SHALL comply with all of the CAMP Provider or Provider mandatory requirements listed in this specification, as summarized in Appendix C.1, "Mandatory Statements". Us similar wording for Consumer and Plan. In addition in 5.6 change: Because of the unique function of this resource, future versions of the CAMP specification SHALL NOT make non-backwards compatible changes to this resource. [RE-16] to: Note: Because of the unique function of this resource, future versions of the CAMP specification are cautioned against making non-backwards compatible changes to this resource.

      this is: https://tools.oasis-open.org/issues/browse/TAB-102

      8.1, 8.2, 8.3 are all variants of the statement:


              • defined in this specification SHALL comply with all of the mandatory statements listed in Appendix C.1, "Mandatory Statements",

      Two general comments:

      First, no conforming CAMP Provider, CAMP Consumer or Platform Deployment Package is given any guidance on the relationship between conformance and C.2 Non-Mandatory Statements. Silence is by its very nature ambiguous.

      Second, phrasing conformance in terms of this table of statements, serves to deprive the statements of any context, making conformance requirements that are nonsensical.

      For example, in C1, RE-16, we learn:


              • Because of the unique function of this resource, future versions of the CAMP specification SHALL NOT make non-backwards compatible changes to this resource.

      In addition to a present specification being by definition unable to constraint a future specification, there is the additional problem that this is being listed as a conformance requirement. for providers (I think, not sure.)

            Assignee:
            Unassigned
            Reporter:
            Gilbert Pilz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: