[OASIS Issue Tracker] Created: (CAMP-94) Figure 2-2: CAMP Resources as UML Classes (UML in general)

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

Figure 2-2: CAMP Resources as UML Classes (UML in general)
----------------------------------------------------------

                 Key: CAMP-94
                 URL: http://tools.oasis-open.org/issues/browse/CAMP-94
             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/msg00022.html):

Under Figure 2-2 CAMP Resources as UML Classes, I read the following
paragraphs:

*****
Figure 2-2 is a UML Class Diagram showing the CAMP resources as UML
classes. All CAMP resources share a set of common attributes shown
here as a CampResource parent class.

Each attribute shown in these UML class diagrams has a CAMP common
type. The '+' symbol before each attribute name in the boxes indicates
that the attribute access is public (i.e. available thru the API).
Non-mandatory resource attributes are indicated using the [0..1] UML
multiplicity tag.
*****

Two questions:

1) Are figures normative? (general to all UML figures)

2) If figures/UML are normative, if there is a conflict between the
UML and the normative prose of the text, which controls? (general to
all UML figures)

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