Issue 19163: Section 11.3 (ifml-ftf)
Source: WebRatio Inc (Dr. Marco Brambilla, marco.brambilla(at)webratio.com)
Nature: Uncategorized Issue
Severity: Critical
Summary: Figure 29 and figure 32: the nested component notation does not mean packaging but component realization. Fix figure and UML Profile structure. ViewComponents can be classes and not components. Nested component instances, on the other hand, mean composite structure, which is neither component packaging nor component realization!

Resolution: The figures derive from the definition of most of the IFML concepts as stereotypes of the UML Component class. The definition of the profile has been updated to fix this problem, as from resolution of issue 19164.
The whole clause 11.3 has been restructured by using classes instead of components for defining ViewComponents. Furthermore, events have been stereotyped from UML Ports. Figures and respective descriptions have been fixed.

Revised Text: see pages 109 - 111 of ptc/2014-03-13 for details
Actions taken:
December 9, 2013: received issue
July 15, 2014: closed issue
Discussion: 

End of Annotations:=====
s is issue # 19163 From: Marco Brambilla <mbrambil@gmail.com>

Issue 14:
Section 11.3:
Figure 29 and figure 32: the nested component notation does not mean packaging but component realization. Fix figure and UML Profile structure. ViewComponents can be classes and not components. Nested component instances, on the other hand, mean composite structure, which is neither component packaging nor component realization!