Missing legality rules for feature connections

[lwrage]

The legality rules for feature connections (section 9.1) only ensures consistent direction of source and destination feature, nothing else.

Examples for missing legality rules

• If both ends are feature groups their feature group types must be inverses of each other
• If both ends reference a classifier (data, bus, etc) those classifiers must be compatible (like for other connections)
• ~A feature group may not be connected to an abstract feature (?)~

[jjhugues]

@lwrage can you please propose wordings for those. Is OSATE already implementing some of these rules?

[lwrage]

This set of rules applies if neither source nor destination end of the connection is an abstract feature. In this case the feature connection must be replaceable by a port, parameter, access, or feature group connection.

• If the source or destination destination feature is a port legality rules 9.2 (L1) -(L4) and 9.2 (L6) - (L16) apply to this feature connection, i.e., the connection must fulfill the legality rules for a port connection.
• If the source or destination feature is a parameter legality rules 9.3 (L1) - (L4) apply to this feature connection, i.e., the connection must fulfill the legality rules for a parameter connection.
• If the source and destination features are access features, or if one end is an access feature and the other end is a subcomponent legality rules 9.4 (L1) - (L11) apply to this feature connection, i.e., the connection must fulfill the legality rules for an access connection.
• If both ends are feature groups legality rules 9.5 (L1) - (L8) apply to this feature connection, i.e., the connection must fulfill the legality rules for a feature group connection.

If one or both ends are abstract features only the following rules apply.

• If both source and destination feature reference a classifier both must be data or bus classifiers and must match according to the Classifier_Matching_Rules property (see 9.2 (L13) and (L14)).
• If more than one feature connection declaration in a semantic feature connection has a property association for a given connection property, then the resulting property values must be identical.