[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=31732#action_31732 ] Adrian Otto commented on CAMP-29: --------------------------------- I support this idea. Rather than { " prevenance" : "platform" } to identify the origin, I suggest: 1) We review the solution to: https://tools.oasis-open.org/issues/browse/CAMP-13 and make sure the resolutions to this issue and CAMP-13 are coordinated. 2) Use a standard type name (defined in the spec) for all Components. For example: { "type" : "component", ... } 3) Identify a required "origin" attribute. { "origin" : { "name" : "platform", "rel" : "http://..." }} or { "origin" : { "name" : "application", "rel" : "http://..." }} > "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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]