Semantic Web of Things Ontology
type: Ontology
comment: Please report any errors to the author's email - "yangyunong@bupt.edu.cn" or "shower0512@bupt.edu.cn"
creator: Yunong Yang and Zhenyu Wu, BUPT
comment: To provide a uniform ontology of CPS applications, the SWoT base ontology (SWoT-O) is mainly referred to and extended from SSN ontology, as well as reusing other IoT ontologies

attached system
type: ObjectProperty
sub property of: isLocationOf
inverse of: on platform
comment: Relation between a Platform and any Systems (e.g., Sensors) that are attached to the Platform.

deployed on platform
type: ObjectProperty
sub property of: hasParticipant
inverse of: in deployment
comment: Relation between a deployment and the platform on which the system was deployed.

deployed system
type: ObjectProperty
sub property of: hasParticipant
inverse of: has deployment
comment: Relation between a deployment and the deployed system.

deployment process part
type: ObjectProperty
sub property of: hasPart
comment: Has part relation between a deployment process and its constituent processes.

detects
type: ObjectProperty
comment: A relation from a sensor to the Stimulus that the sensor can detect. The Stimulus itself will be serving as a proxy for (see isProxyOf) some observable property.

end time
type: ObjectProperty
sub property of: hasRegion

feature of interest
type: ObjectProperty
sub property of: isSettingFor
source: skos:exactMatch 'featureOfInterest' [O&M - ISO/DIS 19156] http://portal.opengeospatial.org/files/?artifact_id=41579
comment: A relation between an observation and the entity whose quality was observed. For example, in an observation of the weight of a person, the feature of interest is the person and the quality is weight.

for property
type: ObjectProperty
comment: A relation between some aspect of a sensing entity and a property. For example, from a sensor to the properties it can observe, or from a deployment to the properties it was installed to observe. Also from a measurement capability to the property the capability is described for. (Used in conjunction with ofFeature).

has deployment
type: ObjectProperty
sub property of: isParticipantIn
comment: Relation between a System and a Deployment, recording that the System/Sensor was deployed in that Deployment.

has input
type: ObjectProperty

has measurement capability
type: ObjectProperty
sub property of: has property
comment: Relation from a Sensor to a MeasurementCapability describing the measurement properties of the sensor.

has measurement property
type: ObjectProperty
sub property of: has property
comment: Relation from a MeasurementCapability to a MeasurementProperty. For example, to an accuracy (see notes at MeasurementCapability).

has output
type: ObjectProperty

has property
type: ObjectProperty
sub property of: hasQuality
inverse of: is property of
comment: A relation between a FeatureOfInterest and a Property of that feature.

has subsystem
type: ObjectProperty
sub property of: hasPart
comment: Haspart relation between a system and its parts.

has survival property
type: ObjectProperty
sub property of: has property
comment: Relation from a SurvivalRange to a Property describing the survial range of a system. For example, to the temperature extreme that a system can withstand before being considered damaged.

has survival range
type: ObjectProperty
sub property of: has property
comment: A Relation from a System to a SurvivalRange.

has value
type: ObjectProperty
sub property of: hasRegion

implemented by
type: ObjectProperty
sub property of: describes
inverse of: implements
comment: A relation between the description of an algorithm, procedure or method and an entity that implements that method in some executable way. For example, between a scientific measuring method and a sensor the senses via that method.

implements
type: ObjectProperty
sub property of: isDescribedBy
comment: A relation between an entity that implements a method in some executable way and the description of an algorithm, procedure or method. For example, between a Sensor and the scientific measuring method that the Sensor uses to observe a Property.

in condition
type: ObjectProperty
comment: Describes the prevailing environmental conditions for MeasurementCapabilites, OperatingConditions and SurvivalRanges. Used for example to say that a sensor has a particular accuracy in particular conditions. (see also MeasurementCapability)

in deployment
type: ObjectProperty
sub property of: isParticipantIn
comment: Relation between a Platform and a Deployment, recording that the object was used as a platform for a system/sensor for a particular deployment: as in this PhysicalObject is acting as a Platform inDeployment Deployment.

is produced by
type: ObjectProperty
comment: Relation between a producer and a produced entity: for example, between a sensor and the produced output.

