Issue 18909: Proxy port “complete” specification (§ 9.3.2.12): (sysml-rtf)
Source: Airbus Group (Mr. Yves Bernard, yves.bernard(at)airbus.com)
Nature: Clarification
Severity: 
Summary:  if a proxy port P1 has a nested proxy port P1::P2 and both are non-behavioral, does it mean that both P1 and P1::P2 must be explicitly connected to internal parts? If P1 is just a logical group of nested proxy ports, there may be no sense to connect P1 per se internally (but it makes sense to connect P1 externally).

 


Resolution: Defer

Postponed to the next RTF
Revised Text: 
Actions taken:
September 12, 2013: received issue
January 3, 2017: Deferred
April 6, 2017: closed issue
Discussion: 

End of Annotations:=====

m: "BERNARD, Yves" <Yves.Bernard@airbus.com>
To: "Juergen Boldt (juergen@omg.org)" <juergen@omg.org>
CC: "'Rouquette, Nicolas F (313K)'" <nicolas.f.rouquette@jpl.nasa.gov>
Date: Thu, 12 Sep 2013 14:18:18 +0200
Subject: [SysML 1.4 RTF] new SysML issues
Thread-Topic: [SysML 1.4 RTF] new SysML issues
Thread-Index: Ac6volMCfW0bsnMjS0iumTKkNBkkkg==
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


Hi Juergen,

 

Following the discussion we had yesterday within a workgroup of the SysML RTF, Would you create the issues described below for SysML, please?