https://w3id.org/saref |
|
http://purl.org/dc/terms/contributor
|
http://www.garcia-castro.com/foaf.rdf#me |
| http://purl.org/net/mpoveda
|
|
http://www.w3.org/2002/07/owl#imports
|
http://www.w3.org/2006/time
|
|
http://purl.org/dc/terms/license
|
http://purl.org/NET/rdflicense/cc-by4.0
|
|
http://purl.org/dc/terms/creator
|
https://www.linkedin.com/in/lauradaniele
|
|
http://purl.org/dc/terms/issued
|
2015-04-01
|
|
http://purl.org/dc/terms/description
|
The Smart Appliances REFerence (SAREF) ontology is a shared model of consensus that facilitates the matching of existing assets (standards/protocols/datamodels/etc.) in the smart appliances domain. The SAREF ontology provides building blocks that allow separation and recombination of different parts of the ontology depending on specific needs. The starting point of SAREF is the concept of device (e.g., a switch). Devices are tangible objects designed to accomplish a particular task in households, common public buildings or offices. In order to accomplish this task, the device performs one or more functions. For example, a washing machine is designed to wash (task) and to accomplish this task it performs the start and stop function. The SAREF ontology offers a lists of basic functions that can be eventually combined in order to have more complex functions in a single device. For example, a switch offers an actuating function of type 'switching on/off'. Each function has some associated commands, which can also be picked up as building blocks from a list. For example, the 'switching on/off' is associated with the commands 'switch on', 'switch off' and 'toggle'. Depending on the function(s) it accomplishes, a device can be found in some corresponding states that are also listed as building blocks. When connected to a network, a device offers a service, which is a representation of a function to a network that makes the function discoverable, registerable and remotely controllable by other devices in the network. A service can represent one or more functions. A service is offered by a device that wants (a certain set of) its function(s) to be discoverable, registerable, remotely controllable by other devices in the network. A service must specify the device that is offering the service and the function(s) to be represented. A device in the SAREF ontology is also characterized by a profile that can be used to optimize some property, such as Energy, in a home or office that are part of a building.
|
|
http://purl.org/dc/terms/publisher
|
https://www.tno.nl
|
|
http://purl.org/dc/terms/created
|
2015-02-10
|
|
http://purl.org/dc/terms/source
|
http://www.etsi.org/deliver/etsi_ts/103200_103299/103264/02.01.01_60/ts_103264v020101p.pdf
|
|
http://www.w3.org/1999/02/22-rdf-syntax-ns#type
|
http://www.w3.org/2002/07/owl#Ontology
|
|
http://www.w3.org/2002/07/owl#versionInfo
|
2.1.2
|
|
http://www.w3.org/2000/01/rdf-schema#comment
|
Information about changes compared to version 1.1.1: (1)The classes and properties related to how to represent devices in building spaces (such as the saref:BuildingSpace class, saref:BuildingObject class and saref:isLocatedIn property) have been removed from SAREF and incorporated into the SAREF4BLDG extension related to buildings (https://w3id.org/def/saref4bldg), including the reuse of the W3C® WGS84 geo positioning vocabulary; (2)The saref:DeviceCategory and saref:FunctionCategory classes have been removed. Instead, the hierarchy of device categories has been implemented directly as subclasses of the saref:Device class; (3)The information specific for energy efficiency has been moved to the SAREF4ENER extension (https://w3id.org/saref4ener). For example, the saref:Profile class has been redefined to accommodate only the properties that are general enough for any type of profile, not only for energy and power. Details on how to specifically model a power profile can be found in the SAREF4ENER extension (https://w3id.org/saref4ener); (4) The subclasses of the saref:Energy class have been removed (i.e., Average Energy, Maximum Energy, Minimum Energy, Total Energy, HVAC Energy, Hot Water Energy and Lighting Energy); (5)The saref:Property class has been split into two classes (saref:Property and saref:Measurement), as it is done in the SAREF4ENVI extension (https://w3id.org/def/saref4envi), in order to properly accommodate the distinction between the concept of property (an observable quality of something) and the concept of measurement (a concrete value observed for a property); (6)Too restrictive cardinality restrictions have been revised, sometimes making them optional rather than mandatory (better to make properties mandatory in the extensions that specialize SAREF for a specific purpose, rather than restricting SAREF, whose purpose is more general). For example, definitions of units of measurement using an enumeration (owl:oneOf) were too restrictive because they did not allow using other units than those enumerated. Therefore, the individuals of each class are still there, but the owl:oneOf enumeration has been removed; (7)The saref:UnitOfMeasure subclassesre use individuals from the OM ontology for unit of measures (http://www.wurvoc.org/vocabularies/om-1.6/), but this is not the only solution. It has been clarified in the comments that the OM ontology is an example, but other ontologies can be used; (8)The global restrictions (rdfs:domain and rdfs:range) in object properties have been completely removed not to hinder interoperability. Object properties are now only restricted locally in the classes; (9)The subclasses of saref:Task have been transormed in individuals; (10)The saref:hasTask property has been removed from the saref:Profile class to resolve an ambiguity with the saref:Task class. |
| Information about changes compared to version 2.1.1: Small version bump to ensure that the turtle-version and the owl-version are up to date.
|
|
http://purl.org/dc/terms/title
|
SAREF: the Smart Appliances REFerence ontology
|
|
http://purl.org/dc/terms/modified
|
2018-05-02
|
https://w3id.org/saref#Function |
|
http://www.w3.org/2000/01/rdf-schema#label
|
Function
|
|
http://www.w3.org/1999/02/22-rdf-syntax-ns#type
|
http://www.w3.org/2002/07/owl#Class
|
|
http://www.w3.org/2000/01/rdf-schema#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.
|
|
http://www.w3.org/2000/01/rdf-schema#subClassOf
|
_:49
|
https://w3id.org/saref#Device |
|
http://www.w3.org/2000/01/rdf-schema#label
|
Device
|
|
http://www.w3.org/1999/02/22-rdf-syntax-ns#type
|
http://www.w3.org/2002/07/owl#Class
|
|
http://www.w3.org/2000/01/rdf-schema#comment
|
A tangible object designed to accomplish a particular task in households, common public buildings or offices. In order to accomplish this task, the device performs one or more functions. For example, a washing machine is designed to wash (task) and to accomplish this task it performs a start and stop function. Devices can be structured in categories (subclasses) that reflect the different domain in which a device is used, e.g., smart appliances domain (subclass FunctionRelated) vs. building domain (subclass BuildingRelated) vs. smart grid domain (subclass EnergyRelated). New categories can be defined,if needed, to reflect other differences, for example different points of view, such as the point of view of the device's user vs. the point of view of the device's manufacturer. We propose a list of devices that are relevant for the purpose of SAREF, but this list can be extended.
|
|
http://www.w3.org/2000/01/rdf-schema#subClassOf
|
_:67 |
| _:68 |
| _:58 |
| _:51 |
| _:43 |
| _:36 |
| _:69 |
| _:70 |
| _:71 |
| _:37 |
| _:72 |
| _:41 |
| _:73 |
| _:74
|