language en

IoT-D: IoT dependencies ontology

Release 04/04/2022

This version:
0.0.4
Latest version:
https://w3id.org/iotd
Revision:
0.0.4
Authors:
Amal GUITTOUM, Orange Innovation, LIG Lab ✉
Contributors:
François AISSAOUI, Orange Innovation ✉
Sébastien BOLLE, Orange Innovation✉
Fabienne Boyer, LIG Lab ✉
Noel De Palma, LIG Lab ✉
Imported Ontologies:
EuPont
SAREF
DK
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
http://insertlicenseURIhere.org
Visualization:
Visualize with WebVowl
Cite as:
IoT dependencies ontology. Revision: 0.0.4.
Ontology Documentation

Abstract

IoT-D ontology reprensents contextual data that allows inference of dependencies between IoT devices across heteregenous DM solutions managed by multiple actors.

Introduction back to ToC

IoT-D ontology describes IoT dependencies and their context that are distributed across heterogenous DM solutions. It allows the documentation and the characterization of IoT dependencies at diffrent levels at the device, the application, and the physical environment levels. It is designed to supports decision-making when addressing dependencies-related threats such as Cascading Failure.

Namespace declarations

Table 1: Namespaces used in the document
IoTd<https://w3id.org/iotd>
ns<http://www.w3.org/2003/06/sw-vocab-status/ns>
owl<http://www.w3.org/2002/07/owl>
dk<http://www.data-knowledge.org/dk>
xsd<http://www.w3.org/2001/XMLSchema>
rdfs<http://www.w3.org/2000/01/rdf-schema>
eupont<http://elite.polito.it/ontologies/eupont.owl>
ns1<http://creativecommons.org/ns>
core<https://saref.etsi.org/core>
rdf<http://www.w3.org/1999/02/22-rdf-syntax-ns>
terms<http://purl.org/dc/terms>
xml<http://www.w3.org/XML/1998/namespace>
vann<http://purl.org/vocab/vann>
wot<http://xmlns.com/wot/0.1>
foaf<http://xmlns.com/foaf/0.1>
dc<http://purl.org/dc/elements/1.1>

IoT dependencies ontology: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

IoT dependencies ontology: Description back to ToC

Conceptually, the IoT-D ontology includes three modules: 1) Device-Device Interaction module: describes the capabilities of IoT devices in terms of service provisioning and usage to model the context of direct dependencies. It is based on the enrichment of the SAREF ontology by describing the direct exchange of services between devices through the relation IoTD:consumes and specializing the saref:Service and saref:Device to account for connectivity devices and services, allowing inference of service and connectivity dependencies; 2) Device-Environment interaction module: represents, using the SAREF ontology, the interaction of devices within the physical environment through sensing and ac- tuation, enabling the inference of environment-based dependencies; 3) Device- Application interaction module: describes device interactions in IoT applications. Based on the EuPont ontology, an IoT application is represented using a set of IoTD:Rule and IoTD:Action that are executed by saref:Service. IoTD:Rule is in the form if (IoTD:Trigger ) then IoTD:Action. Triggers are related to a change in devices state saref:State. This trigger-action-based model allows representing state dependencies between devices i.e. when an IoT application acts on one device based on the state of another. Also, it allows the representation of implicit service dependencies in the form of data flows between IoTD:Action, using the class dk:DataFlow of the DK Ontology.
IoT-D Modules

Cross-reference for IoT dependencies ontology classes, object properties and data properties back to ToC

This section provides details for each class and property defined by IoT dependencies ontology.

Classes

actionc back to ToC or Class ToC

IRI: https://w3id.org/iotd#Action

An action to perform by calling a service of an IoT device.
has super-classes
action c
is in range of
allows action op, flows from op, flows from op, flows to op, flows to op, has action op

actuatorc back to ToC or Class ToC

IRI: https://w3id.org/iotd#Actuator

