SysML: Typing a Port by an InterfaceBlock or ~InterfaceBlock does NOT imply that the Port is a ProxyPort (but ProxyPort must be typed by an InterfaceBlock or ~InterfaceBlock)

The spec only states that: This does NOT mean that other port types can't be typed by an InterfaceBlock! In particular, one might wish to type a "standard" Port by an InterfaceBlock or a conjugating ~InterfaceBlock. And why might one want to type a "standard" Port by an InterfaceBlock?

Reason 1: As part of an incremental development process (before committing to using a ProxyPort or FullPort (in which case one might wish to first extend the InterfaceBlock)

Reason 2: If you are using Blocks (not InterfaceBlocks) to Type your Ports just use "manual" feature-by feature direction inversion to achieve type conjugation (and you can even use a ~ tilde prefix)

Please see also under: