[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [camp] [OASIS Issue Tracker] Commented: (CAMP-29) "Application Component" and "Platform Component" should be collapsed into a single "Component"; "Application Component Template" and "Platform Component Template" should be collapsed into a single "Component Template"
Ooops! I'll update the proposal to remove that change description. Don't want to confuse anyone else … ~ gp On Oct 8, 2013, at 6:38 PM, OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> wrote: > > [ http://tools.oasis-open.org/issues/browse/CAMP-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35161#action_35161 ] > > Alex Heneveld commented on CAMP-29: > ----------------------------------- > > Gil- > > +1 and +1 > > One of the changes listed at the start of the proposal is "Remove "components" array from Platform resource" -- that's why I thought you had done it. Makes sense to keep it for the reason you give, however (especially as it is optional). > > Is it worth some language to explain this and/or clarify that not everything has to be listed at the top level? > > --A > >> "Application Component" and "Platform Component" should be collapsed into a single "Component"; "Application Component Template" and "Platform Component Template" should be collapsed into a single "Component Template" >> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- >> >> Key: CAMP-29 >> URL: http://tools.oasis-open.org/issues/browse/CAMP-29 >> Project: OASIS Cloud Application Management for Platforms (CAMP) TC >> Issue Type: Improvement >> Components: Spec >> Reporter: Gilbert Pilz >> Assignee: Gilbert Pilz >> Priority: Critical >> >> There is no justification for the complexity caused by segregation of components and templates into "Application" and "Platform" sub-types. The methods for discovering a template, figuring out whether that template describes a services that will meet your requirements, indicating that your application will make use of the service described by that template, indicating that your application is using a service, etc. do not vary between "Application" things and "Platform" things. At present, the only purpose of the Application/Platform distinction is to indicate the provenance of a component/template. If such an indication is necessary, it can be provided by some other mechanism such as an attribute (e.g. { "provenance" : "platform" }) > > -- > 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 > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]