Issue 8128: Section: 9.3.13 (uml2-rtf)
Source:  (, )
Nature: Clarification
Severity: Minor
Summary: Associations need derived symbol added to role:ConnectableElement and /part:Property (as shown in fig. 95), a statement that role is derived, and multiplicities added to all associations (as shown in fig. 95).

Resolution: see ptc/2006-04-01 page 140
Revised Text: 
Actions taken:
January 25, 2005: received issue
August 23, 2006: closed issue
Discussion: 


End of Annotations:=====

m: webmaster@omg.org 
Date: 25 Jan 2005 12:41:41 -0500 
To: <issues@omg.org> 
Subject: Issue/Bug Report 



--------------------------------------------------------------------------------

Name: Jane Messenger
Company: U. S. Geological Survey
mailFrom: jmessenger@usgs.gov
Notification: Yes
Specification: Superstructure
Section: 9.3.13
FormalNumber: ptc/04-10-02
Version: 2.0 Draft Adopted
RevisionDate: 10/08/2004
Page: 195
Nature: Clarification
Severity: Minor
HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461)
Description
Associations need derived symbol added to role:ConnectableElement and /part:Property (as shown in fig. 95), a statement that role is derived, and multiplicities added to all associations (as shown in fig. 95).


Issue 8128: Section: 9.3.13 


Issue summary 
Associations need derived symbol added to role:ConnectableElement and /part:Property (as shown in fig. 95), a statement that role is derived, and multiplicities added to all associations (as shown in fig. 95). 


Discussion 
Agreed. These are all editorial fixes. It is not necessary to include an explicit derivation statement, since it is implied by the Subsets description. 
-- BranSelic - 27 Jul 2005 


Revised Test 

On page 195 in the Associations subsection of Structured Classifier?, add a ./. in front of the .role:ConnectableElement. item to indicate that .role. is derived. Also, add an explicit multiplicity of [0..*] (i.e., .role:ConnectableElement [0..*].) 
On page 195 in the Associations subsection of Structured Classifier?, add a ./. in front of the .part:Property. item to indicate that .part. is derived. Also, add an explicit multiplicity of [0..*] (i.e., .part:Property [0..*].) 
On page 195 in the Associations subsection of Structured Classifier?, add an explicit multiplicity of [0..*] to .ownedAttribute:Property. (i.e., .ownedAttribute:Property [0..*].) 
On page 195 in the Associations subsection of Structured Classifier?, add an explicit multiplicity of [0..*] to .ownedConnector:Connector. (i.e., .ownedConnector:Connector [0..*].) 

Resolution 
Resolved
RtfIssue1000000070 (27 Jul 2005 - 20:18 - r1.2 - BranSelic)
Issue 8128: Section: 9.3.13 


Issue summary 
Associations need derived symbol added to role:ConnectableElement and /part:Property (as shown in fig. 95), a statement that role is derived, and multiplicities added to all associations (as shown in fig. 95). 


Discussion 
Agreed. These are all editorial fixes. It is not necessary to include an explicit derivation statement, since it is implied by the Subsets description. 
-- BranSelic - 27 Jul 2005 


Revised Test 

On page 195 in the Associations subsection of Structured Classifier?, add a ./. in front of the .role:ConnectableElement. item to indicate that .role. is derived. Also, add an explicit multiplicity of [0..*] (i.e., .role:ConnectableElement [0..*].) 
On page 195 in the Associations subsection of Structured Classifier?, add a ./. in front of the .part:Property. item to indicate that .part. is derived. Also, add an explicit multiplicity of [0..*] (i.e., .part:Property [0..*].) 
On page 195 in the Associations subsection of Structured Classifier?, add an explicit multiplicity of [0..*] to .ownedAttribute:Property. (i.e., .ownedAttribute:Property [0..*].) 
On page 195 in the Associations subsection of Structured Classifier?, add an explicit multiplicity of [0..*] to .ownedConnector:Connector. (i.e., .ownedConnector:Connector [0..*].) 

Resolution 
Resolved
RtfIssue1000000070 (27 Jul 2005 - 20:18 - r1.2 - BranSelic)