IoT-Lite Ontology

IRI:
http://purl.oclc.org/NET/UNIS/fiware/iot-lite#
Date:
11/04/2017
Current version:
0.4
Authors:
Kerry Taylor
Maria Bermudez-Edo
Payam Barnaghi
Tarek Elsaleh
Contributors:
This work is part of the EU FP7 FIWARE project and the EU H2020 FIESTA-IoT project at the Institution for Communication Systems University of Surrey.
Other visualisation:
Ontology source
This ontology is distributed under a Creative Commons Attribution 3.0 Unported License - http://creativecommons.org/licenses/by/3.0/. This copyright applies to the iot-lite ontology specification and RDF.

Abstract

The IoT lite Ontology is a lightweight ontology to represent Internet of Things resources, entities and services. The lightweight allow the representation and use of IoT platforms without consuming excessive processing time when querying the ontology. However it is also a meta ontology that can be extended in order to represent IoT concepts in a more detail way in different domains.

Table of Content

  1. Introduction
  2. Classes
  3. Object Properties
  4. Data Properties
  5. Annotation Properties
  6. Namespace Declarations

Introduction

This ontology describes IoT concepts into three classes. Objects, system or resources and services. The devices are also splitted into, although not restricted to, three classes: sensing devices actuating devices and tag devices. The services are described with an availability or access control and a coverage. This coverage represents the area covered by the IoT device. The figure below depicts the concepts of the ontology and the main relationships between them. IoT Lite Ontology is created to be used with a common taxonomy to describe the Units and QuantityKind that IoT devices can meassure. This taxonomy represent individuals in the ontology and is based in well-known taxonomies as: qu and qudt.

Classes

actuating devicec back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#ActuatingDevice

Device that can actuate over an object or QuantityKind.
has super-classes
devicec

attributec back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Attribute

An attribute of an IoT object that can be exposed by an IoT service (i.e. a room (IoT Object) has a temperature (Attribute), that can be exposed by a temperature sensor (IoT device).
is in range of
has attributeop

circlec back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Circle

Circle coverage it needs the location of the sensor as the centre of the circle and the radius as a DataProperty.
has super-classes
coveragec
is in domain of
radiusdp

coveragec back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Coverage

The coverage of an IoT device (i.e. a temperature sensor inside a room has a coverage of that room).
has sub-classes
circlec, polygonc, rectanglec
is in range of
has coverageop

devicec back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/ssnx/ssn#Device

has super-classes
systemc
has sub-classes
actuating devicec, sensing devicec, tag devicec
is in domain of
exposed byop, has coverageop, iddp
is in range of
exposesop

entityc back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Entity

Any object that is relevant from a user or application perspective. (IoT-A Definition)
is equivalent to
objectc
has sub-classes
virtual entityc
is in domain of
has attributeop, iddp, is associated withop

metadatac back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Metadata

Class used to describe properties that cannot be described by QuantityKind and Units. i.e. the resolution of a sensor.
is in domain of
metadata typedp, metadata valuedp
is in range of
has metadataop

objectc back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Object

IoT entity
is in domain of
has attributeop, is associated withop

pointc back to ToC or Class ToC

IRI: http://www.w3.org/2003/01/geo/wgs84_pos#Point

is in domain of
alt, alt relative, lat, long, relative location
is in range of
locationop

polygonc back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Polygon

The coverage is made up by linking several points by strait lines.
has super-classes
coveragec

rectanglec back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Rectangle

The coverage is made up by giving two points which are the opposite corners of a rectangle.
has super-classes
coveragec

sensing devicec back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/ssnx/ssn#SensingDevice

has super-classes
devicec
sensorc
is in range of
has sensing deviceop

servicec back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Service

Service provided by an IoT Device
is in domain of
endpointdp, exposesop, interface descriptiondp, interface typedp, is onlinedp
is in range of
exposed byop, is associated withop

tag devicec back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#TagDevice

Tag Device such as QR code or bar code.
has super-classes
devicec

virtual entityc back to ToC or Class ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#VirtualEntity

Computational or data element representing a Physical Entity. Virtual Entities can be either Active or Passive Digital Entities. Physical Entities are represented in the digital world by a Virtual Entity. This term is also referred to as “virtual counterpart” in the literature (Ro¨mer et al. 2002), but using the same root term “entity” in both concepts clearer shows the relationship of these concepts. There are many kinds of digital representations of Physical Entities: 3D models, avatars, database entries, objects (or instances of a class in an object-oriented programming language), and even a social-network account could be viewed as such a representation, because it digitally represents certain aspects of its human owner, such as a photograph or a list of his hobbies. Enabling Things to Talk: Designing IoT solutions with the IoT Architectural Reference Model, Alessandro Bassi, Martin Bauer, Martin Fiedler, Thorsten Kramp, Rob van Kranenburg, Sebastian Lange, Stefan Meissner
has super-classes
entityc

Object Properties

exposed byop back to ToC or Object Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#exposedBy

A device is exposed by a service.
has domain
devicec
has range
servicec
is inverse of
exposesop

exposesop back to ToC or Object Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#exposes

For service-oriented queries. The inverse of exposedBy.
has domain
servicec
has range
devicec
is inverse of
exposed byop

has attributeop back to ToC or Object Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#hasAttribute

Links the devices with their attributes.
has domain
entityc
objectc
has range
attributec

has coverageop back to ToC or Object Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#hasCoverage

Links the devices with their coverages.
has domain
devicec
has range
coveragec

has metadataop back to ToC or Object Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#hasMetadata

Links any concept with metadata about that concept.
has range
metadatac

has quantity kindop back to ToC or Object Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#hasQuantityKind

Links a sensor or an attribute with the quantity kind it measures (e.g. A sensor -sensor1- measures temperature: sensor1 hasQuantityKind temperature).
has domain
attributec or sensorc
has range
quantity kindc

has sensing deviceop back to ToC or Object Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#hasSensingDevice

Links a sensor with a sensing device the same way as SSN.
has domain
sensorc
has range
sensing devicec

has sub systemop back to ToC or Object Property ToC

IRI: http://purl.oclc.org/NET/ssnx/ssn#hasSubSystem

has domain
systemc
has range
systemc
is inverse of
is sub system ofop

has unitop back to ToC or Object Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#hasUnit

Links the sensor with the units of the quantity kind it measures (e.g. A sensor -sensor1- measures temperature in Celsius: senso1 hasUnit celsius).
has domain
sensorc
has range
unitc

is associated withop back to ToC or Object Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#isAssociatedWith

Defines the associations between objects and sensors (e.g. A table (object) has an attribute (temperature at the table) which is associated with a sensor (the temperature sensor of the room).
has domain
entityc
objectc
has range
servicec

is sub system ofop back to ToC or Object Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#isSubSystemOf

This defines that a devices system is a subsystem of another system. For example, a multi-sensor device is a subsystem of a smart building testbed. This is the inverse of the SSN object property "hasSubSystem". It allows a graph to start from a subsystem. This is useful for resource-centric graphs.
has domain
systemc
has range
systemc
is inverse of
has sub systemop

locationop back to ToC or Object Property ToC

IRI: http://www.w3.org/2003/01/geo/wgs84_pos#location

has range
pointc

on platformop back to ToC or Object Property ToC

IRI: http://purl.oclc.org/NET/ssnx/ssn#onPlatform

has domain
systemc
has range
platformc

Data Properties

endpointdp back to ToC or Data Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#endpoint

Endpoint of the service. It is usually a URL where the service is available.
has domain
servicec
has range
any u r i

iddp back to ToC or Data Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#id

The ID of the Device or Entity
has domain
entityc
devicec
has range
string

interface descriptiondp back to ToC or Data Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#interfaceDescription

Interface Description of the service, e.g WADL, WSDL, NGSI9 etc.
has domain
servicec
has range
any u r i

interface typedp back to ToC or Data Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#interfaceType

Defines the type of interface of the service endpoint, e.g. RESTful, NGSI-9, MQTT, CoAP etc.
has domain
servicec
has range
string

is mobiledp back to ToC or Data Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#isMobile

Is the Device mobile? This can be used by an IoT management platform to enable tracking of the device's location.
has domain
platformc
has range
boolean

is onlinedp back to ToC or Data Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#isOnline

Is the IoT Service exposing the Resource, or associated with the Entity, online?
has domain
servicec
has range
boolean

metadata typedp back to ToC or Data Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#metadataType

Defines the type pf the metadata value (e.g. resolution of the sensor).
has domain
metadatac
has range
string

metadata valuedp back to ToC or Data Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#metadataValue

Value of the metadata
has domain
metadatac
has range
string

radiusdp back to ToC or Data Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#radius

Specifies the radius of a circle coverage defined by a point -the center of the circle- and its radius.
has domain
circlec
has range
double

Annotation Properties

altap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2003/01/geo/wgs84_pos#alt

has domain
pointc

alt relativeap back to ToC or Annotation Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#altRelative

Relative Altitude can be used in place of an absolute altitude, especially in buildings, where it makes more sense to locate by levels or floors. For example the value "0" would indicate "ground floor", and "1" would indicate "1st floor" and so on.
has domain
pointc
has range
string

bibliographic citationap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/bibliographicCitation

contributorap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/contributor

creatorap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/creator

dateap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/date

date submittedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/dateSubmitted

descriptionap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/description

latap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2003/01/geo/wgs84_pos#lat

has domain
pointc

longap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2003/01/geo/wgs84_pos#long

has domain
pointc

relative locationap back to ToC or Annotation Property ToC

IRI: http://purl.oclc.org/NET/UNIS/fiware/iot-lite#relativeLocation

Relative Location is used to provide a place for where the Device is in. For example, Geonames URIs can be used to represent a place, city, area, or region. For "University of Surrey" this would be "http://sws.geonames.org/6695971/"
has domain
pointc
has range
string

rightsap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/rights

titleap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/title

Namespace Declarations back to ToC

default namespace
http://purl.oclc.org/NET/UNIS/fiware/iot-lite#
dc
http://purl.org/dc/elements/1.1/
iot-lite
http://purl.oclc.org/NET/UNIS/fiware/iot-lite#
owl
http://www.w3.org/2002/07/owl#
qu
http://purl.org/NET/ssnx/qu/qu#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
ssn
http://purl.oclc.org/NET/ssnx/ssn#
wgs84_pos
http://www.w3.org/2003/01/geo/wgs84_pos#
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.