Issue 11666: Section: 11.3.2.1 (marte-ftf) Source: Commissariat a l Energie Atomique-CEA (Dr. Arnaud Cuccuru, arnaud.cuccuru(at)cea.fr) Nature: Enhancement Severity: Significant Summary: It would probably be clearer if the BFeatureKind enumeration only proposes REQUIRED and PROVIDED enumeration literals (that is to say “qualifiers” that are already used and widely accepted in the UML to denote “direction” of signals and operations in message-oriented communications). IN, OUT, INOUT should be reserved to FlowPorts and FlowProperties (that is to say for data-flow communication schemes). Resolution: Disposition: See issue 11661 for disposition Revised Text: Actions taken: November 20, 2007: received issue February 17, 2010: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 20 Nov 2007 10:09:22 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Arnaud Cuccuru Company: Commissariat a l Energie Atomique - CEA/LIST mailFrom: arnaud.cuccuru@cea.fr Notification: Yes Specification: A UML Profile for MARTE Section: 11.3.2.1 FormalNumber: ptc/07-08-04 Version: Beta 1 RevisionDate: 04/08/07 Page: 121 Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1) Gecko/20061010 Firefox/2.0 Description It would probably be clearer if the BFeatureKind enumeration only proposes REQUIRED and PROVIDED enumeration literals (that is to say .qualifiers. that are already used and widely accepted in the UML to denote .direction. of signals and operations in message-oriented communications). IN, OUT, INOUT should be reserved to FlowPorts and FlowProperties (that is to say for data-flow communication schemes).