277
Semantic Technologies for IoT
From this, a reasoner may infer that no devices may have more than one deviceId
in a sensor network. This does not imply that every device must have at least one
device id in a network however.
• InverseFunctionalProperty: Properties may be inverse functional. If a property
is inverse functional, then the inverse of the property is functional. Therefore, the
inverse of the property will have at the most one value for every individual. As an
example, hasdeviceId (a distinctive identifier for the device in a network) is also
expressed to be inverse functional (or unambiguous). The inverse of this property
(which is also mentioned as isThedeviceIdFor) has at the most one value for any
device (for a unique network). Therefore, any one device’s deviceID is the only
value for its isThedeviceIdFor property. From this, a reasoner will deduce that no
two totally different individual instances of device have the identical deviceId in
an exceedingly unique network. Also, a reasoner will deduce that if two instances
of device in a unique network have a similar deviceID, then those two instances
confer with a similar device.
• SymmetricProperty: Properties may be identified to be symmetric. For example, is_connectedto may be defined as a symmetric property. Then a reasoner
can deduce that “Device_2” is_connectedto “Device_2” provided that “Device_1”
is_connectedto “Device_2.”
• inverseOf: Two properties are identified to be inverse to each other. For example, if
has_sensor is the inverse of has_network and “Network_A” has_sensor “Sensor_1,”
then a reasoner can deduce that “Sensor_1” has_network “Network_A.”
• TransitiveProperty: Properties may be well defined to be transitive. For example, if “part of” property is said to be transitive, and if Device_1 is a partOf
SensorA (i.e., (Device_1, SensorA) is an instance of the property partOf and
Device_2 is partOf Device_1 (i.e., (Device_2, Device_1) is an instance of the
property partOf, then a reasoner can deduce that Device_2 is a part of SensorA.
MaxCardinality 1 restriction is not allowed for transitive properties and their
super properties.
OWL Lite lets restrictions on properties that may be utilized by instances of a
class. The subsequent two restrictions limit the values that may be used, whereas
the cardinality restrictions limit how many values may be used.
• someValuesFrom: The restriction someValuesFrom is declared on a property
with regard to a class having a restriction that a minimum of one value for that
property is of a particular type.
• allValuesFrom: The restriction allValuesFrom declared on a property with
regard to a class implies that the property incorporates a local range restriction
related to it.
OWL Lite cardinality restrictions on properties allow having value zero or one.
They do not permit random values for cardinality, as is the case in OWL dl and
OWL Full. This permits the user to specify “at least one,” “no more than one,” and
“exactly one.”
• minCardinality: This restriction requires that the property should have a value
for all instances of the class. That is, if a minCardinality of one is given on a property with regard to a class, then any instance of that class is correlative to a minimum of one individual by that property.
Semantic Technologies for IoT
From this, a reasoner may infer that no devices may have more than one deviceId
in a sensor network. This does not imply that every device must have at least one
device id in a network however.
• InverseFunctionalProperty: Properties may be inverse functional. If a property
is inverse functional, then the inverse of the property is functional. Therefore, the
inverse of the property will have at the most one value for every individual. As an
example, hasdeviceId (a distinctive identifier for the device in a network) is also
expressed to be inverse functional (or unambiguous). The inverse of this property
(which is also mentioned as isThedeviceIdFor) has at the most one value for any
device (for a unique network). Therefore, any one device’s deviceID is the only
value for its isThedeviceIdFor property. From this, a reasoner will deduce that no
two totally different individual instances of device have the identical deviceId in
an exceedingly unique network. Also, a reasoner will deduce that if two instances
of device in a unique network have a similar deviceID, then those two instances
confer with a similar device.
• SymmetricProperty: Properties may be identified to be symmetric. For example, is_connectedto may be defined as a symmetric property. Then a reasoner
can deduce that “Device_2” is_connectedto “Device_2” provided that “Device_1”
is_connectedto “Device_2.”
• inverseOf: Two properties are identified to be inverse to each other. For example, if
has_sensor is the inverse of has_network and “Network_A” has_sensor “Sensor_1,”
then a reasoner can deduce that “Sensor_1” has_network “Network_A.”
• TransitiveProperty: Properties may be well defined to be transitive. For example, if “part of” property is said to be transitive, and if Device_1 is a partOf
SensorA (i.e., (Device_1, SensorA) is an instance of the property partOf and
Device_2 is partOf Device_1 (i.e., (Device_2, Device_1) is an instance of the
property partOf, then a reasoner can deduce that Device_2 is a part of SensorA.
MaxCardinality 1 restriction is not allowed for transitive properties and their
super properties.
OWL Lite lets restrictions on properties that may be utilized by instances of a
class. The subsequent two restrictions limit the values that may be used, whereas
the cardinality restrictions limit how many values may be used.
• someValuesFrom: The restriction someValuesFrom is declared on a property
with regard to a class having a restriction that a minimum of one value for that
property is of a particular type.
• allValuesFrom: The restriction allValuesFrom declared on a property with
regard to a class implies that the property incorporates a local range restriction
related to it.
OWL Lite cardinality restrictions on properties allow having value zero or one.
They do not permit random values for cardinality, as is the case in OWL dl and
OWL Full. This permits the user to specify “at least one,” “no more than one,” and
“exactly one.”
• minCardinality: This restriction requires that the property should have a value
for all instances of the class. That is, if a minCardinality of one is given on a property with regard to a class, then any instance of that class is correlative to a minimum of one individual by that property.