SYSML2 — Intersection missing for some multiple specializations

Some multiple specializations in the libraries might be intended to be intersections, including feature specializations. For example, from SYSML2-490, under Actions::Actions

action sendSubactions: SendAction[0..*] :> subactions, sendActions {
  doc /* 
      * The subactions of this Action that are SendActions. 
      */ 
}

action acceptSubactions: AcceptAction[0..*] :> subactions, acceptActions {
  doc /* 
      * The subactions of this Action that are AcceptActions. 
      */ 
}

No Change

The KerML Intersecting relationship is not included in SysML, and there is no SysML notation for it. In any case, the semantic constraints for actions (and in other areas) are intended to already ensure the proper subsettings – the limitation being that these constraints currently key off of syntactic constructs. If an intersection capability is added to SysML in the future, or it is decided to revise the semantic constraints more generally, then the question posed in the present issue can be re-addressed at that time.