The naming "Type" should be avoided. Related: - Class BanCommunicationType: "The BAN communication function type, i.e. periodic, event driven or on request."@en , with sub-classes: - s4ehaw:EventDrivenBanCommunicationType "BAN communication function way of working of the type event driven."@en - s4ehaw:OnRequestBanCommunicationType "BAN communication function way of working of the type on request."@en - s4ehaw:PeriodicBanCommunicationType "BAN communication function way of working of the type periodic."@en - OP hasBanCommunicationType : "A BAN has a BAN communication type that is the type of communication carried out between BAN devices and BAN Hub."@en domain Ban, range BanCommunicationType The term _function_ lets me believe these could be defined as kinds of functions (of communication functions) The part _the type of communication carried out between BAN devices and BAN Hub_ lets me think it would best qualify the devices themselves, instead of the BAN (the network) I suggest the following changes: - delete these classes and properties - use the SAREF Core pattern for functions to define CommunicationFunction and its narrower functions.