Issue 14055: Proposal to have a stereotype for reference nested property (sysml-rtf) Source: International Business Machines (Mr. Eldad Palachi, eldad.palachi(at)il.ibm.com) Nature: Enhancement Severity: Significant Summary: When one needs to reference a value of a specific property of part in a composition hierarchy in order to bind it to a constraint parameter, one uses the dot notation shown in section 8.3.1.2. (Example: a box labeled myCar.myEngine.currentTemp in a parametric diagram). When such a box is binded to a constraint parameter a nested connector end may be used to reference this property in the context of the composition hierarchy. However this poses a serious implementation issue for tools since until the box is binded it has no real model element behind it, also if one copies this box or the diagram to another hierarchy in the model then the tool has to complicated analysis. We propose to have a stereotype for reference nested property similar to nested connector end in which the path in the composition hirerchy is specified (i.e. propertyPath: Property [1..*] (ordered) - like in section 8.3.2.6). This will make it easier for tools to implement backed by the standard meta-model. Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: July 5, 2009: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: Extensive discussion occurred during the SysML 1.3 RTF on the opportunity to create a common, generalized form of contextualized reference path to address not only the applications raised by this issue, but to support nested properties as allocation ends, as constrained elements, to support context-specific initial values, for contextualized flow definitions, and to replace the current NestedConnectorEnd. Adopting a common form of reference path is a potential priority for the SysML 1.4 RTF. Disposition: Deferred End of Annotations:===== m: webmaster@omg.org Date: 05 Jul 2009 03:50:12 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Eldad Palachi Company: IBM mailFrom: eldad.palachi@il.ibm.com Notification: Yes Specification: SysML Section: 8/8.3.1.2, 10 FormalNumber: formal/2008-11-02 Version: 1.1 RevisionDate: 11/02/2008 Page: 41 Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 1.1.4322; MS-RTC LM 8; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) Description When one needs to reference a value of a specific property of part in a composition hierarchy in order to bind it to a constraint parameter, one uses the dot notation shown in section 8.3.1.2. (Example: a box labeled myCar.myEngine.currentTemp in a parametric diagram). When such a box is binded to a constraint parameter a nested connector end may be used to reference this property in the context of the composition hierarchy. However this poses a serious implementation issue for tools since until the box is binded it has no real model element behind it, also if one copies this box or the diagram to another hierarchy in the model then the tool has to complicated analysis. We propose to have a stereotype for reference nested property similar to nested connector end in which the path in the composition hirerchy is specified (i.e. propertyPath: Property [1..*] (ordered) - like in section 8.3.2.6). This will make it easier for tools to implement backed by the standard meta-model.