Harmonise naming of properties "hasX" versus "X"
Many properties are named as "hasX", where X is the concept that's the range of the property. There are also many properties that are simply named X, where X usually is the uncapitalised name of the range of the property.
The choice between "hasX" and "X" often seems arbitrary, especially to a non-expert. Can we form a best-practice on when to format a property as "hasX" and when not to?
Considerations:
- On multiple occasions I have heard people who are IT experts but novicein ontology express doubts about this naming convention. They expect a boolean when for the property "hasX", but the actual concept for a property "X".
- Being consistent is probably more important than whichever choice we make.
- The ERA Vocabulary, a modern ontology which I esteem highly, already follows the best practice of only using "hasX" when the intended domain is a boolean, at least when it comes to datatype properties.