SAREF: the Smart Applications REFerence ontology

Latest version:
https://saref.etsi.org/core/
Permanent IRI for this version (v3.2.1)
https://saref.etsi.org/core/v3.2.1/
Previous version
https://saref.etsi.org/core/
ETSI Technical Specification
https://www.etsi.org/deliver/etsi_ts/103200_103299/103264/03.02.01_60/ts_103264v030201p.pdf
Sources on the SAREF Forge
https://saref.etsi.org/sources/saref-core/
Publication Date
2023-12-31
Last Modification Date
2020-12-31
Creators
Ontology requirements and tests
requirements and tests
Prefix and namespace declaration:
Turtle: @prefix saref: <https://saref.etsi.org/core/> .
SPARQL: PREFIX saref: <https://saref.etsi.org/core/>
Download serialization:
License:

Abstract

NOTE: The text in this section is extracted from ETSI TS 103 264 (V3.2.1) [0], and therefore falls inside the ETSI IPR Policy

SAREF explicitly specifies the recurring core concepts in the Smart Applications domain, the main relationships between these concepts, and axioms to constrain the usage of these concepts and relationships.

Introduction

NOTE: The text in this section is extracted from ETSI TS 103 264 (V3.2.1) [0], and therefore falls inside the ETSI IPR Policy

General Overview

Figure 3 shows an overview of the main classes and properties of SAREF Core.

A detailed explanation of each class is presented in clause 5.2 to clause 5.13.

Overview of the SAREF ontology
Figure 3: Overview of the SAREF ontology

Feature kinds and features of interest

Figure 4 illustrates the main classes and properties for feature kinds and features of interest. SAREF extensions and applications may create, specialize, and categorize feature kinds and features of interest as specified in ETSI TS 103 548 [4], clause 5.2.

Feature kinds and features of interest
Figure 4: Feature kinds and features of interest

Class saref:FeatureOfInterest represents any real world entity from which a property or a state may be acted upon, such as observed and controlled. An instance of saref:FeatureOfInterest represents one specific real world entity.

EXAMPLE 1:
<etsi_premises/athena> a saref:FeatureOfInterest ;
    rdfs:label "ATHENA amphitheatre"@en ;
	rdfs:comment "The ATHENA amphitheatre in the ETSI premises."@en .

<etsi_premises/athena/window5> a saref:FeatureOfInterest ;
    rdfs:label "ATHENA Window 5"@en ;
    rdfs:comment "Window 5 of ATHENA amphitheatre"@en .

Class saref:FeatureKind allows to describe kinds of features of interest, with common properties having the same value, and common states being the same. An instance of saref:FeatureKind represents an archetype of real world entities, for example to populate product catalogs.

EXAMPLE 2:
<1000x2000mmWindowOrientedNorth> a saref:FeatureKind ;
    rdfs:label "1000x2000mm window oriented north"@en ;
    rdfs:comment "The kind of windows with dimensions 1000x2000mm and oriented north."@en .

Feature kinds can be organized in a taxonomy using OPs skos:narrower and skos:broader.

EXAMPLE 3:
<1000x2000mmWindowOrientedNorth> a saref:FeatureKind ;
    skos:broader <1000x2000mmWindow> ;
    skos:broader <WindowOrientedNorth> .

A feature of interest can be linked to its kind(s) using OP saref:hasFeatureKind.

EXAMPLE 4:
<etsi_premises/athena/window5>
 			saref:hasFeatureKind <1000x2000mmWindowOrientedNorth> .
NOTE: Feature of interest inherit broader feature kinds.
saref:hasFeatureKind o skos:broader ⊑ saref:hasFeatureKind
EXAMPLE 5:
<etsi_premises/athena/window5>
    saref:hasFeatureKind <1000x2000mmWindow> ;
    saref:hasFeatureKind <WindowOrientedNorth> .

A feature kind (respectively a feature of interest) may consist of (OP saref:consistsOf) other feature kinds (respectively features of interest).

EXAMPLE 6:
s4abcd:AAHeatPumpDryer a saref:FeatureKind ;
	saref:consistsOf s4abcd:HeatPump , s4abcd:AirCyclingCircuit , s4abcd:Dryer .
EXAMPLE 7:
<etsi_premises/athena> a saref:FeatureOfInterest ;
 		saref:consistsOf <etsi_premises/stage> ;
 		saref:consistsOf <etsi_premises/athena/window5> .

Whenever appropriate, SAREF extensions and applications should also use the classes from SAREF4SYST to specify if a saref:FeatureOfInterest is a system (s4syst:System), a Connection between systems (s4syst:Connection), or a connection point of a system (s4syst:ConnectionPoint).

The model and the manufacturer of a saref:FeatureKind or a saref:FeatureOfInterest can be explicited using DPs saref:hasModel and saref:hasManufacturer, respectively.

EXAMPLE 8:
<ball-bearing-xsd215sd7f> a saref:FeatureOfInterest ;
		saref:hasManufacturer "Company X"@en ;
	saref:hasModel "6000-2RZ1 "@en .

Devices

Figure 5 illustrates the main classes and properties for devices. SAREF extensions and applications may create, specialize, and categorize devices as specified in ETSI TS 103 548 [4], clause 5.3.

Devices
Figure 5: Devices

Class saref:Device represents any tangible object designed to accomplish a particular task by performing one or more functions. An instance of saref:Device represents one specific real world entity.

EXAMPLE 1: Examples of devices are a light switch, a temperature sensor, an energy meter, a water flow meter, and a laundry dryer. A laundry dryer is designed to dry laundry, and to accomplish this task it has a start/stop function.
EXAMPLE 2:
ex:Meter4837QW123 a saref:Device ;
    rdfs:label "Meter 4837QW123"@en ;
    rdfs:comment "The meter that measures the incoming water flow of the Computer Science school."@en .
EXAMPLE 3:
ex:Dryer354A1E08FA a saref:Device ;
    rdfs:label "Dryer 354A1E08FA"@en ;
    rdfs:comment "The laundry dryer with serial number 354A1E08FA"@en.

Devices are also systems (s4syst:System) and features of interest (saref:FeatureOfInterest).

A device can be linked to its feature kinds using OP saref:hasDeviceKind. Kinds of devices describe models of devices, with common properties having the same value, common states being the same, common functions, and common services. OP saref:hasDeviceKind is a sub-property of OP saref:hasFeatureKind.

EXAMPLE 4:
ex:Meter4837QW123 saref:hasDeviceKind s4abcd:SmartWaterMeterABC123 .
s4abcd:SmartWaterMeterABC123 a saref:FeatureKind ;
	rdfs:label "Smart Water Meter ABC123"@en ;
	rdfs:comment "The smart water meter ABC123 of manufacturer ABC. A device kind."@en .

A device can act upon (OP saref:actsUpon) features, properties, or states. SAREF Core defines different sub-properties of saref:actsUpon:

  • saref:observes for when a device observes a feature, or property or state of that feature.
  • saref:controls for when a device controls a feature, or property or state of that feature.
NOTE: Property saref:actsUpon also applies to functions, commands, and procedure executions.
EXAMPLE 5:
s4abcd:AAHeatPumpDryer a saref:FeatureKind ;
	saref:controls s4abcd:DryerRotationalSpeed ;
	saref:controls s4abcd:DryerTemperature ;
	saref:observes s4abcd:LaudryBatchHumidity .

As shown in Figure 6, SAREF Core provides some examples of classes of devices including appliances, sensors, actuators, and meters. Their definitions are the following:

  • saref:Appliance: The class of devices designed to accomplish a particular task for occupant use. It consumes, produces, or stores, some commodity.
  • saref:Sensor: A device designed to observe one or more properties or states of one or more features of interest.
  • saref:Actuator: A device designed to control one or more properties or states of one or more features of interest.
  • saref:Meter: A device designed to observe and measure one or more properties of one or more features of interest.
Categories of devices
Figure 6: Categories of devices

Tasks

Class saref:Task represents goals for which a device is designed, from a user perspective.

SAREF extensions and applications may create, specialize, and categorize tasks as specified in ETSI TS 103 548 [4], clause 5.4 and illustrated on Figure 7.

Taxonomy of tasks, grouped by categories
Figure 7: Taxonomy of tasks, grouped by categories

Tasks can be organized in a taxonomy using OPs skos:narrower and skos:broader.

EXAMPLE 1: Example of tasks are cleaning, drying, and lighting.
saref:Drying a saref:Task ;
    rdfs:label "Drying"@en ;
    rdfs:comment "A type of task for which a device is designed."@en .

Device kinds and devices can be linked to the one or more tasks they are designed to accomplish with OP saref:accomplishes.

EXAMPLE 2:
s4abcd:AAHeatPumpDryer a saref:FeatureKind ;
    saref:accomplishes s4abcd:DryingLaundry .
EXAMPLE 3:
ex:switch21354 a saref:Device ;
    saref:hasDeviceKind s4abcd:Switch ;
    saref:accomplishes s4abcd:Lighting .
NOTE: Property saref:accomplishes can also apply to other classes such as functions, commands, and procedure executions.

Commodities

Class saref:Commodity represents marketable items which may be supplied without qualitative differentiation. Commodities may be consumed, produced, or stored, by some feature of interest or device.

SAREF extensions and applications may create, specialize, and categorize commodities as specified in ETSI TS 103 548 [4], clause 5.5 and illustrated on Figure 8.

Taxonomy of commodities, grouped by categories
Figure 8: Taxonomy of commodities, grouped by categories

Commodities can be organized in a taxonomy using OPs skos:narrower and skos:broader.

SAREF Core defines the category of energy commodities that groups electricity, gas, propane (of kind gas), coal. It furthermore defines the category of natural resource commodity.

Categories of commodities
Figure 9: Categories of commodities
EXAMPLE 1:
s4abcd:Electricity a saref:EnergyCommodity ;
    rdfs:label "Electricity"@en ;
    rdfs:comment "The electricity energy commodity."@en .

A feature kind, feature of interest, or device, can consume (OP saref:consumes), produce (OP saref:produces), or store (OP saref:stores), a certain commodity.

EXAMPLE 2:
s4abcd:AAHeatPumpDryer a saref:FeatureKind ;
    saref:consumes s4abcd:Electricity ;
    saref:produces s4abcd:Water .

Properties, properties of interest, and property values

Introduction

In SAREF, properties refer to the identifiable qualities of features of interest that can be acted upon by devices, such as observed or controlled. While properties can apply to different features of interest, properties of interest are specific to a feature of interest. Property values describe the value for a property.

Figure 10 illustrates the main classes and properties for describing properties, properties of interest, and property values.

SAREF extensions and applications may create, specialize, and categorize properties as specified in ETSI TS 103 548 [4], clause 5.6.

Properties, properties of interest, and property values
Figure 10: Properties, properties of interest, and property values

Properties

An instance of saref:Property can apply to different features of interest.

EXAMPLE 1: Air temperature, pressure, luminance, etc. are all properties.
s4abcd:Temperature a saref:Property ;
	rdfs:label "Temperature"@en ;
	rdfs:comment "The temperature property kind."@en . 
s4abcd:Pressure a saref:Property ;
	rdfs:label "Pressure"@en ;
	rdfs:comment "The pressure property kind."@en .
s4abcd:Luminance a saref:Property ;
	rdfs:label "Temperature"@en ;
	rdfs:comment "The luminance property kind."@en .
NOTE 1: Until SAREF V3.1.1 [i.7], there was an ambiguity between whether properties should be specific or generic to features of interest. This ambiguity has been solved in SAREF V3.2.1 (the present document), and the new modeling choice will be enforced in the next release of SAREF.

Properties can be organized in a taxonomy using properties skos:narrower and skos:broader.

NOTE 2: Concepts from existing code lists, vocabularies, and taxonomies, may be used as instances of saref:Property.
EXAMPLE 2: Two examples using the QUDT Quantity Kind vocabulary [i.22], and the British Oceanographic Data Centre Parameter Usage Vocabulary [i.24].
<https://qudt.org/2.1/vocab/quantitykind/ActiveEnergy> a saref:Property ;
	rdfs:label "Active Energy"@en ;
	rdfs:comment "\"Active Energy\" is the electrical energy transformable into some other form of energy."@en .

<http://vocab.nerc.ac.uk/collection/P01/current/CDTSZZ01/> a saref:Property ;
	skos:prefLabel "Absolute temperature standard deviation of the atmosphere by dry bulb thermometer"@en .

The OP saref:hasProperty may be used to link a feature kind or feature of interest to its properties. Its inverse is saref:isPropertyOf.

EXAMPLE 3:
	s4abcd:AAHeatPumpDryer a saref:FeatureKind ;
saref:hasProperty s4abcd:DryerRotationalSpeed ;
saref:hasProperty s4abcd:DryerTemperature .
NOTE 3: Feature kinds inherit the properties of their broader feature kinds.
skos:broader o saref:hasProperty ⊑ saref:hasProperty
NOTE 4: Features of interest inherit the properties of their feature kinds.
  saref:hasFeatureKind o saref:hasProperty ⊑ saref:hasProperty

Properties of interest

An instance of saref:PropertyOfInterest is specific to a feature of interest. It is inherent to and cannot exist without that feature of interest.

EXAMPLE 1: The air temperature of the atmosphere sample at a certain location and altitude, the received signal strength indicator of a wireless IoT connection, the luminance of the ETSI ATHENA amphitheatre.

The OP saref:hasPropertyOfInterest may be used to link a feature of interest to its properties of interest.

Its inverse is saref:isPropertyOfInterestOf and is functional.

A property of interest is the property of (OP saref:isPropertyOfInterestOf) exactly one feature of interest.

NOTE 1: Properties of interest need not always be explicited. It depends on the use case. Typically, properties of interest are useful in applications, where the association between a feature of interest and a property (i.e. the property of interest) needs to be identified and related to other properties of interest.

Given a property of interest belongs to exactly one feature of interest, it is recommended that its identifier consists of the identifier of the feature of interest, followed by character '#' and a fragment identifier. The fragment identifier part of the IRI of a property of interest should not contain "property".

EXAMPLE 2: The luminance of the ETSI ATHENA amphitheatre belongs to the ETSI ATHENA amphitheatre.
<etsi_premises/athena#luminance> a saref:PropertyOfInterest ;
	saref:isPropertyOfInterestOf <etsi_premises/athena> ; 
	rdfs:comment "The luminance of amphitheatre ATHENA"@en .

A property of interest can be linked to its kind(s) using OP saref:hasPropertyKind.

NOTE 2: Properties of interest inherit broader properties.
saref:hasPropertyKind o skos:broader ⊑ saref:hasPropertyKind
EXAMPLE 3: The luminance of the ETSI ATHENA amphitheatre is of kind luminance.
<etsi_premises/athena#luminance> a saref:PropertyOfInterest ;
	saref:hasPropertyKind saref:Luminance .
NOTE 3: Features of interest inherit the property kinds of their properties of interest.
saref:hasPropertyOfInterest o saref:hasPropertyKind ⊑ saref:hasProperty
EXAMPLE 4: The ETSI ATHENA amphitheatre has a property luminance.
<etsi_premises/athena> a saref:FeatureOfInterest ;
	saref:hasPropertyOfInterest <etsi_premises/athena#luminance> ;
	saref:hasProperty saref:Luminance .

Property Values

Class saref:PropertyValue describes the value for a property. The property value is linked to its value expressed as an RDF literal (DP saref:hasValue), optionally to the unit of measurement (OP saref:isMeasuredIn), and optionally to the properties or properties of interest it is a value of (OP saref:isValueOfProperty).

EXAMPLE 1:
[] a saref:PropertyValue ;
    saref:hasValue 22.7
    saref:isMeasuredIn <https://qudt.org/2.1/vocab/unit/DEG_C> .

The range of saref:isMeasuredIn is defined as saref:UnitOfMeasure.

NOTE 1: Concepts from existing code lists, vocabularies, and taxonomies, may be used as instances of saref:UnitOfMeasure. For example the QUDT Unit vocabulary [i.23].

The OP saref:hasPropertyValue links a feature kind, a feature of interest, or a property of interest, to a property value.

