Naming Conventions the example of `SolGel`

[arjunneyyathalaCat]

What do you want to optimize? Type in General, Range, Cardinality a.s.o.

Comment

Please just tell us only what you want to change

Is the reason behind no space between sol and gel is due to this defined as a class?

Please tell us why you request these changes

No response

Additional information.

No response

[HendrikBorgelt]

in general we currently use PascalCase (Capitalized first letter without whitespaces) for writing LinkML class names and snake_case (only lowercase where whitespaces are replaced with/words are connected by underscores) for slots/relations.

This is required as LinkML and the respective file formats involved(yaml/json/python/...) do not allow for whitespaces in names of artefacts.

As such "sol gel" was converted to "SolGel" to still show that there is a seperation in between the sol and the gel part.

We could switch to other naming conventions, however cases like the "kebab-case" are not possible, since regular scores opposite to underscores are not allowed in LinkML named entities.

If this answer is sufficient and you agree with the naming convention, please close this issue.