[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-145) AssemblyTemplate not very useful
[ http://tools.oasis-open.org/issues/browse/CAMP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35229#action_35229 ] Alex Heneveld commented on CAMP-145: ------------------------------------ Discussing at the F2F. General consensus about: * surfacing Plans as top-level resource (replacing AssemblyTemplates) * Plan resource, returned by server, is the DP, converted to JSON, with hrefs updated * Platform object contains plural resources, not arrays immediately * s/ACT/Artifact/ * s/PCT/Service/ * s/.*Component/Component/ * s/.*Requirement/Requirement/ * removing .*Capability This is proposed to resolve CAMP-23 (capabilities) CAMP-29 (.*components) CAMP-145 (assembly templates). > AssemblyTemplate not very useful > -------------------------------- > > Key: CAMP-145 > URL: http://tools.oasis-open.org/issues/browse/CAMP-145 > Project: OASIS Cloud Application Management for Platforms (CAMP) TC > Issue Type: Task > Components: Spec > Reporter: Alex Heneveld > Priority: Critical > > The AT is not a very usable format. I have no clear way to modify it, and it is awkward relating it back to the DP which often generated it. > Also it is not strictly necessary. Posting a DP could go straight to an Assembly. Is it worth keeping? > It has some useful information, essentially telling the user what assemblies can be created, and what the piece parts are, but on the whole I don't think it pulls its weight, in its current guise. -- 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]