is property of
type: ObjectProperty
sub property of: isQualityOf
comment: Relation between a FeatureOfInterest and a Property (a Quality observable by a sensor) of that feature.

isProxyFor
type: ObjectProperty
comment: A relation from a Stimulus to the Property that the Stimulus is serving as a proxy for. For example, the expansion of the quicksilver is a stimulus that serves as a proxy for temperature, or an increase or decrease in the spinning of cups on a wind sensor is serving as a proxy for wind speed.

made observation
type: ObjectProperty
sub property of: isObjectIncludedIn
inverse of: observedBy
comment: Relation between a Sensor and Observations it has made.

observation result
type: ObjectProperty
sub property of: isSettingFor
source: skos:closeMatch 'result' [O&M - ISO/DIS 19156] http://portal.opengeospatial.org/files/?artifact_id=41579
comment: Relation linking an Observation (i.e., a description of the context, the Situation, in which the observatioin was made) and a Result, which contains a value representing the value associated with the observed Property.

observation result time
type: ObjectProperty
sub property of: hasRegion
source: http://www.opengeospatial.org/standards/om
comment: The result time is the time when the procedure associated with the observation act was applied.
comment: The result time shall describe the time when the result became available, typically when the procedure associated with the observation was completed For some observations this is identical to the phenomenonTime. However, there are important cases where they differ.[O&M]

observation sampling time
type: ObjectProperty
sub property of: hasRegion
source: http://www.opengeospatial.org/standards/om
comment: Rebadged as phenomenon time in [O&M]. The phenomenon time shall describe the time that the result applies to the property of the feature-of-interest. This is often the time of interaction by a sampling procedure or observation procedure with a real-world feature.
comment: The sampling time is the time that the result applies to the feature-of-interest. This is the time usually required for geospatial analysis of the result.

observedBy
type: ObjectProperty
sub property of: includesObject

observed property
type: ObjectProperty
sub property of: isSettingFor
source: skos:exactMatch 'observedProperty' [O&M - ISO/DIS 19156] http://portal.opengeospatial.org/files/?artifact_id=41579
comment: Relation linking an Observation to the Property that was observed. The observedProperty should be a Property (hasProperty) of the FeatureOfInterest (linked by featureOfInterest) of this observation.

observes
type: ObjectProperty
property chain axiom: has measurement capability
property chain axiom: for property
property chain axiom: made observation
property chain axiom: observed property
comment: Relation between a Sensor and a Property that the sensor can observe. Note that, given the DUL modelling of Qualities, a sensor defined with 'observes only Windspeed' technically links the sensor to particular instances of Windspeed, not to the concept itself - OWL can't express concept-concept relations, only individual-individual. The property composition ensures that if an observation is made of a particular quality then one can infer that the sensor observes that quality.

of feature
type: ObjectProperty
comment: A relation between some aspect of a sensing entity and a feature. For example, from a sensor to the features it can observe properties of, or from a deployment to the features it was installed to observe. Also from a measurement capability to the feature the capability is described for. (Used in conjunction with forProperty).

on platform
type: ObjectProperty
sub property of: hasLocation
comment: Relation between a System (e.g., a Sensor) and a Platform. The relation locates the sensor relative to other described entities entities: i.e., the Sensor s1's location is Platform p1. More precise locations for sensors in space (relative to other entities, where attached to another entity, or in 3D space) are made using DOLCE's Regions (SpaceRegion).

quality of observation
type: ObjectProperty
sub property of: has property
source: skos:exactMatch 'resultQuality' [O&M - ISO/DIS 19156] http://portal.opengeospatial.org/files/?artifact_id=41579
comment: Relation linking an Observation to the adjudged quality of the result. This is of course complimentary to the MeasurementCapability information recorded for the Sensor that made the Observation.

start time
type: ObjectProperty
sub property of: hasRegion

describes
type: ObjectProperty

hasLocation
type: ObjectProperty
sub property of: has

hasPart
type: ObjectProperty

hasParticipant
type: ObjectProperty

hasQuality
type: ObjectProperty

hasRegion
type: ObjectProperty

includesEvent
type: ObjectProperty

includesObject
type: ObjectProperty

isDescribedBy
type: ObjectProperty

