@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ns0: <https://w3id.org/coswot/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix metadata_def: <http://data.bioontology.org/metadata/def/> .
@prefix metadata: <http://data.bioontology.org/metadata/> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix ns1: <https://w3id.org/coswot/core/> .
ns0:CommandOfInterest
metadata_def:mappingLoom "commandofinterest" ;
metadata_def:mappingSameURI ns0:CommandOfInterest ;
metadata_def:prefLabel "Command Of Interest"@en ;
metadata:prefixIRI "coswot:CommandOfInterest" ;
a owl:Class ;
rdfs:comment "The lowest-level directives a device supports and exposes to some network. Commands can target (OP coswot:targets and its sub-properties) features, properties, or states. A coswot:CommandOfInterest is a directives actually supported by a device and exposed to some network."@en ;
rdfs:isDefinedBy ns1:functions_commands ;
rdfs:label "Command Of Interest"@en ;
rdfs:subClassOf ns0:Command ;
skos:example "The corridor smart light switch supports a command of kind “turn on/off”, which controls the state of the outdoor light."@en, "The smart fridge supports a command of kind “observe temperature”, which observes the temperature of the fridge."@en ;
skos:note "Commands of interest need not always be explicited. It depends on the use case. Typically, commands of interest are useful to specify the actual property of interest or state of interest that is expected as input parameter, output, or that will be targeted."@en, "Like for commands, commands of interest may be described in terms of their input parameters, outputs, and of which properties or states they target."@en .
ns0:hasCommandOfInterest
rdfs:range ns0:CommandOfInterest .
ns0:isCommandOfInterestOf
rdfs:domain ns0:CommandOfInterest .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ns0: <https://w3id.org/coswot/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix metadata_def: <http://data.bioontology.org/metadata/def/> .
@prefix metadata: <http://data.bioontology.org/metadata/> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix ns1: <https://w3id.org/coswot/core/> .
ns0:CommandOfInterest
metadata_def:mappingLoom "commandofinterest" ;
metadata_def:mappingSameURI ns0:CommandOfInterest ;
metadata_def:prefLabel "Command Of Interest"@en ;
metadata:prefixIRI "coswot:CommandOfInterest" ;
a owl:Class ;
rdfs:comment "The lowest-level directives a device supports and exposes to some network. Commands can target (OP coswot:targets and its sub-properties) features, properties, or states. A coswot:CommandOfInterest is a directives actually supported by a device and exposed to some network."@en ;
rdfs:isDefinedBy ns1:functions_commands ;
rdfs:label "Command Of Interest"@en ;
rdfs:subClassOf ns0:Command ;
skos:example "The corridor smart light switch supports a command of kind “turn on/off”, which controls the state of the outdoor light."@en, "The smart fridge supports a command of kind “observe temperature”, which observes the temperature of the fridge."@en ;
skos:note "Commands of interest need not always be explicited. It depends on the use case. Typically, commands of interest are useful to specify the actual property of interest or state of interest that is expected as input parameter, output, or that will be targeted."@en, "Like for commands, commands of interest may be described in terms of their input parameters, outputs, and of which properties or states they target."@en .
ns0:hasCommandOfInterest
rdfs:range ns0:CommandOfInterest .
ns0:isCommandOfInterestOf
rdfs:domain ns0:CommandOfInterest .