ECS has https://www.elastic.co/guide/en/ecs/8.9/ecs-guidelines.html#_guidelines_for_field_names

Avoid abbreviations when possible

• Exceptions can be made, when the name used for the concept is too strongly in favor of the abbreviation. Example: ip fields, or field sets such as os, geo.

It would be good to document some (same or different) guidance for OpenTelemetry semantic conventions to help with:

• Remove abbreviation of kubernetes in resource semantic conventions #58
• Add enduser.anon_id to general attributes #443 (comment)
• db.* vs database.*
• hw.* vs hardware.*

(and probably others, these are just ones on top of mind)