[OASIS Issue Tracker] Issue Comment Edited: (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=31772#action_31772 ] 

Tobias Kunze  edited comment on CAMP-29 at 11/21/12 1:44 PM:
-------------------------------------------------------------

An Assembly is a set of any number of Ca, any number of Ce, and at least one Cp, formally:

    A := {Ca*, Ce*, Cp+}

If there are two assemblies, M = {Ca: {p, q}, Ce: {}, Cp: {r, s, t}} and N = {Ca: {k}, Ce = {p}, Cp = {u, v}} then either p or q or both will depend on each other (explicitly or implicitly--M won't run unless both are there and operational) and k will depend on p as an ExternalComponent, i.e. as a Component that needs to be there but isn't managed directly by N.  IOW, from the perspective of N, p is simply "external", irrespective of whether p and k are "owned" by the same person/group. A Cp is also an "external" Component as far as an ApplicationComponent is concerned, but it is manageable by the Platform, as opposed to Ce, which are not.


      was (Author: tkunze):
    An Assembly is a set of any number of Ca, any number of Ce, and at least one Cp, formally:

    A := {Ca*, Ce*, Cp+}

If there are two assemblies, M = {Ca: {p, q}, Ce: {}, Cp: {r, s, t}} and N = {Ca: {k}, Ce = {p}, Cp = {u, v}} then either p or q or both will depend on each other (M won't run unless both are there and operational) and k will depend on p as an ExternalComponent, i.e. as a Component that needs to be there but isn't managed directly by N.  IOW, from the perspective of N, p is simply "external", irrespective of whether p and k are "owned" by the same person/group. A Cp is also an "external" Component as far as an ApplicationComponent is concerned, but it is manageable by the Platform, as opposed to Ce, which are not.

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