Issue 6484: Section 17 (uml2-superstructure-ftf) Source: Sparx Systems Pty Ltd (Mr. James D. Baker, omg(at)objectsandaspects.com) Nature: Uncategorized Issue Severity: Summary: Page 534 states, "When it is attached to an information channel, a black triangle on the information channel indicates the direction." What is an information channel? This is the only sentence in the document in which this phrase is used. Resolution: see above Revised Text: Actions taken: November 7, 2003: received issue March 8, 2005: closed issue Discussion: On page 532, add the following sentence at the end of the Description sub-section of InformationFlow: Information flows require some kind of “information channel” for transmitting information items from the source to the destination. An information channel is represented in various ways depending on the nature of its sources and targets. It may be represented by connectors, links, associations, or even dependencies. For example, if the source and destination are parts in some composite structure such as a collaboration, then the information channel is likely to be represented by a connector between them. Or, if the source and target are objects (which are a kind of InstanceSpecification), they may be represented by a link that joins the two, and so on. End of Annotations:===== ection 17 Page 534 states, "When it is attached to an information channel, a black triangle on the information channel indicates the direction." What is an information channel? This is the only sentence in the document in which this phrase is used. OMG Issue No: 6484 Title: Section 17 Source: BAE Systems-Mission Solutions (Mr. James D. Baker, james.d.baker@baesystems.com) Summary: Page 534 states, "When it is attached to an information channel, a black triangle on the information channel indicates the direction." What is an information channel? This is the only sentence in the document in which this phrase is used. Discussion: On page 532, add the following sentence at the end of the Description sub-section of InformationFlow: Information flows require some kind of .information channel. for transmitting information items from the source to the destination. An information channel is represented in various ways depending on the nature of its sources and targets. It may be represented by connectors, links, associations, or even dependencies. For example, if the source and destination are parts in some composite structure such as a collaboration, then the information channel is likely to be represented by a connector between them. Or, if the source and target are objects (which are a kind of InstanceSpecification), they may be represented by a link that joins the two, and so on. Disposition: Resolved Reply-To: From: "Conrad Bock" To: "Branislav Selic" , , "Guus Ramackers" Subject: RE: Draft of Ballot 11 -- please review Date: Wed, 31 Mar 2004 16:19:44 -0500 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal Hi Bran, > OMG Issue No: 6351 > Title: InformationFlow realization Sorry I hadn't followed up on this, but the problem is that connector is not directed, whereas flows are. We shouldn't use navigation to indicate flow direction. Also, the issue is that info flow needs much more flexible implementations that can include objects. The resolution to 6484 refers to info flow on connectors, but should be written to be independent of 6351. Issue 6981 (incorrect grammar for ) removes signficant and useful functionality. I searched the email and didn't see any presentation of this before or dicussion, maybe I missed it. Recommending that 6351 and 6981 be excluded from ballot 11, and 6484 be written to not refer to connectors. Conrad