is equivalent to
actuator c
has super-classes
Device c, io t device c
has sub-classes
switch c
is in domain of
controls property op

applicationc back to ToC or Class ToC

IRI: https://w3id.org/iotd#Application

An IoT application that compose IoT devices services to create added value/complex services, it can be a trigger-action plateform.
has sub-classes
broker c, trigger action plateform c
is in domain of
has application action op, has rule op

brokerc back to ToC or Class ToC

IRI: https://w3id.org/iotd#Broker

broker that connect equipments.
has super-classes
application c

complex triggerc back to ToC or Class ToC

IRI: https://w3id.org/iotd#ComplexTrigger

has super-classes
trigger c
is in domain of
has child trigger op

connectivity devicec back to ToC or Class ToC

IRI: https://w3id.org/iotd#ConnectivityDevice

A device that connectes home devices to the internet like: gateway, wifiRepeater, hub.
has super-classes
Device c

connectivity servicec back to ToC or Class ToC

IRI: https://w3id.org/iotd#ConnectivityService

A service offred by a connectivityDevice.
has super-classes
service c

Data Flowc back to ToC or Class ToC

IRI: http://www.data-knowledge.org/dk/DataFlow

Indicates the actual connection and data exchange between two actions in an Iot application
has sub-classes
Data Flow c
is in domain of
flows from op, flows to op

Data Flowc back to ToC or Class ToC

IRI: https://w3id.org/iotd#DataFlow

Indicates the actual connection and data exchange between actions in one application.
has super-classes
Data Flow c
is in domain of
flows from op, flows to op

Devicec back to ToC or Class ToC

IRI: https://w3id.org/iotd#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.
is equivalent to
device c
has sub-classes
actuator c, connectivity device c, io t device c, processor c, sensor c
is in domain of
has implicit service dependency to op, has state op, offers op
is in range of
has implicit service dependency to op

feature of interestc back to ToC or Class ToC

IRI: https://w3id.org/iotd#FeatureOfInterest

is equivalent to
feature of interest c
is in domain of
has property op

io t devicec back to ToC or Class ToC

IRI: https://w3id.org/iotd#IoTDevice

A device that is connected to the internet to share data it can be ether a sensor/actuator/processor or compositition.
has super-classes
Device c
has sub-classes
actuator c, sensor c

processorc back to ToC or Class ToC

IRI: https://w3id.org/iotd#Processor

A device that has the capability to perform computation operations on data.
has super-classes
Device c

propertyc back to ToC or Class ToC

IRI: https://w3id.org/iotd#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
is equivalent to
property c
is in range of
controls property op, has property op, measures property op

rulec back to ToC or Class ToC

IRI: http://elite.polito.it/ontologies/eupont.owl#Rule

is equivalent to
rule c
is in range of
has rule op

sensorc back to ToC or Class ToC

IRI: https://w3id.org/iotd#Sensor

is equivalent to
sensor c
has super-classes
Device c, io t device c
has sub-classes
smokesensor c, temperaturesensor c
is in domain of
measures property op

servicec back to ToC or Class ToC

IRI: https://w3id.org/iotd#Service

is equivalent to
service c
is in domain of
allows action op
is in range of
offers op

smokesensorc back to ToC or Class ToC

IRI: https://w3id.org/iotd#Smokesensor

is equivalent to
smoke sensor c
has super-classes
sensor c

statec back to ToC or Class ToC

IRI: https://w3id.org/iotd#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.
is equivalent to
state c
is in range of
has state op

switchc back to ToC or Class ToC

IRI: https://w3id.org/iotd#Switch

has super-classes
actuator c

temperaturesensorc back to ToC or Class ToC

IRI: https://w3id.org/iotd#Temperaturesensor

is equivalent to
temperature sensor c
has super-classes
sensor c

triggerc back to ToC or Class ToC

IRI: https://w3id.org/iotd#Trigger

