Issue 7242: Missing definition for connection in chapter 5: (deployment-ftf) Source: Fraunhofer FOKUS (Mr. Andreas Hoffmann, andreas.hoffmann@fokus.fraunhofer.de a-hoffmann@gmx.net) Nature: Uncategorized Issue Severity: Summary: The resolution for issue #6026 added several definitions to chapter 5 ("Terms and Definitions"). The definitions 5.10, 5.13, and 5.23 refer directly or implicitely to the term "connection" (between components). However, this term is not defined in chapter 5 yet. Proposed resolution: Don't change current definitions but add an appropriate definition for connection. Resolution: Revised Text: In chapter 5, increase the section numbers of all sections starting with 5.9 by 1. Add an additional section "5.9 Connection" with the following content: A connection is either a communication path among the ports of two or more subcomponents allowing them to communicate with each other, or it is a communication path between an assembly's external ports and an assembly's subcomponents that delegates the external port's behavior to the subcomponent's ports. The endpoint of a connection may also refer to a location outside the assembly. Actions taken: April 15, 2004: received issue May 9, 2005: closed issue Discussion: Resolution: Add a section defining the term connection. End of Annotations:===== Date: Thu, 15 Apr 2004 12:46:05 +0200 From: Andreas Hoffmann Organization: Fraunhofer FOKUS User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: de, en, en-us, en-gb To: issues@omg.org CC: Deployment FTF Subject: missing definition for connection in chapter 5 (Deployment FTF issue) Missing definition for connection in chapter 5: This is an issue for the Deployment FTF. The resolution for issue #6026 added several definitions to chapter 5 ("Terms and Definitions"). The definitions 5.10, 5.13, and 5.23 refer directly or implicitely to the term "connection" (between components). However, this term is not defined in chapter 5 yet. Proposed resolution: Don't change current definitions but add an appropriate definition for connection. Regards Andreas ==================================================================== Andreas Hoffmann Fraunhofer FOKUS - Research Institute for Open Communication Systems Kaiserin-Augusta-Allee 31 D - 10589 Berlin Phone: +49 30 3463-7392 Fax: +49 30 3463-8392 Email: andreas.hoffmann@fokus.fraunhofer.de ==================================================================== Date: Wed, 26 May 2004 08:52:55 +0200 From: Andreas Hoffmann Organization: Fraunhofer FOKUS User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: de, en, en-us, en-gb To: Deployment FTF Subject: proposed resolution for issue #7242 If you want to change the proposed description of connection, please answer asap. Proposed resolution for issue #7242: Missing definition for connection in chapter 5: Add a section defining the term connection. Editing instructions: In chapter 5, increase the section numbers of all sections starting with 5.9 by 1. Add an additional section "5.9 Connection" with the following content: A connection is either a communication link among the ports of two or more subcomponents allowing them to communicate with each other, or it is a communication link between an assembly's external ports and an assembly's subcomponents that delegates the external port's behavior to the subcomponent's ports. The endpoint of a connection may also refer to a location outside the assembly. -- Regards Andreas ==================================================================== Andreas Hoffmann Fraunhofer FOKUS - Research Institute for Open Communication Systems Kaiserin-Augusta-Allee 31 D - 10589 Berlin Phone: +49 30 3463-7392 Fax: +49 30 3463-8392 Email: andreas.hoffmann@fokus.fraunhofer.de ==================================================================== X-Dreamscape-Track-Mars-A: [166.157.160.45] X-Dreamscape-Track-Mars-B: Wed, 26 May 2004 08:55:32 -0400 (EDT) Date: Wed, 26 May 2004 08:54:49 -0400 From: James Kulp Organization: Mercury Computer Systems, Inc. User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en,pdf To: Andreas Hoffmann CC: Deployment FTF Subject: Re: proposed resolution for issue #7242 Andreas Hoffmann wrote: If you want to change the proposed description of connection, please answer asap. Proposed resolution for issue #7242: Missing definition for connection in chapter 5: Add a section defining the term connection. Editing instructions: In chapter 5, increase the section numbers of all sections starting with 5.9 by 1. Add an additional section "5.9 Connection" with the following content: A connection is either a communication link among the ports of two or more subcomponents allowing them to communicate with each other, or it is a communication link between an assembly's external ports and an assembly's subcomponents that delegates the external port's behavior to the subcomponent's ports. The endpoint of a connection may also refer to a location outside the assembly. The term "communication link" sounds too hardwarish. I would use "communication path", and possibly "analogous to signals in a hierarchical electrical design". Date: Wed, 26 May 2004 18:18:27 +0200 From: Andreas Hoffmann Organization: Fraunhofer FOKUS User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: de, en, en-us, en-gb To: James Kulp CC: Deployment FTF Subject: Re: proposed resolution for issue #7242 Hi Jim, thank for your comment. James Kulp wrote: Andreas Hoffmann wrote: If you want to change the proposed description of connection, please answer asap. Proposed resolution for issue #7242: Missing definition for connection in chapter 5: Add a section defining the term connection. Editing instructions: In chapter 5, increase the section numbers of all sections starting with 5.9 by 1. Add an additional section "5.9 Connection" with the following content: A connection is either a communication link among the ports of two or more subcomponents allowing them to communicate with each other, or it is a communication link between an assembly's external ports and an assembly's subcomponents that delegates the external port's behavior to the subcomponent's ports. The endpoint of a connection may also refer to a location outside the assembly. The term "communication link" sounds too hardwarish. I would use "communication path", and possibly "analogous to signals in a hierarchical electrical design". Ok, I take "communication path". I found it somewhat hard to describe a connection without using the term connect. The simple term link sounded too unspecific, maybe communication path is better even though this term is also used for describing bridges. Regards Andreas ==================================================================== Andreas Hoffmann Fraunhofer FOKUS - Research Institute for Open Communication Systems Kaiserin-Augusta-Allee 31 D - 10589 Berlin Phone: +49 30 3463-7392 Fax: +49 30 3463-8392 Email: andreas.hoffmann@fokus.fraunhofer.de ====================================================================