Issue 18993: proxy and full port notation change request (sysml-rtf) Source: No Magic, Inc. (Mr. Nerijus Jankevicius, nerijus(at)nomagic.com) Nature: Uncategorized Issue Severity: Summary: After ˜1 year of using new proxy and full ports, our customers are not happy with using <<proxy>> and <<full>> keywords/labels for port kind identification. In real life, multiple labels on ports makes modeling a nightmare (see image below). In MagicDraw, we use different colors - full port has the same color as part, when proxy port is different, but it is not enough. Diagram may be printed in B&W too. What do you think about the idea to change proxy port graphical notation, by adding some special icons or using a dashed line for example? Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: October 9, 2013: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: End of Annotations:===== ted-NM: yes From: Nerijus Jankevicius Subject: proxy and full port notation change request Date: Wed, 9 Oct 2013 13:50:25 +0300 To: "sysml-rtf@omg.org (sysml-rtf@omg.org)" X-Mailer: Apple Mail (2.1085) X-Virus-Scanned: amavisd-new at omg.org After .1 year of using new proxy and full ports, our customers are not happy with using <> and <> keywords/labels for port kind identification. In real life, multiple labels on ports makes modeling a nightmare (see image below). In MagicDraw, we use different colors - full port has the same color as part, when proxy port is different, but it is not enough. Diagram may be printed in B&W too. What do you think about the idea to change proxy port graphical notation, by adding some special icons or using a dashed line for example? PastedGraphic-1.tif X-Trusted-NM: yes Subject: Re: proxy and full port notation change request From: Nerijus Jankevicius Date: Wed, 9 Oct 2013 16:59:02 +0300 Cc: Andreas Korff , "Watson, John" , "Yves.Bernard@airbus.com" , Eldad Palachi , "sysml-rtf@omg.org (sysml-rtf@omg.org)" To: Matthew Hause X-Mailer: Apple Mail (2.1085) X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r99DxA9A022395 Matthew, Absolutely agree, I want symbolic conjugation notation back too. Also, having direction arrows inside port box clashes with showing name and type inside the box. It would be nice to have more graphical notation for the direction - something like SendSignalAction and AcceptEventAction symbols in Activities. Nerijus On Oct 9, 2013, at 4:43 PM, Matthew Hause wrote: > I am always for symbolic notation to indicate type. The change of conjugated ports from the inverse colors (black) to a tilde was almost impossible to see on a diagram causing unhappiness in our customers. We need to be sure that the diagrams speak for themselves. > > -----Original Message----- > From: Andreas Korff [mailto:Andreas.Korff@atego.com] > Sent: Wednesday, October 09, 2013 7:49 AM > To: Watson, John; Yves.Bernard@airbus.com; Eldad Palachi; Nerijus Jankevicius > Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) > Subject: AW: proxy and full port notation change request > > Hi All, > > Atego also supports the idea for a different notation for proxy ports, e.g. indicated with dotted or dashed lines. Especially as the <> stereotype on top of the port name makes it hard to find a suitable spot to place the port name on the diagram. > > Kind regards, > Andreas > > > > Andreas Korff > Product Manager > T: +49 (0)8341 960 960 F: +49 (0)5361 897 6001 M: +49 (0)170 422 844 3 www.Atego.com > > Atego System GmbH, Sitz: Wolfsburg, eingetragen beim Amtsgericht Braunschweig unter HRB 202211, UST-ID-Nr.: DE 210 900 491, Geschäsfü Kevin Lawrence. > > > -----Ursprühe Nachricht----- > Von: Watson, John [mailto:john.watson@lmco.com] > Gesendet: Mittwoch, 9. Oktober 2013 14:22 > An: Yves.Bernard@airbus.com; Eldad Palachi; Nerijus Jankevicius > Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) > Betreff: RE: proxy and full port notation change request > > I see the same issue with our users so I support this idea as well. Dotted line for proxy as suggested and a filled square for full ports with directional arrows included as well for both. > > Diagram real-estate is always at a premium and the textual stereotype notation is not the most efficient means to convey this information. I believe we should maximize the graphical representation as much as practical and minimize textual representation wherever possible. > > John > > > ======================== > John C. Watson > PMES, CE&T System Modeling CoP Lead > LM Qualified Systems Architect > OMG Certified SysML Modeling Professional - Advanced Level Lockheed Martin Mission Systems and Training > 199 Borton Landing Road, > Moorestown, NJ 08057 > Office: 856-722-2783 > > Links To: > CE&T MBSD Integrated Website > System Modeling CoP Homepage > INCOSE MBSE Initiative Wiki > > > -----Original Message----- > From: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] > Sent: Wednesday, October 09, 2013 7:45 AM > To: Eldad Palachi; Nerijus Jankevicius > Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) > Subject: EXTERNAL: RE: proxy and full port notation change request > > I support this too. > > The point is to agree on something... I remember we try to define a specific notation for SysML 1.3 but we finally decided use the keyword. > > Yves > > -----Message d'origine----- > De : Eldad Palachi [mailto:eldad.palachi@il.ibm.com] Envoyé mercredi 9 octobre 2013 13:01 À: Nerijus Jankevicius Cc : sysml-rtf@omg.org (sysml-rtf@omg.org) Objet : Re: proxy and full port notation change request > > I support this idea. > > To me it makes sense to have proxy as dashed or dotted. Full with some fill pattern or heavy solid and UML as just a box with regular solid line (as in UML). > > > > From: Nerijus Jankevicius > To: "sysml-rtf@omg.org (sysml-rtf@omg.org)" , > Date: 09/10/2013 01:54 PM > Subject: proxy and full port notation change request > > > > After .1 year of using new proxy and full ports, our customers are not happy with using <> and <> keywords/labels for port kind identification. > > In real life, multiple labels on ports makes modeling a nightmare (see image below). > > In MagicDraw, we use different colors - full port has the same color as part, when proxy port is different, but it is not enough. Diagram may be printed in B&W too. > What do you think about the idea to change proxy port graphical notation, by adding some special icons or using a dashed line for example? > > [attachment "PastedGraphic-1.tiff" deleted by Eldad Palachi/Haifa/IBM] This mail has originated outside your organization, either from an external partner or the Global Internet. > Keep this in mind if you answer this message. > > > > The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. > If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. > Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. > All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. > > Subject: Re: proxy and full port notation change request X-KeepSent: C6EB6069:E92C7CA9-C2257BFF:003C5F56; type=4; name=$KeepSent To: Nerijus Jankevicius Cc: "sysml-rtf@omg.org (sysml-rtf@omg.org)" X-Mailer: Lotus Notes Release 8.5.3FP5 August 01, 2013 From: Eldad Palachi Date: Wed, 9 Oct 2013 14:01:20 +0300 X-MIMETrack: Serialize by Router on D06ML319/06/M/IBM(Release 8.5.3FP5|July 31, 2013) at 09/10/2013 14:01:08 X-TM-AS-MML: No X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13100911-5024-0000-0000-0000077580DA X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from base64 to 8bit by amethyst.omg.org id r99B1TQ8002820 Content-Transfer-Encoding: 8bit I support this idea. To me it makes sense to have proxy as dashed or dotted. Full with some fill pattern or heavy solid and UML as just a box with regular solid line (as in UML). From: Nerijus Jankevicius To: "sysml-rtf@omg.org (sysml-rtf@omg.org)" , Date: 09/10/2013 01:54 PM Subject: proxy and full port notation change request After .1 year of using new proxy and full ports, our customers are not happy with using <> and <> keywords/labels for port kind identification. In real life, multiple labels on ports makes modeling a nightmare (see image below). In MagicDraw, we use different colors - full port has the same color as part, when proxy port is different, but it is not enough. Diagram may be printed in B&W too. What do you think about the idea to change proxy port graphical notation, by adding some special icons or using a dashed line for example? [attachment "PastedGraphic-1.tiff" deleted by Eldad Palachi/Haifa/IBM] X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on saturn.nomagic.com X-Spam-Level: X-Spam-Status: No, score=-7.0 required=4.1 tests=ALL_TRUSTED,TJ_UML autolearn=disabled version=3.2.5 Date: Wed, 09 Oct 2013 08:09:56 -0600 From: Lonnie VanZandt Reply-To: lvanzandt@nomagic.com Organization: NoMagic, Inc. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 To: Nerijus Jankevicius CC: Matthew Hause , Andreas Korff , "Watson, John" , "Yves.Bernard@airbus.com" , Eldad Palachi , "sysml-rtf@omg.org (sysml-rtf@omg.org)" Subject: Re: proxy and full port notation change request X-Enigmail-Version: 1.5.2 X-Virus-Scanned: amavisd-new at omg.org And "~" and " " lack the nice ying and yang of black and white. Vote +1 for their return. Lonnie VanZandt Chief Architect No Magic, Inc. Mailstop: 700 Central Expressway S, Suite 110, Allen, TX 75013 Office: 637 Witter Gulch Rd, Suite 425, Evergreen, CO 80439 Direct: 303-900-3048 Email: lvanzandt@nomagic.com Skype: lonnie.vanzandt On 10/9/2013 7:59 AM, Nerijus Jankevicius wrote: > Matthew, > > Absolutely agree, I want symbolic conjugation notation back too. > Also, having direction arrows inside port box clashes with showing name and type inside the box. It would be nice to have more graphical notation for the direction - something like SendSignalAction and AcceptEventAction symbols in Activities. > > Nerijus > > On Oct 9, 2013, at 4:43 PM, Matthew Hause wrote: > >> I am always for symbolic notation to indicate type. The change of conjugated ports from the inverse colors (black) to a tilde was almost impossible to see on a diagram causing unhappiness in our customers. We need to be sure that the diagrams speak for themselves. >> >> -----Original Message----- >> From: Andreas Korff [mailto:Andreas.Korff@atego.com] >> Sent: Wednesday, October 09, 2013 7:49 AM >> To: Watson, John; Yves.Bernard@airbus.com; Eldad Palachi; Nerijus Jankevicius >> Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) >> Subject: AW: proxy and full port notation change request >> >> Hi All, >> >> Atego also supports the idea for a different notation for proxy ports, e.g. indicated with dotted or dashed lines. Especially as the <> stereotype on top of the port name makes it hard to find a suitable spot to place the port name on the diagram. >> >> Kind regards, >> Andreas >> >> >> >> Andreas Korff >> Product Manager >> T: +49 (0)8341 960 960 F: +49 (0)5361 897 6001 M: +49 (0)170 422 844 3 www.Atego.com >> >> Atego System GmbH, Sitz: Wolfsburg, eingetragen beim Amtsgericht Braunschweig unter HRB 202211, UST-ID-Nr.: DE 210 900 491, Geschäsfü Kevin Lawrence. >> >> >> -----Ursprühe Nachricht----- >> Von: Watson, John [mailto:john.watson@lmco.com] >> Gesendet: Mittwoch, 9. Oktober 2013 14:22 >> An: Yves.Bernard@airbus.com; Eldad Palachi; Nerijus Jankevicius >> Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) >> Betreff: RE: proxy and full port notation change request >> >> I see the same issue with our users so I support this idea as well. Dotted line for proxy as suggested and a filled square for full ports with directional arrows included as well for both. >> >> Diagram real-estate is always at a premium and the textual stereotype notation is not the most efficient means to convey this information. I believe we should maximize the graphical representation as much as practical and minimize textual representation wherever possible. >> >> John >> >> >> ======================== >> John C. Watson >> PMES, CE&T System Modeling CoP Lead >> LM Qualified Systems Architect >> OMG Certified SysML Modeling Professional - Advanced Level Lockheed Martin Mission Systems and Training >> 199 Borton Landing Road, >> Moorestown, NJ 08057 >> Office: 856-722-2783 >> >> Links To: >> CE&T MBSD Integrated Website >> System Modeling CoP Homepage >> INCOSE MBSE Initiative Wiki >> >> >> -----Original Message----- >> From: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] >> Sent: Wednesday, October 09, 2013 7:45 AM >> To: Eldad Palachi; Nerijus Jankevicius >> Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) >> Subject: EXTERNAL: RE: proxy and full port notation change request >> >> I support this too. >> >> The point is to agree on something... I remember we try to define a specific notation for SysML 1.3 but we finally decided use the keyword. >> >> Yves >> >> -----Message d'origine----- >> De : Eldad Palachi [mailto:eldad.palachi@il.ibm.com] Envoyé mercredi 9 octobre 2013 13:01 À: Nerijus Jankevicius Cc : sysml-rtf@omg.org (sysml-rtf@omg.org) Objet : Re: proxy and full port notation change request >> >> I support this idea. >> >> To me it makes sense to have proxy as dashed or dotted. Full with some fill pattern or heavy solid and UML as just a box with regular solid line (as in UML). >> >> >> >> From: Nerijus Jankevicius >> To: "sysml-rtf@omg.org (sysml-rtf@omg.org)" , >> Date: 09/10/2013 01:54 PM >> Subject: proxy and full port notation change request >> >> >> >> After .1 year of using new proxy and full ports, our customers are not happy with using <> and <> keywords/labels for port kind identification. >> >> In real life, multiple labels on ports makes modeling a nightmare (see image below). >> >> In MagicDraw, we use different colors - full port has the same color as part, when proxy port is different, but it is not enough. Diagram may be printed in B&W too. >> What do you think about the idea to change proxy port graphical notation, by adding some special icons or using a dashed line for example? >> >> [attachment "PastedGraphic-1.tiff" deleted by Eldad Palachi/Haifa/IBM] This mail has originated outside your organization, either from an external partner or the Global Internet. >> Keep this in mind if you answer this message. >> >> >> >> The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. >> If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. >> Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. >> All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. >> >> signature3.asc signature3.asc From: Matthew Hause To: Andreas Korff , "Watson, John" , "Yves.Bernard@airbus.com" , Eldad Palachi , Nerijus Jankevicius CC: "sysml-rtf@omg.org (sysml-rtf@omg.org)" Subject: RE: proxy and full port notation change request Thread-Topic: proxy and full port notation change request Thread-Index: AQHOxN3KSueJtwKKOUS2SkTk+lngKAABUiTwmey1VoCAAAdvgP//mXUQ Date: Wed, 9 Oct 2013 13:43:18 +0000 Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [166.147.64.226] x-esetresult: clean, is OK x-esetid: 350DFF23A501E0716349A2 X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from base64 to 8bit by amethyst.omg.org id r99Dibmt021192 Content-Transfer-Encoding: 8bit I am always for symbolic notation to indicate type. The change of conjugated ports from the inverse colors (black) to a tilde was almost impossible to see on a diagram causing unhappiness in our customers. We need to be sure that the diagrams speak for themselves. -----Original Message----- From: Andreas Korff [mailto:Andreas.Korff@atego.com] Sent: Wednesday, October 09, 2013 7:49 AM To: Watson, John; Yves.Bernard@airbus.com; Eldad Palachi; Nerijus Jankevicius Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) Subject: AW: proxy and full port notation change request Hi All, Atego also supports the idea for a different notation for proxy ports, e.g. indicated with dotted or dashed lines. Especially as the <> stereotype on top of the port name makes it hard to find a suitable spot to place the port name on the diagram. Kind regards, Andreas Andreas Korff Product Manager T: +49 (0)8341 960 960 F: +49 (0)5361 897 6001 M: +49 (0)170 422 844 3 www.Atego.com Atego System GmbH, Sitz: Wolfsburg, eingetragen beim Amtsgericht Braunschweig unter HRB 202211, UST-ID-Nr.: DE 210 900 491, Geschäsfü Kevin Lawrence. -----Ursprühe Nachricht----- Von: Watson, John [mailto:john.watson@lmco.com] Gesendet: Mittwoch, 9. Oktober 2013 14:22 An: Yves.Bernard@airbus.com; Eldad Palachi; Nerijus Jankevicius Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) Betreff: RE: proxy and full port notation change request I see the same issue with our users so I support this idea as well. Dotted line for proxy as suggested and a filled square for full ports with directional arrows included as well for both. Diagram real-estate is always at a premium and the textual stereotype notation is not the most efficient means to convey this information. I believe we should maximize the graphical representation as much as practical and minimize textual representation wherever possible. John ======================== John C. Watson PMES, CE&T System Modeling CoP Lead LM Qualified Systems Architect OMG Certified SysML Modeling Professional - Advanced Level Lockheed Martin Mission Systems and Training 199 Borton Landing Road, Moorestown, NJ 08057 Office: 856-722-2783 Links To: CE&T MBSD Integrated Website System Modeling CoP Homepage INCOSE MBSE Initiative Wiki -----Original Message----- From: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] Sent: Wednesday, October 09, 2013 7:45 AM To: Eldad Palachi; Nerijus Jankevicius Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) Subject: EXTERNAL: RE: proxy and full port notation change request I support this too. The point is to agree on something... I remember we try to define a specific notation for SysML 1.3 but we finally decided use the keyword. Yves -----Message d'origine----- De : Eldad Palachi [mailto:eldad.palachi@il.ibm.com] Envoyé mercredi 9 octobre 2013 13:01 À: Nerijus Jankevicius Cc : sysml-rtf@omg.org (sysml-rtf@omg.org) Objet : Re: proxy and full port notation change request I support this idea. To me it makes sense to have proxy as dashed or dotted. Full with some fill pattern or heavy solid and UML as just a box with regular solid line (as in UML). From: Nerijus Jankevicius To: "sysml-rtf@omg.org (sysml-rtf@omg.org)" , Date: 09/10/2013 01:54 PM Subject: proxy and full port notation change request After .1 year of using new proxy and full ports, our customers are not happy with using <> and <> keywords/labels for port kind identification. In real life, multiple labels on ports makes modeling a nightmare (see image below). In MagicDraw, we use different colors - full port has the same color as part, when proxy port is different, but it is not enough. Diagram may be printed in B&W too. What do you think about the idea to change proxy port graphical notation, by adding some special icons or using a dashed line for example? [attachment "PastedGraphic-1.tiff" deleted by Eldad Palachi/Haifa/IBM] This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: Andreas Korff To: "Watson, John" , "Yves.Bernard@airbus.com" , Eldad Palachi , Nerijus Jankevicius CC: "sysml-rtf@omg.org (sysml-rtf@omg.org)" Subject: AW: proxy and full port notation change request Thread-Topic: proxy and full port notation change request Thread-Index: AQHOxN3bN6PJOrt00UKl7zoW4xl/hAABUiTwmewedoCAACapYA== Date: Wed, 9 Oct 2013 12:48:33 +0000 Accept-Language: en-GB, de-DE, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [79.222.151.121] x-esetresult: clean, is OK x-esetid: EC46D23D88543435BA028F X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from base64 to 8bit by amethyst.omg.org id r99CmiDk014925 Content-Transfer-Encoding: 8bit Hi All, Atego also supports the idea for a different notation for proxy ports, e.g. indicated with dotted or dashed lines. Especially as the <> stereotype on top of the port name makes it hard to find a suitable spot to place the port name on the diagram. Kind regards, Andreas Andreas Korff Product Manager T: +49 (0)8341 960 960 F: +49 (0)5361 897 6001 M: +49 (0)170 422 844 3 www.Atego.com Atego System GmbH, Sitz: Wolfsburg, eingetragen beim Amtsgericht Braunschweig unter HRB 202211, UST-ID-Nr.: DE 210 900 491, Geschäsfü Kevin Lawrence. -----Ursprühe Nachricht----- Von: Watson, John [mailto:john.watson@lmco.com] Gesendet: Mittwoch, 9. Oktober 2013 14:22 An: Yves.Bernard@airbus.com; Eldad Palachi; Nerijus Jankevicius Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) Betreff: RE: proxy and full port notation change request I see the same issue with our users so I support this idea as well. Dotted line for proxy as suggested and a filled square for full ports with directional arrows included as well for both. Diagram real-estate is always at a premium and the textual stereotype notation is not the most efficient means to convey this information. I believe we should maximize the graphical representation as much as practical and minimize textual representation wherever possible. John ======================== John C. Watson PMES, CE&T System Modeling CoP Lead LM Qualified Systems Architect OMG Certified SysML Modeling Professional - Advanced Level Lockheed Martin Mission Systems and Training 199 Borton Landing Road, Moorestown, NJ 08057 Office: 856-722-2783 Links To: CE&T MBSD Integrated Website System Modeling CoP Homepage INCOSE MBSE Initiative Wiki -----Original Message----- From: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] Sent: Wednesday, October 09, 2013 7:45 AM To: Eldad Palachi; Nerijus Jankevicius Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) Subject: EXTERNAL: RE: proxy and full port notation change request I support this too. The point is to agree on something... I remember we try to define a specific notation for SysML 1.3 but we finally decided use the keyword. Yves -----Message d'origine----- De : Eldad Palachi [mailto:eldad.palachi@il.ibm.com] Envoyé mercredi 9 octobre 2013 13:01 À: Nerijus Jankevicius Cc : sysml-rtf@omg.org (sysml-rtf@omg.org) Objet : Re: proxy and full port notation change request I support this idea. To me it makes sense to have proxy as dashed or dotted. Full with some fill pattern or heavy solid and UML as just a box with regular solid line (as in UML). From: Nerijus Jankevicius To: "sysml-rtf@omg.org (sysml-rtf@omg.org)" , Date: 09/10/2013 01:54 PM Subject: proxy and full port notation change request After .1 year of using new proxy and full ports, our customers are not happy with using <> and <> keywords/labels for port kind identification. In real life, multiple labels on ports makes modeling a nightmare (see image below). In MagicDraw, we use different colors - full port has the same color as part, when proxy port is different, but it is not enough. Diagram may be printed in B&W too. What do you think about the idea to change proxy port graphical notation, by adding some special icons or using a dashed line for example? [attachment "PastedGraphic-1.tiff" deleted by Eldad Palachi/Haifa/IBM] This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: BAGNATO Alessandra To: "BERNARD, Yves" , Eldad Palachi , Nerijus Jankevicius CC: "sysml-rtf@omg.org (sysml-rtf@omg.org)" Subject: RE: proxy and full port notation change request Thread-Topic: proxy and full port notation change request Thread-Index: AQHOxN5iKUYzzOmI/kW/a9XRirdlSwABUiTwmew2TVA= Date: Wed, 9 Oct 2013 11:51:03 +0000 Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [82.239.224.199] x-forefront-prvs: 0994F5E0C5 x-forefront-antispam-report: SFV:NSPM;SFS:(76104003)(189002)(199002)(53754006)(13464003)(479174003)(377454003)(365934002)(55784002)(74316001)(31966008)(74876001)(81686001)(69226001)(59766001)(47446002)(85306002)(74662001)(74482001)(74502001)(33646001)(47976001)(74706001)(81816001)(47736001)(49866001)(50986001)(74366001)(4396001)(83322001)(19580405001)(19580395003)(80976001)(65816001)(56776001)(54316002)(83072001)(66066001)(76482001)(80022001)(53806001)(54356001)(77096001)(56816003)(81542001)(76786001)(81342001)(51856001)(76796001)(63696002)(76576001)(79102001)(77982001)(46102001)(24736002);DIR:OUT;SFP:;SCL:1;SRVR:AMSPR07MB193;H:AMSPR07MB193.eurprd07.prod.outlook.com;CLIP:82.239.224.199;FPR:;RD:InfoNoRecords;MX:1;A:1;LANG:en; X-OriginatorOrg: softeam.fr X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from base64 to 8bit by amethyst.omg.org id r99BpGO1008476 Content-Transfer-Encoding: 8bit Hi All, Softeam support this idea too. Best Regards, Alessandra -----Original Message----- From: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] Sent: mercredi 9 octobre 2013 13:45 To: Eldad Palachi; Nerijus Jankevicius Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) Subject: RE: proxy and full port notation change request I support this too. The point is to agree on something... I remember we try to define a specific notation for SysML 1.3 but we finally decided use the keyword. Yves -----Message d'origine----- De : Eldad Palachi [mailto:eldad.palachi@il.ibm.com] Envoyé mercredi 9 octobre 2013 13:01 À: Nerijus Jankevicius Cc : sysml-rtf@omg.org (sysml-rtf@omg.org) Objet : Re: proxy and full port notation change request I support this idea. To me it makes sense to have proxy as dashed or dotted. Full with some fill pattern or heavy solid and UML as just a box with regular solid line (as in UML). From: Nerijus Jankevicius To: "sysml-rtf@omg.org (sysml-rtf@omg.org)" , Date: 09/10/2013 01:54 PM Subject: proxy and full port notation change request After .1 year of using new proxy and full ports, our customers are not happy with using <> and <> keywords/labels for port kind identification. In real life, multiple labels on ports makes modeling a nightmare (see image below). In MagicDraw, we use different colors - full port has the same color as part, when proxy port is different, but it is not enough. Diagram may be printed in B&W too. What do you think about the idea to change proxy port graphical notation, by adding some special icons or using a dashed line for example? [attachment "PastedGraphic-1.tiff" deleted by Eldad Palachi/Haifa/IBM] This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: "BERNARD, Yves" To: Eldad Palachi , Nerijus Jankevicius CC: "sysml-rtf@omg.org (sysml-rtf@omg.org)" Date: Wed, 9 Oct 2013 13:44:45 +0200 Subject: RE: proxy and full port notation change request Thread-Topic: proxy and full port notation change request Thread-Index: Ac7E3uqdI8xYowJ5RziEhdTnnZKsFgABUiTw Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from base64 to 8bit by amethyst.omg.org id r99Biscj008267 Content-Transfer-Encoding: 8bit I support this too. The point is to agree on something... I remember we try to define a specific notation for SysML 1.3 but we finally decided use the keyword. Yves -----Message d'origine----- De : Eldad Palachi [mailto:eldad.palachi@il.ibm.com] Envoyé mercredi 9 octobre 2013 13:01 À: Nerijus Jankevicius Cc : sysml-rtf@omg.org (sysml-rtf@omg.org) Objet : Re: proxy and full port notation change request I support this idea. To me it makes sense to have proxy as dashed or dotted. Full with some fill pattern or heavy solid and UML as just a box with regular solid line (as in UML). From: Nerijus Jankevicius To: "sysml-rtf@omg.org (sysml-rtf@omg.org)" , Date: 09/10/2013 01:54 PM Subject: proxy and full port notation change request After .1 year of using new proxy and full ports, our customers are not happy with using <> and <> keywords/labels for port kind identification. In real life, multiple labels on ports makes modeling a nightmare (see image below). In MagicDraw, we use different colors - full port has the same color as part, when proxy port is different, but it is not enough. Diagram may be printed in B&W too. What do you think about the idea to change proxy port graphical notation, by adding some special icons or using a dashed line for example? [attachment "PastedGraphic-1.tiff" deleted by Eldad Palachi/Haifa/IBM] This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: "Watson, John" To: "Yves.Bernard@airbus.com" , Eldad Palachi , Nerijus Jankevicius CC: "sysml-rtf@omg.org (sysml-rtf@omg.org)" Subject: RE: proxy and full port notation change request Thread-Topic: proxy and full port notation change request Thread-Index: AQHOxOT7UNzm1ZhJHkCp5hn8YLB+XpnsR2UQ Date: Wed, 9 Oct 2013 12:21:57 +0000 Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [158.186.156.93] X-LM-Outbound: External 158.186.149.28 cntry=us g=80423114722518d8ca527df2a996b013 q=r99CMeZd024980 m=8 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794,1.0.431,0.0.0000 definitions=2013-10-09_03:2013-10-09,2013-10-09,1970-01-01 signatures=0 X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from base64 to 8bit by amethyst.omg.org id r99CN0t3011704 Content-Transfer-Encoding: 8bit I see the same issue with our users so I support this idea as well. Dotted line for proxy as suggested and a filled square for full ports with directional arrows included as well for both. Diagram real-estate is always at a premium and the textual stereotype notation is not the most efficient means to convey this information. I believe we should maximize the graphical representation as much as practical and minimize textual representation wherever possible. John ======================== John C. Watson PMES, CE&T System Modeling CoP Lead LM Qualified Systems Architect OMG Certified SysML Modeling Professional - Advanced Level Lockheed Martin Mission Systems and Training 199 Borton Landing Road, Moorestown, NJ 08057 Office: 856-722-2783 Links To: CE&T MBSD Integrated Website System Modeling CoP Homepage INCOSE MBSE Initiative Wiki -----Original Message----- From: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] Sent: Wednesday, October 09, 2013 7:45 AM To: Eldad Palachi; Nerijus Jankevicius Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) Subject: EXTERNAL: RE: proxy and full port notation change request I support this too. The point is to agree on something... I remember we try to define a specific notation for SysML 1.3 but we finally decided use the keyword. Yves -----Message d'origine----- De : Eldad Palachi [mailto:eldad.palachi@il.ibm.com] Envoyé mercredi 9 octobre 2013 13:01 À: Nerijus Jankevicius Cc : sysml-rtf@omg.org (sysml-rtf@omg.org) Objet : Re: proxy and full port notation change request I support this idea. To me it makes sense to have proxy as dashed or dotted. Full with some fill pattern or heavy solid and UML as just a box with regular solid line (as in UML). From: Nerijus Jankevicius To: "sysml-rtf@omg.org (sysml-rtf@omg.org)" , Date: 09/10/2013 01:54 PM Subject: proxy and full port notation change request After .1 year of using new proxy and full ports, our customers are not happy with using <> and <> keywords/labels for port kind identification. In real life, multiple labels on ports makes modeling a nightmare (see image below). In MagicDraw, we use different colors - full port has the same color as part, when proxy port is different, but it is not enough. Diagram may be printed in B&W too. What do you think about the idea to change proxy port graphical notation, by adding some special icons or using a dashed line for example? [attachment "PastedGraphic-1.tiff" deleted by Eldad Palachi/Haifa/IBM] This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: Tim Weilkiens To: "john.watson@lmco.com" , "Yves.Bernard@airbus.com" , "eldad.palachi@il.ibm.com" , "nerijus@nomagic.com" , "Andreas.Korff@atego.com" CC: "sysml-rtf@omg.org" Subject: AW: proxy and full port notation change request Thread-Topic: proxy and full port notation change request Thread-Index: Ac7E7zNbAokkndE4pEyiHAhGiLYeTQ== Date: Wed, 9 Oct 2013 12:58:07 +0000 Accept-Language: de-DE, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: X-XWALL-BCKS: auto X-Virus-Scanned: amavisd-new at omg.org I fully support the proposal and like the idea to use dotted lines for proxy ports. Tim -----Original Message----- From: Andreas Korff [Andreas.Korff@atego.com] Received: Mittwoch, 09 Okt. 2013, 14:50 To: Watson, John [john.watson@lmco.com]; Yves.Bernard@airbus.com [Yves.Bernard@airbus.com]; Eldad Palachi [eldad.palachi@il.ibm.com]; Nerijus Jankevicius [nerijus@nomagic.com] CC: sysml-rtf@omg.org (sysml-rtf@omg.org) [sysml-rtf@omg.org] Subject: AW: proxy and full port notation change request Hi All, Atego also supports the idea for a different notation for proxy ports, e.g. indicated with dotted or dashed lines. Especially as the <> stereotype on top of the port name makes it hard to find a suitable spot to place the port name on the diagram. Kind regards, Andreas Andreas Korff Product Manager T: +49 (0)8341 960 960 F: +49 (0)5361 897 6001 M: +49 (0)170 422 844 3 www.Atego.com Atego System GmbH, Sitz: Wolfsburg, eingetragen beim Amtsgericht Braunschweig unter HRB 202211, UST-ID-Nr.: DE 210 900 491, Geschäsfü Kevin Lawrence. -----Ursprühe Nachricht----- Von: Watson, John [mailto:john.watson@lmco.com] Gesendet: Mittwoch, 9. Oktober 2013 14:22 An: Yves.Bernard@airbus.com; Eldad Palachi; Nerijus Jankevicius Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) Betreff: RE: proxy and full port notation change request I see the same issue with our users so I support this idea as well. Dotted line for proxy as suggested and a filled square for full ports with directional arrows included as well for both. Diagram real-estate is always at a premium and the textual stereotype notation is not the most efficient means to convey this information. I believe we should maximize the graphical representation as much as practical and minimize textual representation wherever possible. John ======================== John C. Watson PMES, CE&T System Modeling CoP Lead LM Qualified Systems Architect OMG Certified SysML Modeling Professional - Advanced Level Lockheed Martin Mission Systems and Training 199 Borton Landing Road, Moorestown, NJ 08057 Office: 856-722-2783 Links To: CE&T MBSD Integrated Website System Modeling CoP Homepage INCOSE MBSE Initiative Wiki -----Original Message----- From: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] Sent: Wednesday, October 09, 2013 7:45 AM To: Eldad Palachi; Nerijus Jankevicius Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) Subject: EXTERNAL: RE: proxy and full port notation change request I support this too. The point is to agree on something... I remember we try to define a specific notation for SysML 1.3 but we finally decided use the keyword. Yves -----Message d'origine----- De : Eldad Palachi [mailto:eldad.palachi@il.ibm.com] Envoyé mercredi 9 octobre 2013 13:01 À: Nerijus Jankevicius Cc : sysml-rtf@omg.org (sysml-rtf@omg.org) Objet : Re: proxy and full port notation change request I support this idea. To me it makes sense to have proxy as dashed or dotted. Full with some fill pattern or heavy solid and UML as just a box with regular solid line (as in UML). From: Nerijus Jankevicius To: "sysml-rtf@omg.org (sysml-rtf@omg.org)" , Date: 09/10/2013 01:54 PM Subject: proxy and full port notation change request After .1 year of using new proxy and full ports, our customers are not happy with using <> and <> keywords/labels for port kind identification. In real life, multiple labels on ports makes modeling a nightmare (see image below). In MagicDraw, we use different colors - full port has the same color as part, when proxy port is different, but it is not enough. Diagram may be printed in B&W too. What do you think about the idea to change proxy port graphical notation, by adding some special icons or using a dashed line for example? [attachment "PastedGraphic-1.tiff" deleted by Eldad Palachi/Haifa/IBM] This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. X-Trusted-NM: yes Subject: Re: proxy and full port notation change request From: Nerijus Jankevicius Date: Wed, 9 Oct 2013 16:59:02 +0300 Cc: Andreas Korff , "Watson, John" , "Yves.Bernard@airbus.com" , Eldad Palachi , "sysml-rtf@omg.org (sysml-rtf@omg.org)" To: Matthew Hause X-Mailer: Apple Mail (2.1085) X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r99DxA9A022395 Matthew, Absolutely agree, I want symbolic conjugation notation back too. Also, having direction arrows inside port box clashes with showing name and type inside the box. It would be nice to have more graphical notation for the direction - something like SendSignalAction and AcceptEventAction symbols in Activities. Nerijus On Oct 9, 2013, at 4:43 PM, Matthew Hause wrote: > I am always for symbolic notation to indicate type. The change of conjugated ports from the inverse colors (black) to a tilde was almost impossible to see on a diagram causing unhappiness in our customers. We need to be sure that the diagrams speak for themselves. > > -----Original Message----- > From: Andreas Korff [mailto:Andreas.Korff@atego.com] > Sent: Wednesday, October 09, 2013 7:49 AM > To: Watson, John; Yves.Bernard@airbus.com; Eldad Palachi; Nerijus Jankevicius > Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) > Subject: AW: proxy and full port notation change request > > Hi All, > > Atego also supports the idea for a different notation for proxy ports, e.g. indicated with dotted or dashed lines. Especially as the <> stereotype on top of the port name makes it hard to find a suitable spot to place the port name on the diagram. > > Kind regards, > Andreas > > > > Andreas Korff > Product Manager > T: +49 (0)8341 960 960 F: +49 (0)5361 897 6001 M: +49 (0)170 422 844 3 www.Atego.com > > Atego System GmbH, Sitz: Wolfsburg, eingetragen beim Amtsgericht Braunschweig unter HRB 202211, UST-ID-Nr.: DE 210 900 491, Geschäsfü Kevin Lawrence. > > > -----Ursprühe Nachricht----- > Von: Watson, John [mailto:john.watson@lmco.com] > Gesendet: Mittwoch, 9. Oktober 2013 14:22 > An: Yves.Bernard@airbus.com; Eldad Palachi; Nerijus Jankevicius > Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) > Betreff: RE: proxy and full port notation change request > > I see the same issue with our users so I support this idea as well. Dotted line for proxy as suggested and a filled square for full ports with directional arrows included as well for both. > > Diagram real-estate is always at a premium and the textual stereotype notation is not the most efficient means to convey this information. I believe we should maximize the graphical representation as much as practical and minimize textual representation wherever possible. > > John > > > ======================== > John C. Watson > PMES, CE&T System Modeling CoP Lead > LM Qualified Systems Architect > OMG Certified SysML Modeling Professional - Advanced Level Lockheed Martin Mission Systems and Training > 199 Borton Landing Road, > Moorestown, NJ 08057 > Office: 856-722-2783 > > Links To: > CE&T MBSD Integrated Website > System Modeling CoP Homepage > INCOSE MBSE Initiative Wiki > > > -----Original Message----- > From: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] > Sent: Wednesday, October 09, 2013 7:45 AM > To: Eldad Palachi; Nerijus Jankevicius > Cc: sysml-rtf@omg.org (sysml-rtf@omg.org) > Subject: EXTERNAL: RE: proxy and full port notation change request > > I support this too. > > The point is to agree on something... I remember we try to define a specific notation for SysML 1.3 but we finally decided use the keyword. > > Yves > > -----Message d'origine----- > De : Eldad Palachi [mailto:eldad.palachi@il.ibm.com] Envoyé mercredi 9 octobre 2013 13:01 À: Nerijus Jankevicius Cc : sysml-rtf@omg.org (sysml-rtf@omg.org) Objet : Re: proxy and full port notation change request > > I support this idea. > > To me it makes sense to have proxy as dashed or dotted. Full with some fill pattern or heavy solid and UML as just a box with regular solid line (as in UML). > > > > From: Nerijus Jankevicius > To: "sysml-rtf@omg.org (sysml-rtf@omg.org)" , > Date: 09/10/2013 01:54 PM > Subject: proxy and full port notation change request > > > > After .1 year of using new proxy and full ports, our customers are not happy with using <> and <> keywords/labels for port kind identification. > > In real life, multiple labels on ports makes modeling a nightmare (see image below). > > In MagicDraw, we use different colors - full port has the same color as part, when proxy port is different, but it is not enough. Diagram may be printed in B&W too. > What do you think about the idea to change proxy port graphical notation, by adding some special icons or using a dashed line for example? > > [attachment "PastedGraphic-1.tiff" deleted by Eldad Palachi/Haifa/IBM] This mail has originated outside your organization, either from an external partner or the Global Internet. > Keep this in mind if you answer this message. > > > > The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. > If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. > Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. > All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. > > X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=kdqfdK2o5PqfptaX9fc+aCgdHw/iIHfvIRsdt1YTseA=; b=Y6vfb0ZLztNu5KIBOcEa0N32PS+uAcT6ayNwHVJuUAiRvPKHrkbMgVyJqyDGwvmWzr OiW94PDpCtRGunYP08mnOwulU6uJpYyCNVjnlvxcxUh+QqXuKVtwChswY5k2jomwraWX qjGtpevTV/gmV4R6Hp/dAI9rxde3WQTYg5w0dsY+RTQoXnQLyGMgygb7DvWH9AsN1DaQ 4S7Tziu4XPBFgxju+Q3KN+6MzNl7DoSZrdYfQVh3dqUadVkE/lNdjwqwgecn1+CzTbdF mQL9JG1oBPbHN5gumiOpeetaEef6a3+98dpgrRXDGIJ37idgWLDtRRuWTJutsj1oxX1q AOUw== X-Gm-Message-State: ALoCoQm8q1NtqXoL9k3ZgfTVBr+yiCEz+5bEuV7GAf5VAwb64WGSfXjwvh1DEtJv8WVxbisGoUu9 X-Received: by 10.224.38.135 with SMTP id b7mr11780460qae.10.1381330161700; Wed, 09 Oct 2013 07:49:21 -0700 (PDT) Date: Wed, 9 Oct 2013 10:49:21 -0400 Subject: Re: proxy and full port notation change request From: Manas Bajaj To: Nerijus Jankevicius Cc: "BERNARD, Yves" , Juergen Boldt , Matthew Hause , Andreas Korff , "Watson, John" , Eldad Palachi , "sysml-rtf@omg.org (sysml-rtf@omg.org)" X-Virus-Scanned: amavisd-new at omg.org +1 for dashed boundary for proxy ports and normal boundary for full ports (Nerijus - thanks for bringing that up) +1 for fill / no-fill notation for conjugate ports (Matthew - thanks for bringing that up) Very good to see the community easily agree on something ;). It seems we all support easy, clean, visual communication. Manas On Wed, Oct 9, 2013 at 10:39 AM, Nerijus Jankevicius wrote: yes, waiting for Juergen... On Oct 9, 2013, at 5:26 PM, BERNARD, Yves wrote: Would you fill an issue so that we can propose a resolution? Thanks, Yves -- Manas Bajaj, PhD Chief Systems Officer InterCAX LLC 75 5th Street NW, Suite 312 Atlanta GA 30308 USA voice: +1-404-592-6897 (ext 101) email: manas.bajaj@intercax.com web: www.intercax.com twitter: www.twitter.com/InterCAX X-Trusted-NM: yes Subject: Re: proxy and full port notation change request From: Nerijus Jankevicius Date: Wed, 9 Oct 2013 18:01:12 +0300 Cc: "BERNARD, Yves" , Juergen Boldt , Matthew Hause , Andreas Korff , "Watson, John" , Eldad Palachi , "sysml-rtf@omg.org (sysml-rtf@omg.org)" To: Manas Bajaj X-Mailer: Apple Mail (2.1085) X-Virus-Scanned: amavisd-new at omg.org Thanks, Manas. The only issue with dashed line could be, that it is used for "non-composite" properties in IBD, but that never was used on ports, as ports are always composite. Nerijus On Oct 9, 2013, at 5:49 PM, Manas Bajaj wrote: +1 for dashed boundary for proxy ports and normal boundary for full ports (Nerijus - thanks for bringing that up) +1 for fill / no-fill notation for conjugate ports (Matthew - thanks for bringing that up) Very good to see the community easily agree on something ;). It seems we all support easy, clean, visual communication. Manas On Wed, Oct 9, 2013 at 10:39 AM, Nerijus Jankevicius wrote: yes, waiting for Juergen... On Oct 9, 2013, at 5:26 PM, BERNARD, Yves wrote: Would you fill an issue so that we can propose a resolution? Thanks, Yves -- Manas Bajaj, PhD Chief Systems Officer InterCAX LLC 75 5th Street NW, Suite 312 Atlanta GA 30308 USA voice: +1-404-592-6897 (ext 101) email: manas.bajaj@intercax.com web: www.intercax.com twitter: www.twitter.com/InterCAX Subject: Re: proxy and full port notation change request X-KeepSent: 98AF80ED:C11DD714-C2257BFF:00528BEA; type=4; name=$KeepSent To: Manas Bajaj Cc: Andreas Korff , "Watson, John" , Juergen Boldt , Matthew Hause , Nerijus Jankevicius , "sysml-rtf@omg.org (sysml-rtf@omg.org)" , "BERNARD, Yves" X-Mailer: Lotus Notes Release 8.5.3FP5 August 01, 2013 From: Eldad Palachi Date: Wed, 9 Oct 2013 18:04:04 +0300 X-MIMETrack: Serialize by Router on D06ML319/06/M/IBM(Release 8.5.3FP5|July 31, 2013) at 09/10/2013 18:03:52 X-TM-AS-MML: No X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13100915-5024-0000-0000-0000077669AB X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r99F4Dgk002842 As I wrote before - I support this too. Two small comments: 1. Need to make sure that if full port is different than uml port without changing the notation for uml port. 2. Recommend we separate fill/no fill of conjugated ports to a separate issue just in case people have issues with this. In the past we had that and I remember we decided to change it so there is a good chance this will not be accpted. Eldad From: Manas Bajaj To: Nerijus Jankevicius , Cc: "BERNARD, Yves" , Juergen Boldt , Matthew Hause , Andreas Korff , "Watson, John" , Eldad Palachi/Haifa/IBM@IBMIL, "sysml-rtf@omg.org (sysml-rtf@omg.org)" Date: 09/10/2013 05:49 PM Subject: Re: proxy and full port notation change request +1 for dashed boundary for proxy ports and normal boundary for full ports (Nerijus - thanks for bringing that up) +1 for fill / no-fill notation for conjugate ports (Matthew - thanks for bringing that up) Very good to see the community easily agree on something ;). It seems we all support easy, clean, visual communication. Manas On Wed, Oct 9, 2013 at 10:39 AM, Nerijus Jankevicius wrote: yes, waiting for Juergen... On Oct 9, 2013, at 5:26 PM, BERNARD, Yves wrote: Would you fill an issue so that we can propose a resolution? Thanks, Yves -- Manas Bajaj, PhD Chief Systems Officer InterCAX LLC 75 5th Street NW, Suite 312 Atlanta GA 30308 USA voice: +1-404-592-6897 (ext 101) email: manas.bajaj@intercax.com web: www.intercax.com twitter: www.twitter.com/InterCAX X-Trusted-NM: yes Subject: Re: proxy and full port notation change request From: Nerijus Jankevicius Date: Wed, 9 Oct 2013 18:13:04 +0300 Cc: Manas Bajaj , Andreas Korff , "Watson, John" , Juergen Boldt , Matthew Hause , "sysml-rtf@omg.org (sysml-rtf@omg.org)" , "BERNARD, Yves" To: Eldad Palachi X-Mailer: Apple Mail (2.1085) X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r99FD8r5005270 Eldad, When "isConjugated" was moved to UML metamodel, UML introduces "~" notation for that. SysML removed "isConjugated" together with notation. I would suggest to allow both - pre SysML 1.3 AND UML notation for conjugated ports. Most tools had "fill/no fill" notation before, so it can be restored easily, while also supporting UML style. Nerijus On Oct 9, 2013, at 6:04 PM, Eldad Palachi wrote: > As I wrote before - I support this too. > > Two small comments: > > 1. Need to make sure that if full port is different than uml port without > changing the notation for uml port. > 2. Recommend we separate fill/no fill of conjugated ports to a separate > issue just in case people have issues with this. In the past we had that > and I remember we decided to change it so there is a good chance this will > not be accpted. > > Eldad > > > > From: Manas Bajaj > To: Nerijus Jankevicius , > Cc: "BERNARD, Yves" , Juergen Boldt > , Matthew Hause , > Andreas Korff , "Watson, John" > , Eldad Palachi/Haifa/IBM@IBMIL, > "sysml-rtf@omg.org (sysml-rtf@omg.org)" > Date: 09/10/2013 05:49 PM > Subject: Re: proxy and full port notation change request > > > > +1 for dashed boundary for proxy ports and normal boundary for full ports > (Nerijus - thanks for bringing that up) > +1 for fill / no-fill notation for conjugate ports (Matthew - thanks for > bringing that up) > > Very good to see the community easily agree on something ;). It seems we > all support easy, clean, visual communication. > > Manas > > > On Wed, Oct 9, 2013 at 10:39 AM, Nerijus Jankevicius > wrote: > yes, waiting for Juergen... > > > On Oct 9, 2013, at 5:26 PM, BERNARD, Yves wrote: > > Would you fill an issue so that we can propose a resolution? > > Thanks, > > Yves > > > > > -- > Manas Bajaj, PhD > Chief Systems Officer > InterCAX LLC > 75 5th Street NW, Suite 312 > Atlanta GA 30308 USA > voice: +1-404-592-6897 (ext 101) > email: manas.bajaj@intercax.com > web: www.intercax.com > twitter: www.twitter.com/InterCAX > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1381335847; bh=q5R5F+rHJ0yC10nehcl5PahNrVgU6QEy57ZLIUcSIKg=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language; b=i2qjHUF1TXIb7Y200DN2kpvih+eb5OD89kBY0ioVx6KCigzJdIizlmlme6kw30E+npS5SIU1Vpsw+qqgOBPXMYj21//g6HiDTBQYH0NDNrRIerwQETSdwtEfRh+Ygl9LQ5p1zh8K+QG/ZBvxjjXOMy0ci73JLYEjWyTbr2OdThg= X-Yahoo-Newman-Id: 570929.51683.bm@smtp204.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: ti_NZ2oVM1ln2G5tIGlulmNexLcUeW0F7lF4ocatVhcfXsS UyoFJjAj66itYn1jTu2wD_RcryYy8Sa_w6c_njKXkVCt_df20nsNPesadyBL BtIfFxjzLbGEisNNNjLU12c5KvkOjhfDNmpudUuvfsKMWi.DrM9gIGhpevVj OUvs26qnHETkxLQgHa49ulMaN._Ww0N6QXXijBErqD0TFRxU9hyIY1GO6fgB xyF7Qvp9U5CoMVy5FWtxioti4rL5cJ8gyy1SfjeRXDgRAVjnUfayOE3VbiKZ ZkAhtb3_iFDqCDZCP1fKr3tuf7Z0EA6RexJDl4ge5BqrGUgxKRijqHOAtTOH 03yQAQwGUIO.pOmqxjcq7fmvV23N5UjDsYMfQP6biNauDtstIz9JMfshkw1P bOjIU20yb9BeYy0fpwzKPifMMM3jUitL6ntOvtyY4oHmdYqXLWdL58cnnVfR hlekz91fP0Nsti2lAULGu8FXOeGvFGNaop9ezczbx5E97ZCai07Tif9Wc_gA d27E5EQxLS_.ZhUJcQjK28SuiWMoRwjZy9t4ryRzB_AZlTmoBN11pI6DxsEO 8j9vuiEwF7hUL0BHkH00SIrt2ljsrrPnNiPhO.1cPxsl7TubVsp1aVlubJr6 opMm2CVIbI1G3z6h2PWu2mkoTrTaDTyO.I2YRNy9deraO.0mi2DNWLw-- X-Yahoo-SMTP: BHehp.2swBCs4PqecFo6LCqjUcnFjw4- X-Rocket-Received: from mjchonolesHP (mjchonoles@71.225.92.207 with ) by smtp204.mail.bf1.yahoo.com with SMTP; 09 Oct 2013 09:24:07 -0700 PDT From: "Michael Chonoles" To: "'Eldad Palachi'" , "'Manas Bajaj'" Cc: "'Andreas Korff'" , "'Watson, John'" , "'Juergen Boldt'" , "'Matthew Hause'" , "'Nerijus Jankevicius'" , , "'BERNARD, Yves'" Subject: RE: proxy and full port notation change request Date: Wed, 9 Oct 2013 12:24:04 -0400 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQF13uKsH5G4Zii14G52mg0BG2fRdAF5KXSZAZv5jcIA7S1V/gJrOqDMAUXf0+0BgDU7AQF5QiitAf963S0BzHObRQKCbkVymhZ9rcA= X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r99GOBFK024196 I would suggest that we don't use dotted/dashed lines. This choice would doom us to additional problems every time diagrams are printed or cut/paste from a modeling tool to an office-like tool (including Frame, PDF, etc.), as the dot/dashes often look like a solid line, and occasionally a solid line will look like it is dashed. Hollow vs Filled: This might work, though when the ports are small any text in a solid port would be difficult to read. It also has the disadvantage of colliding with the previous notation for conjugate (which I liked) Placement: I would generally prefer to see placement being part of the solution, e.g., on the block's border vs overlapping the box's border. Shape: If placement doesn't work, perhaps we can have slightly modified shapes. Perhaps a proxy port should have one rounded/ovalish side. BTW, does SysML support the behavioral port notation? Michael -----Original Message----- From: Eldad Palachi [mailto:eldad.palachi@il.ibm.com] Sent: Wednesday, October 09, 2013 11:04 AM To: Manas Bajaj Cc: Andreas Korff; Watson, John; Juergen Boldt; Matthew Hause; Nerijus Jankevicius; sysml-rtf@omg.org (sysml-rtf@omg.org); BERNARD, Yves Subject: Re: proxy and full port notation change request As I wrote before - I support this too. Two small comments: 1. Need to make sure that if full port is different than uml port without changing the notation for uml port. 2. Recommend we separate fill/no fill of conjugated ports to a separate issue just in case people have issues with this. In the past we had that and I remember we decided to change it so there is a good chance this will not be accpted. Eldad From: Manas Bajaj To: Nerijus Jankevicius , Cc: "BERNARD, Yves" , Juergen Boldt , Matthew Hause , Andreas Korff , "Watson, John" , Eldad Palachi/Haifa/IBM@IBMIL, "sysml-rtf@omg.org (sysml-rtf@omg.org)" Date: 09/10/2013 05:49 PM Subject: Re: proxy and full port notation change request +1 for dashed boundary for proxy ports and normal boundary for full +ports (Nerijus - thanks for bringing that up) +1 for fill / no-fill notation for conjugate ports (Matthew - thanks for bringing that up) Very good to see the community easily agree on something ;). It seems we all support easy, clean, visual communication. Manas On Wed, Oct 9, 2013 at 10:39 AM, Nerijus Jankevicius wrote: yes, waiting for Juergen... On Oct 9, 2013, at 5:26 PM, BERNARD, Yves wrote: Would you fill an issue so that we can propose a resolution? Thanks, Yves -- Manas Bajaj, PhD Chief Systems Officer InterCAX LLC 75 5th Street NW, Suite 312 Atlanta GA 30308 USA voice: +1-404-592-6897 (ext 101) email: manas.bajaj@intercax.com web: www.intercax.com twitter: www.twitter.com/InterCAX From: Pete Rivett To: "BERNARD, Yves" , Nerijus Jankevicius , Eldad Palachi , "Manfred Koethe (koethe@88solutions.com)" , "Rouquette, Nicolas F (313K) (nicolas.f.rouquette@jpl.nasa.gov)" CC: Manas Bajaj , Andreas Korff , "Watson, John" , "Juergen Boldt" , Matthew Hause , "sysml-rtf@omg.org (sysml-rtf@omg.org)" Subject: RE: proxy and full port notation change request Thread-Topic: proxy and full port notation change request Thread-Index: Ac7FAg1DC2JGePjhSC261TOuvfIL8QAgAyoAAAAyyVA= Date: Thu, 10 Oct 2013 06:36:11 +0000 Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [68.231.194.190] X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r9A6aFL8028698 Why is this being discussed as a SysML and not a UML issue? -----Original Message----- From: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] Sent: Wednesday, October 09, 2013 11:34 PM To: Nerijus Jankevicius; Eldad Palachi Cc: Manas Bajaj; Andreas Korff; Watson, John; Juergen Boldt; Matthew Hause; sysml-rtf@omg.org (sysml-rtf@omg.org) Subject: RE: proxy and full port notation change request Nerijus, Eldad, I support the idea of dealing with conjugation as a separate issue. As pointed out in a previous email, and independently of the notation, with have a semantic issue with conjugation that we need to discuss. The convenient notation will depends on the decision we will make to fix it. Thanks, Yves -----Message d'origine----- De : Nerijus Jankevicius [mailto:nerijus@nomagic.com] Envoyé mercredi 9 octobre 2013 17:13 À: Eldad Palachi Cc : Manas Bajaj; Andreas Korff; Watson, John; Juergen Boldt; Matthew Hause; sysml-rtf@omg.org (sysml-rtf@omg.org); BERNARD, Yves Objet : Re: proxy and full port notation change request Eldad, When "isConjugated" was moved to UML metamodel, UML introduces "~" notation for that. SysML removed "isConjugated" together with notation. I would suggest to allow both - pre SysML 1.3 AND UML notation for conjugated ports. Most tools had "fill/no fill" notation before, so it can be restored easily, while also supporting UML style. Nerijus On Oct 9, 2013, at 6:04 PM, Eldad Palachi wrote: > As I wrote before - I support this too. > > Two small comments: > > 1. Need to make sure that if full port is different than uml port > without changing the notation for uml port. > 2. Recommend we separate fill/no fill of conjugated ports to a > separate issue just in case people have issues with this. In the past > we had that and I remember we decided to change it so there is a good > chance this will not be accpted. > > Eldad > > > > From: Manas Bajaj > To: Nerijus Jankevicius , > Cc: "BERNARD, Yves" , Juergen Boldt > , Matthew Hause , > Andreas Korff , "Watson, John" > , Eldad Palachi/Haifa/IBM@IBMIL, > "sysml-rtf@omg.org (sysml-rtf@omg.org)" > Date: 09/10/2013 05:49 PM > Subject: Re: proxy and full port notation change request > > > > +1 for dashed boundary for proxy ports and normal boundary for full > +ports > (Nerijus - thanks for bringing that up) > +1 for fill / no-fill notation for conjugate ports (Matthew - thanks > +for > bringing that up) > > Very good to see the community easily agree on something ;). It seems > we all support easy, clean, visual communication. > > Manas > > > On Wed, Oct 9, 2013 at 10:39 AM, Nerijus Jankevicius > > wrote: > yes, waiting for Juergen... > > > On Oct 9, 2013, at 5:26 PM, BERNARD, Yves wrote: > > Would you fill an issue so that we can propose a resolution? > > Thanks, > > Yves > > > > > -- > Manas Bajaj, PhD > Chief Systems Officer > InterCAX LLC > 75 5th Street NW, Suite 312 > Atlanta GA 30308 USA > voice: +1-404-592-6897 (ext 101) > email: manas.bajaj@intercax.com > web: www.intercax.com > twitter: www.twitter.com/InterCAX > This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: "BERNARD, Yves" To: Pete Rivett , Nerijus Jankevicius , Eldad Palachi , "Manfred Koethe (koethe@88solutions.com)" , "Rouquette, Nicolas F (313K) (nicolas.f.rouquette@jpl.nasa.gov)" CC: Manas Bajaj , Andreas Korff , "Watson, John" , Juergen Boldt , Matthew Hause , "sysml-rtf@omg.org (sysml-rtf@omg.org)" Date: Thu, 10 Oct 2013 08:38:39 +0200 Subject: RE: proxy and full port notation change request Thread-Topic: proxy and full port notation change request Thread-Index: Ac7FAg1DC2JGePjhSC261TOuvfIL8QAgAyoAAAAyyVAAAAyEYA== Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r9A6cnBd028771 Pete, Proxy vs Full port notation is actually in the SysML scope but I agree that the issue about conjugation should be discussed as an UML issue. Yves -----Message d'origine----- De : Pete Rivett [mailto:pete.rivett@adaptive.com] Envoyé jeudi 10 octobre 2013 08:36 À: BERNARD, Yves; Nerijus Jankevicius; Eldad Palachi; Manfred Koethe (koethe@88solutions.com); Rouquette, Nicolas F (313K) (nicolas.f.rouquette@jpl.nasa.gov) Cc : Manas Bajaj; Andreas Korff; Watson, John; Juergen Boldt; Matthew Hause; sysml-rtf@omg.org (sysml-rtf@omg.org) Objet : RE: proxy and full port notation change request Why is this being discussed as a SysML and not a UML issue? -----Original Message----- From: BERNARD, Yves [mailto:Yves.Bernard@airbus.com] Sent: Wednesday, October 09, 2013 11:34 PM To: Nerijus Jankevicius; Eldad Palachi Cc: Manas Bajaj; Andreas Korff; Watson, John; Juergen Boldt; Matthew Hause; sysml-rtf@omg.org (sysml-rtf@omg.org) Subject: RE: proxy and full port notation change request Nerijus, Eldad, I support the idea of dealing with conjugation as a separate issue. As pointed out in a previous email, and independently of the notation, with have a semantic issue with conjugation that we need to discuss. The convenient notation will depends on the decision we will make to fix it. Thanks, Yves -----Message d'origine----- De : Nerijus Jankevicius [mailto:nerijus@nomagic.com] Envoyé mercredi 9 octobre 2013 17:13 À: Eldad Palachi Cc : Manas Bajaj; Andreas Korff; Watson, John; Juergen Boldt; Matthew Hause; sysml-rtf@omg.org (sysml-rtf@omg.org); BERNARD, Yves Objet : Re: proxy and full port notation change request Eldad, When "isConjugated" was moved to UML metamodel, UML introduces "~" notation for that. SysML removed "isConjugated" together with notation. I would suggest to allow both - pre SysML 1.3 AND UML notation for conjugated ports. Most tools had "fill/no fill" notation before, so it can be restored easily, while also supporting UML style. Nerijus On Oct 9, 2013, at 6:04 PM, Eldad Palachi wrote: > As I wrote before - I support this too. > > Two small comments: > > 1. Need to make sure that if full port is different than uml port > without changing the notation for uml port. > 2. Recommend we separate fill/no fill of conjugated ports to a > separate issue just in case people have issues with this. In the past > we had that and I remember we decided to change it so there is a good > chance this will not be accpted. > > Eldad > > > > From: Manas Bajaj > To: Nerijus Jankevicius , > Cc: "BERNARD, Yves" , Juergen Boldt > , Matthew Hause , > Andreas Korff , "Watson, John" > , Eldad Palachi/Haifa/IBM@IBMIL, > "sysml-rtf@omg.org (sysml-rtf@omg.org)" > Date: 09/10/2013 05:49 PM > Subject: Re: proxy and full port notation change request > > > > +1 for dashed boundary for proxy ports and normal boundary for full > +ports > (Nerijus - thanks for bringing that up) > +1 for fill / no-fill notation for conjugate ports (Matthew - thanks > +for > bringing that up) > > Very good to see the community easily agree on something ;). It seems > we all support easy, clean, visual communication. > > Manas > > > On Wed, Oct 9, 2013 at 10:39 AM, Nerijus Jankevicius > > wrote: > yes, waiting for Juergen... > > > On Oct 9, 2013, at 5:26 PM, BERNARD, Yves wrote: > > Would you fill an issue so that we can propose a resolution? > > Thanks, > > Yves > > > > > -- > Manas Bajaj, PhD > Chief Systems Officer > InterCAX LLC > 75 5th Street NW, Suite 312 > Atlanta GA 30308 USA > voice: +1-404-592-6897 (ext 101) > email: manas.bajaj@intercax.com > web: www.intercax.com > twitter: www.twitter.com/InterCAX > This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: "BERNARD, Yves" To: Michael Chonoles , "'Eldad Palachi'" , "'Manas Bajaj'" CC: "'Andreas Korff'" , "'Watson, John'" , "'Juergen Boldt'" , "'Matthew Hause'" , "'Nerijus Jankevicius'" , "sysml-rtf@omg.org" Date: Thu, 10 Oct 2013 13:11:24 +0200 Subject: RE: proxy and full port notation change request Thread-Topic: proxy and full port notation change request Thread-Index: AQF13uKsH5G4Zii14G52mg0BG2fRdAF5KXSZAZv5jcIA7S1V/gJrOqDMAUXf0+0BgDU7AQF5QiitAf963S0BzHObRQKCbkVymhZ9rcCAATw9UA== Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r9ABBUTL027529 Michael, I don't understand your point about dotted/dashed line in diagrams. Dashed line style is already used by UML and I'm not aware of registered issue about this. Yves -----Message d'origine----- De : Michael Chonoles [mailto:mjchonoles@yahoo.com] Envoyé mercredi 9 octobre 2013 18:24 À: 'Eldad Palachi'; 'Manas Bajaj' Cc : 'Andreas Korff'; 'Watson, John'; 'Juergen Boldt'; 'Matthew Hause'; 'Nerijus Jankevicius'; sysml-rtf@omg.org; BERNARD, Yves Objet : RE: proxy and full port notation change request I would suggest that we don't use dotted/dashed lines. This choice would doom us to additional problems every time diagrams are printed or cut/paste from a modeling tool to an office-like tool (including Frame, PDF, etc.), as the dot/dashes often look like a solid line, and occasionally a solid line will look like it is dashed. Hollow vs Filled: This might work, though when the ports are small any text in a solid port would be difficult to read. It also has the disadvantage of colliding with the previous notation for conjugate (which I liked) Placement: I would generally prefer to see placement being part of the solution, e.g., on the block's border vs overlapping the box's border. Shape: If placement doesn't work, perhaps we can have slightly modified shapes. Perhaps a proxy port should have one rounded/ovalish side. BTW, does SysML support the behavioral port notation? Michael -----Original Message----- From: Eldad Palachi [mailto:eldad.palachi@il.ibm.com] Sent: Wednesday, October 09, 2013 11:04 AM To: Manas Bajaj Cc: Andreas Korff; Watson, John; Juergen Boldt; Matthew Hause; Nerijus Jankevicius; sysml-rtf@omg.org (sysml-rtf@omg.org); BERNARD, Yves Subject: Re: proxy and full port notation change request As I wrote before - I support this too. Two small comments: 1. Need to make sure that if full port is different than uml port without changing the notation for uml port. 2. Recommend we separate fill/no fill of conjugated ports to a separate issue just in case people have issues with this. In the past we had that and I remember we decided to change it so there is a good chance this will not be accpted. Eldad From: Manas Bajaj To: Nerijus Jankevicius , Cc: "BERNARD, Yves" , Juergen Boldt , Matthew Hause , Andreas Korff , "Watson, John" , Eldad Palachi/Haifa/IBM@IBMIL, "sysml-rtf@omg.org (sysml-rtf@omg.org)" Date: 09/10/2013 05:49 PM Subject: Re: proxy and full port notation change request +1 for dashed boundary for proxy ports and normal boundary for full +ports (Nerijus - thanks for bringing that up) +1 for fill / no-fill notation for conjugate ports (Matthew - thanks for bringing that up) Very good to see the community easily agree on something ;). It seems we all support easy, clean, visual communication. Manas On Wed, Oct 9, 2013 at 10:39 AM, Nerijus Jankevicius wrote: yes, waiting for Juergen... On Oct 9, 2013, at 5:26 PM, BERNARD, Yves wrote: Would you fill an issue so that we can propose a resolution? Thanks, Yves -- Manas Bajaj, PhD Chief Systems Officer InterCAX LLC 75 5th Street NW, Suite 312 Atlanta GA 30308 USA voice: +1-404-592-6897 (ext 101) email: manas.bajaj@intercax.com web: www.intercax.com twitter: www.twitter.com/InterCAX This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. X-Trusted-NM: yes Subject: Re: proxy and full port notation change request From: Nerijus Jankevicius Date: Thu, 10 Oct 2013 14:30:33 +0300 Cc: Michael Chonoles , "'Eldad Palachi'" , "'Manas Bajaj'" , "'Andreas Korff'" , "'Watson, John'" , "'Juergen Boldt'" , "'Matthew Hause'" , "sysml-rtf@omg.org" To: "BERNARD, Yves" X-Mailer: Apple Mail (2.1085) X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r9ABUbhL029286 Even more, we use dashed control flows in SysML, dashed line border for reference properties and more. Never had problems with that. Time to upgrade to high-res printers and monitors :) Nerijus On Oct 10, 2013, at 2:11 PM, BERNARD, Yves wrote: > Michael, > > I don't understand your point about dotted/dashed line in diagrams. Dashed line style is already used by UML and I'm not aware of registered issue about this. > > Yves > > -----Message d'origine----- > De : Michael Chonoles [mailto:mjchonoles@yahoo.com] > Envoyé mercredi 9 octobre 2013 18:24 > À: 'Eldad Palachi'; 'Manas Bajaj' > Cc : 'Andreas Korff'; 'Watson, John'; 'Juergen Boldt'; 'Matthew Hause'; 'Nerijus Jankevicius'; sysml-rtf@omg.org; BERNARD, Yves > Objet : RE: proxy and full port notation change request > > I would suggest that we don't use dotted/dashed lines. This choice would doom us to additional problems every time diagrams are printed or cut/paste from a modeling tool to an office-like tool (including Frame, PDF, etc.), as the dot/dashes often look like a solid line, and occasionally a solid line will look like it is dashed. > > Hollow vs Filled: > This might work, though when the ports are small any text in a solid port would be difficult to read. It also has the disadvantage of colliding with the previous notation for conjugate (which I liked) > > Placement: > I would generally prefer to see placement being part of the solution, e.g., on the block's border vs overlapping the box's border. > > Shape: > If placement doesn't work, perhaps we can have slightly modified shapes. > Perhaps a proxy port should have one rounded/ovalish side. > > BTW, does SysML support the behavioral port notation? > Michael > > -----Original Message----- > From: Eldad Palachi [mailto:eldad.palachi@il.ibm.com] > Sent: Wednesday, October 09, 2013 11:04 AM > To: Manas Bajaj > Cc: Andreas Korff; Watson, John; Juergen Boldt; Matthew Hause; Nerijus Jankevicius; sysml-rtf@omg.org (sysml-rtf@omg.org); BERNARD, Yves > Subject: Re: proxy and full port notation change request > > As I wrote before - I support this too. > > Two small comments: > > 1. Need to make sure that if full port is different than uml port without changing the notation for uml port. > 2. Recommend we separate fill/no fill of conjugated ports to a separate issue just in case people have issues with this. In the past we had that and I remember we decided to change it so there is a good chance this will not be accpted. > > Eldad > > > > From: Manas Bajaj > To: Nerijus Jankevicius , > Cc: "BERNARD, Yves" , Juergen Boldt > , Matthew Hause , > Andreas Korff , "Watson, John" > , Eldad Palachi/Haifa/IBM@IBMIL, > "sysml-rtf@omg.org (sysml-rtf@omg.org)" > Date: 09/10/2013 05:49 PM > Subject: Re: proxy and full port notation change request > > > > +1 for dashed boundary for proxy ports and normal boundary for full > +ports > (Nerijus - thanks for bringing that up) > +1 for fill / no-fill notation for conjugate ports (Matthew - thanks for > bringing that up) > > Very good to see the community easily agree on something ;). It seems we all support easy, clean, visual communication. > > Manas > > > On Wed, Oct 9, 2013 at 10:39 AM, Nerijus Jankevicius > wrote: > yes, waiting for Juergen... > > > On Oct 9, 2013, at 5:26 PM, BERNARD, Yves wrote: > > Would you fill an issue so that we can propose a resolution? > > Thanks, > > Yves > > > > > -- > Manas Bajaj, PhD > Chief Systems Officer > InterCAX LLC > 75 5th Street NW, Suite 312 > Atlanta GA 30308 USA > voice: +1-404-592-6897 (ext 101) > email: manas.bajaj@intercax.com > web: www.intercax.com > twitter: www.twitter.com/InterCAX > > > > This mail has originated outside your organization, either from an external partner or the Global Internet. > Keep this in mind if you answer this message. > > > > The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. > If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. > Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. > All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. > From: "BERNARD, Yves" To: Nerijus Jankevicius , Eldad Palachi CC: Manas Bajaj , Andreas Korff , "Watson, John" , Juergen Boldt , Matthew Hause , "sysml-rtf@omg.org (sysml-rtf@omg.org)" Date: Thu, 10 Oct 2013 08:34:20 +0200 Subject: RE: proxy and full port notation change request Thread-Topic: proxy and full port notation change request Thread-Index: Ac7FAg1DC2JGePjhSC261TOuvfIL8QAgAyoA Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r9A6YQKw028624 Nerijus, Eldad, I support the idea of dealing with conjugation as a separate issue. As pointed out in a previous email, and independently of the notation, with have a semantic issue with conjugation that we need to discuss. The convenient notation will depends on the decision we will make to fix it. Thanks, Yves -----Message d'origine----- De : Nerijus Jankevicius [mailto:nerijus@nomagic.com] Envoyé mercredi 9 octobre 2013 17:13 À: Eldad Palachi Cc : Manas Bajaj; Andreas Korff; Watson, John; Juergen Boldt; Matthew Hause; sysml-rtf@omg.org (sysml-rtf@omg.org); BERNARD, Yves Objet : Re: proxy and full port notation change request Eldad, When "isConjugated" was moved to UML metamodel, UML introduces "~" notation for that. SysML removed "isConjugated" together with notation. I would suggest to allow both - pre SysML 1.3 AND UML notation for conjugated ports. Most tools had "fill/no fill" notation before, so it can be restored easily, while also supporting UML style. Nerijus On Oct 9, 2013, at 6:04 PM, Eldad Palachi wrote: > As I wrote before - I support this too. > > Two small comments: > > 1. Need to make sure that if full port is different than uml port > without changing the notation for uml port. > 2. Recommend we separate fill/no fill of conjugated ports to a > separate issue just in case people have issues with this. In the past > we had that and I remember we decided to change it so there is a good > chance this will not be accpted. > > Eldad > > > > From: Manas Bajaj > To: Nerijus Jankevicius , > Cc: "BERNARD, Yves" , Juergen Boldt > , Matthew Hause , > Andreas Korff , "Watson, John" > , Eldad Palachi/Haifa/IBM@IBMIL, > "sysml-rtf@omg.org (sysml-rtf@omg.org)" > Date: 09/10/2013 05:49 PM > Subject: Re: proxy and full port notation change request > > > > +1 for dashed boundary for proxy ports and normal boundary for full > +ports > (Nerijus - thanks for bringing that up) > +1 for fill / no-fill notation for conjugate ports (Matthew - thanks > +for > bringing that up) > > Very good to see the community easily agree on something ;). It seems > we all support easy, clean, visual communication. > > Manas > > > On Wed, Oct 9, 2013 at 10:39 AM, Nerijus Jankevicius > > wrote: > yes, waiting for Juergen... > > > On Oct 9, 2013, at 5:26 PM, BERNARD, Yves wrote: > > Would you fill an issue so that we can propose a resolution? > > Thanks, > > Yves > > > > > -- > Manas Bajaj, PhD > Chief Systems Officer > InterCAX LLC > 75 5th Street NW, Suite 312 > Atlanta GA 30308 USA > voice: +1-404-592-6897 (ext 101) > email: manas.bajaj@intercax.com > web: www.intercax.com > twitter: www.twitter.com/InterCAX > This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: Matthew Hause To: Nerijus Jankevicius , "BERNARD, Yves" CC: Michael Chonoles , "'Eldad Palachi'" , "'Manas Bajaj'" , Andreas Korff , "'Watson, John'" , "'Juergen Boldt'" , "sysml-rtf@omg.org" Subject: RE: proxy and full port notation change request Thread-Topic: proxy and full port notation change request Thread-Index: AQF13uKsSueJtwKKOUS2SkTk+lngKAF5KXSZAZv5jcIA7S1V/gJrOqDMAUXf0+0BgDU7AQF5QiitAf963S0BzHObRQKCbkVymhZ9rcCAATw9UIAAe/WA//+2hFA= Date: Thu, 10 Oct 2013 14:09:00 +0000 Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [64.134.237.225] x-esetresult: clean, is OK x-esetid: 350DFF23A501E071634AAF X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r9AE9HPo008467 Michael does have a point. It may be a problem with ports as they are generally fairly small on a diagram. Lines and reference properties are usually much larger than a port would be. -----Original Message----- From: Nerijus Jankevicius [mailto:nerijus@nomagic.com] Sent: Thursday, October 10, 2013 4:31 AM To: BERNARD, Yves Cc: Michael Chonoles; 'Eldad Palachi'; 'Manas Bajaj'; Andreas Korff; 'Watson, John'; 'Juergen Boldt'; Matthew Hause; sysml-rtf@omg.org Subject: Re: proxy and full port notation change request Even more, we use dashed control flows in SysML, dashed line border for reference properties and more. Never had problems with that. Time to upgrade to high-res printers and monitors :) Nerijus On Oct 10, 2013, at 2:11 PM, BERNARD, Yves wrote: > Michael, > > I don't understand your point about dotted/dashed line in diagrams. Dashed line style is already used by UML and I'm not aware of registered issue about this. > > Yves > > -----Message d'origine----- > De : Michael Chonoles [mailto:mjchonoles@yahoo.com] Envoyé mercredi > 9 octobre 2013 18:24 À: 'Eldad Palachi'; 'Manas Bajaj' > Cc : 'Andreas Korff'; 'Watson, John'; 'Juergen Boldt'; 'Matthew > Hause'; 'Nerijus Jankevicius'; sysml-rtf@omg.org; BERNARD, Yves Objet > : RE: proxy and full port notation change request > > I would suggest that we don't use dotted/dashed lines. This choice would doom us to additional problems every time diagrams are printed or cut/paste from a modeling tool to an office-like tool (including Frame, PDF, etc.), as the dot/dashes often look like a solid line, and occasionally a solid line will look like it is dashed. > > Hollow vs Filled: > This might work, though when the ports are small any text in a solid > port would be difficult to read. It also has the disadvantage of > colliding with the previous notation for conjugate (which I liked) > > Placement: > I would generally prefer to see placement being part of the solution, e.g., on the block's border vs overlapping the box's border. > > Shape: > If placement doesn't work, perhaps we can have slightly modified shapes. > Perhaps a proxy port should have one rounded/ovalish side. > > BTW, does SysML support the behavioral port notation? > Michael > > -----Original Message----- > From: Eldad Palachi [mailto:eldad.palachi@il.ibm.com] > Sent: Wednesday, October 09, 2013 11:04 AM > To: Manas Bajaj > Cc: Andreas Korff; Watson, John; Juergen Boldt; Matthew Hause; Nerijus > Jankevicius; sysml-rtf@omg.org (sysml-rtf@omg.org); BERNARD, Yves > Subject: Re: proxy and full port notation change request > > As I wrote before - I support this too. > > Two small comments: > > 1. Need to make sure that if full port is different than uml port without changing the notation for uml port. > 2. Recommend we separate fill/no fill of conjugated ports to a separate issue just in case people have issues with this. In the past we had that and I remember we decided to change it so there is a good chance this will not be accpted. > > Eldad > > > > From: Manas Bajaj > To: Nerijus Jankevicius , > Cc: "BERNARD, Yves" , Juergen Boldt > , Matthew Hause , > Andreas Korff , "Watson, John" > , Eldad Palachi/Haifa/IBM@IBMIL, > "sysml-rtf@omg.org (sysml-rtf@omg.org)" > Date: 09/10/2013 05:49 PM > Subject: Re: proxy and full port notation change request > > > > +1 for dashed boundary for proxy ports and normal boundary for full > +ports > (Nerijus - thanks for bringing that up) > +1 for fill / no-fill notation for conjugate ports (Matthew - thanks > +for > bringing that up) > > Very good to see the community easily agree on something ;). It seems we all support easy, clean, visual communication. > > Manas > > > On Wed, Oct 9, 2013 at 10:39 AM, Nerijus Jankevicius > > wrote: > yes, waiting for Juergen... > > > On Oct 9, 2013, at 5:26 PM, BERNARD, Yves wrote: > > Would you fill an issue so that we can propose a resolution? > > Thanks, > > Yves > > > > > -- > Manas Bajaj, PhD > Chief Systems Officer > InterCAX LLC > 75 5th Street NW, Suite 312 > Atlanta GA 30308 USA > voice: +1-404-592-6897 (ext 101) > email: manas.bajaj@intercax.com > web: www.intercax.com > twitter: www.twitter.com/InterCAX > > > > This mail has originated outside your organization, either from an external partner or the Global Internet. > Keep this in mind if you answer this message. > > > > The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. > If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. > Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. > All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. >