Issue 17587: Clarification on the semantics of ports in Encapsulated Classifiers (uml25-ftf)
Source: THALES (Mr. Hugues Vincent, hugues.vincent(at)thalesgroup.com)
Nature: Clarification
Severity: Minor
Summary: Title: Clarification on the semantics of ports in Encapsulated Classifiers
Where: section 11.3.2
Nature of Issue: Clarification
Severity of Issue: Minor
Full Description of the Issue:
Please specify clearly that the ConnectableElements connected by a same Connector must belong to the same StructuredClassifier: this made some issues in the past (UML4DDS).
* The concept of 'side' of a port is not explained enough, depending if it is a port or a port on a part.
* "if there is  a Connector attached to only one side of a Port, any requests arriving this Port will be lost" does it also stand for port which are not 'on a part'? Because in that case, the Port is an external boundary and a Connector may only be inside the Encapsulated Classifiers, may it not?


Resolution: 
Revised Text: 
Actions taken:
September 13, 2012: received issue
Discussion: 

End of Annotations:=====
ssues From: VINCENT Hugues <hugues.vincent@thalesgroup.com>

This is issue # 17587

Title: Clarification on the semantics of ports in Encapsulated Classifiers
Where: section 11.3.2
Nature of Issue: Clarification
Severity of Issue: Minor
Full Description of the Issue:
Please specify clearly that the ConnectableElements connected by a same Connector must belong to the same StructuredClassifier: this made some issues in the past (UML4DDS).
* The concept of 'side' of a port is not explained enough, depending if it is a port or a port on a part.
* "if there is  a Connector attached to only one side of a Port, any requests arriving this Port will be lost" does it also stand for port which are not 'on a part'? Because in that case, the Port is an external boundary and a Connector may only be inside the Encapsulated Classifiers, may it not?