[OASIS Issue Tracker] Created: (CAMP-35) Spec needs to clarify the constraints on the relationship between Assembly Templates and Application Component Templates

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

Spec needs to clarify the constraints on the relationship between Assembly Templates and Application Component Templates
------------------------------------------------------------------------------------------------------------------------

                 Key: CAMP-35
                 URL: http://tools.oasis-open.org/issues/browse/CAMP-35
             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
          Issue Type: Bug
          Components: Spec
            Reporter: Gilbert Pilz
            Assignee: Mark Carlson


<a href="https://tools.oasis-open.org/issues/browse/CAMP-24";>CAMP-24></a> clarified that an Assembly Template (AT) must have at least one Application Component Template (ACT) if it is to be instantiated. However, there are a number of things about ACTs and their relationship with ATs that are not discussed in the current draft of the specification (<a href="https://www.oasis-open.org/apps/org/workgroup/camp/download.php/47637/camp-spec-v1.1-wd01.pdf";>WD01</a>). For example:

Q1: Do ACTs exist outside the context of a particular AT?

Q2: Can a single ACT be contained by more than one AT?

Q3: Can you add an ACT to an existing AT and, if so, how did the ACT you are adding get created?

Since you can't implement the spec unless you know the answers to these questions, answering them is necessary.

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