EXAMPLE 2:
<etsi_premises/athena#size> a saref:PropertyOfInterest ;
    saref:isPropertyOf <etsi_premises/athena> ;
    saref:hasPropertyValue [
        a saref:PropertyValue ;
        saref:hasValue 105.0 ;
        saref:isMeasuredIn <https://qudt.org/2.1/vocab/unit/M2> ] .
NOTE 2: The property values are inherited in the hierarchy of feature kinds. This enables to incrementally construct prototypical descriptions of features of interest.
  skos:broader saref:hasPropertyValue ⊑ saref:hasPropertyValue
NOTE 3: A feature of interest does not inherit the property values of its kinds. There may be multiple reasons why the property value of a feature of interest is different from that of its prototypical descriptions. For example, it may be caused by a defect, a deterioration, or a customization.

The OP saref:isValueOfProperty links a property value to the properties and properties of interest it is a value of.

EXAMPLE 3:
<1000x2000mmWindowOrientedNorth> a saref:FeatureKind ;
    saref:hasProperty <WindowArea> ;
    saref:hasPropertyValue [
        a saref:PropertyValue ;
        saref:hasValue 2.0 ;
        saref:isMeasuredIn <https://qudt.org/2.1/vocab/unit/M2> ;
        saref:isValueOfProperty <WindowArea> ] .
NOTE 4: A property value about a property of interest is also a property value of its property kinds.
  saref:isValueOfProperty o saref:hasPropertyKind ⊑ saref:isValueOfProperty
NOTE 5: saref:hasPropertyValue and saref:isValueOfProperty are not inverse properties.

States and states of interest

Introduction

In SAREF, states refer to the identifiable conditions that features of interest are or may be in, and that can be acted upon by devices, such as observed and controlled. While states can apply to different features of interest, states of interest are specific to a feature of interest.

Figure 11 illustrates the main classes and properties for describing states and states of interest.

SAREF extensions and applications may create, specialize, and categorize states as specified in ETSI TS 103 548 [4], clause 5.7.

States and states of interest
Figure 11: States and states of interest

States

An instance of saref:State can apply to different features of interest.

EXAMPLE 1: A switch can be found in the saref:OnOffState, which is further specialized in saref:OnState and saref:OffState.
saref:OnOffState a saref:State .
saref:OnState a saref:State ;
    skos:broader saref:OnOffState .
	saref:OffState a saref:State ;
    skos:broader saref:OnOffState .
 	s4abcd:Switch a saref:FeatureKind ;
 	saref:hasState saref:OnOffState .
NOTE 1: SAREF is not restricted to binary states such as the saref:OnOffState, but allows to define also n-ary states (see, for example, the saref:MultiLevelState class).

States can be organized in a taxonomy using properties skos:narrower and skos:broader.

NOTE 2: Concepts from existing code lists, vocabularies, and taxonomies, may be used as instances of saref:State.

The OP saref:hasState may be used to link a feature kind to its states. Its inverse is saref:isStateOf.

EXAMPLE 2:
s4abcd:TwoButtonsOneWaySwitch a saref:FeatureKind ;
	saref:hasState s4abcd:Button1UpDownState , s4abcd:Button2UpDownState .
s4abcd:Button1UpDownState a saref:State ;
	skos:broader s4abcd:ButtonUpDownState .
s4abcd:Button2UpDownState a saref:State ;
	skos:broader s4abcd:ButtonUpDownState .

The narrowest states of the taxonomy of states can be considered as the state values.

EXAMPLE 3: s4abcd:ButtonUp and s4abcd:ButtonDown can be considered as the possible values for state s4abcd:ButtonUpDownState.
s4abcd:ButtonUp a saref:State ;
	skos:broader s4abcd:ButtonUpDownState .
s4abcd:ButtonDown a saref:State ;
	skos:broader s4abcd:ButtonUpDownState .
NOTE 3: Feature kinds inherit the states of their broader feature kinds.
skos:broader o saref:hasState ⊑ saref:hasState
NOTE 4: Features of interest inherit the states of their feature kinds.
saref:hasFeatureKind o saref:hasState ⊑ saref:hasState

States of Interest

An instance of saref:StateOfInterest is specific to a feature of interest. It is inherent to and cannot exist without that feature of interest.

The OP saref:hasStateOfInterest may be used to link a feature of interest to its states of interest.

Its inverse is saref:isStateOfInterestOf and is functional.

A state of interest is the state of (OP saref:isStateOfInterestOf) exactly one feature of interest.

NOTE 1: States of interest need not always be explicited. It depends on the use case. Typically, states of interest are useful in applications where the association between a feature of interest and a state (i.e. the state of interest) needs to be identified and related to other states of interest.

Given a state of interest belongs to exactly one feature of interest, it is recommended that its identifier consists of the identifier of the feature of interest, followed by character '#' and a fragment identifier. The fragment identifier part of the IRI of a property of interest should not contain "state".

EXAMPLE 1: Switch has two up/down states of interest.
<switch_sdf5ze4fz3> a saref:Device ;
    saref:hasDeviceKind s4abcd:TwoButtonsOneWaySwitch ; 
    saref:hasState <switch_sdf5ze4fz3#btn1>, <switch_sdf5ze4fz3#btn2> .
<switch_sdf5ze4fz3#btn1> a saref:StateOfInterest ;
    saref:hasStateKind s4abcd:Button1UpDownState .
<switch_sdf5ze4fz3#btn2> a saref:StateOfInterest ;
    saref:hasStateKind s4abcd:Button2UpDownState .

A state of interest can be linked to its kind(s) using OP saref:hasStateKind.

NOTE 2: States of interest inherit broader states.
  saref:hasStateKind o skos:broader ⊑ saref:hasStateKind
NOTE 3: Features of interest inherit the state kinds of their states of interest.
  saref:hasStateOfInterest o saref:hasStateKind ⊑ saref:hasState

As the narrowest states of the taxonomy of states can be thought of as the state values, it is possible to assign a stable value to a state as follows:

EXAMPLE 2: Button 2 of switch is in stable up position.
<switch_sdf5ze4fz3#btn2> a saref:StateOfInterest ;
    saref:hasStateKind s4abcd:Button2UpDownState ;
    saref:hasState s4abcd:ButtonUp .

Functions and functions of interest

Introduction

In SAREF, functions are logical groups of commands that devices support to accomplish their tasks. Function can act upon (OP saref:actsUpon and its sub-properties) features, properties, or states. While functions are independent of any devices, functions of interest are functions actually supported by a device.

Figure 12 illustrates the main classes and properties for describing functions and functions of interest.

SAREF extensions and applications may create, specialize, and categorize functions as specified in ETSI TS 103 548 [4], clause 5.8.

Functions and functions of interest
Figure 12: Functions and functions of interest

Functions

An instance of saref:Function can apply to different devices.

EXAMPLE 1: To accomplish the task of controlling the light, a smart light switch may have a function for turning on and off the light, and another to set the luminosity of the light.
EXAMPLE 2: To accomplish the task of sensing the temperature, a temperature sensor should have a sensing function.
EXAMPLE 3: To accomplish the task of washing clothes, a washing machine should have a function for washing.

Functions can be organized in a taxonomy using properties skos:narrower and skos:broader.

NOTE 1: Concepts from existing code lists, vocabularies, and taxonomies, may be used as instances of saref:Function.

Kinds of devices can be defined from pre-defined building blocks, based on the functions they have.

EXAMPLE 4:
s4abcd:AAHeatPumpDryer a saref:FeatureKind ;
    saref:hasFunction s4acd:WashingFunction .

The OP saref:hasFunction may be used to link a feature kind or device to its functions. Its inverse is saref:isFunctionOf.

NOTE 2: Feature kinds inherit the functions of their broader feature kinds.
skos:broader o saref:hasFunction ⊑ saref:hasFunction
NOTE 3: Devices inherit the functions of their device kinds.
  saref:hasDeviceKind o saref:hasFunction ⊑ saref:hasFunction

Functions of Interest

An instance of saref:FunctionOfInterest is supported by exactly one device.

The OP saref:hasFunctionOfInterest may be used to link a device to its function of interest.

Its inverse is saref:isFunctionOfInterestOf and is functional.

A function of interest is the function of (OP saref:isFunctionOfInterestOf) exactly one device.

NOTE 1: Functions of interest need not always be explicited. It depends on the use case. Typically, functions of interest are useful to specify which command is actually exposed, and which actual property of interest or state of interest it acts upon.

A function of interest can be linked to its kind(s) using OP saref:hasFunctionKind.

NOTE 2: Functions of interest inherit broader functions.
saref:hasFunctionKind o skos:broader ⊑ saref:hasFunctionKind
NOTE 3: Devices inherit the function kinds of their functions of interest.
saref:hasFunctionOfInterest o saref:hasFunctionKind ⊑ saref:hasFunction

Commands and commands of interest

Introduction

In SAREF, commands represent the lowest-level directives a device supports and exposes to some network. Commands can act upon (OP saref:actsUpon and its sub-properties) features, properties, or states. While commands are independent of any function, commands of interest are commands actually supported by a function of interest.

Figure 13 illustrates the main classes and properties for describing commands and device commands.

SAREF extensions and applications may create, specialize, and categorize commands as specified in ETSI TS 103 548 [4], clause 5.8.

Command kinds and device commands
Figure 13: Command kinds and device commands

Commands

An instance of saref:Command is independent of any device.

EXAMPLE 1: Observe property, control property, observe state, control state, invoke action, cancel action, turn on or off, change color, subscribe, publish, etc. are all commands.

Commands can be organized in a taxonomy using OPs skos:narrower and skos:broader. Functions can be defined from pre-defined building blocks, based on the commands they have.

The OP saref:hasCommand may be used to link a function or function of interest to its commands. Its inverse is saref:isCommandOf. SAREF Core defines two sub-properties of saref:hasCommand, that only apply to functions:

NOTE 1: Functions inherit the mandatory commands of their broader functions.
skos:broader o saref:hasMandatoryCommand ⊑ saref:hasMandatoryCommand
NOTE 2: Functions of interest inherit the mandatory commands of their function kinds.
saref:hasFunctionKind o saref:hasMandatoryCommand ⊑ saref:hasCommand

A command may be described in terms of its input parameters using OP saref:hasInput. Typically, input parameters are feature kinds, properties, or states.

EXAMPLE 2: Different complementary commands can be defined for controlling a light. Turn on or off the light based on a desired state, toggle the light status of a specific light, set the luminosity level with a transition time, set the default transition time.

A command may be described in terms of its outputs using OP saref:hasOutput. Typically, outputs are properties or states.

EXAMPLE 3: Different complementary commands can be defined for observing a smart home. Observe the temperature once will output the indoor temperature property; observe status of the entry door will output an open/close state.

A command may be described in terms of the properties or states it acts upon, such as observe, or control.

Commands of Interest

A saref:CommandOfInterest is a directives actually supported by a device and exposed to some network.

Like for commands, commands of interest may be described in terms of their input parameters, outputs, and of which properties or states they act upon.

The OP saref:hasCommandOfInterest may be used to link a function of interest to its command of interest.

Its inverse is saref:isCommandOfInterestOf and is functional.

A command of interest is the command of (OP saref:isCommandOfInterestOf) exactly one function.

NOTE 1: Commands of interest need not always be explicited. It depends on the use case. Typically, commands of interest are useful to specify the actual property of interest or state of interest that is expected as input parameter, output, or that will be acted upon.
EXAMPLE 4: The corridor smart light switch supports a command of kind "turn on/off", which controls the state of the outdoor light.
EXAMPLE 5: The smart fridge supports a command of kind "observes temperature", which observes the temperature of the fridge.

A command of interest can be linked to its kind(s) using OP saref:hasCommandKind.

NOTE 2: Commands of interest inherit broader commands.
saref:hasCommandKind o skos:broader ⊑ saref:hasCommandKind
NOTE 3: Devices inherit the commands of their commands of interest.
saref:hasCommandOfInterest o saref:hasCommandKind ⊑ saref:hasCommand

Services and Operations

Figure 14 illustrates the main classes and properties for describing services and operations.

Services and operations
Figure 14: Services and operations

A saref:Service is a digital representation of a function in a network, making it discoverable, registerable and remotely controllable in the network.

OP saref:represents links a service to some function or function of interest it exposes to the network.

A service represents at least one function of interest.

OP saref:offers links a device to a service it exposes to a network. Its inverse if saref:isOfferedBy.

A service is offered by exactly one device.

NOTE 1: Typically, a device connected to a given network offers one service for each of its functions of interest.
EXAMPLE 1: A light switch can offer the service of remotely switching the lights in a home through mobile phone devices that are connected to the local network (ex:SwitchOnService class). This "remote switching" service represents the ex:OnOffFunction.

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.

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.

EXAMPLE 2: To turn on a light, send a CoAP PUT request with CBOR content `0xf5` (true).

OP saref:represents also links an operation to some command or command of interest it exposes to the network. An operation represents at least one command of interest.

OP saref:hasOperation links a service to its operations. Its inverse is saref:isOperationOf.

An operation belongs to exactly one service.

NOTE 2: 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.
EXAMPLE 3: 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).
EXAMPLE 4: 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.
NOTE 3: The concept of service is further elaborated in the oneM2M Base Ontology [1], to which the reader is referred in order to model the details of a service that are out of the scope of SAREF.

