This page identifies a possible issue, inconsistency, concern, error, or bug!
One of the ways Webel IT Australia helps promote tools, technologies, and languages is by donating a lot of time identifying, tracking, and reporting potential issues, in order to help vendors and developers improve the tools and technologies. In some cases, we also offer workarounds and advice for users. All issues tracked on our public site are offered most constructively and with sincerest gratitude to the tool vendors and technology developers.
DISCLAIMER: Vendors do not officially endorse issue analysis by Webel IT Australia.
Subsection 8.4.9.1 Connection Definitions within 8.4.9 Connections Semantics describes actual feature values on the nested features corresponding to cross features, and further explains that the existence of these values is sufficient to require existence of instances of connection usages with corresponding cross features (unowned or owned) and vice versa.
But none of the SysML2.0 specification examples or SysMLv2 GitHub PILOT examples actually show this (most only show definition level examples).
Webel has created very detailed examples of such available in a dedicated Cross Subsetting learning module as part of the Webel SysMLv2 course: