@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ns0: <https://saref.etsi.org/core/> .
@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/> .
ns0:ActuatingFunction
rdfs:subClassOf ns0:Function .
ns0:EventFunction
rdfs:subClassOf ns0:Function .
ns0:Function
metadata_def:mappingLoom "function" ;
metadata_def:mappingSameURI ns0:Function ;
metadata_def:prefLabel "Function" ;
metadata:prefixIRI "saref:Function" ;
a owl:Class ;
rdfs:comment "The functionality necessary to accomplish the task for which a device is designed. A device can be designed to perform more than one function. Functions can be structured in categories (subclasses) that reflect different points of view, for example, considering the specific application area for which a function can be used (e.g., light, temperature, motion, heat, power, etc.), or the capability that a function can support (e.g., receive, reply, notify, etc.), and so forth. "@en ;
rdfs:label "Function"@en ;
rdfs:subClassOf owl:Thing .
ns0:MeteringFunction
rdfs:subClassOf ns0:Function .
ns0:SensingFunction
rdfs:subClassOf ns0:Function .
ns0:hasCommand
rdfs:domain ns0:Function .
ns0:hasFunction
rdfs:range ns0:Function .
ns0:isCommandOf
rdfs:range ns0:Function .
ns0:represents
rdfs:range ns0:Function .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ns0: <https://saref.etsi.org/core/> .
@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/> .
ns0:ActuatingFunction
rdfs:subClassOf ns0:Function .
ns0:EventFunction
rdfs:subClassOf ns0:Function .
ns0:Function
metadata_def:mappingLoom "function" ;
metadata_def:mappingSameURI ns0:Function ;
metadata_def:prefLabel "Function" ;
metadata:prefixIRI "saref:Function" ;
a owl:Class ;
rdfs:comment "The functionality necessary to accomplish the task for which a device is designed. A device can be designed to perform more than one function. Functions can be structured in categories (subclasses) that reflect different points of view, for example, considering the specific application area for which a function can be used (e.g., light, temperature, motion, heat, power, etc.), or the capability that a function can support (e.g., receive, reply, notify, etc.), and so forth. "@en ;
rdfs:label "Function"@en ;
rdfs:subClassOf owl:Thing .
ns0:MeteringFunction
rdfs:subClassOf ns0:Function .
ns0:SensingFunction
rdfs:subClassOf ns0:Function .
ns0:hasCommand
rdfs:domain ns0:Function .
ns0:hasFunction
rdfs:range ns0:Function .
ns0:isCommandOf
rdfs:range ns0:Function .
ns0:represents
rdfs:range ns0:Function .