289
Semantic Technologies for IoT
ontology language can be applied. We have taken the domain of home automation scenario to provide security to home when occupants are out of home. The actors of the scenario are elucidated below:
• IoT application consumers and infrastructure owners: Buy applications and IoT devices
for their house such as alarm lights/lamp, air-conditioner, etc.
• IoT infrastructure and data providers: Home automation device sellers for devices
such as sensors, actuators, gateway boxes, IoT data feeds from the Cloud such as
temperature sensor, motion detection sensor, switch actuator, luminosity sensor,
and gateway box.
• IoT application providers: Software providers for the IoT home automation/building
management domain such as application for security monitoring and application
for energy monitoring.
• IoT semantic interoperability providers: Service providers for the semantic registry
and the alignment/matchmaking of IoT entities such as ontology alignment,
matchmaking, message translation, and message transformation.
Representing IoT entities and their alignments
The following ontology namespaces were utilized in the design of the required application
ontology:
http://purl.oclc.org/NET/ssnx/ssn# for conceptualizations related to sensing and observations of different sensors.
http://www.loa-cnr.it/ontologies/DUL.owl# for high-level generic ones from the DUL
ontology
http://purl.org/IoT/iot# for the IoT entities layer of the proposed IoT-ontology namespace.
For the sake of brevity, only the most relevant properties for IoT entities’ registration are
presented here. A physical object, a lamp can be registered by the end-user in the repository as:
Light
The label “Light” is provided as an annotation of the class of the object. The remotecontrolled electrical socket is registered as:
Semantic Technologies for IoT
ontology language can be applied. We have taken the domain of home automation scenario to provide security to home when occupants are out of home. The actors of the scenario are elucidated below:
• IoT application consumers and infrastructure owners: Buy applications and IoT devices
for their house such as alarm lights/lamp, air-conditioner, etc.
• IoT infrastructure and data providers: Home automation device sellers for devices
such as sensors, actuators, gateway boxes, IoT data feeds from the Cloud such as
temperature sensor, motion detection sensor, switch actuator, luminosity sensor,
and gateway box.
• IoT application providers: Software providers for the IoT home automation/building
management domain such as application for security monitoring and application
for energy monitoring.
• IoT semantic interoperability providers: Service providers for the semantic registry
and the alignment/matchmaking of IoT entities such as ontology alignment,
matchmaking, message translation, and message transformation.
Representing IoT entities and their alignments
The following ontology namespaces were utilized in the design of the required application
ontology:
http://purl.oclc.org/NET/ssnx/ssn# for conceptualizations related to sensing and observations of different sensors.
http://www.loa-cnr.it/ontologies/DUL.owl# for high-level generic ones from the DUL
ontology
http://purl.org/IoT/iot# for the IoT entities layer of the proposed IoT-ontology namespace.
For the sake of brevity, only the most relevant properties for IoT entities’ registration are
presented here. A physical object, a lamp can be registered by the end-user in the repository as:
The label “Light” is provided as an annotation of the class of the object. The remotecontrolled electrical socket is registered as: