from saref-portal#49 > SAREF4ENVI could use SAREF4SYST patterns to describe the following concepts: > > - s4envi:hasComponent links a system and the system in which it might be decomposed. The “might” in this definition makes it ambiguous ; The domain and range is not defined. This property could be replaced by s4syst:hasSubSystem. > - s4envi:isConnectedTo link a system and the system to which it is connected to. This property could be replaced by s4syst:connectedTo. > - s4envi:usesCommunicationInterface and s4envi:usesCommmunicationProtocol. > - s4envi:System, from its definition, read more like a CommunicatingSystem Agreed by @gnabasik and @bouter @garciacastro then wrote: > I agree to reuse SAREF4SYST but I'm not sure in the case of: > - s4envi:usesCommunicationInterface and s4envi:usesCommmunicationProtocol > - Changing System to CommunicatingSystem. It has communication capabilities but that is not what defines the system itself.