SYSML2_ — Accept action in representative notation tables is confusing and needs cleanup

Clause 7.16.1 (rep. notation for actions) shows a graphical notation example of an accept action corresponding to the following textual notation:

action trigger1 : Trigger 
accept scene : Scene via viewPort;

It shows 3 alternative graphical notations which are confusing and inconsistent.
That graphical representative example needs to be corrected. Here are few issues:

• it shows an unbound parameter "receiver" in 2nd and 3rd examples
• first example uses the type Trigger instead of Trigger1
• 3rd example uses guillemets in the wrong way
• too many options instead of one "canonical" way to do this
• it uses a parameter that in 2nd example called scene and in 3rd example called payload

Improve graphical notation of accept action

Agreed that the representative notation for accept action needs to be simplified and disambiguated. It is proposed to split the example into two:

1. A simple single trigger accept action.
2. The same trigger accept action but now with a binding of its scene parameter to the scene input parameter of a next action2 in succession after the trigger.