Procedure executions and sub-classes

Procedure executions

A saref:ProcedureExecution represents the act of carrying out a procedure.

Figure 15 illustrates the main properties for describing procedure executions.

Procedure executions
Figure 15: Procedure executions

OP saref:madeBy links a procedure execution to the device that made it.

A procedure execution may be linked to its inputs using OP saref:hasInput.

A procedure execution may be linked to its result using OP saref:hasResult.

DP saref:hasResultTime links a procedure execution to the instant of time when the procedure is completed, expressed as an xsd:dateTime literal.

OP saref:hasPhenomenonTime links a procedure execution to the time that the result applies. It may be an interval or an instant, or some other compound temporal entity expressed using OWL Time [7].

When the execution time and the phenomenon time are the same time instants, then DP saref:hasTimestamp can be used to simply link a procedure execution to the time of these instants, expressed as an xsd:dateTime literal.

Optionally, a procedure execution can act upon (OP saref:actsUpon) a feature, property, or state.

Command executions and operation executions

Figure 16 illustrates the main classes and properties for describing command executions and operation executions.

Command executions and operation executions
Figure 16: Command executions and operation executions

A saref:CommandExecution describes the execution of a command. Typically, its inputs and outputs are human understandable and relate to some feature of interest, such as its state (e.g. s4abcd:On), or the value of its temperature (e.g. property value 21,0 °C).

A saref:OperationExecution describes the execution of an operation in a network: the-machine interpretable- description of a communication between devices over the network. Typically, its input and result are network messages, that conform to the input and output of the executed operation.

EXAMPLE 1: A CoAP PUT request with CBOR content `0xf5` (true), a CoAP response with code `2.04` (Changed).

OP saref:isExecutionOf links a command execution to the command or command of interest that was executed.

It also liks an operation execution to the operation that was executed.

NOTE 1: If a command execution is an execution of a command, it is also the execution of its broader commands.
saref:isExecutionOf o skos:broader ⊑ saref:isExecutionOf
NOTE 2: If a command execution is an execution of a command of interest, it is also the execution of the command kind of that command of interest.
saref:isExecutionOf o saref:hasCommandKind ⊑ saref:isExecutionOf

Observations, Measurements, and Actuations

Figure 17 illustrates the main classes and properties for describing observations, measurements, and actuations.

Observations, measurements, and actuations
Figure 17: Observations, measurements, and actuations

A saref:Observation is the act of carrying out a procedure to estimate or calculate a value of a property of a feature of interest, or a state of a feature of interest. It links to a sensor to describe what made the observation, and to the observed feature, property, property of interest, state, or state of interest. Typically, its result is a property value or a state. An observation of a state (OP saref:observes) should have a state as a result (OP saref:hasResult). Respectively, an observation of a property should have a property value as a result.

EXAMPLE 2:
ex:DTSObservation106 a saref:Observation ;
	saref:madeBy <meter> ;
  saref:hasTimestamp "2023-12-06T21:01:10"^^xsd:dateTime ;
	saref:observes s4watr:Cadmium ;
saref:hasResult ex:Meter4837QW123Value184 .
ex:Meter4837QW123Value184 a saref:PropertyValue ;
  saref:isValueOfProperty s4watr:Cadmium ;
	saref:hasValue 0.005 .
EXAMPLE 3:
[] a saref:Observation ;
  saref:madeBy <sensor> ;
 	saref:hasTimestamp "2023-12-06T21:47:10"^^xsd:dateTime .
saref:observes <door_zef53ze7> ;
    saref:observes <door_zef53ze7#openclose> ;
	saref:observes saref:OpenClose ;
saref:hasResult saref:Open .
NOTE 3: saref:Observation is more general than saref:Measurement, as it apply to states in addition to properties. The indirection saref:hasResult to a property value improves its semantic correctness. It also improves the alignment with the OGC® and W3C® SOSA/SSN ontology [6]. Therefore, saref:Measurement has been deprecated in the present document, and may be deleted in the next release of SAREF.

A saref:Actuation is the act of carrying out a procedure to control the state of the world using an actuator. It links to an actuator to describe what made the actuation, and to the controlled feature, property, property of interest, state, or state of interest. Typically, its input is a property value or a state. An actuation of a state (OP saref:controls) should have a state as input (OP saref:hasInput). Respectively, an actuation of a property should have a property value as input.

NOTE 4: An observation or an actuation may also be a command execution, if it corresponds to the execution of a directives a device supports and exposes to some network. However, an observation or an actuation should not be an operation execution, as these are intended to be machine interpretable descriptions of network communications.
NOTE 5: It is acceptable that the inputs or results of a command execution are observations or actuations. For example:
  • A command execution to aggregate observations will have these observations as input.
  • A command execution to retrieve the past five observations will have these observations as output.
  • A command execution to plan a series of actuations will have these actuations as input, and potentially also as result if successful.

Profiles

A device in SAREF can be further characterized by profiles. Figure 18 illustrates the main classes and properties for describing profiles.

Profiles
Figure 18: Profiles

A saref:Profile describes the money earned (negative values) or paied (positive values) for the use (production or consumption) of a commodity by a device in a certain context.

OP saref:hasProfile links a device to its profile. Its inverse is saref:isProfileOf. The device should be linked to a certain commodity using OP saref:isUsedFor or its sub-properties, and optionally to some property or state using OP saref:actsUpon or its sub-properties.

