Is your feature request related to a problem?

When using stereotyped blocks in SysML the stereotype label starts to get crowded due to appended stereotypes <<block, stereo1>>. If multiple stereotypes are explicitly specified, I'd expect them all to show up. However, <<block>> is defined as implicit for all unlabeled blocks:

The SysML 1.7 spec says:

So, there is an implicit association that everything's a block if unlabeled on a sysml bdd.

Describe the solution you'd like

When a block is stereotyped remove the text <<block>>

Describe alternatives you've considered

• add a toggle switch for displaying <> stereotype
• Use classes instead of blocks, where possible, for a cleaner diagram (this is not an option if you need the block-specific attributes defined by SysML, but is okay for things like metamodels)