UMLR — UML2 Super/Deployments/Manifestation

Manifestation should inherit from Realization

In Section 10.3.10 and Figure 124 it would make more sense for
Manifestation to inherit from Realization rather than directly from
Abstraction. The semantics of Realization are described as "A
Realization signifies that the client set of elements are an
implementation of the supplier set,.." which surely includes
manifestation.
The spec also states that Realization may be used to model
transformations, which fits with the example given in Manifestation:
"<<tool generated>> and <<custom code>> might be two manifestations for
different classes".

BTW There is a missing word in the description of Manifestation "A
manifestation is the concrete physical of one or more model elements by
an artifact."