EXAMPLE 1:
ex:Device_1 a saref:Device ;
	saref:isUsedFor s4abcd:Electricity ;
	saref:hasProfile ex:FlexibilityProfile ;
	saref:controls <house#temperature> .
ex:FlexibilityProfile a saref:Profile ;
	saref:hasPrice <pricePropertyValue> .

The applicable context of a profile can be bound temporally using DP saref:hasTimestamp or its subproperties defined by SAREF extensions, or OP saref:hasApplicableTime which links to instant or interval or other compound temporal entity expressed using OWL Time [7].

NOTE: saref:hasApplicableTime may be applied to other entities, such as functions, commands, or procedure executions.
EXAMPLE 2:
ex:FlexibilityProfile [saref:hasTimestamp](#saref:hasTimestamp) "2023-12-15T11:00:00"^^xsd:dateTime .
EXAMPLE 3:
ex:FlexibilityProfile
	rdfs:comment "applies only on Saturdays"@en ;
saref:hasApplicableTime [ 
		a time:DateTimeDescription ;
		time:dayOfWeek time:Saturday ] .

The applicable context can be restricted to when the property of a feature of interest has some value (OPs saref:whenPropertyValue).

EXAMPLE 4:
ex:FlexibilityProfile
saref:whenPropertyValue [
    a saref:PropertyValue ;
    saref:hasValue 22.0 ;
    saref:isMeasuredIn <http://qudt.org/vocab/unit/DEG_C> ;
 	saref:isValueForProperty <house#comfort_temperature_setpoint> ] .

The applicable context can be restricted to when a feature of interest has a certain state (OPs saref:whenState).

EXAMPLE 5:
ex:FlexibilityProfile
saref:whenState [
    a saref:State ;
    skos:broader s4abcd:ComfortSetpoint ;
 	saref:isStateOf <house#temperature_setpoint> ] .

OP saref:profileHasPrice links a profile to the money earned (negative values) or paid (positive values) for the use (production or consumption) of the commodity by the device.

EXAMPLE 6:
ex:FlexibilityProfile
saref:profileHasPrice [
    a saref:PropertyValue ;
    saref:hasValue 0.2 ;
    saref:isMeasuredIn <http://qudt.org/vocab/currency/EUR> ] .	

A set of specializations of a Profile is given via the Flexibility Profile defined in the SAREF4ENER extension in ETSI TS 103 410-1 [i.8]. Each Flexibility Profile describes the ways in which a device can regulate its energy consumption and production. Therefore, the Flexibility Profile is a static set of options to choose from and a set of user preferences, instead of a pre-calculated energy usage time series. The details of each Flexibility Profile can be specified using the related extensions. A specialization of a Profile may additionally relate to other SAREF classes via properties defined in the extensions, including, but not limited to a state, property, property value, function, and command.

EXAMPLE 7:
ex:FlexibilityProfile a saref:Profile ;
	s4abcd:{someConditionDefinedBySAREF4ABCD} <conditionSpecification> .

Features of Interest, devices, and spatial objects

An instance may be classified as both saref:FeatureOfInterest and geo:SpatialObject.

The class saref:Device is a sub-class of geo:Feature from the GeoSPARQL standard [8], section 6.2.

SAREF application may attach a geometry to a saref:FeatureOfInterest or a saref:Device using geo:hasGeometry or its sub-properties geo:hasBoundingBox, geo:hasCentroid, geo:hasDefaultGeometry [8], section 6.4.

EXAMPLE 1:
<etsi_premises> a saref:FeatureOfInterest , geo:Feature ; 
	geo:hasCentroid "POINT( 7.052986 43.6169446 )"^^geo:wktLiteral .

SAREF application may describe how things are spatially related using different families of topological relations from GeoSPARQL, such as the Simple Features relation family (e.g. geo:sfWithin, geo:sfOverlaps), the Egenhoer Relation Family (e.g. geo:ehInside, geo:ehOverlap), the RCC8 Relation Family (e.g. geo:rcc8tpp, geo:rcc8po) [8], section 7.

EXAMPLE 2:
<etsi_premises/athena> a saref:FeatureOfInterest , geo:Feature ; 
	geo:sfWithin <etsi_premises> .

Namespace Declarations

default namespace:
https://saref.etsi.org/core/
owl:
http://www.w3.org/2002/07/owl#
saref:
https://saref.etsi.org/core/
xsd:
http://www.w3.org/2001/XMLSchema#
skos:
http://www.w3.org/2004/02/skos/core#
rdfs:
http://www.w3.org/2000/01/rdf-schema#
rdf:
http://www.w3.org/1999/02/22-rdf-syntax-ns#
xml:
http://www.w3.org/XML/1998/namespace
s4syst:
https://saref.etsi.org/saref4syst/
dcterms:
http://purl.org/dc/terms/
time:
http://www.w3.org/2006/time#
vann:
http://purl.org/vocab/vann/
foaf:
http://xmlns.com/foaf/0.1/

Classes

Actuating function ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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)

Actuation back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Actuation

A saref:Actuation is the act of carrying out a procedure to control the state of the world using an actuator. It links to an actuator to describe what made the actuation, and to the controlled feature, property, property of interest, state, or state of interest. Typically, its input is a property value or a state. An actuation of a state (OP saref:controls) should have a state as input (OP saref:hasInput). Respectively, an actuation of a property should have a property value as input.

Actuator back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Actuator

A device designed to control one or more properties or states of one or more features of interest.

has super-classes
saref:Devicec
saref:controlsop min 1
has sub-classes
saref:Switchc

Appliance back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Appliance

A device designed to accomplish a particular task for occupant use. It consumes, produces, or stores, some commodity.

has super-classes
saref:Devicec
saref:isUsedForop min 1

Close command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/CloseCommand

A type of command

has super-classes
saref:Commandc

Close state ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/CloseState

The state of a device that is CLOSE

has super-classes
saref:OpenCloseStatec

Coal ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Coal

A type of commodity

has super-classes
saref:Commodityc

Command back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Command

The lowest-level directives a function exposes to some network. Commands can act upon (OP saref:actsUpon and its sub-properties) features, properties, or states. An instance of saref:Command is independent of any device.

Command Execution back to ToC or Class ToC

IRI: https://saref.etsi.org/core/CommandExecution

Describes the execution of a command. Typically, its inputs and outputs are human understandable and relate to some feature of interest, such as its state (e.g., s4abcd:On), or the value of its temperature (e.g., property value 21.0 °C).

Command Of Interest back to ToC or Class ToC

IRI: https://saref.etsi.org/core/CommandOfInterest

The lowest-level directives a device supports and exposes to some network. Commands can act upon (OP saref:actsUpon and its sub-properties) features, properties, or states. A saref:CommandOfInterest is a directives actually supported by a device and exposed to some network.

Commodity back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Commodity

A marketable item which may be supplied without qualitative differentiation.

Currency ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Currency

The class of units of measure for price

has super-classes
saref:UnitOfMeasurec

Device back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Device

A tangible object designed to accomplish a particular task. In order to accomplish this task, the device performs one or more functions. An instance of saref:Device represents one specific real world entity.

Door switch ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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.

has super-classes
saref:Switchc

Electricity ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Electricity

A type of energy commodity

has super-classes
saref:Commodityc

Energy ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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.

has super-classes
saref:Propertyc

Energy Commodity back to ToC or Class ToC

IRI: https://saref.etsi.org/core/EnergyCommodity

The class of energy commodities

has super-classes
saref:Commodityc

Energy unit ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/EnergyUnit

The unit of measure for energy

has super-classes
saref:UnitOfMeasurec

Event function ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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.

has super-classes
saref:Functionc
is in domain of
saref:hasThresholdMeasurementc

Feature kinds back to ToC or Class ToC

IRI: https://saref.etsi.org/core/FeatureKind

Feature kinds allow to describe kinds of features of interest, with common properties having the same value, and common states being the same. An instance of saref:FeatureKind represents an archetype of real world entities, for example to populate product catalogs.

Feature of interest back to ToC or Class ToC

IRI: https://saref.etsi.org/core/FeatureOfInterest

A feature of interest represents any real world entity from which a property or a state may be acted upon, such as observed and controlled. An instance of saref:FeatureOfInterest represents one specific real world entity.

Function back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Function

Logical groups of commands that devices support to accomplish their tasks. Function can act upon (OP saref:actsUpon and its sub-properties) features, properties, or states. An instance of saref:Function can apply to different devices.

Function of Interest back to ToC or Class ToC

IRI: https://saref.etsi.org/core/FunctionOfInterest

Logical groups of commands that devices support to accomplish their tasks. Function can act upon (OP saref:actsUpon and its sub-properties) features, properties, or states. An instance of saref:FunctionOfInterest is supported by exactly one device.

Gas ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Gas

A type of energy commodity

has super-classes
saref:Commodityc

Get command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/GetCommand

A type of command

Get current meter value command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/GetCurrentMeterValueCommand

A type of get command

has super-classes
saref:GetCommandc

Get meter data command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/GetMeterDataCommand

A type of get command

has super-classes
saref:GetCommandc

Get meter history command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/GetMeterHistoryCommand

A type of get command

has super-classes
saref:GetCommandc

Get sensing data command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/GetSensingDataCommand

A type of get command

has super-classes
saref:Commandc

HVAC ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/HVAC

Heating, Ventilation and Air Conditioning (HVAC) device that provides indoor environmental comfort. A saref:HVAC is typically used to accomplish saref:Comfort.

has super-classes
saref:Devicec

Humidity ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Humidity

A saref:Property related to some measurements that are characterized by a certain value that is measured in a humidity unit

has super-classes
saref:Propertyc

Illuminance unit ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/IlluminanceUnit

The unit of measure for light

has super-classes
saref:UnitOfMeasurec

Level control function ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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.

has super-classes
saref:ActuatingFunctionc

Light ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Light

A saref:Property related to some measurements that are characterized by a certain value that is measured in a illuminance unit (lux)

has super-classes
saref:Propertyc

Light switch ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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.

has super-classes
saref:Switchc

Measurement ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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.

Meter back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Meter

A device designed to observe and measure one or more properties of one or more features of interest.

has super-classes
saref:Devicec
saref:observesop min 1

Metering function ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/MeteringFunction

A function that allows to get data from a meter, such as current meter reading or instantaneous demand

Motion ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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

has super-classes
saref:Propertyc

Multi level state ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/MultiLevelState

A type of state

has super-classes
saref:Statec

Natural Resource Commodity back to ToC or Class ToC

IRI: https://saref.etsi.org/core/NaturalResourceCommodity

The class of natural resource commodities

has super-classes
saref:Commodityc

Notify command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/NotifyCommand

A type of command

has super-classes
saref:Commandc

Observation back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Observation

A saref:Observation is the act of carrying out a procedure to estimate or calculate a value of a property of a feature of interest, or a state of a feature of interest. It links to a sensor to describe what made the observation, and to the observed feature, property, property of interest, state, or state of interest. Typically, its result is a property value or a state. An observation of a state (OP saref:observes) should have a state as a result (OP saref:hasResult). Respectively, an observation of a property should have a property value as a result.

Occupancy ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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

has super-classes
saref:Propertyc

Off command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/OffCommand

A type of command

has super-classes
saref:Commandc

Off state ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/OffState

The state of a device that is Off

has super-classes
saref:OnOffStatec

On command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/OnCommand

A type of command

has super-classes
saref:Commandc

On off function ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/OnOffFunction

An actuating function that allows to switch on and off an actuator

has super-classes
saref:ActuatingFunctionc

On off state ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/OnOffState

A type of state

has super-classes
saref:Statec
has sub-classes
saref:OffStatec
saref:OnStatec

On state ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/OnState

The state of a device that is On

has super-classes
saref:OnOffStatec

Open close function ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/OpenCloseFunction

An actuating function that allows to open and close a device

has super-classes
saref:ActuatingFunctionc

Open close state ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/OpenCloseState

A type of state

has super-classes
saref:Statec
has sub-classes
saref:CloseStatec
saref:OpenStatec

Open command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/OpenCommand

A type of command

has super-classes
saref:Commandc

Open state ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/OpenState

The state of a device that is OPEN

has super-classes
saref:OpenCloseStatec

Operation back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Operation

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.

Operation Execution back to ToC or Class ToC

IRI: https://saref.etsi.org/core/OperationExecution

Describes the execution of an operation in a network: the–machine interpretable– description of a communication between devices over the network. Typically, its input and result are network messages, that conform to the input and output of the executed operation.

Pause command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/PauseCommand

A type of command

has super-classes
saref:Commandc

Power ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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.

has super-classes
saref:Propertyc

Power unit ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/PowerUnit

The unit of measure for power

has super-classes
saref:UnitOfMeasurec

Pressure ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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)

has super-classes
saref:Propertyc

Pressure unit ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/PressureUnit

The unit of measure for pressure

has super-classes
saref:UnitOfMeasurec

Price ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Price

A saref:Property crelated to some measurements that are characterized by a certain value that is measured using saref:Currency
A saref:Property related to some measurements that are characterized by a certain value that is measured using saref:Currency

has super-classes
saref:Propertyc
is in range of
saref:hasPricec

Procedure Execution back to ToC or Class ToC

IRI: https://saref.etsi.org/core/ProcedureExecution

Represents the act of carrying out a procedure.

Profile back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Profile

A saref:Profile describes the money earned (negative values) or paied (positive values) for the use (production or consumption) of a commodity by a device in a certain context.

Property back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Property

Identifiable qualities of features of interest that can be acted upon by devices, such as observed or controlled. A property can apply to different features of interest.

Property of Interest back to ToC or Class ToC

IRI: https://saref.etsi.org/core/PropertyOfInterest

Identifiable qualities of features of interest that can be acted upon by devices, such as observed or controlled. An instance of saref:PropertyOfInterest is specific to a feature of interest. It is inherent to and cannot exist without that feature of interest.

Property Value back to ToC or Class ToC

IRI: https://saref.etsi.org/core/PropertyValue

Describes the value for a property. The property value is linked to its value expressed as an RDF literal (DP saref:hasValue), optionally to the unit of measurement (OP saref:isMeasuredIn), and optionally to the properties or properties of interest it is a value of (OP saref:isValueOfProperty).

Sensing function ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/SensingFunction

A function that allows to transmit data from sensors, such as measurement values (e.g., temperature) or sensing data (e.g., occupancy)

has super-classes
saref:Functionc
is in domain of
saref:hasSensingRangec
saref:hasSensorTypec

Sensor back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Sensor

A device designed to observe one or more properties or states of one or more features of interest.

has super-classes
saref:Devicec
saref:observesop min 1
has sub-classes
saref:SmokeSensorc
saref:TemperatureSensorc

Service back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Service

A saref:Service is a digital representation of a function in a network, making it discoverable, registerable and remotely controllable in the network.

Set absolute level command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/SetAbsoluteLevelCommand

A type of set level command

has super-classes
saref:Commandc

Set level command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/SetLevelCommand

A type of command

has super-classes
saref:Commandc
has sub-classes
saref:SetRelativeLevelCommandc

Set relative level command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/SetRelativeLevelCommand

A type of set level command

has super-classes
saref:SetLevelCommandc

Smoke ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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

has super-classes
saref:Propertyc

Smoke sensor ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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.

has super-classes
saref:Sensorc

Start command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/StartCommand

A type of command

has super-classes
saref:Commandc

Start state ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/StartState

The state of a device that is STARTED

has super-classes
saref:StartStopStatec

Start stop function ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/StartStopFunction

An actuating function that allows to start and stop a device

has super-classes
saref:ActuatingFunctionc

Start stop state ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/StartStopState

A type of state

has super-classes
saref:Statec
has sub-classes
saref:StartStatec
saref:StopStatec

State back to ToC or Class ToC

IRI: https://saref.etsi.org/core/State

Identifiable conditions that features of interest are or may be in, and that can be acted upon by devices, such as observed and controlled. A state can apply to different features of interest.

State of Interest back to ToC or Class ToC

IRI: https://saref.etsi.org/core/StateOfInterest

Identifiable conditions that features of interest are or may be in, and that can be acted upon by devices, such as observed and controlled. An instance of saref:StateOfInterest is specific to a feature of interest. It is inherent to and cannot exist without that feature of interest.

has super-classes
saref:isStateOfInterestOfop exactly 1
is in domain of
saref:hasStateKindc
saref:isStateOfInterestOfc
is in range of
saref:hasStateOfInterestc

Step down command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/StepDownCommand

A type of command

has super-classes
saref:Commandc

Step up command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/StepUpCommand

A type of command

has super-classes
saref:Commandc

Stop command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/StopCommand

A type of command

has super-classes
saref:Commandc

Stop state ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/StopState

The state of a device that is STOPPED

has super-classes
saref:StartStopStatec

Switch ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Switch

A device of category saref:Actuator that performs an actuating function of type saref:OnOffFunction or saref:OpenCloseFunction

has super-classes
saref:Actuatorc
has sub-classes
saref:DoorSwitchc
saref:LightSwitchc

Switch on service ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/SwitchOnService

A type of service that represents an on/off function to the network

has super-classes
saref:Servicec

Task back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Task

The goal for which a device is designed, from a user perspective.

Temperature ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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)

has super-classes
saref:Propertyc

Temperature sensor ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/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.

has super-classes
saref:Sensorc

Temperature unit ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/TemperatureUnit

The unit of measure for temperature

has super-classes
saref:UnitOfMeasurec

Time ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Time

A class that allows to specify the time concept.

is in range of
saref:hasTimec

Toggle command ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/ToggleCommand

A type of command

has super-classes
saref:Commandc

Unit of measure back to ToC or Class ToC

IRI: https://saref.etsi.org/core/UnitOfMeasure

The unit of measure is a standard for measurement of a quantity, such as a Property.

Water ⚠ Is deprecated back to ToC or Class ToC

IRI: https://saref.etsi.org/core/Water

A type of commodity

has super-classes
saref:Commodityc

Object Properties

accomplishes back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/accomplishes

Links a certain entity (e.g., a device) to the task it accomplishes.

has range
saref:Taskc
is inverse of
saref:isAccomplishedByop

acts upon back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/actsUpon

Links a device, function, command, or procedure execution, to the feature, property, or state, it acts upon.

consists of back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/consistsOf

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)

