The Smart Applications REFerence ontology (SAREF) is intended to enable interoperability between solutions from different providers and among various activity sectors in the Internet of Things (IoT), thus contributing to the development of the global digital market.
2020-02-11
2020-05-29
SAREF: the Smart Applications REFerence ontology
saref
https://saref.etsi.org/core/
Information about changes compared to version 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, including the reuse of the W3C? WGS84 geo positioning vocabulary.
- 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.
- The information specific for energy efficiency has been moved to the SAREF4ENER extension. 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.
- 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).
- The saref:Property class has been split into two classes (saref:Property and saref:Measurement), as it is done in the SAREF4ENVI extension, 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).
- 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.
- The saref:UnitOfMeasure subclasses use individuals from the OM ontology for unit of measures, 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.
- 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.
- The subclasses of saref:Task have been transormed in individuals.
- 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:
- Added the saref:FeatureOfInterest class and the properties used to relate it to saref:Measurement (saref:hasMeasurement and saref:isMeasurementOf) and to saref:Property (saref:hasProperty and saref:isPropertyOf).
- Added the saref:measurementMadeBy property as inverse of saref:makesMeasurement.
- The saref:relatesToProperty and saref:relatesToMeasurement properties are now inverse of each other.
- The range of saref:hasValue, which was defined as xsd:float, has been removed to support other datatypes for measurements.
- The range of datatype properties, which was defined as xsd:string, has been removed in order to support strings with language tags (rdf:langString). This affects saref:hasDescription, saref:hasManufacturer, saref:hasModel and saref:hasName, which now have implicitly a range of rdfs:Literal.
- The saref:hasName property has been removed and the use of rdfs:label is recommended.
- The saref:hasDescription property has been deprecated and the use of rdfs:comment is recommended.
- Too restrictive restrictions have been removed and in some cases the ontology documentation has been updated to reflect this: a saref:Command having at most one saref:hasDescription; a saref:Task being accomplished by at least one saref:Device; a saref:Device having a typical consumption of only energy or power; a saref:Commodity being measured in units of measure; restrictions on the values of saref:accomplishes that only covered specific use cases; universal restrictions on the saref:actsUpon property have been changed to existential ones; restrictions on the commands that a saref:Function may have, since there could be others not included in the defined enumerations; restrictive documentation of saref:EventFunction and saref:SmokeSensor.
- Bugs have been fixed: some devices (saref:DoorSwitch, saref:EnergyMeter, saref:LigthSwitch, saref:SmokeSensor, and saref:TemperatureSensor) were defined as subclass of a device and at the same time as consisting of such device; a saref:LightSwitch controls light and does not measure light, since it is an actuator; incorrect documentation of saref:OnState and saref:OffState.
- The saref:BuildingRelated, saref:EnergyRelated and saref:FunctionRelated classes have been removed, since the different extensions already classify the device types.
- The instances of the subclasses of saref:Command have been removed, since they represent examples.
- The instances of saref:UnitOfMeasure have been moved to examples.
- The classes related to the SAREF4ENER extension have been removed: saref:Generator, saref:Storage, saref:Load and saref:EnergyMeter.
- Some instances of saref:Device have been moved to examples: saref:WashingMachine, saref:LightingDevice, saref:MicroRenewable, saref:Multimedia, and saref:Network.
- Added domain and range axioms wherever the definition of a property unambiguously identifies the domain or the range of the property.
- The OWL Time ontology is not imported anymore.
- The documentation of some ontology terms has been updated for clarification.
- Language tags have been added to all labels and comments.
v3.1.1
A relationship between a certain entity (e.g., a device) and the task it accomplishes
accomplishes
A relationship between a command and a state
acts upon
A relationship indicating a composite entity that consists of other entities (e.g., a temperature/humidity sensor that consists of a temperature sensor and a humidity sensor)
consists of
A relationship specifying the property that can be controlled by a certain device
controls property
A relationship between a function and a command
has command
A relationship identifying the function of a device
has function
A relationship between a feature of interest and a measurement about it
has measurement
A relationship between a metering function and the measurement of the reading
has meter reading
A relationship identifying the reading type of a metering function (e.g., Water, Gas, Pressure , Energy , Power, etc.)
has meter reading type
A relationship indentifying the price associated to an entity
has price
A relationship associating a profile to a certain device
has profile
A relationship between a feature of interest and a property of that feature
has property
A relationship between a sensing function and a measurement identifying the range of a sensor detection
has sensing range
A relationship identifying the sensing type of a sensor detection (i.e., Temperature, Occupancy, Humidity, Motion , Smoke, Pressure, etc.)
has sensor type
A relationship identifying the type of state of a device
has state
A relationship associated with an event function to notify that a certain threshold measurement has been exceeded
has threshold measurement
A relationship to associate time information to an entity
has time
A relationship identifying the typical (energy or power) consumption of a device
has typical consumption
A relationship identifying what an entity, such as a profile, is about
isAbout
A relationship identifying an entity (e.g., a device) that can accomplish a task.
is accomplished by
A relationship between a command and a function.
is command of
A relationship specifying the devices that can control a certain property
is controlled by device
A relationship specifying the devices that can measure a certain property
is measured by device
A relationship identifying the unit of measure used for a certain entity.
is measured in
A relationship between a measurement and the feature of interest whose quality was measured
isMeasurementOf
A relationship between a service and a device that offers the service
is offered by
A relationship between a property and the feature of interest it belongs to
is property of
A relationship specifying the commodity for which a device is used for
is used for
A relation between a device and the measurements it makes. Such measurement will link together the value of the measurement, its unit of measure and the property to which it relates.
makes measurement
A relation between a measurement and the device that made it.
measurement made by
A relationship specifying the property that can be measured by a certain device
measures property
A relationship between a device and a service
offers
A relationship between a property and the measurements it relates to
relates to measurement
A relationship between a measurement and the property it relates to
relates to property
A relationship between a service and a function.
represents
A relationship providing a description of an entity (e.g., device). The value is expected to be a string or a string with language tag.
DEPRECATED: The use of rdfs:comment is recommended instead.
has description
true
A relationship identifying the manufacturer of an entity (e.g., device). The value is expected to be a string or a string with language tag.
has manufacturer
A relationship identifying the model of an entity (e.g., device). The value is expected to be a string or a string with language tag.
has model
A relationship stating the timestamp of an entity (e.g. a measurement).
has timestamp
A relationship defining the value of a certain property, e.g., energy or power. Note that, even if numeric values are expected to enable reasoning, measurement values could use other datatypes.
has value
saref:ActuatingFunction
A function that allows to transmit data to actuators, such as level settings (e.g., temperature) or binary switching (e.g., open/close, on/off)
Actuating function
saref:Actuator
A device responsible for moving or controlling a mechanism or system by performing an actuating function
Actuator
saref:Appliance
An electrical/mechanical machine that accomplish some household functions, such as cleaning or cooking
Appliance
saref:CloseCommand
A type of command
Close command
saref:CloseState
The state of a device that is CLOSE
Close state
saref:Coal
A type of commodity
Coal
1
saref:Command
A directive that a device must support to perform a certain function. A command may act upon a state, but does not necessarily act upon a state. For example, the ON command acts upon the ON/OFF state, but the GET command does not act upon any state, it simply gives a directive to retrieve a certain value. We propose here a list of commands that are relevant for the purpose of SAREF, but this list can be extended.
Command
saref:Commodity
A marketable item for which there is demand, but which is supplied without qualitative differentiation across a market. SAREF refers to energy commodities such as electricity, gas, coal and oil.
Commodity
saref:Currency
The class of units of measure for price
Currency
1
1
1
1
saref:Device
A tangible object designed to accomplish a particular task. 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.
Device
saref:DoorSwitch
A switch that performs the saref:OpenCloseFunction, is used for controlling a door, and can be found in the state saref:OpenCloseState. A saref:DoorSwitch is typically used to accomplish saref:Safety.
Door switch
saref:Electricity
A type of commodity
Electricity
saref:Energy
A saref:Property related to some measurements that are characterized by a certain value measured in an energy unit (such as Kilowatt_Hour or Watt_hour). Furter specializations of the saref:Energy class can be found in the SAREF4ENER extension, where classes such as EnergyMax, EnergyMin and EnergyExpected are defined.
Energy
saref:EnergyUnit
The unit of measure for energy
Energy unit
1
saref:EventFunction
A function that allows to notify about some relevant activity; e.g., that a certain threshold value has been exceeded or that some object has moved.
Event function
saref:FeatureOfInterest
A feature of interest represents any real world entity from which a property is measured.
Feature of interest
1
saref:Function
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.
Function
saref:Gas
A type of commodity
Gas
saref:GetCommand
A type of command
Get command
saref:GetCurrentMeterValueCommand
A type of get command
Get current meter value command
saref:GetMeterDataCommand
A type of get command
Get meter data command
saref:GetMeterHistoryCommand
A type of get command
Get meter history command
saref:GetSensingDataCommand
A type of get command
Get sensing data command
saref:HVAC
Heating, Ventilation and Air Conditioning (HVAC) device that provides indoor environmental comfort. A saref:HVAC is typically used to accomplish saref:Comfort.
HVAC
saref:Humidity
A saref:Property related to some measurements that are characterized by a certain value that is measured in a humidity unit
Humidity
saref:IlluminanceUnit
The unit of measure for light
Illuminance unit
saref:LevelControlFunction
An actuating function that allows to do level adjustments of a property in a certain range (e.g., 0%-100%), such as dimming a light in a room or setting the speed of an electric motor.
Level control function
saref:Light
A saref:Property related to some measurements that are characterized by a certain value that is measured in a illuminance unit (lux)
Light
saref:LightSwitch
A switch that performs the saref:OnOffFunction, controls the property saref:Light, and can be found in the state saref:OnOffState. It can offer a switch on service. A saref:LightSwitch is typically used to accomplish saref:Lighting.
Light switch
1
1
1
saref:Measurement
Represents the measured value made over a property. It is also linked to the unit of measure in which the value is expressed and the timestamp of the measurement.
Measurement
saref:Meter
A device built to accurately detect and display a quantity in a form readable by a human being. Further, a device of category saref:Meter that performs a saref:MeteringFunction.
Meter
saref:MeteringFunction
A function that allows to get data from a meter, such as current meter reading or instantaneous demand
Metering function
saref:Motion
A saref:Property related to some measurements that are characterized by a certain value that is measured in a unit of measure for motion
Motion
saref:MultiLevelState
A type of state
Multi level state
saref:NotifyCommand
A type of command
Notify command
saref:Occupancy
A saref:Property related to some measurements that are characterized by a certain value (saref:hasValue property) that is measured in a unit of measure for occupancy
Occupancy
saref:OffCommand
A type of command
Off command
saref:OffState
The state of a device that is Off
Off state
saref:OnCommand
A type of command
On command
saref:OnOffFunction
An actuating function that allows to switch on and off an actuator
On off function
saref:OnOffState
A type of state
On off state
saref:OnState
The state of a device that is On
On state
saref:OpenCloseFunction
An actuating function that allows to open and close a device
Open close function
saref:OpenCloseState
A type of state
Open close state
saref:OpenCommand
A type of command
Open command
saref:OpenState
The state of a device that is OPEN
Open state
saref:PauseCommand
A type of command
Pause command
saref:Power
A saref:Property related to some measurements that are characterized by a certain value that is measured in a power unit (such as watt or kilowatt). Further specializations of the saref:Power class can be found in the SAREF4ENER extension, where classes such as PowerMax, PowerMin and PowerExpected are defined.
Power
saref:PowerUnit
The unit of measure for power
Power unit
saref:Pressure
A saref:Property related to some measurements that are characterized by a certain value that is measured in a pressure unit (bar or pascal)
Pressure
saref:PressureUnit
The unit of measure for pressure
Pressure unit
saref:Price
A saref:Property crelated to some measurements that are characterized by a certain value that is measured using saref:Currency
Price
saref:Profile
A specification associated to a device to collect information about a certain Property (e.g., Energy) for optimizing its usage in the home, office or building in which the device is located. This specification is about a certain Property (saref:isAbout), can be calculated over a time span (saref:hasTime) and can be associated to some costs (saref:hasPrice). An example is the Power Profile defined in the SAREF4ENER extension that can be associated to a device for optimizing the Energy efficiency in the home, office or building in which the device is located.
Profile
saref:Property
A quality of a feature of interest that can be measured; an aspect of a feature of interest that is intrinsic to and cannot exist without the feature
Property
saref:SensingFunction
A function that allows to transmit data from sensors, such as measurement values (e.g., temperature) or sensing data (e.g., occupancy)
Sensing function
saref:Sensor
A device that detects and responds to events or changes in the physical environment such as light, motion, or temperature changes. Further, a device of category saref:Sensor that performs a saref:SensingFunction.
Sensor
1
1
saref:Service
A service is a representation of a function to a network that makes the function discoverable, registerable, 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.
Service
saref:SetAbsoluteLevelCommand
A type of set level command
Set absolute level command
saref:SetLevelCommand
A type of command
Set level command
saref:SetRelativeLevelCommand
A type of set level command
Set relative level command
saref:Smoke
A saref:Property related to some measurements that are characterized by a certain value that is measured in a unit of measure for smoke
Smoke
saref:SmokeSensor
A sensor that performs the saref:SensingFunction and the saref:EventFunction, and is used for the purpose of sensing a property of type saref:Smoke. A saref:SmokeSensor is typically used to saref:accomplish saref:Safety.
Smoke sensor
saref:StartCommand
A type of command
Start command
saref:StartState
The state of a device that is STARTED
Start state
saref:StartStopFunction
An actuating function that allows to start and stop a device
Start stop function
saref:StartStopState
A type of state
Start stop state
saref:State
The state in which a device can be found, e.g, ON/OFF/STANDBY, or ONLINE/OFFLINE. We propose here a list of states that are relevant for the purpose of SAREF, but this list can be extended.
State
saref:StepDownCommand
A type of command
Step down command
saref:StepUpCommand
A type of command
Step up command
saref:StopCommand
A type of command
Stop command
saref:StopState
The state of a device that is STOPPED
Stop state
saref:Switch
A device of category saref:Actuator that performs an actuating function of type saref:OnOffFunction or saref:OpenCloseFunction
Switch
saref:SwitchOnService
A type of service that represents an on/off function to the network
Switch on service
saref:Task
The goal for which a device is designed (from a user perspective). For example, a washing machine is designed for the task of washing. We propose here a list of tasks that are relevant for the purpose of SAREF, but this list can be extended. Tasks can be accomplished by devices (saref:isAccomplishedBy).
Task
saref:Temperature
A saref:Property related to some measurements that are characterized by a certain value that is measured in a temperature unit (degree_Celsius, degree_Fahrenheit, or degree_kelvin)
Temperature
saref:TemperatureSensor
A sensor that is used for the purpose of sensing a property of type saref:Temperature. A saref:TemperatureSensor is typically used to saref:accomplish saref:Comfort.
Temperature sensor
saref:TemperatureUnit
The unit of measure for temperature
Temperature unit
saref:Time
A class that allows to specify the time concept.
Time
saref:ToggleCommand
A type of command
Toggle command
saref:UnitOfMeasure
The unit of measure is a standard for measurement of a quantity, such as a Property. For example, Power is a property and Watt is a unit of power that represents a definite predetermined power: when we say 10 Watt, we actually mean 10 times the definite predetermined power called "watt". Our definition is based on the definition of unit of measure in the Ontology of units of Measure (OM). We propose here a list of some units of measure that are relevant for the purpose of SAREF, but this list can be extended, also using some other ontologies rather than the Ontology of units of Measure (OM).
Unit of measure
saref:Water
A type of commodity
Water
A type of task for which a device is designed
Cleaning
A type of task for which a device is designed
Comfort
A type of task for which a device is designed
Drying
A type of task for which a device is designed
EnergyEfficiency
A type of task for which a device is designed
Entertainment
A type of task for which a device is designed
Lighting
A type of task for which a device is designed
Meter reading
A type of task for which a device is designed
Safety
A type of task for which a device is designed
Washing
A type of task for which a device is designed
WellBeing
https://saref.etsi.org/core/
v3.1.1
The Smart Applications REFerence ontology (SAREF) is intended to enable interoperability between solutions from different providers and among various activity sectors in the Internet of Things (IoT), thus contributing to the development of the global digital market.
2020-02-11
2020-05-29
SAREF: the Smart Applications REFerence ontology
saref
https://saref.etsi.org/core/
Information about changes compared to version 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, including the reuse of the W3C? WGS84 geo positioning vocabulary.
- 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.
- The information specific for energy efficiency has been moved to the SAREF4ENER extension. 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.
- 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).
- The saref:Property class has been split into two classes (saref:Property and saref:Measurement), as it is done in the SAREF4ENVI extension, 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).
- 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.
- The saref:UnitOfMeasure subclasses use individuals from the OM ontology for unit of measures, 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.
- 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.
- The subclasses of saref:Task have been transormed in individuals.
- 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:
- Added the saref:FeatureOfInterest class and the properties used to relate it to saref:Measurement (saref:hasMeasurement and saref:isMeasurementOf) and to saref:Property (saref:hasProperty and saref:isPropertyOf).
- Added the saref:measurementMadeBy property as inverse of saref:makesMeasurement.
- The saref:relatesToProperty and saref:relatesToMeasurement properties are now inverse of each other.
- The range of saref:hasValue, which was defined as xsd:float, has been removed to support other datatypes for measurements.
- The range of datatype properties, which was defined as xsd:string, has been removed in order to support strings with language tags (rdf:langString). This affects saref:hasDescription, saref:hasManufacturer, saref:hasModel and saref:hasName, which now have implicitly a range of rdfs:Literal.
- The saref:hasName property has been removed and the use of rdfs:label is recommended.
- The saref:hasDescription property has been deprecated and the use of rdfs:comment is recommended.
- Too restrictive restrictions have been removed and in some cases the ontology documentation has been updated to reflect this: a saref:Command having at most one saref:hasDescription; a saref:Task being accomplished by at least one saref:Device; a saref:Device having a typical consumption of only energy or power; a saref:Commodity being measured in units of measure; restrictions on the values of saref:accomplishes that only covered specific use cases; universal restrictions on the saref:actsUpon property have been changed to existential ones; restrictions on the commands that a saref:Function may have, since there could be others not included in the defined enumerations; restrictive documentation of saref:EventFunction and saref:SmokeSensor.
- Bugs have been fixed: some devices (saref:DoorSwitch, saref:EnergyMeter, saref:LigthSwitch, saref:SmokeSensor, and saref:TemperatureSensor) were defined as subclass of a device and at the same time as consisting of such device; a saref:LightSwitch controls light and does not measure light, since it is an actuator; incorrect documentation of saref:OnState and saref:OffState.
- The saref:BuildingRelated, saref:EnergyRelated and saref:FunctionRelated classes have been removed, since the different extensions already classify the device types.
- The instances of the subclasses of saref:Command have been removed, since they represent examples.
- The instances of saref:UnitOfMeasure have been moved to examples.
- The classes related to the SAREF4ENER extension have been removed: saref:Generator, saref:Storage, saref:Load and saref:EnergyMeter.
- Some instances of saref:Device have been moved to examples: saref:WashingMachine, saref:LightingDevice, saref:MicroRenewable, saref:Multimedia, and saref:Network.
- Added domain and range axioms wherever the definition of a property unambiguously identifies the domain or the range of the property.
- The OWL Time ontology is not imported anymore.
- The documentation of some ontology terms has been updated for clarification.
- Language tags have been added to all labels and comments.
v3.1.1