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)

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
Specification keywords
UML keywords
SysMLv1.x keywords
The spec only states that: This does NOT mean that other port types can't be typed by an InterfaceBlock!
If it is stated that 'all fish live in the water' does it mean that dolphins (which are mammals) do not live in the water?
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:
Relates to
Related notes
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)