consumes back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/consumes

Links a feature kind, feature of interest, or device, to the commodity it consumes

has super-properties
saref:isUsedForop
is inverse of
saref:isConsumedByop

controls back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/controls

Links a device, function, command, or procedure execution, to the feature, property, or state, it controls.

controls property ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/controlsProperty

A relationship specifying the property that can be controlled by a certain device

has super-properties
saref:controlsop
has domain
saref:Devicec
has range
saref:Propertyc

has applicable time back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasApplicableTime

Links an entity (e.g., a profile) to an instant or interval or other compound temporal entity expressed using OWL Time, which bounds temporally the applicable context of that entity.

has command back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasCommand

Links a function or function of interest and the command it supports.

has command kind back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasCommandKind

links a command of interest to its kind, a command.

has domain
saref:CommandOfInterestc
has range
saref:Commandc
has sub-property chains
saref:hasCommandKindop o skos:broaderop

has command of interest back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasCommandOfInterest

Links a function of interest to one of its commands of interest.

has device kind back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasDeviceKind

Links a device to its kind, a feature kind. Kinds of devices describe models of devices, with common properties having the same value, common states being the same, common functions, and common services.

has super-properties
saref:hasFeatureKindop
has domain
saref:Devicec
has range
saref:FeatureKindc

has feature kind back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasFeatureKind

links a feature of interest to its kind, a feature kind

has sub-properties
saref:hasDeviceKindop
has domain
saref:FeatureOfInterestc
has range
saref:FeatureKindc
has sub-property chains
saref:hasFeatureKindop o skos:broaderop

has function back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasFunction

Links a feature kind or a device to one of its functions.

has function kind back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasFunctionKind

links a function of interest to its kind, a function

has domain
saref:FunctionOfInterestc
has range
saref:Functionc
has sub-property chains
saref:hasFunctionKindop o skos:broaderop

has function of interest back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasFunctionOfInterest

Links a device to one of its functions of interest.

has input back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasInput

Links a command, operation, or procedure execution, to its inputs.

has mandatory command back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasMandatoryCommand

Links a function and one of its mandatory commands

has domain
saref:Functionc
has sub-property chains
skos:broaderop o saref:hasMandatoryCommandop

has measurement ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasMeasurement

A relationship between a feature of interest and a measurement about it

has meter reading ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasMeterReading

A relationship between a metering function and the measurement of the reading

has meter reading type ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasMeterReadingType

A relationship identifying the reading type of a metering function (e.g., Water, Gas, Pressure , Energy , Power, etc.)

has domain
saref:MeteringFunctionc
has range
saref:Propertyc

has operation back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasOperation

Links a service to one of its operations.

has domain
saref:Servicec
has range
saref:Operationc
is inverse of
saref:isOperationOfop

has optional command back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasOptionalCommand

Links a function and one of its optional commands

has domain
saref:Functionc

has output back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasOutput

Links a command or operation to its outputs.

has phenomenon time back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasPhenomenonTime

Links a procedure execution to the time that the result applies. It may be an interval or an instant, or some other compound temporal entity expressed using OWL Time.

has price ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasPrice

A relationship indentifying the price associated to an entity

has range
saref:Pricec

has profile back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasProfile

Links a device to its profile. Its inverse is saref:isProfileOf. The device should be linked to a certain commodity using OP saref:isUsedFor or its sub-properties, and optionally to some property or state using OP saref:actsUpon or its sub-properties.

has domain
saref:FeatureKindc or saref:Devicec
has range
saref:Profilec
is inverse of
saref:isProfileOfop

has property back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasProperty

Links a feature kind or a feature of interest to one of its properties.

has property kind back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasPropertyKind

links a property of interest to its kind, a property.

has domain
saref:PropertyOfInterestc
has range
saref:Propertyc
has sub-property chains
saref:hasPropertyKindop o skos:broaderop

has property of interest back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasPropertyOfInterest

Links a feature of interest to one of its properties of interest.

has property value back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasPropertyValue

Links a feature kind, a feature of interest, or a property of interest, to a property value.

has result back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasResult

Links a procedure execution (e.g., an observation) to its result (e.g., a property value).

has sensing range ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasSensingRange

A relationship between a sensing function and a measurement identifying the range of a sensor detection

has sensor type ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasSensorType

A relationship identifying the sensing type of a sensor detection (i.e., Temperature, Occupancy, Humidity, Motion , Smoke, Pressure, etc.)

has domain
saref:SensingFunctionc
has range
saref:Propertyc

has state back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasState

Links a feature kind or a feature of interest to one of its states.

has state kind back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasStateKind

links a state of interest to its kind, a state

has domain
saref:StateOfInterestc
has range
saref:Statec
has sub-property chains
saref:hasStateKindop o skos:broaderop

has state of interest back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasStateOfInterest

Links a feature of interest to one of its states of interest.

has threshold measurement ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasThresholdMeasurement

A relationship associated with an event function to notify that a certain threshold measurement has been exceeded

has domain
saref:EventFunctionc
has range
saref:Measurementc

has time ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasTime

A relationship to associate time information to an entity

has range
saref:Timec

has typical consumption ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/hasTypicalConsumption

A relationship identifying the typical (energy or power) consumption of a device

isAbout ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isAbout

A relationship identifying what an entity, such as a profile, is about

is accomplished by back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isAccomplishedBy

A relationship identifying an entity (e.g., a device) that can accomplish a task.

has domain
saref:Taskc
is inverse of
saref:accomplishesop

is acted upon by back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isActedUponBy

Links a feature, property, or state, to the device, function, command, or procedure execution, that acts on it.

is command of back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isCommandOf

Links a command and a function or function of interest that supports it.

has domain
saref:Commandc
has range
saref:Functionc or saref:FunctionOfInterestc
is inverse of
saref:hasCommandop

is command of interest of back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isCommandOfInterestOf

Links a command of interest to the function of interest it is a command of.

has characteristics: functional

has domain
saref:CommandOfInterestc
has range
saref:FeatureOfInterestc
is inverse of
saref:hasCommandOfInterestop

is consumed by back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isConsumedBy

Links a commodity to the feature kind, feature of interest, or device, that consumes it

is inverse of
saref:consumesop

is controlled by back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isControlledBy

Links a feature, property, or state, to the device, function, command, or procedure execution, that controls it.

has super-properties
saref:isActedUponByop
has sub-properties
saref:isControlledByDeviceop
is inverse of
saref:controlsop

is controlled by device ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isControlledByDevice

A relationship specifying the devices that can control a certain property

has super-properties
saref:isControlledByop
has domain
saref:Propertyc
has range
saref:Devicec

is execution of back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isExecutionOf

Links a command execution to the command or command of interest that was executed. Also liks an operation execution to the operation that was executed

is function of back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isFunctionOf

Links a function to the feature kind or device it is a function of.

is function of interest of back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isFunctionOfInterestOf

Links a function of interest to the device it is a function of.

has characteristics: functional

has domain
saref:FunctionOfInterestc
has range
saref:Devicec
is inverse of
saref:hasFunctionOfInterestop

is measured by device ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isMeasuredByDevice

A relationship specifying the devices that can measure a certain property

has super-properties
saref:isObservedByop
has domain
saref:Propertyc
has range
saref:Devicec

is measured in back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isMeasuredIn

A relationship identifying the unit of measure used for a certain entity.

isMeasurementOf ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isMeasurementOf

A relationship between a measurement and the feature of interest whose quality was measured

has domain
saref:Measurementc
has range
saref:FeatureOfInterestc
is inverse of
saref:hasMeasurementop

is observed by back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isObservedBy

Links a feature, property, or state, to the device, function, command, or procedure execution, that observes it.

has super-properties
saref:isActedUponByop
has sub-properties
saref:isMeasuredByDeviceop
is inverse of
saref:observesop

is offered by back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isOfferedBy

Links a service to the device that exposes it to a network

has characteristics: functional

has domain
saref:Servicec
has range
saref:Devicec
is inverse of
saref:offersop

