SYSML2_ — Each FlowConnectionUsage owned by PartUsage subsets 3 features

In current implementation each FlowConnectionUsage owned by PartUsage subsets (automatically) 3 features:

1. FlowConnectionUsage::flowConnections
2. PartUsage::subparts
3. ActionUsage::ownedActions

This could be optimized for the sake of model size. Maybe it would be better idea to introduce

    Part::Part::ownedFlows :> ownedActions, subparts, flowConections

and define something like CheckFlowConnectionSubFlowSpecialization constraint?

Defer to RTF

This issue was submitted after the end of the comment period, and the FTF has decided to defer its consideration to a future RTF.