isLocationOf
type: ObjectProperty

isObjectIncludedIn
type: ObjectProperty

isParticipantIn
type: ObjectProperty

isQualityOf
type: ObjectProperty

isRegionFor
type: ObjectProperty

isSettingFor
type: ObjectProperty

generate
type: ObjectProperty

hasPotCause
type: ObjectProperty

hasState
type: ObjectProperty
sub property of: topObjectProperty

hasUnit
type: ObjectProperty
sub property of: has

isOwnedBy
type: ObjectProperty

subscribe
type: ObjectProperty

triggers
type: ObjectProperty

description
type: DatatypeProperty

linkTo
type: DatatypeProperty

name
type: DatatypeProperty

Device
type: Class
subclass of: WoT_Entity
subclass of: Restriction
  on property: hasSpot
  some values from: Spot
subclass of: Restriction
  on property: hasState
  some values from: State
subclass of: Restriction
  on property: isOwnedBy
  some values from: Owner
subclass of: Restriction
  on property: hasLocation
  all values from: Region
subclass of: Restriction
  on property: hasType
  all values from: EntityType
subclass of: Restriction
  on property: hasValue
  all values from: float
source: http://www.w3.org/2005/Incubator/ssn/
comment: A device is a physical piece of technology - a system in a box. Devices may of course be built of smaller devices and software components (i.e. systems have components).

Sensor
type: Class
subclass of: Device
subclass of: Restriction
  on property: detects
  some values from: Anomaly
subclass of: Restriction
  on property: generate
  some values from: ObservedCause
source: skos:exactMatch 'sensor' [SensorML OGC-0700] http://www.opengeospatial.org/standards/sensorml skos:closeMatch 'observation procedure' [O&M] http://www.opengeospatial.org/standards/om O&M allows sensors, methods, instruments, systems, algorithms and process chains as the processUsed of an observation; this ontology allows a similar range of things (any thing that can do sensing), just they are all grouped under the term sensor (which is thus wider than the O&M concept).
comment: A sensor can do (implements) sensing: that is, a sensor is any entity that can follow a sensing method and thus observe some Property of a FeatureOfInterest. Sensors may be physical devices, computational methods, a laboratory setup with a person following a method, or any other thing that can follow a Sensing Method to observe a Property.

Stimulus
type: Class
subclass of: Event
source: http://www.w3.org/2005/Incubator/ssn/
comment: An Event in the real world that 'triggers' the sensor. The properties associated to the stimulus may be different to eventual observed property. It is the event, not the object that triggers the sensor.

Event
type: Class
subclass of: Restriction
  on property: observation sampling time
  all values from: dateTime

Anomaly
type: Class
subclass of: Stimulus
subclass of: Restriction
  on property: hasPotCause
  all values from: ObservedCause

Cooling
type: Class
subclass of: SensorProperty
has neg infl: Energy
high threshold: 26.0
low threshold: 20.0

EntityType
type: Class
subclass of: WoTProperty

Location
type: Class
subclass of: WoTProperty

ObservedCause
type: Class
subclass of: Event

Occupation
type: Class
subclass of: SensorProperty
has neg infl: AirQuality
has pos infl: Energy
high threshold: 30.0

Owner
type: Class
subclass of: WoTProperty

PhysicalProcess
type: Class
subclass of: Process
subclass of: Restriction
  on property: has input
  all values from: SensorProperty
subclass of: Restriction
  on property: has output
  all values from: SensorProperty

Region
type: Class
subclass of: Location
comment: large scale location

Spot
type: Class
subclass of: Location
comment: small scale location

State
type: Class
subclass of: Restriction
  on property: hasValue
  all values from: int

Temperature
type: Class
subclass of: SensorProperty
high threshold: 26.0
low threshold: 20.0

WoT_Entity
type: Class
subclass of: Restriction
  on property: has
  some values from: WoTProperty
subclass of: Restriction
  on property: of feature
  all values from: FeatureOfInterest
subclass of: Restriction
  on property: description
  all values from: string
subclass of: Restriction
  on property: name
  all values from: string

high
type: NamedIndividual
type: High
has value: 1

low
type: NamedIndividual
type: Low
has value: -1

nomal
type: NamedIndividual
type: Nomal
has value: 0