{"@context":{"ns0":"https://saref.etsi.org/core/","rdf":"http://www.w3.org/1999/02/22-rdf-syntax-ns#","owl":"http://www.w3.org/2002/07/owl#","rdfs":"http://www.w3.org/2000/01/rdf-schema#","skos":"http://www.w3.org/2004/02/skos/core#","metadata_def":"http://data.bioontology.org/metadata/def/","metadata":"http://data.bioontology.org/metadata/"},"@graph":[{"@id":"ns0:Operation","@type":"owl:Class","rdfs:subClassOf":{"@id":"owl:Thing"},"rdfs:label":{"@language":"en","@value":"Operation"},"rdfs:comment":{"@language":"en","@value":"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."},"skos:example":[{"@language":"en","@value":"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."},{"@language":"en","@value":"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)."},{"@language":"en","@value":"To turn on a light, send a CoAP PUT request with CBOR content 0xf5 (true)"}],"skos:historyNote":{"@language":"en","@value":"V3.2.1: Introduced saref:Operation and associated properties from oneM2M base ontology."},"metadata:def/prefLabel":{"@language":"en","@value":"Operation"},"metadata:def/mappingLoom":"operation","metadata:def/mappingSameURI":{"@id":"ns0:Operation"},"metadata:prefixIRI":"saref:Operation","skos:note":[{"@language":"en","@value":"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."},{"@language":"en","@value":"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."}]},{"@id":"ns0:isOperationOf","rdfs:domain":{"@id":"ns0:Operation"}},{"@id":"ns0:hasOperation","rdfs:range":{"@id":"ns0:Operation"}}]}
{"@context":{"ns0":"https://saref.etsi.org/core/","rdf":"http://www.w3.org/1999/02/22-rdf-syntax-ns#","owl":"http://www.w3.org/2002/07/owl#","rdfs":"http://www.w3.org/2000/01/rdf-schema#","skos":"http://www.w3.org/2004/02/skos/core#","metadata_def":"http://data.bioontology.org/metadata/def/","metadata":"http://data.bioontology.org/metadata/"},"@graph":[{"@id":"ns0:Operation","@type":"owl:Class","rdfs:subClassOf":{"@id":"owl:Thing"},"rdfs:label":{"@language":"en","@value":"Operation"},"rdfs:comment":{"@language":"en","@value":"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."},"skos:example":[{"@language":"en","@value":"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."},{"@language":"en","@value":"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)."},{"@language":"en","@value":"To turn on a light, send a CoAP PUT request with CBOR content 0xf5 (true)"}],"skos:historyNote":{"@language":"en","@value":"V3.2.1: Introduced saref:Operation and associated properties from oneM2M base ontology."},"metadata:def/prefLabel":{"@language":"en","@value":"Operation"},"metadata:def/mappingLoom":"operation","metadata:def/mappingSameURI":{"@id":"ns0:Operation"},"metadata:prefixIRI":"saref:Operation","skos:note":[{"@language":"en","@value":"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."},{"@language":"en","@value":"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."}]},{"@id":"ns0:isOperationOf","rdfs:domain":{"@id":"ns0:Operation"}},{"@id":"ns0:hasOperation","rdfs:range":{"@id":"ns0:Operation"}}]}