<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:ns0="https://saref.etsi.org/core/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:metadata_def="http://data.bioontology.org/metadata/def/" xmlns:metadata="http://data.bioontology.org/metadata/">
<owl:Class rdf:about="https://saref.etsi.org/core/Operation">
<rdfs:subClassOf rdf:resource="http://www.w3.org/2002/07/owl#Thing"/>
<rdfs:label xml:lang="en">Operation</rdfs:label>
<rdfs:comment xml:lang="en">A saref:Operation is the means of a service to communicate in a procedure-type manner over the network (i.e. transmit data to/from other devices). It is the –machine interpretable– exposure of a –human understandable– command to a network.</rdfs:comment>
<skos:example xml:lang="en">In the set of operations exposed by a smart washing machine on a given network, one may be dedicated to set the water temperature for the washing cycle, and expected as input a enumerated value. Another one may be dedicated to start, pause, or stop the washing cycle.</skos:example>
<skos:example xml:lang="en">In the set of operations exposed by a smart light bulb on a given network, one may be dedicated to turn on and off the light and expect a boolean as input. Another one may be dedicated to set the luminosity status and expect a target luminosity level (a byte) and a transition time (encoded on two bytes).</skos:example>
<skos:example xml:lang="en">To turn on a light, send a CoAP PUT request with CBOR content 0xf5 (true)</skos:example>
<skos:historyNote xml:lang="en">V3.2.1: Introduced saref:Operation and associated properties from oneM2M base ontology.</skos:historyNote>
<metadata_def:prefLabel xml:lang="en">Operation</metadata_def:prefLabel>
<metadata_def:mappingLoom>operation</metadata_def:mappingLoom>
<metadata_def:mappingSameURI rdf:resource="https://saref.etsi.org/core/Operation"/>
<metadata:prefixIRI>saref:Operation</metadata:prefixIRI>
<skos:note xml:lang="en">Typically, a device connected to a given network offers one service for each of its functions of interest, and each service has one operation per command of interest of the function of interest it represents.</skos:note>
<skos:note xml:lang="en">An operation may be described in terms of its inputs and outputs using OP saref:hasInput and saref:hasOutput. Inputs and outputs of operations typically describe the expected schema or shape of network messages.</skos:note>
</owl:Class>
<rdf:Description rdf:about="https://saref.etsi.org/core/hasOperation">
<rdfs:range>
<rdf:Description rdf:about="https://saref.etsi.org/core/Operation">
<metadata_def:mappingSameURI rdf:resource="https://saref.etsi.org/core/Operation"/>
</rdf:Description>
</rdfs:range>
</rdf:Description>
<rdf:Description rdf:about="https://saref.etsi.org/core/isOperationOf">
<rdfs:domain rdf:resource="https://saref.etsi.org/core/Operation"/>
</rdf:Description>
</rdf:RDF>
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:ns0="https://saref.etsi.org/core/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:metadata_def="http://data.bioontology.org/metadata/def/" xmlns:metadata="http://data.bioontology.org/metadata/">
<owl:Class rdf:about="https://saref.etsi.org/core/Operation">
<rdfs:subClassOf rdf:resource="http://www.w3.org/2002/07/owl#Thing"/>
<rdfs:label xml:lang="en">Operation</rdfs:label>
<rdfs:comment xml:lang="en">A saref:Operation is the means of a service to communicate in a procedure-type manner over the network (i.e. transmit data to/from other devices). It is the –machine interpretable– exposure of a –human understandable– command to a network.</rdfs:comment>
<skos:example xml:lang="en">In the set of operations exposed by a smart washing machine on a given network, one may be dedicated to set the water temperature for the washing cycle, and expected as input a enumerated value. Another one may be dedicated to start, pause, or stop the washing cycle.</skos:example>
<skos:example xml:lang="en">In the set of operations exposed by a smart light bulb on a given network, one may be dedicated to turn on and off the light and expect a boolean as input. Another one may be dedicated to set the luminosity status and expect a target luminosity level (a byte) and a transition time (encoded on two bytes).</skos:example>
<skos:example xml:lang="en">To turn on a light, send a CoAP PUT request with CBOR content 0xf5 (true)</skos:example>
<skos:historyNote xml:lang="en">V3.2.1: Introduced saref:Operation and associated properties from oneM2M base ontology.</skos:historyNote>
<metadata_def:prefLabel xml:lang="en">Operation</metadata_def:prefLabel>
<metadata_def:mappingLoom>operation</metadata_def:mappingLoom>
<metadata_def:mappingSameURI rdf:resource="https://saref.etsi.org/core/Operation"/>
<metadata:prefixIRI>saref:Operation</metadata:prefixIRI>
<skos:note xml:lang="en">Typically, a device connected to a given network offers one service for each of its functions of interest, and each service has one operation per command of interest of the function of interest it represents.</skos:note>
<skos:note xml:lang="en">An operation may be described in terms of its inputs and outputs using OP saref:hasInput and saref:hasOutput. Inputs and outputs of operations typically describe the expected schema or shape of network messages.</skos:note>
</owl:Class>
<rdf:Description rdf:about="https://saref.etsi.org/core/hasOperation">
<rdfs:range>
<rdf:Description rdf:about="https://saref.etsi.org/core/Operation">
<metadata_def:mappingSameURI rdf:resource="https://saref.etsi.org/core/Operation"/>
</rdf:Description>
</rdfs:range>
</rdf:Description>
<rdf:Description rdf:about="https://saref.etsi.org/core/isOperationOf">
<rdfs:domain rdf:resource="https://saref.etsi.org/core/Operation"/>
</rdf:Description>
</rdf:RDF>