is operation of back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isOperationOf

Links an operation to the service it belongs to.

has characteristics: functional

has domain
saref:Operationc
has range
saref:Servicec
is inverse of
saref:hasOperationop

is produced by back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isProducedBy

Links a commodity to the feature kind, feature of interest, or device, that produces it

is inverse of
saref:producesop

is profile of back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isProfileOf

Links a profile to the device it describes. The device should be linked to a certain commodity using OP saref:isUsedFor or its sub-properties, and optionally to some property or state using OP saref:actsUpon or its sub-properties.

has domain
saref:Profilec
has range
saref:FeatureKindc or saref:Devicec
is inverse of
saref:hasProfileop

is property of back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isPropertyOf

Links a property to the feature kind or feature of interest it is a property of.

is property of interest of back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isPropertyOfInterestOf

Links a property of interest to the feature of interest it is a property of.

has characteristics: functional

has domain
saref:PropertyOfInterestc
has range
saref:FeatureOfInterestc
is inverse of
saref:hasPropertyOfInterestop

is state of back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isStateOf

Links a state to the feature kind or feature of interest it is a state of.

has domain
saref:Statec
has range
saref:FeatureKindc or saref:FeatureOfInterestc
is inverse of
saref:hasStateop

is state of interest of back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isStateOfInterestOf

Links a state of interest to the feature of interest it is a state of.

has characteristics: functional

has domain
saref:StateOfInterestc
has range
saref:FeatureOfInterestc
is inverse of
saref:hasStateOfInterestop

is stored by back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isStoredBy

Links a commodity to the feature kind, feature of interest, or device, that stores it

is inverse of
saref:storesop

is used for ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isUsedFor

Links a feature kind, feature of interest, or device, to the commodity it is used for

is value of property back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/isValueOfProperty

Links a property value to the property or property of interest it is a value of.

made by back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/madeBy

Links a procedure execution to the entity (e.g., device) that made it.

made execution back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/madeExecution

Links an entity (e.g., device) to the procedure execution it made.

has domain
saref:FeatureOfInterestc
has range
saref:ProcedureExecutionc
is inverse of
saref:madeByop

makes measurement ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/makesMeasurement

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.

has domain
saref:Devicec
has range
saref:Measurementc
is inverse of
saref:measurementMadeByop

measurement made by ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/measurementMadeBy

A relation between a measurement and the device that made it.

has domain
saref:Measurementc
has range
saref:Devicec
is inverse of
saref:makesMeasurementop

measures property ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/measuresProperty

A relationship specifying the property that can be measured by a certain device

has super-properties
saref:observesop
has domain
saref:Devicec
has range
saref:Propertyc

observes back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/observes

Links a device, function, command, or procedure execution, to the feature, property, or state, it observes.

offers back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/offers

Links a device to a service it exposes to a network.

has domain
saref:Devicec
has range
saref:Servicec
is inverse of
saref:isOfferedByop

produces back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/produces

Links a feature kind, feature of interest, or device, to the commodity it produces

has super-properties
saref:isUsedForop
is inverse of
saref:isProducedByop

has price back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/profileHasPrice

Links a profile to the money earned (negative values) or paid (positive values) for the use (production or consumption) of the commodity by the device

has domain
saref:Profilec
has range
saref:PropertyValuec

relates to measurement ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/relatesToMeasurement

A relationship between a property and the measurements it relates to

has domain
saref:Propertyc
has range
saref:Measurementc
is inverse of
saref:relatesToPropertyop

relates to property ⚠ Is deprecated back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/relatesToProperty

A relationship between a measurement and the property it relates to

has domain
saref:Measurementc
has range
saref:Propertyc
is inverse of
saref:relatesToMeasurementop

represents back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/represents

Links a service to some function or function of interest it exposes to the network. Also links an operation to some command or command of interest it exposes to the network.

stores back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/stores

Links a feature kind, feature of interest, or device, to the commodity it stores

has super-properties
saref:isUsedForop
is inverse of
saref:isStoredByop

when property value back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/whenPropertyValue

Links a profile to a property value that contributes to restricting its applicable context.

has domain
saref:Profilec
has range
saref:PropertyValuec

when state back to ToC or Object Property ToC

IRI: https://saref.etsi.org/core/whenState

Links a profile to a state that contributes to restricting its applicable context.

has domain
saref:Profilec
has range
saref:Statec

Data Properties

has description ⚠ Is deprecated back to ToC or Data Property ToC

IRI: https://saref.etsi.org/core/hasDescription

DEPRECATED: The use of rdfs:comment is recommended instead.
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.

has identifier back to ToC or Data Property ToC

IRI: https://saref.etsi.org/core/hasIdentifier

Links some entity to its identifier. Extensions of SAREF may define sub-properties such as s4abcd:hasUUID, s4abcd:hasGTIN12, etc.

has manufacturer back to ToC or Data Property ToC

IRI: https://saref.etsi.org/core/hasManufacturer

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 model back to ToC or Data Property ToC

IRI: https://saref.etsi.org/core/hasModel

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 result time back to ToC or Data Property ToC

IRI: https://saref.etsi.org/core/hasResultTime

Links a procedure execution to the instant of time when the activity was completed, expressed as an xsd:dateTime literal.

has timestamp back to ToC or Data Property ToC

IRI: https://saref.etsi.org/core/hasTimestamp

Links a procedure execution or a profile to an instant.

has value back to ToC or Data Property ToC

IRI: https://saref.etsi.org/core/hasValue

Value of a property value expressed as an RDF literal. Note that, even if decimal values are expected, values could use other datatypes.

Named Individuals

Cleaning, aka Cleaning ⚠ Is deprecated back to ToC or Named Individuals ToC

IRI: https://saref.etsi.org/core/Cleaning

A type of task for which a device is designed
A type of task for which a device is designed

belongs to
saref:Taskc

Comfort, aka Comfort ⚠ Is deprecated back to ToC or Named Individuals ToC

IRI: https://saref.etsi.org/core/Comfort

A type of task for which a device is designed
A type of task for which a device is designed

belongs to
saref:Taskc

Drying, aka Drying ⚠ Is deprecated back to ToC or Named Individuals ToC

IRI: https://saref.etsi.org/core/Drying

A type of task for which a device is designed
A type of task for which a device is designed

belongs to
saref:Taskc

EnergyEfficiency, aka EnergyEfficiency ⚠ Is deprecated back to ToC or Named Individuals ToC

IRI: https://saref.etsi.org/core/EnergyEfficiency

A type of task for which a device is designed
A type of task for which a device is designed

belongs to
saref:Taskc

Entertainment, aka Entertainment ⚠ Is deprecated back to ToC or Named Individuals ToC

IRI: https://saref.etsi.org/core/Entertainment

A type of task for which a device is designed
A type of task for which a device is designed

belongs to
saref:Taskc

Lighting, aka Lighting ⚠ Is deprecated back to ToC or Named Individuals ToC

IRI: https://saref.etsi.org/core/Lighting

A type of task for which a device is designed
A type of task for which a device is designed

belongs to
saref:Taskc

Meter reading, aka Meter reading ⚠ Is deprecated back to ToC or Named Individuals ToC

IRI: https://saref.etsi.org/core/MeterReading

A type of task for which a device is designed
A type of task for which a device is designed

belongs to
saref:Taskc

Safety, aka Safety ⚠ Is deprecated back to ToC or Named Individuals ToC

IRI: https://saref.etsi.org/core/Safety

A type of task for which a device is designed
A type of task for which a device is designed

belongs to
saref:Taskc

Washing, aka Washing ⚠ Is deprecated back to ToC or Named Individuals ToC

IRI: https://saref.etsi.org/core/Washing

A type of task for which a device is designed
A type of task for which a device is designed

belongs to
saref:Taskc

WellBeing, aka WellBeing ⚠ Is deprecated back to ToC or Named Individuals ToC

IRI: https://saref.etsi.org/core/WellBeing

A type of task for which a device is designed
A type of task for which a device is designed

belongs to
saref:Taskc

References

Normative references

Informative references

Acknowledgements

The editors would like to thank the ETSI SmartM2M technical committee for providing guidance and expertise.

Also, many thanks to the ETSI staff and all other current and former active Participants of the ETSI SmartM2M group for their support, technical input and suggestions that led to improvements to this ontology.

Also, special thanks goes to the ETSI SmartM2M Technical Officer Guillemin Patrick.

This documentation page was generated automatically using SPARQL-Generate, developed by Maxime Lefrançois. The SAREF public portal, the SAREF sources with continuous integration and deployment, the SAREF Pipeline software, and ETSI Technical Specification TS 103 673 v1.1.1 "SAREF Development Framework and Workflow, Streamlining the Development of SAREF and its Extensions", have been developed in the context of the ETSI STF 578, which followed the ETSI STF 556.