An event to react to. It is launched when the state of an IoT device changes.
has super-classes
trigger c
has sub-classes
complex trigger c
is in domain of
related to op
is in range of
has child trigger op, has trigger op

trigger action plateformc back to ToC or Class ToC

IRI: https://w3id.org/iotd#triggerActionPlateform

a kind of IoT application that is composed of rules created by end user.
has super-classes
application c

Object Properties

allows actionop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#allowsAction

A relationship between a service and an action, a service call allow action execution.
has domain
service c
has range
action c

consumesop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#consumes

A relationship between a device and a service.
has domain
device c
has range
service c

controls propertyop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#controlsProperty

has equivalent properties
controls property op
has domain
actuator c
has range
property c

flows fromop back to ToC or Object Property ToC

IRI: http://www.data-knowledge.org/dk/flowsFrom

denotes that an action produce data
Is defined by
http://www.data-knowledge.org/dk/
has equivalent properties
flows from op
has domain
Data Flow c
has range
action c

flows fromop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#flowsFrom

has equivalent properties
flows from op
has domain
Data Flow c
has range
action c

flows toop back to ToC or Object Property ToC

IRI: http://www.data-knowledge.org/dk/flowsTo

denotes that an Action recieve data
Is defined by
http://www.data-knowledge.org/dk/
has equivalent properties
flows to op
has domain
Data Flow c
has range
action c

flows toop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#flowsTo

has equivalent properties
flows to op
has domain
Data Flow c
has range
action c

has actionop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#hasAction

has domain
rule c
has range
action c

has application actionop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#hasApplicationAction

has domain
application c
has range
action c

has child triggerop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#hasChildTrigger

has domain
complex trigger c
has range
trigger c

has connectivity dependencyop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#hasConnectivityDependency

Denotes connectivity dependency relationship between two devices.
has domain
device c
has range
device c

has environment dependency toop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#hasEnvironmentDependencyTo

Denotes environment dependency relationship between two devices.
has domain
device c
has range
device c

has implicit service dependency toop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#hasImplicitServiceDependencyTo

Denotes implicit service dependency between two IoT devices.
has domain
Device c
has range
Device c

has propertyop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#hasProperty

has domain
feature of interest c
has range
property c

has ruleop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#hasRule

has domain
application c
has range
rule c

has service dependency toop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#hasServiceDependencyTo

Denotes direct service dependency relationship between two devices.
has domain
device c
has range
device c

has stateop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#hasState

has domain
Device c
has range
state c

has state dependency toop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#hasStateDependencyTo

Denotes state dependency relationship between two devices.
has domain
device c
has range
device c

has triggerop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#hasTrigger

has domain
rule c
has range
trigger c

measures propertyop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#measuresProperty

has domain
sensor c
has range
property c

offersop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#offers

has domain
Device c
has range
service c

related toop back to ToC or Object Property ToC

IRI: https://w3id.org/iotd#relatedTo

A relationship between a trigger and state to experss that a trigger occurs at a defined state of the device.
has domain
trigger c
has range
state c

Data Properties

has device namedp back to ToC or Data Property ToC

IRI: https://w3id.org/iotd#hasDeviceName

has domain
device c

has device type namedp back to ToC or Data Property ToC

IRI: https://w3id.org/iotd#hasDeviceTypeName

has domain
device c

has i p addressdp back to ToC or Data Property ToC

IRI: https://w3id.org/iotd#hasIPAddress

has domain
device c

has mac addressdp back to ToC or Data Property ToC

IRI: https://w3id.org/iotd#hasMacAddress

has super-properties
top data property
has domain
device c

has manufacturer namedp back to ToC or Data Property ToC

IRI: https://w3id.org/iotd#hasManufacturerName

has domain
device c

has service namedp back to ToC or Data Property ToC

IRI: https://w3id.org/iotd#hasServiceName

has domain
service c

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties

References back to ToC

Add your references here. It is recommended to have them as a list.

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.