Issue 8313: Section: 13.3.22 (uml2-rtf) Source: (, ) Nature: Clarification Severity: Minor Summary: Add OCL notation to constraint [2] or the note that ICL notation is not definable Resolution: see above Revised Text: In Section 13.3.22., subsection "Constraints", delete constraint [2]. In Section 13.3.8., add subsection "Constraints" with the following constraint: [1] A passive class may not own receptions. not self.isActive implies self.ownedReception.isEmpty() Actions taken: February 22, 2005: received issue August 23, 2006: closed issue Discussion: I propose to move the constraint to Class (from Communications) with the same text and the OCL: not self.isActive implies self.ownedReception.isEmpty() It isn't easy to navigate from Reception to Class. It's possible to go via Behavioral Feature ? ::method to Behavior and via Behavior::context to Behaviored Classifier ? . Then checking if the Behaviored Classifier ? is a Class (downcast) and evaluating the isActive property. So it's possible to define such a constraint, but it's not nice. And I think it's the responsibility of Class and not of Reception. -- TimWeilkiens This is a good idea. -- ThomasWeigert - 24 May 2005 End of Annotations:===== m: webmaster@omg.org Date: 22 Feb 2005 15:17:56 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Jane Messenger Company: U. S. Geological Survey mailFrom: jmessenger@usgs.gov Notification: Yes Specification: Superstructure Section: 13.3.22 FormalNumber: ptc/04-10-02 Version: 2.0 Draft Adopted RevisionDate: 10/08/2004 Page: 486 Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description Add OCL notation to constraint [2] or the note that ICL notation is not definable. Issue 8313: Section: 13.3.22 Issue summary Add OCL notation to constraint [2] or the note that ICL notation is not definable Discussion I propose to move the constraint to Class (from Communications) with the same text and the OCL: not self.isActive implies self.ownedReception.isEmpty() It isn't easy to navigate from Reception to Class. It's possible to go via Behavioral Feature?::method to Behavior and via Behavior::context to Behaviored Classifier?. Then checking if the Behaviored Classifier? is a Class (downcast) and evaluating the isActive property. So it's possible to define such a constraint, but it's not nice. And I think it's the responsibility of Class and not of Reception. -- TimWeilkiens This is a good idea. -- ThomasWeigert - 24 May 2005 Revised Test In Section 13.3.22., subsection "Constraints", delete constraint [2]. In Section 13.3.8., add subsection "Constraints" with the following constraint: [1] A passive class may not own receptions. not self.isActive implies self.ownedReception.isEmpty() Resolution