[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-98) 3 Application Management Lifecycle
[ http://tools.oasis-open.org/issues/browse/CAMP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35231#action_35231 ] Alex Heneveld commented on CAMP-98: ----------------------------------- Answers: (1) This is non-normative but useful to ground/clarify the concepts in the specs. (2) The diagrams here are UML *instance* diagrams, very distinct from the *class* diagrams in chapter 2. Personally I feel the diagrams help make the text readable, and they fit here. They should not be merged with those in chap 2. To the OP's larger point, I agree it is overly complicated. I hope resolving CAMP-145 and CAMP-29 will simplify this. I suggest this issue can be closed. > 3 Application Management Lifecycle > ---------------------------------- > > Key: CAMP-98 > URL: http://tools.oasis-open.org/issues/browse/CAMP-98 > 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/msg00035.html): > The paragraphs immediately following 3 Application Management > Lifecycle read: > ***** > The figures in this section are UML object instance diagrams, which > represent related Resource instances at various stages of Platform > Resource instantiation. For simplification, attributes for these > resources are not shown. For a comprehensive list of attributes for > resources see Section 5, "Resources". > Instances in these diagrams are indicated by boxes, with an underlined > "object-name: Class" label. Relationships visible thru the API are > shown using associations with navigation arrows. Implementation > specific relationships are indicated using the association end > notation, without navigation arrows. > ***** > 1) As it is unclear whether Section 3 is normative or not (subject of > a separate comment), these hanging paragraphs will make it difficult > to separate them from the rest of Section 3, should some of it prove > to be normative. > 2) What is the relationship between this UML diagram explanation and > the one following figure 2-6? > Perhaps consolidation of all UML diagram explanations in Section 2 > would give a reader all the information they need? > Doesn't seem to really "fit" here when discussing Application > Management Lifecycle. -- 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]