Use 'UpperCamelCase' (a.k.a. PascalCase) names for Classifiers such as UML Classes and SysML Blocks) to avoid confusion with 'lowerCase' Property names [see however special naming conventions for acronyms and SysML contract and flow Blocks]

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
NAMING
POLICY
Policy level
STRONG
UML keywords
Classifier
Class
SysMLv1.x keywords
Block
Keywords
In the case of ValueTypes, however, this can sometimes be difficult, because some from existing units libraries are lower case

Note that Webel uses some special additional naming conventions for SysML Blocks and InterfaceBlocks used as Port contracts and to type Ports with Flows!

Relates to
More block Generalization examples: Home entertainment system
«pa:triple»: Pseudo semantic triples (c.f. RDF/S and OWL)
Related notes
[NAMING, POLICY]{STRONG} Prefer 'UpperCamelCase' (a.k.a. PascalCase) names for Behaviors such as Activities intended for use in CallBehaviorActions, or at least use a 'Capital first letter'; avoid 'all lower case' (as it leads to confusion with lower case Action names)
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)