The SysML spec is clear on Property (StructuralFeature):
SysML-1.6: 'A Binding Connector is a connector which specifies that the properties at both ends of the connector have equal values.'
SysML-1.6: 'If the properties at the ends of a binding connector are typed by a ValueType, the connector specifies that the instances of the properties shall hold equal values, recursively through any nested properties within the connected properties.'
SysML-1.6: 'If the properties at the ends of a binding connector are typed by a Block, the connector specifies that the instances of the properties shall refer to the same block instance.'
The SysML-1.6 spec is not clear on per-BehavioralFeature matching for Operations and ReceptionsThis constraint is spoiling the show, Webel is lobbying to have it changed:
SysML-1.6: 'BindingConnector::1_compatible_types The two ends of a binding connector shall have either the same type or types that are compatible so that equality of their values can be defined. 'Because it is not consistent with the description of connection compatiblity for ProxyPort:
SysML-1.6: 'Proxy ports can be connected to internal parts or ports on internal parts, identifying features on those parts or ports that are available to external blocks.'
SysML-1.6: 'When a proxy port is connected to a single internal part [or port or internal part], the connector shall be a binding connector, or have the same semantics as a binding connector ... (the value of the proxy port and the connected internal part are the same; links of associations typing the connector are between all objects and themselves, and no others)'
SysML-1.6: 'When a proxy port is connected to multiple internal parts, the connectors have the same semantics as a single binding connector to an aggregate of those parts, supporting all their features, and treating flows and invocations from outside the aggregate... This aggregate is not a separate element of the system, and only groups the internal parts for purposes of binding to the proxy port.'