[OASIS Issue Tracker] Commented: (CAMP-56) Add Conformance Section

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

    [ http://tools.oasis-open.org/issues/browse/CAMP-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33977#action_33977 ] 

Gilbert Pilz commented on CAMP-56:
----------------------------------

I like the overall structure of this proposal, but I think the details need some work.

PaaS Provider:
    - I'm uncomfortable with the idea of normative requirements in Section 2, "Architecture". I think Section 2 should simply describe CAMP's architecture. Any normative requirements can be made in Section 5 and Section 6.
    - I'm uncertain about the requirement to use extension resources to describe any extensions. I thought we had consensus around the idea that the extension resources were optional?

PaaS Consumer:
    - I don't think we should make it the Consumers job to "adhere" to the lifecycle. The Consumer should be free to try and do whatever it likes. It should be up to the Provider to enforce the lifecycle and respond with an error if the Consumer requests something that violates a lifecycle constraint (e.g. attempts to instantiate an Assembly Template with unresolved dependencies).




> Add Conformance Section
> -----------------------
>
>                 Key: CAMP-56
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-56
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Adrian Otto
>            Assignee: Anish Karmarkar
>            Priority: Critical
>
> The Conformance section of the spec simply shows "TBD". This must be filled in. Anish indicated that he had appropriate text to add in there.

-- 
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