Issue 6372: Notes versus curly braces (uml2-rtf) Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov) Nature: Revision Severity: Summary: Why do decision input behaviors use the note notation and join specification use curly braces? Resolution: A decision input behavior is a behavior, and it could potentially involve a lengthy computation. A join specification is a value specification and will typically be very short, perhaps even just a single operator (the default is "and"). Revised Text: None Disposition: Closed, no Change Revised Text: Actions taken: October 20, 2003: received issue April 26, 2010: closed issue April 26, 2010: closed issue Discussion: This is does not affect usage or implementability enough for the FTF to address, and requires too many changes. Due to lack of time, the RTF/FTF agrees that the following are problems that need fixing, but decided to defer their resolution to a future RTF working on this specification. End of Annotations:===== me: Conrad Bock Company: NIST mailFrom: conrad.bock@nist.gov Nature: Revision Severity: Clarification Subject: Notes versus curly braces Why do decision input behaviors use the note notation and join specification use curly braces? OMG Issue No: 6372 Title: Notes versus curly braces Source: NIST (Mr. Conrad Bock, conrad.bock@nist.gov) Summary: Why do decision input behaviors use the note notation and join specification use curly braces? Discussion: This is does not affect usage or implementability enough for the FTF to address, and requires too many changes. Subject: Proposed issue resolutions, set 1: Activities -- No change and duplicates Date: Fri, 30 Jan 2009 18:00:16 -0500 X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: Proposed issue resolutions, set 1: Activities -- No change and duplicates thread-index: AcmDLoPo5ZLYjIHbRwaX3F8d2ZwvGA== From: "Ed Seidewitz" To: Attached is a Word document with draft resolutions for Activities issues that I propose to close with no change or that I have identified as duplicates of other issues. -- Ed OMG Issue No: 6372 Title: Note versus curly braces Source: NIST (Mr. Conrad Bock, conrad.bock@nist.gov conradb@nist.gov) Summary: Why do decision input behaviors use the note notation and join specification use curly braces? Resolution: A decision input behavior is a behavior, and it could potentially involve a lengthy computation. A join specification is a value specification and will typically be very short, perhaps even just a single operator (the default is .and.). Revised Text: None Disposition: Closed, no Change Disposition: Defer