Issue 18876: Pull semantics for flow properties (sysml-rtf) Source: Airbus Group (Mr. Yves Bernard, yves.bernard(at)airbus.com) Nature: Uncategorized Issue Severity: Summary: Currently in SysML, flow properties have “Push” semantics (cf. sub-clause 9.3.2.7): writing to a flow property with direction out, propagates value to matching flow property at opposite end of the connector. This implies that there is a behavior running on the part from the “out” side. “Pull” semantics could be useful as well: the value propagation is the result of a read made on the flow property with direction in to the matching property at the opposite end of the connector. This implies that there is a behavior running on the part from the “in” side. SysML should introduce a semantic variation point on this topic, and/or some specific notations/abstract syntax Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: August 19, 2013: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: End of Annotations:===== m: "BERNARD, Yves" To: "Juergen Boldt (juergen@omg.org)" CC: "Sysml-Rtf (sysml-rtf@omg.org)" Date: Mon, 19 Aug 2013 17:03:43 +0200 Subject: Pull semantics for flow properties Thread-Topic: Pull semantics for flow properties Thread-Index: Ac6c7UwLya8JB7iES3W04hMkKMlLLg== 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 Hello Juergen, Would you please create the following issue for SysML, as discussed during the Berlin.s meeting? Currently in SysML, flow properties have .Push. semantics (cf. sub-clause 9.3.2.7): writing to a flow property with direction out, propagates value to matching flow property at opposite end of the connector. This implies that there is a behavior running on the part from the .out. side. .Pull. semantics could be useful as well: the value propagation is the result of a read made on the flow property with direction in to the matching property at the opposite end of the connector. This implies that there is a behavior running on the part from the .in. side. SysML should introduce a semantic variation point on this topic, and/or some specific notations/abstract syntax. Thanks, Yves 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.