[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [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"
[ http://tools.oasis-open.org/issues/browse/CAMP-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34681#action_34681 ]
Tom Rutt commented on CAMP-29:
------------------------------
To facillitate discussion of this issue resolution, I took a first cut at modifying the UML model to specify a unified set of Component, ComponentTemplate, ComponentRequirment, and ComponentCapability resource types.
https://www.oasis-open.org/apps/org/workgroup/camp/download.php/50743/Unified%20Model%20for%20Components.docx
I allowed a ComponentTemplate to be owned by either a Platform or an AssemblyTemplate, and a Component to be owned by either a Platform or Assembly, and a Capability to be owned by either a Platform or AssemblyTemplate.
These unified resource types have two optional back pointers to their owning resource, where there is a constraint that exactly one of these back pointers must be present.
The existence of the appropriate back pointer is what distinguishes a platform side resource from anapplication side resource.
This proposal retains the separate applicationComponentDependencies and platformComponentDependencies attributes in the unified componentTemplate.. There would have to be a constraint to require that applicationComponentDependencies attributes point at components owned by an AssemblyTemplate, and that platformComponentDependencies attributes point at componeents owned by a Platform.
> "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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]