Issue 8493: Semantics of isAssured/isDeterminant in conditional node (uml2-rtf) Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov) Nature: Clarification Severity: Minor Summary: Semantics of isAssured/isDeterminant in conditional node, the phrase "concurrently yield a value" sounds it is referring to tests that complete at the same instant in time. Would be clearer to drop "concurrently", since it isn't the concurrency that isAssured/isDeterminant is concerned with, it's the results. Resolution: Revised Text: In Activities, ConditionalNode, Semantics, fourth paragraph, fifth sentence (the one beginning "If the isDeterminate attribute has a true value"), remove "concurrently". Actions taken: March 6, 2005: received issue August 23, 2006: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 06 Mar 2005 10:21:40 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Conrad Bock Company: NIST mailFrom: conrad.bock@nist.gov Notification: No Specification: UML 2 Superstructure Section: Activities FormalNumber: ptc/04-10-02 Version: RevisionDate: Page: Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322) Description Semantics of isAssured/isDeterminant in conditional node, the phrase "concurrently yield a value" sounds it is referring to tests that complete at the same instant in time. Would be clearer to drop "concurrently", since it isn't the concurrency that isAssured/isDeterminant is concerned with, it's the results. Subject: Proposed issue resolutions, Set 2: Activities -- Low and trivial effort changes Date: Sun, 1 Feb 2009 23:25:51 -0500 X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: Proposed issue resolutions, Set 2: Activities -- Low and trivial effort changes thread-index: AcmE7lQ9kq9LsV5zRgKwNovhcAlo8A== From: "Ed Seidewitz" To: Attached are proposed resolutions to 21 additional Activity issues that only required low or trivial effort changes (though there are a few that, on further analysis, I decided to propose to close or identified as duplicate). -- Ed UML 2.3 Resolutions 090201 Seidewitz 2.doc