Related: - Class Interface: "Used for modelling the interfaces of a health device (e.g. Bluetooth, UWB, IEEE 802.15.6, serial interface...)."@en - OP hasInterface: "A health device has one or multiple interfaces (Bluetooth, UWB, IEEE 802.15.6, serial interface...)."@en domain HealthDevice, range Interface - DP interfaceAddress "The interface address. The interface may have many addresses like MAC address, IP address or others."@en domain Interface range string - DP interfaceDescription "The interface type description."@en range string - OP interfaceProtocol "The interface communication protocol can be e.g. BLE, serial, Ethernet..."@en range CommunicationProtocol (see #18 ) - DP isGateway "This boolean variable indicates if the interface is a gateway or not."@en range xsd:boolean - DP transmissionRate "The transmission rate of the interface, i.e. the number of bits transmitted per second (usually expressed in kbps or Mbps)."@en range xsd:float Proposed change: rename Interface -> CommunicationInterface, and model communication interfaces as s4syst:ConnectionPoint at which systems can connect to a network. In details: ## interfaceAddress delete and define sub-properties of saref:hasIdentifier --> saref:hasMACAddress, saref:hasIPAddress, ... ## interfaceDescription delete, we can use standard rdfs:label, rdfs:comment, dct:description ## interfaceProtocol Instances Bluetooth, UWB, IEEE 802.15.6, ... should be defined once and used in many places. Best modelled as FeatureKind. The CommunicationInterface may be of that kind. In practice: ``` <device> connectsAt <device#bluetoothInterface> . <device#bluetoothInterface> a CommunicationInterface ; hasFeatureKind <Bluetooth> . ``` ## isGateway A device (connected at a certain communication interface to a certain communication network) be the gateway for the network. This is a role, and as such, it should be modelled using some OP . For example, OP hasGateway a sub-property of s4syst:connectsSystem `hasGateway a owl:ObjectProperty; rdfs:subPropertyOf s4syst:connectsSystem` Some Devices are designed to actually serve the role of a gateway. It may make sense to define a featurekind Gateway for these. `saref:Gateway a saref:FeatureKind` ## transmissionRate DP transmissionRate rdfs:comment "The transmission rate of the interface, i.e. the number of bits transmitted per second (usually expressed in kbps or Mbps)."@en Better use the SAREF core pattern for properties `TransmissionRate a saref:Property`.