Issue 17029: Multiplicity of Components::Component::ownedPort ambiguous (deployment-rtf)
Source: Fraunhofer FOKUS (Mr. Max Bureck, max.bureck(at)fokus.fraunhofer.de)
Nature: Clarification
Severity: Significant
Summary: The property Components::ComponentImplementation::capacity is of type Sequence(Capacity). The type Capacity is not existent, neither in the UML meta-model nor in the DEPL specification. It is most likely (also judging from the stand-alone PIM meta-model) that the type Capability was meant here. So the property should be exchanged by the property:
Components::ComponentImplementation::capability(Capability)
Resolution: 
Revised Text: 
Actions taken:
January 23, 2012: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Max Bureck
Employer:        Fraunhofer FOKUS
mailFrom:        max.bureck@fokus.fraunhofer.de
Terms_Agreement: I agree
Specification:   Deployment and Configuration of Component-based Distributed Applications Specification
Section:         8.2.4.2
FormalNumber:    formal/2006-04-02
Version:         4.0
Doc_Year:        2006
Doc_Month:       April
Doc_Day:         02
Page:            103
Title:           Multiplicity of Components::Component::ownedPort ambiguous.
Nature:          Clarification
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue


Description:


The property Components::ComponentImplementation::capacity is of type Sequence(Capacity). The type Capacity is not existent, neither in the UML meta-model nor in the DEPL specification. It is most likely (also judging from the stand-alone PIM meta-model) that the type Capability was meant here. So the property should be exchanged by the property:
Components::ComponentImplementation::capability(Capability)