[OASIS Issue Tracker] Commented: (CAMP-5) Suggest to simplify {Application,Platform} Component {Requirements,Capability}

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

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

Gilbert Pilz commented on CAMP-5:
---------------------------------

This is related to CAMP-29: https://tools.oasis-open.org/issues/browse/CAMP-29

> Suggest to simplify {Application,Platform} Component {Requirements,Capability}
> ------------------------------------------------------------------------------
>
>                 Key: CAMP-5
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-5
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Anish Karmarkar
>
> Instead of talking about
>   1.  Application Component Requirement
>   2.  Application Component Capability
>   3.  Platform Component Requirement
>   4.  Platform Component Capability
> I suggest we simplify these terms to just Capability and Requirement. Rationale is that, since these structures are all likely to be very unique, we should actually be talking about (and introducing types for) "Application Component X Requirement" etc., which would be overkill. Hence, my suggestion to use only one simple type for each.
> However, as Mark pointed out, there are differences between these types on the Application and Platform side regarding whether or not they are required, etc. My sense is that we'd stand to gain more from simplification, though.
> [This issues was raised by Tobias and was drupal issue # 1032]

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