SYSML21 — Abstract syntax from resolution of SYSML2_-159 were not made

The resolution of SYSML2_-159, approved in SysML v2 FTF2 Ballot #5, included the following abstract syntax changes that were not actually made in the specification:

1. In 8.3.17.1 Overview (of Actions Abstract Syntax), in Figure 26
   Send and Accept Actions, change the multiplicity of the association end SendActionUsage::payloadArgument from [1] to [0..1].
2. In 8.3.17.2 AcceptActionUsage, under "Constraints", replace the description and OCL for the constraint validateAcceptActionUsageParameters:

   An AcceptUsageAction must have at least one input parameter, corresponding to its payload (even if it has no FeatureValue). (Note that the payloadParameter is an input as well as an output.)

   inputParameters()->notEmpty()
   

3. In 8.3.17.15 SendActionUsage:

• Under "Attributes", after "/payloadArgument : Expression" add "[0..1]".
• Under "Constraints", replace the constraint validateSendActionParameters with:

  validateSendActionUsagePayloadArgument

  If a SendActionUsage is owned via a StateSubactionMembership or a TransitionFeatureMembership, then it must have a payloadArgument.

  owningFeatureMembership <> null and
  (owningFeatureMembership.oclIsKindOf(StateSubactionMembership) or
   owningFeatureMembership.oclIsKindOf(TransitionFeatureMembership)) implies
      payloadArgument <> null