I think it should be changed with an intentional marker instead of Capital letter, to avoid current problems:
In some languages, the Capitalization is unavoidable for something to make sense grammatically: Substantive are capitalized in German (see below). → Concept/descriptors shouldn’t rely on aspect of language that are mandatory for it to make sense…
Letters and special character are interpreted as Capital Letter : Starting with numbers and special characters → Concept . In my experience: a lot of my descriptor start with the number of element to list (e.g.: “3 properties of…”)
there are concepts that require lower casing : there are many times when a lower-case starting letter makes sense for a Concept. In my experience, case-sensitive function (while learning programming) come often.
ambiguous, and it interrupts the workflow: It is possible to switch a Capitalized word to a descriptor via the toolbar. However, it forces switching between Concept and Descriptor (with mouse, via the bottom toolbar, see bottom of post). The result of that is that, the lower capitalized can be concepts as well as the opposite. This unambiguous situation is unnecessary.
By principle, IMO, the concept vs descriptor framework deserves an intentional, non-ambiguous input method, that isn’t case-sensitive, as sometime case sensitivity is useful for what we put in our knowledge base.
I suggest “:=” vs “::” but there probably is a better looking (less ambiguous visually) way to do so.
I hope my request make sense
Concept := this is the concept definition
3 properties :: these are the names of the 3 properties