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

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

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

Tobias Kunze  commented on CAMP-29:
-----------------------------------

Apologies for the idiosyncrasy, I just thought using an informal formalism would somehow help things along. Braces here are sets and "*" and "+" are the same as in regular expressions (i.e. any number of and one or more of something). So, M = {Ca: {p, q}, Ce: {}, Cp: {r, s, t}} means M is a set of 3 sets: a set of Ca which has members p and q, a set of Ce, which is empty and a set of Cp with contains r, s and t.

ExternalComponents are Components that are logically part of the Assembly but not managed within the context of the Assembly by either the application owner or the platform. For instance, an AWS such as SQS or S3 would be an ExternalComponent. It is important that the Assembly is able to express such Components so that the Platform can manage e.g. the network connection. (This is straightforward for port 80, but often less so for port 25, for instance).


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