Tags and keywords
The gist is that a FullPort can be any kind of port EXCEPT a ProxyPort, because being a FullPort is not about what it does, it's about how it does it, namely itself (or in collaboration with other elements):
This slide deliberately does not expose any of the Features of these ports yet, we'll see how to do that later.
A FullPort can be port with a contract of provided and required DirectedFeatures, or a port with one or more FlowProperty items, or it may be specify a contract using provided and required Interfaces.
It is not recommended here that you mix these modes!
In general, the SysML DirectedFeature approach is more powerful and the notation is cleaner than UML provided/required Interfaces. Prefer SysML DirectedFeatures unless you have a really good reason to use Interfaces!You don't have to always show the «full» keywords, they mostly just add clutter, noting that clients of a Port do not EVER need to know whether a Port is a FullPort, a ProxyPort, or a "standard" Port, they just have to see the contract Features:
SysML-1.6: 'Using existing blocks with ports only requires knowing the port types, because they define the features available for linking or communication with those ports via connectors. The stereotypes of proxy and full ports might be elided in these cases to simplify diagrams.'Also: