Issue 8149: Section: 11.3.5 (uml2-rtf) Source: (, ) Nature: Clarification Severity: Minor Summary: It seems to me that the OCL statement does not specify that the UnlimitedNatural needs to be >0. Remove the header Examples as there are none Resolution: Revised Text: Actions taken: January 27, 2005: received issue August 23, 2006: closed issue Discussion: The fact that the value of the insertAtPin must be greater than 0 is a run-time semantic constraint that cannot be captured in the abstract syntax constraint OCL. The rest is a duplicate of 8155. Disposition: Closed, no change End of Annotations:===== m: webmaster@omg.org Date: 27 Jan 2005 13:02:20 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Jane Messenger Company: U. S. Geological Survey mailFrom: jmessenger@usgs.gov Notification: Yes Specification: Superstructure Section: 11.3.5 FormalNumber: ptc/04-10-02 Version: 2.0 Draft Adopted RevisionDate: 10/08/2004 Page: 255-256 Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description It seems to me that the OCL statement does not specify that the UnlimitedNatural needs to be >0. Remove the header Examples as there are none. Issue 8149: Section: 11.3.5 Nature: Clarification Severity: Minor Summary: It seems to me that the OCL statement does not specify that the UnlimitedNatural needs to be >0. Remove the header Examples as there are none Discussion: The fact that the value of the insertAtPin must be greater than 0 is a run-time semantic constraint that cannot be captured in the abstract syntax constraint OCL. The rest is a duplicate of 8155. Revised Text: None. Resolution: Closed, no change.