Just a thought - as by design CDS transforms HDBDD entity columns into upper case we then don't really care what mix of case is used in the HDBDD, provided reference to types by columns within the HDBDD matches, as all external references to columns, such as within UI5 view elements, will refer to the generated catalog version (uppercase)?
Would "best practice" may be to use uppercase in the HDBDD to align with catalog casing if we want to be pedantic? I guess what Im trying to say is that within HDBDD use of camel case for column naming is in practice irrelevant as it's not honoured during catalog creation, and I'm not sure of using camel case for documentation/readability value?
You have any in-house practice you an recommend, and confirm there are no external artefacts (or other) to the HDBDD specification that refer to and are sensitive to the internal HDBDD entity column typing?
Thanks.