[OASIS Issue Tracker] Created: (CAMP-127) 8 Conformance - 8.1, 8.2, 8.3 - General comment

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

8 Conformance - 8.1, 8.2, 8.3 - General comment
-----------------------------------------------

                 Key: CAMP-127
                 URL: http://tools.oasis-open.org/issues/browse/CAMP-127
             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
          Issue Type: Bug
          Components: Public Review
            Reporter: Gilbert Pilz


From the comment list: https://lists.oasis-open.org/archives/camp-comment/201309/msg00078.html 
TAB issue: 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.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira