Typing a "standard" Port by an InterfaceBlock or ~InterfaceBlock IS allowed AND can be useful; typing a FullPort by an InterfaceBlock or ~InterfaceBlock is formally allowed but not so useful, because it would have no parts or behaviors to do anything.

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
ASSERTION
UML keywords
Port
SysMLv1.x keywords
"standard" Port
FullPort
InterfaceBlock
~InterfaceBlock
See detailed discussion under:
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)
Relates to
Related notes
[TIP] 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)
[ASSERTION] 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)
Related notes (backlinks)
Related snippets (extracts)
  [SysML-1.6] Proxy ports are always typed by interface blocks, a specialized kind of block that has no behaviors or internal parts.
Visit also
Visit also (backlinks)