[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (CAMP-97) 2.1.4 Capabilities and Requirements and following
2.1.4 Capabilities and Requirements and following
-------------------------------------------------
Key: CAMP-97
URL: http://tools.oasis-open.org/issues/browse/CAMP-97
Project: OASIS Cloud Application Management for Platforms (CAMP) TC
Issue Type: Bug
Components: Public Review
Reporter: Gilbert Pilz
Patrick Durusau submitted the following PR comment (https://lists.oasis-open.org/archives/camp-comment/201309/msg00025.html):
I have already comments on the UML diagrams in general and won't
repeat those concerns here.
The balance of section 2 reads as though it is a set of definitions,
accompanied by diagrams to aid the reader in understanding
relationships between the defined items.
If that is the case and I don't know that it is, you make normative
definitions with references to formal definitions, for all of the
terms that appear in Section 2, in CAMP terminology.
Then, in Section 2, as a non-normative section, could be replete with
diagrams that illustrate the points currently being made by the text.
That would avoid the need to resolve conflicts between UML and other
provisions of normative text for CAMP.
--
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]