Copyright © 2017 OGC & W3C ® ( MIT, ERCIM, Keio, Beihang), W3C liability, trademark and document use rules apply.
The Semantic Sensor Network (SSN) ontology is an ontology for describing sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties, as well as actuators. SSN follows a horizontal and vertical modularization architecture by including a lightweight but self-contained core ontology called SOSA (Sensor, Observation, Sample, and Actuator) for its elementary classes and properties. With their different scope and different degrees of axiomatization, SSN and SOSA are able to support a wide range of applications and use cases, including satellite imagery, large-scale scientific monitoring, industrial and household infrastructures, social sensing, citizen science, observation-driven ontology engineering, and the Web of Things. Both ontologies are described below, and examples of their usage are given.
The namespace for SSN terms is http://www.w3.org/ns/ssn/.
The namespace for SOSA terms is
http://www.w3.org/ns/sosa/.
The suggested prefix for the SSN namespace is ssn.
The suggested prefix for the SOSA namespace is sosa.
The SSN ontology is available at http://www.w3.org/ns/ssn/.
The SOSA ontology is available at http://www.w3.org/ns/sosa/.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.
General Information
For OGC this is a Public Draft of a document prepared by the Spatial Data on the Web Working Group (SDWWG) — a joint W3C-OGC project (see charter). The document is prepared following W3C conventions. The document is released at this time to solicit public comment.
This document was published by the Spatial Data on the Web Working Group as a Proposed Recommendation. This document is intended to become a W3C Recommendation. Comments regarding this document are welcome. Please send them to public-sdw-comments@w3.org (subscribe, archives). The W3C Membership and other interested parties are invited to review the document and send comments to public-sdw-comments@w3.org (subscribe, archives) through 05 October 2017. Advisory Committee Representatives should consult their WBS questionnaires. Note that substantive technical comments were expected during the Candidate Recommendation review period that ended 08 August 2017.
Please see the Working Group's implementation report.
Publication as a Proposed Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
This document is governed by the 1 March 2017 W3C Process Document.
This section is non-normative.
Sensors are a major source of data available on the Web today. While sensor data may be published as mere values, searching, reusing, integrating, and intepreting these data requires more than just the observation results. Of equal importance for the proper interpretation of these values is information about the studied feature of interest, such as a river, the observed property, such as flow velocity, the utilized sampling strategy, such as the specific locations and times at which the velocity was measured, and a variety of other information. OGC's Sensor Web Enablement standards [ OandM], [SensorML] provide a means to annotate sensors and their observations. However, these standards are not integrated and aligned with W3C Semantic Web technologies and Linked Data in particular, which are key drivers for creating and maintaining a global and densely interconnected graph of data. With the rise of the Web of Things and smart cities and homes more generally, actuators and the data they produce also become first-class citizens of the Web. Given their close relation to sensors, observations, procedures, and features of interest, it is desirable to provide a common ontology that also includes actuators and actuation. Finally, with the increasing diversity of data and data providers, definitions such as those for sensors need to be broadened, e.g., to include social sensing. The following specifications introduce the new Semantic Sensor Network (SSN) and Sensor, Observation, Sample, and Actuator (SOSA) ontologies that are set out to provide flexible but coherent perspectives for representing the entities, relations, and activities involved in sensing, sampling, and actuation. SOSA provides a lightweight core for SSN and aims at broadening the target audience and application areas that can make use of Semantic Web ontologies. At the same time, SOSA acts as minimal interoperability fall-back level, i.e., it defines those common classes and properties for which data can be safely exchanged across all uses of SSN, its modules, and SOSA.
This section is non-normative.
Practitioners using the original Semantic Sensor Network Ontology as defined in the W3C Semantic Sensor Network Incubator Group [SSNO] have identified a major issue in its complexity, partly due to the layering underneath the Dolce-UltraLite (DUL) upper level ontology. In response to this, the new Semantic Sensor Network (SSN) ontology offers several ontology subsets that are distinguished mainly through their ontological commitments. This section explains the rationale and method for modularizing SSN, i.e., offering several distinct ontologies that are similar in their domain of discourse, but with different ontological commitments, suitable to several use cases and target audiences. For example, SOSA is intended to provide Schema.org-style semantic enrichment capabilities for data repositories managed by an audience broader than typical ontology engineers, while still ensuring interoperability with SSN-based repositories.
Ontology modularization is a common method used in ontology engineering to segment an ontology into smaller parts. In general, ontology modularization aims at providing users of ontologies with the knowledge they require, reducing the scope as much as possible to what is strictly necessary in a given use case. Two main categories of ontology modularization can be distinguished.
The first category comprises those approaches that focus on the composition of existing ontologies by means of integrating and mapping ontologies, most commonly through owl:import
statements. OWL import has a direction from a dependent
ontology to a dependency ontology. Although import is transitive, knowledge is propagated in only one direction. The importing ontology assumes all the meaning of the imported terms used, by including all axioms relevant to the meaning of
these terms. However, the imported ontology does not capture any of the semantics of the importing ontology.
The second category comprises of mapping approaches that aim to partition and extract parts of ontologies as modules. These mapping approaches are not necessarily directional, but most approaches of ontology extraction rely on the directionality of the imported modules. The main feature of an ontology module under the second category is that it is self-contained, i.e., the module captures the meaning of the imported terms used by including all axioms relevant to the meaning of these terms. This means, that the result of certain reasoning tasks such as subsumption or query answering within a single module should be possible and result in the same answers without the need to access other modules of the ontology.
Our modularization uses the first approach by composing the ontology into several modules that use owl:import
statements, whereby we distinguish two methods depending on the directionality of the segmentation: a vertical segmentation
and a horizontal segmentation.
Vertical modules build upon each other, i.e., they directionally owl:import
lower level modules. Lower level modules are independent of their higher level modules and logically consistent on their own.
For example, the Dolce-UltraLite Alignment Module imports the SSN Ontology which itself imports the SOSA Ontology. However, in reverse, neither SOSA nor SSN import the Dolce-UltraLite Alignment Module. In fact, SOSA as the core, does not import any other ontologies, which makes it truly independent of vertical modules that add more expressivity and further ontological commitments to the lightweight semantics of SOSA.
Note that higher level here is not to be confused with upper level ontologies. Upper level ontologies are general knowledge ontologies that can be directionally imported in many domains, whereas our definition of higher level ontologies here refers to an ontology that extends one or several ontology modules to capture a larger part of a knowledge domain and/or combine knowledge domains.
Modules that are horizontally layered may depend on each other, i.e., they may rely on the directional import of another horizontal module. Only one horizontal module that is dependent on the SSN ontology is presented in this specification, the Sample Relations Module. Other ontologies that add domain-specific terms to SSN, but require the import of SSN, can be considered horizontal modules.
This section is non-normative.
Here we briefly review the origins of SSN and SOSA, namely the initial SSN version published by the W3C Semantic Sensor Network Incubator Group [SSNO] and work on Sensor Web Enablement by the OGC. We also highlight the most substantial changes made since the initial release of the SSN ontology.
Starting in 2002, the OGC's Sensor Web Enablement initiative has developed a generic framework for delivering sensor data, dealing with remote-sensing, moving platforms, and in-situ monitoring and sensing. The Sensor Observation Service defines a standard query interface for sensor and observation data, following the pattern established by OGC for their Web Services. The returned XML data conforms with the Sensor Model Language [SensorML] and OMXML [OMXML], whereby the latter implements Observations and Measurements [OandM].
SensorML and O&M are complementary viewpoints. SensorML is 'provider-centric' and encodes details of the sensor along with raw observation data. SensorML is self-contained and highly flexible. This makes life easy for data producers but is demanding on consumers. SensorML provides extensive support for serialization of numeric data arrays and is particularly optimized for data that includes multiple parallel streams that must be processed together. For example, the data collected by cameras on airborne vehicles must be geo-referenced based on the instantaneous position of the platform and orientation of the camera. In contrast, O&M was designed to be more 'user-centric' with the target of the observation and the observed property as first-class objects. O&M works at a higher semantic level than SensorML, but only provides abstract classes for sensors, features of interest and observable properties, expecting the details to be provided by specific applications and domains. O&M also provided a model for sampling, since almost all scientific observations are made on a subset of, or proxy for, the ultimate feature of interest.
The initial W3C Semantic Sensor Network Incubator Group ontology (SSN) was built around an ontology design pattern called the Stimulus Sensor Observation (SSO) pattern [SSO-Pattern]. The SSO was developed as a minimal and common ground for heavy-weight ontologies for the use on the Semantic Sensor Web as well as to explicitly address the need for light-weight semantics requested by the Linked Data community. The SSO was also aligned to the Dolce-Ultralite upper ontology (DUL).
The new SSN described in this document is based on a revised and expanded version of this pattern, namely the Sensor, Observation,
Sample, and Actuator (SOSA) ontology. Similar to the original SSO, SOSA acts as a central building block for the SSN but puts more emphasis on light-weight use and the ability to be used standalone. The axiomatization also changed to
provide an experience more related to Schema.org. Notable differences include the usage of the Schema.org
domainIncludes
and rangeIncludes
annotation properties that provide an informal semantics compared to the inferential semantics of their OWL 2 counterparts. In line with the changes implemented for the new SSN, SOSA
also drops the direct DUL alignment although an optional alignment can be achieved via the SSN-DUL alignment provided in Section 6.1. SOSA is also more explicit than SSO in its support for virtual and human sensor.
Finally, and most notably, SOSA extends SSO's original scope beyond sensors and their observations by including classes and properties for actuators and sampling. SOSA also distinguishes between phenomenonTime
and
resultTime
.
Drawing on considerable implementation and application experience with SSN and sensor and observation ontologies more broadly, the new SSN and SOSA ontologies presented here are set out to address changes in scope and audience, shortcomings of the initial work, as well as new technical developments. The list below highlights the most important (but by far not exclusive) updates.
domainIncludes
and rangeIncludes
annotation properties defined in Schema.org. These had not been available before.This section introduces the specifications for SOSA and SSN.
The namespace for SSN terms is http://www.w3.org/ns/ssn/.
The namespace for SOSA terms is http://www.w3.org/ns/sosa/.
The suggested prefix for the SSN namespace is ssn.
The suggested prefix for the SOSA namespace is sosa.
The SSN ontology is available at http://www.w3.org/ns/ssn/.
The SOSA ontology is available at http://www.w3.org/ns/sosa/.
This section is non-normative.
Classes: sosa:ActuatableProperty , sosa:Actuation , sosa:Actuator , ssn:Deployment , sosa:FeatureOfInterest , ssn:Input , sosa:ObservableProperty , sosa:Observation , ssn:Output , sosa:Platform , ssn:Property , sosa:Procedure , sosa:Result , sosa:Sample , sosa:Sampler , sosa:Sampling , sosa:Sensor , ssn:Stimulus , ssn:System
Object Properties: sosa:actsOnProperty , sosa:madeByActuator , ssn:deployedOnPlatform , ssn:deployedSystem , ssn:detects , ssn:forProperty , ssn:hasDeployment , sosa:hasFeatureOfInterest , ssn:hasInput , ssn:hasOutput , ssn:hasProperty , sosa:hasResult , sosa:hasSample , ssn:hasSubSystem , sosa:hosts , ssn:implementedBy , ssn:implements , ssn:inDeployment , sosa:isActedOnBy , sosa:isFeatureOfInterestOf , sosa:isHostedBy , sosa:isObservedBy , ssn:isPropertyOf , ssn:isProxyFor , sosa:isResultOf , sosa:isSampleOf , sosa:madeActuation , sosa:madeBySampler , sosa:madeBySensor , sosa:madeObservation , sosa:madeSampling , sosa:observedProperty , sosa:observes , sosa:phenomenonTime , sosa:usedProcedure , ssn:wasOriginatedBy
Datatype Properties: sosa:hasSimpleResult , sosa:resultTime
Several conceptual modules have been defined to cover key sensor, actuation and sampling concepts. The different conceptual modules of SOSA/SSN can be seen in the following figure.
An overview of the main classes and properties inside the ontology modules can be seen in the following figures, from the perspectives of Observation, Actuation and Sampling. In the figures, and in the rest of the document, SOSA-related components and restrictions are shown in green, while SSN-only components are shown in blue.
This section is non-normative.
The following figure provides an overview of the core classes and properties that are secifically related to modeling Observations. SOSA axioms are shown in green, while SSN-only axioms are shown in blue.
The following examples illustrate how the terms related to Observation can be used:
This section introduces the following classes and properties:
sosa:ObservableProperty, sosa:Observation, sosa:observedProperty, sosa:phenomenonTime, sosa:Sensor, sosa:observes, sosa:isObservedBy, sosa:madeObservation, sosa:madeBySensor, ssn:Stimulus, ssn:isProxyFor, ssn:wasOriginatedBy, ssn:detects
IRI: http://www.w3.org/ns/sosa/ObservableProperty
a OWL Class
Observable Property - An observable quality (property, characteristic) of aFeatureOfInterest
.
Example | The height of a tree, the depth of a water body, or the temperature of a surface are examples of observable properties, while the value of a classic car is not (directly) observable but asserted. |
---|---|
Sub class of | ssn:Property |
Restrictions |
sosa:isObservedBy
ONLY sosa:Sensor
inverse Of sosa:observedProperty ONLY sosa:Observation inverse Of ssn:isProxyFor ONLY ssn:Stimulus |
is Defined By | http://www.w3.org/ns/sosa/ |
IRI: http://www.w3.org/ns/sosa/Observation
a OWL Class
Observation - Act of carrying out an (Observation)Procedure
to estimate or calculate a value of a property of a FeatureOfInterest
. Links to a Sensor
to describe what made the Observation
and how; links to an ObservableProperty
to describe what the result is an estimate of, and to a FeatureOfInterest
to detail what that property was associated with.Example | The activity of estimating the intensity of an Earthquake using the Mercalli intensity scale is an Observation as is measuring the moment magnitude, i.e., the energy released by said earthquake. |
---|---|
Restrictions |
sosa:madeBySensor
EXACTLY 1
sosa:madeBySensor ONLY sosa:Sensor sosa:usedProcedure ONLY sosa:Procedure sosa:hasFeatureOfInterest EXACTLY 1 sosa:hasFeatureOfInterest ONLY sosa:FeatureOfInterest sosa:observedProperty EXACTLY 1 sosa:observedProperty ONLY sosa:ObservableProperty ssn:wasOriginatedBy EXACTLY 1 ssn:wasOriginatedBy ONLY ssn:Stimulus sosa:phenomenonTime EXACTLY 1 sosa:hasResult MIN 1 sosa:hasResult ONLY sosa:Result sosa:resultTime EXACTLY 1 |
IRI: http://www.w3.org/ns/sosa/observedProperty
a OWL Object Property
observed property - Relation linking anObservation
to the property that was observed. The ObservableProperty
should be a property of the FeatureOfInterest
(linked by hasFeatureOfInterest
) of this Observation
.
Domain Includes | sosa:Observation |
---|---|
Range Includes | sosa:ObservableProperty |
IRI: http://www.w3.org/ns/sosa/phenomenonTime
a OWL Object Property
phenomenon time - The time that theResult
of an Observation
, Actuation
, or Sampling
applies to the FeatureOfInterest
. Not necessarily the same as the resultTime
. May be an interval or an instant, or some other compound temporal entity [owl-time]. Domain Includes | sosa:Actuation, sosa:Observation, sosa:Sampling |
---|---|
Range Includes | time:TemporalEntity |
IRI: http://www.w3.org/ns/sosa/Sensor
a OWL Class
Sensor - Device, agent (including humans), or software (simulation) involved in, or implementing, aProcedure
. Sensors
respond to a Stimulus
, e.g., a change in the environment, or Input
data composed from the Results
of prior Observations
, and generate a Result
. Sensors
can be hosted by Platforms
.
Example | Accelerometers, gyroscopes, barometers, magnetometers, and so forth are Sensors that are typically mounted on a modern smart phone (which acts as Platform ). Other examples of Sensors include the human eyes. |
---|---|
Sub class of | ssn:System |
Restrictions |
ssn:implements
MIN 1
sosa:observes ONLY sosa:ObservableProperty ssn:detects ONLY ssn:Stimulus sosa:madeObservation ONLY sosa:Observation |
IRI: http://www.w3.org/ns/sosa/observes
a OWL Object Property
observes - Relation between aSensor
and an ObservableProperty
that it is capable of sensing. Domain Includes | sosa:Sensor |
---|---|
Range Includes | sosa:ObservableProperty |
Inverse property of | sosa:isObservedBy |
Sub property of | ssn:forProperty |
IRI: http://www.w3.org/ns/sosa/isObservedBy
a OWL Object Property
is observed by - Relation between anObservableProperty
and the Sensor
able to observe it.
Domain Includes | sosa:ObservableProperty |
---|---|
Range Includes | sosa:Sensor |
Inverse property of | sosa:observes |
IRI: http://www.w3.org/ns/sosa/madeObservation
a OWL Object Property
made observation - Relation between aSensor
and an Observation
made by the Sensor
. Domain Includes | sosa:Sensor |
---|---|
Range Includes | sosa:Observation |
Inverse property of | sosa:madeBySensor |
IRI: http://www.w3.org/ns/sosa/madeBySensor
a OWL Object Property
made bySensor
-
Relation between an Observation
and the Sensor
which made the Observations
. Domain Includes | sosa:Observation |
---|---|
Range Includes | sosa:Sensor |
Inverse property of | sosa:madeObservation |
IRI: http://www.w3.org/ns/ssn/Stimulus
a OWL Class
Stimulus - An event in the real world that 'triggers' theSensor
. The properties associated to the Stimulus
may be different to the eventual observed ObservableProperty
. It is the event, not the object, that triggers the Sensor
.
Restrictions |
ssn:isProxyFor
ONLY sosa:ObservableProperty
inverse Of ssn:wasOriginatedBy ONLY sosa:Observation inverse Of ssn:detects ONLY sosa:Sensor |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/isProxyFor
a OWL Object Property
isProxyFor - A relation from aStimulus
to the Property
that the Stimulus
is serving as a proxy for.
Example |
For example, the expansion of quicksilver is a Stimulus that serves as a proxy for some temperature Property . An increase or decrease in the velocity of spinning cups on a wind Sensor is serving as a proxy for the wind speed. |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/wasOriginatedBy
a OWL Object Property
was originated by - Relation between anObservation
and the Stimulus
that originated it.
is Defined By | http://www.w3.org/ns/ssn/ |
---|
IRI: http://www.w3.org/ns/ssn/detects
a OWL Object Property
detects - A relation from aSensor
to the Stimulus
that the Sensor
detects. The Stimulus
itself will be serving as a proxy (isProxyFor
) for some ObservableProperty
.
is Defined By | http://www.w3.org/ns/ssn/ |
---|
This section is non-normative.
The following figure provides an overview of the core classes and properties that are secifically related to modeling Actuations. SOSA axioms are shown in green, while SSN-only axioms are shown in blue.
The following example illustrate how the terms related to Actuations can be used:
This section introduces the following classes and properties:
sosa:ActuatableProperty, sosa:Actuation, sosa:actsOnProperty, sosa:isActedOnBy, sosa:Actuator, sosa:madeActuation, sosa:madeByActuator
IRI: http://www.w3.org/ns/sosa/ActuatableProperty
a OWL Class
Actuatable Property - An actuatable quality (property, characteristic) of aFeatureOfInterest
. Example | A window actuator acts by changing the state between a frame and a window. The ability of the window to be opened and closed is its ActuatableProperty . |
---|---|
Sub class of | ssn:Property |
Restriction | sosa:isActedOnBy ONLY sosa:Actuation |
is Defined By | http://www.w3.org/ns/sosa/ |
IRI: http://www.w3.org/ns/sosa/Actuation
a OWL Class
Actuation - AnActuation
carries out an (Actuation) Procedure
to change the state of the world using an Actuator
. Example | The activity of automatically closing a window if the temperature in a room drops below 20 degree Celsius. The activity is the Actuation and the device that closes the window is the Actuator . The Procedure is the rule, plan, or specification that defines the Conditions that triggers the Actuation , here a drop in temperature. |
---|---|
Restrictions |
sosa:madeByActuator
EXACTLY 1
sosa:madeByActuator ONLY sosa:Actuator sosa:usedProcedure ONLY sosa:Procedure sosa:hasFeatureOfInterest EXACTLY 1 sosa:hasFeatureOfInterest ONLY sosa:FeatureOfInterest sosa:actsOnProperty MIN 1 sosa:actsOnProperty ONLY sosa:ActuatableProperty sosa:hasResult MIN 1 sosa:hasResult ONLY sosa:Result sosa:resultTime EXACTLY 1 |
IRI: http://www.w3.org/ns/sosa/actsOnProperty
a OWL Object Property
acts on property - Relation between anActuation
and the property of a FeatureOfInterest
it is acting upon. Example | In the activity (Actuation ) of automatically closing a window if the temperature in a room drops below 20 degrees Celsius, the property on which the Actuator acts upon is the state of the window as it changes from being open to being closed. |
---|---|
Domain Includes | sosa:Actuation |
Range Includes | sosa:ActuatableProperty |
Inverse property of | sosa:isActedOnBy |
IRI: http://www.w3.org/ns/sosa/isActedOnBy
a OWL Object Property
is acted on by - Relation between anActuatableProperty
of a FeatureOfInterest
and an Actuation
changing its state. Example | In the activity (Actuation ) of automatically closing a window if the temperature in a room drops below 20 degrees Celsius, the property on which the Actuator acts upon is the state of the window as it changes from being open to being closed. |
---|---|
Domain Includes | sosa:ActuatableProperty |
Range Includes | sosa:Actuation |
Inverse property of | sosa:actsOnProperty |
IRI: http://www.w3.org/ns/sosa/Actuator
a OWL Class
Actuator - A device that is used by, or implements, an (Actuation)Procedure
that changes the state of the world. Example | A window actuator for automatic window control, i.e., opening or closing the window. |
---|---|
Sub class of | ssn:System |
Restrictions |
ssn:implements
MIN 1
ssn:forProperty ONLY sosa:ActuatableProperty sosa:madeActuation ONLY sosa:Actuation |
IRI: http://www.w3.org/ns/sosa/madeActuation
a OWL Object Property
made actuation - Relation between anActuator
and the Actuation
made by the Actuator
. Domain Includes | sosa:Actuator |
---|---|
Range Includes | sosa:Actuation |
Inverse property of | sosa:madeByActuator |
IRI: http://www.w3.org/ns/sosa/madeByActuator
a OWL Object Property
made by actuator - Relation linking anActuation
to the Actuator
that made that Actuation
.
Domain Includes | sosa:Actuation |
---|---|
Range Includes | sosa:Actuator |
Inverse property of | sosa:madeActuation |
This section is non-normative.
The following figure provides an overview of the core classes and properties that are secifically related to modeling Samplings. SOSA axioms are shown in green, while SSN-only axioms are shown in blue.
The following examples illustrate how the terms related to Samplings can be used:
This section introduces the following classes and properties:
sosa:Sample, sosa:hasSample, sosa:isSampleOf, sosa:Sampling, sosa:Sampler, sosa:madeSampling, sosa:madeBySampler
IRI: http://www.w3.org/ns/sosa/Sample
a OWL Class
Sample - Feature which is intended to be representative of aFeatureOfInterest
on which Observations
may be made. Comment | Samples are typically subsets or extracts from the feature of interest of an observation. They are used in situations where observations cannot be made directly on the ultimate feature of interest, either because the entire feature cannot be observed, or because it is more convenient to use a proxy. Samples are thus artifacts of an observational strategy, and usually have no significant function outside of their role in the observation process. The characteristics of the samples themselves are generally of little interest, except to the manager of a sampling campaign, or sample curator.
A Sample is intended to sample some FeatureOfInterest, so there is an expectation of at least one isSampleOf property. However, in some cases the identity, and even the exact type, of the sampled feature may not be known when observations are made using the sampling features. Physical samples are sometimes known as 'specimens'. |
---|---|
Example | A 'station' is essentially an identifiable locality where a Sensor system or procedure may be deployed and an observation made. In the context of the observation model, it connotes the 'world in the vicinity of the station', so the observed properties relate to the physical medium at the station, and not to any physical artifact such as a mooring, buoy, benchmark, monument, well, etc.
A statistical sample is often designed to be characteristic of an entire population, so that Observations can be made regarding the sample that provide a good estimate of the properties of the population.
|
Sub class of | sosa:FeatureOfInterest, sosa:Result |
Restrictions |
sosa:isResultOf
ONLY sosa:Sampling
sosa:isResultOf MIN 1 sosa:Sampling sosa:isSampleOf ONLY sosa:FeatureOfInterest sosa:isSampleOf MIN 1 |
is Defined By | http://www.w3.org/ns/sosa/ |
IRI: http://www.w3.org/ns/sosa/hasSample
a OWL Object Property
has sample - Relation between aFeatureOfInterest
and the Sample
used to represent it.
Domain Includes | sosa:FeatureOfInterest |
---|---|
Range Includes | sosa:Sample |
Inverse property of | sosa:isSampleOf |
is Inverse-Functional |
IRI: http://www.w3.org/ns/sosa/isSampleOf
a OWL Object Property
is sample of - Relation from aSample
to the FeatureOfInterest
that it is intended to be representative of. Domain Includes | sosa:Sample |
---|---|
Range Includes | sosa:FeatureOfInterest |
Inverse property of | sosa:hasSample |
is Functional |
IRI: http://www.w3.org/ns/sosa/Sampling
a OWL Class
Sampling - An act ofSampling
carries out a (Sampling) Procedure
to create or transform one or more Samples
.
Example |
Crushing a rock sample in a ball mill. Digging a pit through a soil sequence. Dividing a field site into quadrants. Drawing blood from a patient. Drilling an observation well. Establishing a station for environmental monitoring. Registering an image of the landscape. Sieving a powder to separate the subset finer than 100-mesh. Selecting a subset of a population. Splitting a piece of drill-core to create two new samples. Taking a diamond-drill core from a rock outcrop. |
---|---|
Restrictions |
sosa:madeBySampler
EXACTLY 1
sosa:madeBySampler ONLY sosa:Sampler sosa:usedProcedure ONLY sosa:Procedure sosa:hasFeatureOfInterest EXACTLY 1 sosa:hasFeatureOfInterest ONLY sosa:FeatureOfInterest sosa:hasResult MIN 1 sosa:Sample sosa:hasResult ONLY sosa:Sample sosa:resultTime EXACTLY 1 |
IRI: http://www.w3.org/ns/sosa/Sampler
a OWL Class
Sampler - A device that is used by, or implements, a (Sampling)Procedure
to create or transform one or more samples. Example | A ball mill, diamond drill, hammer, hypodermic syringe and needle, image Sensor or a soil auger can all act as sampling devices (i.e., be Samplers ). However, sometimes the distinction between the Sampler and the Sensor is not evident, as they are packaged as a unit. A Sampler need not be a physical device. |
---|---|
Sub class of | ssn:System |
Restrictions |
ssn:implements
MIN 1
sosa:madeSampling ONLY sosa:Sampling |
IRI: http://www.w3.org/ns/sosa/madeSampling
a OWL Object Property
made sampling - Relation between aSampler
(sampling device or entity) and the Sampling
act it performed.
Domain Includes | sosa:Sampler |
---|---|
Range Includes | sosa:Sampling |
Inverse property of | sosa:madeBySampler |
IRI: http://www.w3.org/ns/sosa/madeBySampler
a OWL Object Property
made by sampler - Relation linking an act ofSampling
to the Sampler
(sampling device or entity) that made it. Domain Includes | sosa:Sampling |
---|---|
Range Includes | sosa:Sampler |
Inverse property of | sosa:madeSampling |
This section is non-normative.
The following figure provides an overview of the core classes and properties that are secifically related to modeling Features of Interest and Properties. SOSA axioms are shown in green, while SSN-only axioms are shown in blue.
The following examples illustrate how the terms related to Features of Interest and Properties can be used:
This section introduces the following classes and properties:
sosa:FeatureOfInterest, sosa:hasFeatureOfInterest, sosa:isFeatureOfInterestOf, ssn:Property, ssn:hasProperty, ssn:isPropertyOf, ssn:forProperty
IRI: http://www.w3.org/ns/sosa/FeatureOfInterest
a OWL Class
Feature Of Interest - The thing whose property is being estimated or calculated in the course of anObservation
to arrive at a Result
, or whose property is being manipulated by an Actuator
, or which is being sampled or transformed in an act of Sampling
.
Example | When measuring the height of a tree, the height is the observed ObservableProperty , 20m may be the Result of the Observation , and the tree is the FeatureOfInterest . A window is a FeatureOfInterest for an automatic window control Actuator . |
---|---|
Restrictions |
ssn:hasProperty
ONLY ssn:Property
ssn:hasProperty MIN 1 sosa:hasSample ONLY sosa:Sample |
is Defined By | http://www.w3.org/ns/sosa/ |
IRI: http://www.w3.org/ns/sosa/hasFeatureOfInterest
a OWL Object Property
has feature of interest - A relation between anObservation
and the entity whose quality was observed, or between an Actuation
and the entity whose property was modified, or between an act of Sampling
and the entity that was sampled.
Example | For example, in an Observation of the weight of a person, the FeatureOfInterest is the person and the property is its weight. |
---|---|
Domain Includes | sosa:Observation, sosa:Actuation, sosa:Sampling |
Range Includes | sosa:FeatureOfInterest, sosa:Sample |
Inverse property of | sosa:isFeatureOfInterestOf |
IRI: http://www.w3.org/ns/sosa/isFeatureOfInterestOf
a OWL Object Property
is feature of interest of - A relation between aFeatureOfInterest
and an Observation
about it or an Actuation
acting on it, or an act of Sampling
that sampled it. Domain Includes | sosa:FeatureOfInterest, sosa:Sample |
---|---|
Range Includes | sosa:Observation, sosa:Actuation, sosa:Sampling |
Inverse property of | sosa:hasFeatureOfInterest |
IRI: http://www.w3.org/ns/ssn/Property
a OWL Class
Property - A quality of an entity. An aspect of an entity that is intrinsic to and cannot exist without the entity.Restrictions: | ssn:isPropertyOf ONLY sosa:FeatureOfInterest |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/hasProperty
a OWL Object Property
has property - Relation between an entity and aProperty
of that entity.
Inverse property of | ssn:isPropertyOf |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/isPropertyOf
a OWL Object Property
is property of - Relation between aProperty
and the entity it belongs to.
Inverse property of | ssn:hasProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/forProperty
a OWL Object Property
for property - A relation between some aspect of an entity and aProperty
. Example |
For example, from a Sensor to the properties it can observe; from an Actuator to the properties it can act on; from a Deployment to the properties it was installed to observe or act on; from a SystemCapability to the Property the capability is described for. |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
This section is non-normative.
The following figure provides an overview of the core classes and properties that are secifically related to modeling Results. SOSA axioms are shown in green, while SSN-only axioms are shown in blue.
The following examples illustrate how the terms related to Results can be used:
This section introduces the following classes and properties:
IRI: http://www.w3.org/ns/sosa/Result
a OWL Class
Result - TheResult
of an Observation
, Actuation
, or act of Sampling
. To store an observation's simple result value one can use the hasSimpleResult
property. Example | The value 20 as the height of a certain tree together with the unit, e.g., Meter. |
---|---|
Restriction | sosa:isResultOf MIN 1 |
IRI: http://www.w3.org/ns/sosa/hasResult
a OWL Object Property
has result - Relation linking anObservation
and a Sensor
or Actuator
and a Result
, which contains a value representing the value associated with the observed Property
. Domain Includes | sosa:Actuation, sosa:Observation, sosa:Sampling |
---|---|
Range Includes | sosa:Result, sosa:Sample |
Inverse property of | sosa:isResultOf |
IRI: http://www.w3.org/ns/sosa/isResultOf
a OWL Object Property
is result of - Relation linking aResult
to the Observation
or Actuation
that created or caused it. Domain Includes | sosa:Result, sosa:Sample |
---|---|
Range Includes | sosa:Actuation, sosa:Observation, sosa:Sampling |
Inverse property of | sosa:hasResult |
IRI: http://www.w3.org/ns/sosa/hasSimpleResult
a OWL Datatype Property
has simple result - The simple value of anObservation
or Actuation
. Example | For instance, the values 23 or true. |
---|---|
Domain Includes | sosa:Observation, sosa:Actuation |
IRI: http://www.w3.org/ns/sosa/resultTime
a OWL Datatype Property
result time - The result time is the instant of time when theObservation
, Actuation
or Sampling
activity was completed. Domain Includes | sosa:Actuation, sosa:Observation, sosa:Sampling |
---|---|
Range | xsd:dateTime |
This section is non-normative.
The following figure provides an overview of the core classes and properties that are secifically related to modeling Procedures. SOSA axioms are shown in green, while SSN-only axioms are shown in blue.
The following examples illustrate how the terms related to Procedures can be used:
This section introduces the following classes and properties:
sosa:Procedure, sosa:usedProcedure, ssn:implements, ssn:implementedBy, ssn:hasInput, ssn:hasOutput, ssn:Input, ssn:Output,
IRI: http://www.w3.org/ns/sosa/Procedure
a OWL Class
Procedure - A workflow, protocol, plan, algorithm, or computational method specifying how to make anObservation
, create a Sample
, or make a change to the state of the world (via an Actuator
). A Procedure
is re-usable, and might be involved in many Observations
, Samplings
, or Actuations
. It explains the steps to be carried out to arrive at reproducible Results
. Example | The measured wind speed differs depending on the height of the Sensor above the surface, e.g., due to friction. Consequently, procedures for measuring wind speed define a standard height for anemometers above ground, typically 10m for meteorological measures and 2m in Agrometeorology. This definition of height, Sensor placement, and so forth are defined by the Procedure . |
---|---|
Note | Many Observations may be created via the same Procedure, the same way as many tables are assembled using the same instructions (as information objects, not their concrete realization). |
Restrictions |
ssn:hasInput
ONLY ssn:Input
ssn:hasOutput ONLY ssn:Output ssn:implementedBy ONLY ssn:System |
IRI: http://www.w3.org/ns/sosa/usedProcedure
a OWL Object Property
used procedure - A relation to link to a re-usableProcedure
used in making an Observation
, an Actuation
, or a Sample
, typically through a Sensor
, Actuator
or Sampler
. Domain Includes | sosa:Actuation, sosa:Observation, sosa:Sampling |
---|---|
Range Includes | sosa:Procedure |
Sub property of Chain |
sosa:madeBySensor o
ssn:implements
sosa:madeByActuator o ssn:implements sosa:madeBySampler o ssn:implements |
IRI: http://www.w3.org/ns/ssn/implements
a OWL Object Property
implements - Relation between an entity that implements aProcedure
in some executable way and the Procedure
(an algorithm, procedure or method).
Inverse property of | ssn:implementedBy |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/implementedBy
a OWL Object Property
implemented by - Relation between aProcedure
(an algorithm, procedure or method) and an entity that implements that Procedure
in some executable way.
Inverse property of | ssn:implements |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/hasInput
a OWL Object Property
has Input - Relation between aProcedure
and an Input
to it.
is Defined By | http://www.w3.org/ns/ssn/ |
---|
IRI: http://www.w3.org/ns/ssn/Input
a OWL Class
Input - Any information that is provided to aProcedure
for its use.
Restrictions |
inverse Of ssn:hasInput
ONLY sosa:Procedure
inverse Of ssn:hasInput MIN 1 |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/hasOutput
a OWL Object Property
has Output - Relation between aProcedure
and an Output
of it.
is Defined By | http://www.w3.org/ns/ssn/ |
---|
IRI: http://www.w3.org/ns/ssn/Output
a OWL Class
Output - Any information that is reported from aProcedure
.
Restrictions |
inverse Of ssn:hasOutput
ONLY sosa:Procedure
inverse Of ssn:hasOutput MIN 1 |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
This section is non-normative.
The following figure provides an overview of the core classes and properties that are secifically related to modeling systems and their deployment. SOSA axioms are shown in green, while SSN-only axioms are shown in blue.
The following examples illustrate how the terms related to Systems and their Deployment can be used:
This section introduces the following classes and properties:
sosa:Platform, sosa:hosts, sosa:isHostedBy, ssn:System, ssn:hasSubSystem, ssn:Deployment, ssn:deployedSystem, ssn:hasDeployment, ssn:deployedOnPlatform, ssn:inDeployment
IRI: http://www.w3.org/ns/sosa/Platform
a OWL Class
Platform - APlatform
is an entity that hosts
other entities, particularly Sensors
, Actuators
, Samplers
, and other Platforms
. Example | A post, buoy, vehicle, ship, aircraft, satellite, cell-phone, human or animal may act as Platforms for (technical or biological) Sensors or Actuators . |
---|---|
Restrictions |
sosa:hosts
ONLY ssn:System
ssn:inDeployment ONLY ssn:Deployment |
IRI: http://www.w3.org/ns/sosa/hosts
a OWL Object Property
hosts - Relation between aPlatform
and a Sensor
, Actuator
, Sampler
, or Platform
, hosted or mounted on it.Domain Includes | sosa:Platform |
---|---|
Range Includes | sosa:Actuator, sosa:Sensor, sosa:Sampler, sosa:Platform |
Inverse property of | sosa:isHostedBy |
Sub property of Chain | ssn:inDeployment o ssn:deployedSystem |
IRI: http://www.w3.org/ns/sosa/isHostedBy
a OWL Object Property
is hosted by - Relation between aSensor
, or Actuator
, Sampler
, or Platform
, and the Platform
that it is mounted on or hosted by. Domain Includes | sosa:Actuator, sosa:Sensor, sosa:Sampler, sosa:Platform |
---|---|
Range Includes | sosa:Platform |
Inverse property of | sosa:hosts |
IRI: http://www.w3.org/ns/ssn/System
a OWL Class
System - System is a unit of abstraction for pieces of infrastructure that implementProcedures
. A System may have components, its subsystems, which are other Systems.
Restrictions |
sosa:isHostedBy
ONLY sosa:Platform
ssn:implements ONLY sosa:Procedure ssn:hasSubSystem ONLY ssn:System inverse Of ssn:hasSubSystem ONLY ssn:System ssn:hasDeployment ONLY ssn:Deployment |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/hasSubSystem
a OWL Object Property
has subsystem - Relation between aSystem
and its component parts.
is Defined By | http://www.w3.org/ns/ssn/ |
---|
IRI: http://www.w3.org/ns/ssn/Deployment
a OWL Class
Deployment - Describes theDeployment
of one or more Systems
for a particular purpose. Deployment
may be done on a Platform
.
Example | For example, a temperature Sensor deployed on a wall, or a whole network of Sensors deployed for an Observation campaign. |
---|---|
Restrictions |
ssn:deployedSystem
ONLY ssn:System
ssn:deployedOnPlatform ONLY sosa:Platform ssn:forProperty ONLY ssn:Property |
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/deployedSystem
a OWL Object Property
deployed system - Relation between aDeployment
and a deployed System
.
Inverse property of | ssn:hasDeployment |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/hasDeployment
a OWL Object Property
has deployment - Relation between aSystem
and a Deployment
, recording that the System
is deployed in that Deployment
.
Inverse property of | ssn:deployedSystem |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/deployedOnPlatform
a OWL Object Property
deployed on platform - Relation between aDeployment
and the Platform
on which the Systems are deployed. Inverse property of | ssn:inDeployment |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/inDeployment
a OWL Object Property
in deployment - Relation between aPlatform
and a Deployment
, meaning that the deployedSystems
of the Deployment
are hosted on the Platform
.
Example |
For example, a relation between a buoy and a Deployment of several Sensors . |
---|---|
Inverse property of | ssn:deployedOnPlatform |
is Defined By | http://www.w3.org/ns/ssn/ |
This section is non-normative.
This section provides details on the currently available horizontal segmentation modules.The namespace for system capabilities, operating ranges, and survival ranges terms is http://www.w3.org/ns/ssn/systems/
The suggested prefix for the system capabilities, operating ranges, and survival ranges terms is ssn-system
An ontology graph for this is available.
This section is non-normative.
The following figure provides an overview on the core classes and properties that are specifically related to modeling System capabilities, operating ranges, and survival ranges, under given conditions.
The following examples illustrate how the terms related to System capabilities, operating ranges, and survival ranges can be used:
This section introduces the following classes and properties:
ssn-system:inCondition, ssn-system:Condition, ssn-system:hasSystemCapability, ssn-system:SystemCapability, ssn-system:hasSystemProperty, ssn-system:SystemProperty, ssn-system:MeasurementRange, ssn-system:ActuationRange, ssn-system:Accuracy, ssn-system:DetectionLimit, ssn-system:Drift, ssn-system:Frequency, ssn-system:Latency, ssn-system:Precision, ssn-system:Resolution, ssn-system:ResponseTime, ssn-system:Selectivity, ssn-system:Sensitivity, ssn-system:hasOperatingRange, ssn-system:OperatingRange, ssn-system:hasOperatingProperty, ssn-system:OperatingProperty, ssn-system:MaintenanceSchedule, ssn-system:OperatingPowerRange ssn-system:hasSurvivalRange, ssn-system:SurvivalRange, ssn-system:hasSurvivalProperty, ssn-system:SurvivalProperty ssn-system:SystemLifetime, ssn-system:BatteryLifetime ssn-system:qualityOfObservation
IRI: http://www.w3.org/ns/ssn/System
a OWL Class
System - System is a unit of abstraction for pieces of infrastructure that implementProcedures
. A System may have components, its subsystems, which are other Systems.
Additional Restrictions |
ssn-system:hasSystemCapability
ONLY ssn-system:SystemCapability
ssn-system:hasOperatingRange ONLY ssn-system:OperatingRange ssn-system:hasSurvivalRange ONLY ssn-system:SurvivalRange |
---|---|
is Defined By | http://www.w3.org/ns/ssn/ |
IRI: http://www.w3.org/ns/ssn/systems/inCondition
a OWL Object Property
in condition - Describes the prevailing environmentalConditions
for SystemCapabilites
, OperatingRanges
and SurvivalRanges
.
Example |
Used for example to say that a Sensor has a particular accuracy in particular Conditions . |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/Condition
a OWL Class
Condition - Used to specify ranges for qualities that act asConditions
on a Systems' operation.
Example | For example, wind speed of 10-60m/s may be used as the Condition on a SystemProperty , for example, to state that a Sensor has a particular Accuracy under that Condition . |
---|---|
Sub class of | ssn:Property |
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/hasSystemCapability
a OWL Object Property
has system capability - Relation from aSystem
to a SystemCapability
describing the capabilities of the System
under certain Conditions
.
Sub property of | ssn:hasProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/SystemCapability
a OWL Class
System Capability - Describes normal measurement, actuation, sampling properties such as accuracy, range, precision, etc. of aSystem
under some specified Conditions
such as a temperature range.
System
, while those in OperatingRange
represent the system's normal operating environment, including Conditions
that don't affect the Observations
or the Actuations
.
Sub class of | ssn:Property |
---|---|
Restrictions |
ssn:forProperty
ONLY ssn:Property
ssn-system:hasSystemProperty ONLY ssn-system:SystemProperty ssn-system:inCondition ONLY ssn-system:Condition ssn-system:inCondition MIN 1 inverse Of ssn-system:hasSystemCapability ONLY ssn:System |
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/hasSystemProperty
a OWL Object Property
has system property - Relation from anSystemCapability
of a System
to a SystemProperty
describing the capabilities of the System
.
Sub property of | ssn:hasProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/SystemProperty
a OWL Class
System Property - An identifiable and observable characteristic that represents theSystem
's ability to operate its primary purpose: a Sensor
to make Observations
, an Actuator
to make Actuations
, or a Sampler
to make Sampling
.
Sub class of | ssn:Property |
---|---|
Restrictions |
inverse Of ssn-system:hasSystemProperty
ONLY ssn-system:SystemCapability inverse Of ssn-system:hasSystemProperty MIN 1 |
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/MeasurementRange
a OWL Class
Measurement Range - The set of values that theSensor
can return as the Result
of an Observation
under the defined Conditions
with the defined system properties.
Sub class of | ssn-system:SystemProperty |
---|---|
Restrictions | inverse Of ssn-system:hasSystemProperty ONLY inverse Of ssn-system:hasSystemCapability ONLY sosa:Sensor |
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/ActuationRange
a OWL Class
Actuation Range - The range ofProperty
values that can be the Result
of an Actuation
under the defined Conditions
.
Sub class of | ssn-system:SystemProperty |
---|---|
Restriction | inverse Of ssn-system:hasSystemProperty ONLY inverse Of ssn-system:hasSystemCapability ONLY sosa:Actuator |
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/Accuracy
a OWL Class
Accuracy - The closeness of agreement between theResult
of an Observation
(resp. the command of an Actuation
) and the true value of the observed ObservableProperty
(resp. of the acted on ActuatableProperty
) under the defined Conditions
.
Sub class of | ssn-system:SystemProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/DetectionLimit
a OWL Class
Detection Limit - An observed value for which the probability of falsely claiming the absence of a component in a material is beta, given a probability alpha of falsely claiming its presence.Sub class of | ssn-system:SystemProperty |
---|---|
Restriction | inverse Of ssn-system:hasSystemProperty ONLY inverse Of ssn-system:hasSystemCapability ONLY sosa:Sensor |
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/Drift
a OWL Class
Drift - As aSensor
Property
: a continuous or incremental change in the reported values of Observations
over time for an unchanging Property
under the defined Conditions
.
Actuator
Property
: a continuous or incremental change in the true value of the acted on ActuatableProperty
over time for an unchanging command under the defined Conditions
.
Sub class of | ssn-system:SystemProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/Frequency
a OWL Class
Frequency - The smallest possible time between oneObservation
, Actuation
, or Sampling
and the next, under the defined Conditions
.
Sub class of | ssn-system:SystemProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/Latency
a OWL Class
Latency - The time between a command for anObservation
(resp. Actuation
) and the Sensor
providing a Result
(resp. the Actuator
operating the Actuation
), under the defined Conditions
.
Sub class of | ssn-system:SystemProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/Precision
a OWL Class
Precision - As a sensor capability: The closeness of agreement between replicateObservations
on an unchanged or similar quality value: i.e., a measure of a Sensor
's ability to consistently reproduce an Observation
, under the defined Conditions
.Actuations
for an unchanged or similar command: i.e., a measure of an Actuator
's ability to consistently reproduce an Actuations
, under the defined Conditions
.
Sub class of | ssn-system:SystemProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/Resolution
a OWL Class
Resolution - As aSensor
Property
: the smallest difference in the value of a ObservableProperty
being observed that would result in perceptably different values of Observation
Results
, under the defined Conditions
.
Actuator
Property
: the smallest difference in the value of an Actuation
command that would result in a value change of the ActuatableProperty
being acted on, under the defined Conditions
.
Sub class of | ssn-system:SystemProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/ResponseTime
a OWL Class
Response time - As aSensor
Property
: the time between a (step) change in the value of an observed ObservableProperty
and a Sensor
(possibly with specified error) 'settling' on an observed value, under the defined Conditions
.
Actuator
Property
: the time between a (step) change in the command of an Actuator
and the 'settling' of the value of the acted on ActuatableProperty
, under the defined Conditions
.
Sub class of | ssn-system:SystemProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/Selectivity
a OWL Class
Selectivity - As aSensor
Property
: Selectivity is a Property
of a Sensor
whereby it provides observed values for one or more ObservableProperties
such that the Result
for each ObservableProperty
are independent of other Properties
in the FeatureOfInterest
being investigated, under the defined Conditions
.
Actuator
Property
: Selectivity is a Property
of an Actuator
whereby it acts on one or more ActuatableProperties
such as the Results
for each ActuatableProperty
are independent of other Properties
in the FeatureOfInterest
being acted on, under the defined Conditions
.
Sub class of | ssn-system:SystemProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/Sensitivity
a OWL Class
Sensitivity - As aSensor
Property
: Sensitivity is the quotient of the change in a Result
of Observations
and the corresponding change in a value of an ObservableProperty
being observed, under the defined Conditions
.
Actuator
Property
: Sensitivity is the quotient of the change in a command of Actuation
and the corresponding change in a value of an ActuatableProperty
being acted on, under the defined Conditions
.
Sub class of | ssn-system:SystemProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/hasOperatingRange
a OWL Object Property
has operating range - Relation from aSystem
to an OperatingRange
describing the normal operating environment of the System
.
Sub property of | ssn:hasProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/OperatingRange
a OWL Class
Operating Range - Describes normalOperatingProperties
of a System
under some specified Conditions
. For example, to the power requirement or maintenance schedule of a System
under a specified temperature range.
OperatingProperties
, it simply describes the Conditions
in which a System
is expected to operate.
System
continues to operate as defined using SystemCapability
. If, however, the OperatingProperty
is violated, the System is operating 'out of operating range' and SystemCapability
specifications may no longer hold.
Sub class of | ssn:Property |
---|---|
Restrictions: |
ssn-system:hasOperatingProperty
ONLY ssn-system:OperatingProperty
ssn-system:inCondition ONLY ssn-system:Condition ssn-system:inCondition MIN 1 inverse Of ssn-system:hasOperatingRange ONLY ssn:System |
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/hasOperatingProperty
a OWL Object Property
has operating property - Relation from anOperatingRange
of a System
to an OperatingProperty
describing the operating range of the System
.
Sub property of | ssn:hasProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/OperatingProperty
a OWL Class
Operating Property - An identifiable characteristic that represents how theSystem
operates under the specified Conditions
. May describe power ranges, power sources, standard configurations, attachments and the like.
Sub class of | ssn:Property |
---|---|
Restrictions |
inverse Of ssn-system:hasOperatingProperty
ONLY ssn-system:OperatingRange inverse Of ssn-system:hasOperatingProperty MIN 1 |
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/MaintenanceSchedule
a OWL Class
Maintenance Schedule - Schedule of maintenance for aSystem
in the specified Conditions
.
Sub class of | ssn-system:OperatingProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/OperatingPowerRange
a OWL Class
Operating Power Range - Power range in whichSystem
is expected to operate in the specified Conditions
.
Sub class of | ssn-system:OperatingProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/hasSurvivalRange
a OWL Object Property
has survival range - Relation from aSystem
to a SurvivalRange
.
Sub property of | ssn:hasProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/SurvivalRange
a OWL Class
Survival Range - DescribesSurvivalProperties
of a System
under some specified Conditions
. For example, the lifetime of a System under a specified temperature range.
SurvivalProperties
, simply describes the Conditions
a System
can be exposed to without damage. For example, the temperature range a System can withstand before being considered damaged.
SystemCapability
. If, however, the SurvivalRange is violated, the System
is 'damaged' and SystemCapability
specifications may no longer hold. Sub class of | ssn:Property |
---|---|
Restrictions |
ssn-system:hasSurvivalProperty
ONLY ssn-system:SurvivalProperty
ssn-system:inCondition ONLY ssn-system:Condition ssn-system:inCondition MIN 1 inverse Of ssn-system:hasSurvivalRange ONLY ssn:System |
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/hasSurvivalProperty
a OWL Object Property
has survival property - Relation from aSurvivalRange
of a System
to a SurvivalProperty
describing the survival range of the System
.
Sub property of | ssn:hasProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/SurvivalProperty
a OWL Class
Survival Property - An identifiable characteristic that represents the extent of theSystem
's useful life under the specified Conditions
. May describe for example total battery life or number of recharges, or, for Sensors
that are used only a fixed number of times, the number of Observations
that can be made before the sensing capability is depleted.
Sub class of | ssn:Property |
---|---|
Restrictions |
inverse Of ssn-system:hasSurvivalProperty
ONLY ssn-system:SurvivalRange inverse Of ssn-system:hasSurvivalProperty MIN 1 |
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/SystemLifetime
a OWL Class
System Lifetime - Total useful life of aSystem
(expressed as total life since manufacture, time in use, number of operations, etc.) in the specified Conditions
.
Sub class of | ssn-system:SurvivalProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/BatteryLifetime
a OWL Class
Battery Lifetime - Total useful life of aSystem
's battery in the specified Conditions
.
Sub class of | ssn-system:SurvivalProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
IRI: http://www.w3.org/ns/ssn/systems/qualityOfObservation
a OWL Object Property
quality of observation - Relation linking anObservation
to the adjudged quality of the Result
. This is complementary to the SystemCapability
information recorded for the Sensor
that made the Observation
.
Sub property of | ssn:hasProperty |
---|---|
is Defined By | http://www.w3.org/ns/ssn/systems/ |
This section is non-normative.
Samples are often related to other samples, by sub-sampling, topological relationships (stations along a traverse, pixels within an image, probe spots on a polished section, specimens retrieved within a borehole) or as parts of sample processing chains (crushing, splitting, dissecting, disolving). There are an essentially unlimited set of relationships between samples, so the nature of the relationship has its own class. This section describes a flexible model to describe such relationships between samples. The model is based on the QualifiedRelation pattern.
The namespace for Sample relationships terms is http://www.w3.org/ns/sosa/sampling/
The suggested prefix for the sample relationships namespace is sampling
An ontology graph for this is available.
The following figure provides an overview on the classes and properties that are specifically related to modeling Sample relationships.
This section introduces the following classes and properties:
sampling:RelationshipNature, sampling:hasSampleRelationship, sampling:natureOfRelationship, sampling:relatedSample
IRI: http://www.w3.org/ns/sosa/sampling/RelationshipNature
a OWL Class
Nature of relationship (between samples) - Members of this class indicate the nature of a relationship between twoSamples.
Sub class of | skos:Concept |
---|---|
Examples | Adjacent flight-line
Females Juveniles Males Pixel within image or scene Probe spot on polished specimen Specimen taken from borehole Split of core sample Station along a traverse Sub-sample with grain size smaller than specified seive mesh |
is Defined By | http://www.w3.org/ns/sosa/sampling/ |
IRI: http://www.w3.org/ns/sosa/sampling/SampleRelationship
a OWL Class
Sample relationship - Members of this class represent a relationship between aSample
and another.
is Defined By | http://www.w3.org/ns/sosa/sampling/ |
---|
IRI: http://www.w3.org/ns/sosa/sampling/hasSampleRelationship
a OWL Object Property
has sample relationship - Links a sample to aSample Relationship
(which links to a related Sample
).
Domain Includes | sosa:Sample |
---|---|
Range Includes | sampling:SampleRelationship |
is Defined By | http://www.w3.org/ns/sosa/sampling/ |
IRI: http://www.w3.org/ns/sosa/sampling/natureOfRelationship
a OWL Object Property
nature of (sample) relationship - Links aSample Relationship
to an indication of the nature of the relationship.
Domain Includes | sampling:SampleRelationship |
---|---|
Range Includes | sampling:SampleRelationship |
is Defined By | http://www.w3.org/ns/sosa/sampling/ |
This section introduces the specifications for the vertical segmentation modules that align SOSA and SSN to a variety of related ontologies and specifications.
This section is non-normative.
This section introduces the alignment of SSN to the DOLCE UltraLite upper ontology (DUL) which is the core dependency of the previous version of SSN. This serves to axiomatically clarify the intended meaning of SSN terms and will assist SSN users wishing to interoperate with other DUL-aligned ontologies. It is also imported in the SSNX alignment module that aligns SSN to the previous version of SSN. Note, however, that the DUL alignment can be used independently to align SSN with more generic concepts/properties of DUL.
The DUL alignment, known as "ssn-dul" is available at http://www.w3.org/ns/ssn/dul.This section is non-normative.
The following namespace prefixes are used in the alignment to SOSA and SSN
Prefix | Namespace |
---|---|
sosa: | http://www.w3.org/ns/sosa/ |
ssn: | http://www.w3.org/ns/ssn/ |
dul: | http://www.ontologydesignpatterns.org/ont/dul/DUL.owl# |
This section is non-normative.
The following classes in SOSA and SSN can be aligned via a subclass relation as follows.
sosa:Procedure | subclass of | dul:Method |
sosa:Sensor | subclass of | dul:Object |
sosa:Observation | subclass of | dul:Event |
ssn:Property | subclass of | dul:Quality |
ssn:Stimulus | subclass of | dul:Event |
ssn:System | subclass of | dul:Object |
sosa:Platform | subclass of | dul:Object |
ssn:Deployment | subclass of | dul:Event |
For more complex alignments, the axiomatic alignments are defined as follows.
sosa:FeatureOfInterest | subclass of | owl:unionOf ( dul:Event dul:Object dul:InformationEntity) |
sosa:Result | subclass of | owl:unionOf ( dul:Region dul:Object ) |
(not (oldssn:Observation)) and (old-ssn:observationResult some owl:Thing) | subclass of | sosa:Observation |
This section is non-normative.
Additional alignments from SOSA/SSN to DUL properties are defined as follows.
ssn:hasProperty | sub-property of | dul:hasQuality |
ssn:isPropertyOf | sub-property of | dul:isQualityOf |
sosa:hosts | sub-property of | dul:isLocationOf |
sosa:isHostedBy | sub-property of | dul:hasLocation |
ssn:implementedBy | sub-property of | dul:describes |
ssn:implements | sub-property of | dul:isDescribedBy |
sosa:usedProcedure | sub-property of | dul:hasParticipant |
sosa:madeObservation | sub-property of | dul:associatedWith |
sosa:madeBySensor | sub-property of | dul:associatedWith |
sosa:observedProperty | sub-property of | dul:associatedWith |
sosa:hasResult | sub-property of | dul:associatedWith |
sosa:phenomenonTime | sub-property of | dul:hasRegion |
ssn:hasSubSystem | sub-property of | dul:hasPart |
ssn:deployedOnPlatform | sub-property of | dul:associatedWith |
ssn:deployedSystem | sub-property of | dul:associatedWith |
ssn:hasDeployment | sub-property of | dul:associatedWith |
ssn:inDeployment | sub-property of | dul:associatedWith |
This section is non-normative.
This section formally relates the SSN ontology to the previous version of SSN that was published by the SSN-XG ("old SSN"). This may be useful for backward-compatibility and transition purposes. While the namespaces for SSN and DUL have changed since the SSN-XG first published the old SSN, the SSN alignment, known as "SSN-SSNX" is available at http://www.w3.org/2017/01/ssn-ssnx/. Note that SSN-SSNX imports SSN-DUL.
This section is non-normative.
The following namespace prefixes are used in the alignment to SOSA and SSN
Prefix | Namespace |
---|---|
sosa: | http://www.w3.org/ns/sosa/ |
ssn: | http://www.w3.org/ns/ssn/ |
oldssn: | http://purl.oclc.org/NET/ssnx/ssn# |
This section is non-normative.
The primary classes from SSN-XG have direct equivalent classes in SOSA and SSN as shown below.
oldssn:FeatureOfInterest | equivalent class | sosa:FeatureOfInterest |
oldssn:Property | equivalent class | ssn:Property |
oldssn:System | equivalent class | ssn:System |
oldssn:Platform | equivalent class | sosa:Platform |
oldssn:Input | equivalent class | ssn:Input |
oldssn:Output | equivalent class | ssn:Output |
oldssn:Stimulus | equivalent class | ssn:Stimulus |
oldssn:MeasurementRange | equivalent class | ssn-system:MeasurementRange |
oldssn:Sensor | equivalent class | sosa:Sensor |
oldssn:Condition | equivalent class | ssn-system:Condition |
oldssn:Precision | equivalent class | ssn-system:Precision |
oldssn:Sensitivity | equivalent class | ssn-system:Sensitivity |
oldssn:OperatingProperty | equivalent class | ssn-system:OperatingProperty |
oldssn:MaintenanceSchedule | equivalent class | ssn-system:MaintenanceSchedule |
oldssn:OperatingPowerRange | equivalent class | ssn-system:OperatingPowerRange |
oldssn:SurvivalProperty | equivalent class | ssn-system:SurvivalProperty |
oldssn:BatteryLifetime | equivalent class | ssn-system:BatteryLifetime |
oldssn:SystemLifetime | equivalent class | ssn-system:SystemLifetime |
The following classes in SOSA and SSN are interpreted as superclasses of the corresponding ones in SSN-XG.
oldssn:Device | subclass of | sosa:Platform; ssn:System |
oldssn:Sensing | subclass of | sosa:Procedure |
oldssn:ObservationValue | subclass of | sosa:Result |
oldssn:MeasurementProperty | subclass of | ssn-system:SystemProperty |
oldssn:Accuracy | subclass of | ssn-system:Accuracy |
oldssn:DetectionLimit | subclass of | ssn-system:DetectionLimit |
oldssn:Drift | subclass of | ssn-system:Drift |
oldssn:Frequency | subclass of | ssn-system:Frequency |
oldssn:Latency | subclass of | ssn-system:Latency |
oldssn:Resolution | subclass of | ssn-system:Resolution |
oldssn:ResponseTime | subclass of | ssn-system:ResponseTime |
oldssn:Selectivity | subclass of | ssn-system:Selectivity |
The more complex aligments of SSN-XG classes are expressed as combinations of axiomatic statements as follows.
oldssn:Process | equivalent class | sosa:Procedure |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:hasOutput ; owl:someValuesFrom oldssn:Output ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:hasInput ; owl:allValuesFrom oldssn:Input ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:hasOutput ; owl:allValuesFrom oldssn:Output ] | |
oldssn:Observation | subclass of | [ a owl:Restriction ; owl:onProperty oldssn:featureOfInterest ; owl:allValuesFrom oldssn:FeatureOfInterest ] |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:observationResult ; owl:allValuesFrom oldssn:SensorOutput ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:observedBy ; owl:allValuesFrom oldssn:Sensor ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:observedProperty ; owl:allValuesFrom oldssn:Property ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:sensingMethodUsed ; owl:allValuesFrom oldssn:Sensing ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:observationResultTime ; owl:minCardinality "0"^^xsd:nonNegativeInteger ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:observationSamplingTime ; owl:minCardinality "0"^^xsd:nonNegativeInteger ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:qualityOfObservation ; owl:minCardinality "0"^^xsd:nonNegativeInteger ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:featureOfInterest ; owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass oldssn:FeatureOfInterest ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:observedBy ; owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass oldssn:Sensor ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:observedProperty ; owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass oldssn:Property ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:sensingMethodUsed ; owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass oldssn:Sensing ] | |
oldssn:SensorOutput | subclass of | sosa:Result |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:hasValue ; owl:someValuesFrom oldssn:ObservationValue ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:isProducedBy ; owl:someValuesFrom oldssn:Sensor ] | |
oldssn:ObservationValue | subclass of | sosa:Result |
subclass of | [ a owl:Restriction ; owl:onProperty dul:isRegionFor ; owl:someValuesFrom oldssn:SensorOutput ] | |
oldssn:Deployment | equivalent class | ssn:Deployment |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:deployedOnPlatform ; owl:allValuesFrom oldssn:Platform ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:deployedSystem ; owl:allValuesFrom oldssn:System ] | |
oldssn:MeasurementCapability | subclass of | ssn-system:SystemCapability |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:forProperty ; owl:allValuesFrom oldssn:Property ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:hasMeasurementProperty ; owl:allValuesFrom oldssn:MeasurementProperty ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:inCondition ; owl:allValuesFrom oldssn:Condition ] | |
oldssn:OperatingRange | equivalent class | ssn-system:OperatingRange |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:hasOperatingProperty ; owl:allValuesFrom oldssn:OperatingProperty ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:inCondition ; owl:allValuesFrom oldssn:Condition ] | |
oldssn:SurvivalRange | equivalent class | ssn-system:SurvivalRange |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:hasSurvivalProperty ; owl:allValuesFrom oldssn:SurvivalProperty ] | |
subclass of | [ a owl:Restriction ; owl:onProperty oldssn:inCondition ; owl:allValuesFrom oldssn:Condition ] |
This section is non-normative.
The following properties from SSN-XG have direct equivalent properties in SOSA and SSN.
oldssn:hasProperty | equivalent property | ssn:hasProperty |
oldssn:isPropertyOf | equivalent property | ssn:isPropertyOf |
oldssn:attachedSystem | equivalent property | sosa:hosts |
oldssn:onPlatform | equivalent property | sosa:isHostedBy |
oldssn:hasInput | equivalent property | ssn:hasInput |
oldssn:hasOutput | equivalent property | ssn:hasOutput |
oldssn:implements | equivalent property | ssn:implements |
oldssn:implementedBy | equivalent property | ssn:implementedBy |
oldssn:sensingMethodUsed | equivalent property | sosa:usedProcedure |
oldssn:featureOfInterest | equivalent property | sosa:hasFeatureOfInterest |
oldssn:madeObservation | equivalent property | sosa:madeObservation |
oldssn:observedBy | equivalent property | sosa:madeBySensor |
oldssn:observedProperty | equivalent property | sosa:observedProperty |
oldssn:detects | equivalent property | ssn:detects |
oldssn:isProxyFor | equivalent property | ssn:isProxyFor |
oldssn:hasValue | equivalent property | sosa:hasResult |
oldssn:isProducedBy | equivalent property | sosa:isResultOf |
oldssn:observationResult | equivalent property | sosa:hasResult |
oldssn:observationSamplingTime | equivalent property | sosa:phenomenonTime |
oldssn:qualityOfObservation | equivalent property | ssn-system:qualityOfObservation |
oldssn:hasSubSystem | equivalent property | ssn:hasSubSystem |
oldssn:deployedOnPlatform | equivalent property | ssn:deployedOnPlatform |
oldssn:deployedSystem | equivalent property | ssn:deployedSystem |
oldssn:hasDeployment | equivalent property | ssn:hasDeployment |
oldssn:inDeployment | equivalent property | ssn:inDeployment |
oldssn:forProperty | equivalent property | ssn:forProperty |
oldssn:inCondition | equivalent property | ssn-system:inCondition |
oldssn:hasSurvivalRange | equivalent property | ssn-system:hasSurvivalRange |
oldssn:hasSurvivalProperty | equivalent property | ssn-system:hasSurvivalProperty |
oldssn:hasOperatingRange | equivalent property | ssn-system:hasOperatingRange |
oldssn:hasOperatingProperty | equivalent property | ssn-system:hasOperatingProperty |
Additional alignments from SSG-XG properties to SOSA and SSN are defined as follows.
oldssn:hasMeasurementCapability | sub-property of | ssn-system:hasSystemCapability |
oldssn:hasMeasurementProperty | sub-property of | ssn-system:hasSystemProperty |
oldssn:hasSurvivalRange | sub-property of | sosa:hasResult |
The more complicated alignments are presented in combination with the property-chain axioms as follows.
oldssn:observes | equivalent property | sosa:observes |
property chain axiom | ( oldssn:hasMeasurementCapability oldssn:forProperty ) | |
property chain axiom | ( oldssn:madeObservation oldssn:observedProperty ) |
This section introduces the alignment of SOSA/SSN to OGC Observations and Measurements [OandM] (also known as ISO 19156:2011).
The XML implementation of O&M [OMXML] is used for the payload for Sensor Observation Services, of which there are many operational deployments. Integration of these with observation data formalized using SOSA and SSN is highly desirable, and would be expected to significantly enrich the set of resources represented using SOSA/SSN. The alignment presented here provides a basis for transforming OM-XML data into RDF resources or OWL individuals according to the SOSA/SSN ontologies.
O&M is specified as a UML model, following the patterns specified in ISO 19109 Geographic Information - Rules for Application Schema [ISO-19109]. This means that the classes represent concepts from the application domain, so can be approximately equated with classes in an ontology.
An OWL implementation of O&M may be generated by explicit translation of the UML following rules specified in [ISO-19150-2] - see [OM-Heavy]. This translation generates an RDF entity denoted by a URI for every class, class attribute, and association-role from the original O&M UML model. The form of the URIs is also specified in [ISO-19150-2], and appear explicitly in the official OWL implementation of ISO 19156 (O&M) maintained by the ISO/TC 211 Group on Ontology Management. These URIs are therefore convenient identifiers for elements of the O&M in a formal alignment.
The explicit translation from the UML model comes at the cost of a large set of dependencies on similar OWL translations of other UML models from the ISO 19100 series standards. Furthermore, the ontology structure reflects artefacts of the UML-style of modeling. This implementation may introduce entailments that are inconsistent with SOSA/SSN (though no inconsistencies have been identified yet) so it is important to understand that use of these URIs here are principally intended to denote the original UML classes and properties, rather than this OWL implementation.
NOTE: In response to the complexity of the explicit translation, a handcrafted version in more idiomatic OWL, without the dependencies, is also available [OM-Lite].
NOTE: At time of writing, the ISO-specified URIs do not de-reference. However, ISO/TC 211 are currently developing a publication system to enable this and thus the use of these URIs as Linked Data.
The following namespace prefixes are used in the alignment to SOSA.
Prefix | Namespace |
---|---|
sosa: | http://www.w3.org/ns/sosa/ |
sosa-om: | http://www.w3.org/ns/sosa/om# |
iso19156-gfi: | http://def.isotc211.org/iso19156/2011/GeneralFeatureInstance# |
iso19156-om: | http://def.isotc211.org/iso19156/2011/Observation# |
iso19156-sf: | http://def.isotc211.org/iso19156/2011/SamplingFeature# |
iso19156-sfs: | http://def.isotc211.org/iso19156/2011/SpatialSamplingFeature# |
iso19156-sp: | http://def.isotc211.org/iso19156/2011/Specimen# |
Three utility classes are defined locally to support the formalization of the alignment.
sosa-om:ActuationProcedure | Actuation procedures or recipes |
sosa-om:ObservationProcedure | Observation procedures or recipes |
sosa-om:SamplingProcedure | Sampling, sample preparation or processing procedures or recipes |
The primary classes from [OandM] have direct equivalents in SOSA classes supplemented by the utility classes described above, as follows.
iso19156-om:OM_Observation | equivalent class | sosa:Observation |
iso19156-om:OM_Process | equivalent class | Union of ( sosa:Sensor or sosa-om:ObservationProcedure ) |
iso19156-sf:SF_SamplingFeature | equivalent class | sosa:Sample |
iso19156-sf:SF_Process | equivalent class | Union of ( sosa:Sampler or sosa-om:SamplingProcedure ) |
Additional alignments from SOSA/SSN classes to O&M classes are as follows.
iso19156_sp:PreparationStep | subclass of | sosa:Sampling |
iso19156_sp:PreparationStep is a subclass since the act of Sampling applies to all sample types, not only physical specimens.
sosa:FeatureOfInterest | subclass of | iso19156_gfi:GFI_DomainFeature |
where iso19156_gfi:GFI_DomainFeature has the definition:
sosa:FeatureOfInterest is a subclass of iso19156_gfi:GFI_DomainFeature since not all domain features are subjects of observation.
sosa:Actuator | subclass of | iso19156_gfi:GFI_Feature |
sosa:Platform | subclass of | iso19156_gfi:GFI_Feature |
where iso19156_gfi:GFI_Feature has the definition
The following properties from [OandM] have direct equivalents in SOSA properties.
iso19156-om:OM_Observation.featureOfInterest | equivalent property | sosa:hasFeatureOfInterest |
iso19156-om:OM_Observation.observedProperty | equivalent property | sosa:observedProperty |
iso19156-om:OM_Observation.phenomenonTime | equivalent property | sosa:phenomenonTime |
iso19156-sf:SF_SamplingFeature.sampledFeature | equivalent property | sosa:isSampleOf |
Additional alignments from O&M properties to SOSA are as follows.
iso19156-om:OM_Observation.procedure | sub-property of | sosa:usedProcedure |
iso19156-sp:SF_Specimen.samplingMethod | sub-property of | sosa:usedProcedure |
iso19156-om:OM_Observation.result | sub-property of | sosa:hasResult |
iso19156-om:OM_Observation.resultTime | sub-property of | sosa:resultTime |
iso19156-sp:SF_Specimen.samplingTime | sub-property of | sosa:resultTime |
iso19156-sp:PreparationStep.time | sub-property of | sosa:resultTime |
iso19156-sp:SF_Specimen.processingDetails | sub-property of | sosa:isResultOf |
These are modeled as sub-properties because sosa:usedProcedure, sosa:hasResult, sosa:isResultOf and sosa:resultTime applies to actuation, observation or sampling activities.
iso19156-sfs:SF_SpatialSamplingFeature.hostedProcedure | sub-property of | sosa:hosts |
This is modeled as a sub-property because the domain of iso19156-sfs:SF_SpatialSamplingFeature.hostedProcedure is a spatial sampling feature, such as a station, rather than a more general platform.
An RDF file containing a graph corresponding to this alignment is available.
This section is non-normative.
This section introduces the alignment of SOSA to OBOE.
OBOE, the Extensible Observation Ontology, is used within the biodiversity community for semantic representation of observation data. The ontology is composed of multiple modules. The core observation elements are in the module OBOE-core.
The following namespace prefixes are used in the alignment to SOSA.
Prefix | Namespace |
---|---|
sosa: | http://www.w3.org/ns/sosa/ |
oboe: | http://ecoinformatics.org/oboe/oboe.1.0/oboe-core.owl# |
This section is non-normative.
An oboe:Observation is composed of a collection of oboe:Measurements with the same feature of interest. Each oboe:Measurement concerns a distinct observed-property ("characteristic") and uses a distinct procedure ("protocol"). We therefore choose to align sosa:Observation with oboe:Measurement.
The primary classes from [OBOE] are aligned with SOSA classes as follows.
oboe:Measurement | subclass of | sosa:Observation |
oboe:Characteristic | equivalent class | sosa:ObservableProperty |
oboe:Protocol | equivalent class | sosa:Procedure |
The class oboe:Entity appears in OBOE as the range of the oboe:ofEntity and oboe:hasValue properties, so we interpret it as a general superclass.
sosa:FeatureOfInterest | subclass of | oboe:Entity |
sosa:Result | subclass of | oboe:Entity |
This section is non-normative.
The following properties from [OBOE] may be directly aligned with SOSA properties.
oboe:ofCharacteristic | equivalent property | sosa:observedProperty |
oboe:hasValue | equivalent property | sosa:hasResult |
oboe:usesProtocol | equivalent property | sosa:usedProcedure |
oboe:usesMethod | equivalent property | sosa:usedProcedure |
oboe:hasValue, oboe:usesProtocol and oboe:usesMethod are sub-properties of the corresponding SOSA properties which apply to actuation and sampling as well as observation.
The feature of interest is linked to the oboe:Observation that contains a oboe:Measurement, rather than to the oboe:Measurement directly, so a property-chain axiom is required to express the alignment.
sosa:hasFeatureOfInterest | property-chain axiom | [oboe:measurementFor, oboe:ofEntity] |
The properties oboe:hasMeasurement and its inverse oboe:measurementFor link an oboe:Observation to its member oboe:Measurements. These could be modeled as sub-properties related to rdfs:member and its inverse as follows.
oboe:hasMeasurement | sub-property of | rdfs:member |
oboe:measurementFor | sub-property of | [ owl:inverseOf rdfs:member ] |
An RDF file containing a graph corresponding to this alignment is available.
This section is non-normative.
This section introduces the alignment of SOSA to W3C PROV ([prov-overview], [prov-dm], [prov-o]).
The underlying structure of PROV is based around a process-flow model, with three base classes: Entity, which is the class of physical, digital, conceptual, or other kinds of things with some fixed aspects; Activity, which is the class of things that occur over a period of time and act upon or with entities, and it may include consuming, processing, transforming, modifying, relocating, using, or generating entities; and Agent, the class of things that bear some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity.
The SOSA/SSN ontologies conceive observations, actuations, and acts of sampling as activities or events, that results in information being produced, or a change in the world, or the production or transformation of a sample. Thus, an alignment of SOSA to PROV is natural. Compton et al. [SSN-PROV] and Cox [OM-Lite] have previously described alignments of the SSNX and O&M models with [prov-o]. The alignment here is based on that work, also extended to consider actuation.
This section is non-normative.
The following namespace prefixes are used in the alignment of SOSA to PROV.
Prefix | Namespace |
---|---|
sosa: | http://www.w3.org/ns/sosa/ |
prov: | http://www.w3.org/ns/prov# |
sp: | http://www.w3.org/ns/sosa/prov/ |
This section is non-normative.
The primary classes from SOSA are aligned with the PROV classes as follows.
1. Acts of Observation, Actuation and Sampling are each kinds of Activity, thus:
sosa:Observation | subclass of | prov:Activity |
sosa:Actuation | ||
sosa:Sampling |
2. Sensors, Actuators and Samplers are entities that are responsible for the corresponding activities, thus:
sosa:Sensor | subclass of | prov:Agent , prov:Entity |
sosa:Actuator | ||
sosa:Sampler |
3. Procedures for observation, actuation or sampling are a kind of prov:Plan, thus:
sosa:Procedure | subclass of | prov:Plan |
4. The other classes from the core SOSA ontology represent either real or information resources, so are interpreted as kinds of prov:Entity, thus:
sosa:FeatureOfInterest | subclass of | prov:Entity |
sosa:ObservableProperty | subclass of | prov:Entity |
sosa:Platform | subclass of | prov:Entity |
sosa:Result | subclass of | prov:Entity |
sosa:Sample | subclass of | prov:Entity |
This section is non-normative.
The following properties from SOSA have simple alignments with PROV properties:
sosa:madeByActuator | subproperty of | prov:wasAssociatedWith |
sosa:hasFeatureOfInterest | subproperty of | prov:used |
sosa:hasResult | subproperty of | prov:generated |
sosa:invokedBy | subproperty of | prov:wasAssociatedWith |
sosa:isResultOf | subproperty of | prov:wasGeneratedBy |
sosa:isSampleOf | subproperty of | prov:wasDerivedFrom |
sosa:madeBySampler | subproperty of | prov:wasAssociatedWith |
sosa:madeBySensor | subproperty of | prov:wasAssociatedWith |
sosa:resultTime | subproperty of | prov:endedAtTime |
The final property alignment first requires some sub-properties of PROV properties to be defined:
sp:eventAssociation | subproperty of | prov:qualifiedAssociation |
domain | Union of ( sosa:Observation or sosa:Actuation or sosa:Sampling ) | |
sp:hadProcedure | subproperty of | prov:hadPlan |
range | sosa:Procedure |
Then sosa:usedProcedure is given by a property chain axiom:
sosa:usedProcedure | property chain axiom | [ sp:eventAssociation , sp:hadProcedure ] |
An RDF file containing a graph corresponding to this alignment is available.
This section is non-normative.
This section informally discusses how to handle common modeling questions such as locations, forecasts, and quantity values with a unit of measure.Many of the key classes provided by SOSA and SSN represent entities that can be located in space such as sensors, features of interest, actuators, samples, and so forth, or activities that can be located via their participating entities, e.g., platforms. These entities will usually be described using models and ontologies defined for application domains, including technical disciplines, social and business contexts. In these contexts there are a number of implementations that support the expression of spatial properties, including location. These are discussed further in the Spatial Data on the Web Best Practices note [SDW-BP].
In particular, GeoSPARQL [GeoSPARQL] provides a flexible and relatively complete platform for geospatial objects, that fosters interoperability between geo-datasets. To do so, these entities can be declared as instances of geo:Feature and geometries can be assigned to them via the geo:hasGeometry property. In case of classes, e.g., specific features of interests such as rivers, these can be defined as subclasses of geo:Feature.
This section is non-normative.
One may also represent forecasts as observations if the value of sosa:phenomenonTime
is later in time than the sosa:resultTime
. Given the definition of these terms, it means that: The time when the
Observation act was completed is before the time that the Result of
the observation applies to the FeatureOfInterest.
Other means to represent forecasts are reported, but not in the scope of this specification. For example [
Lefrancois-et-al-2017] derives the SSN Sensing/Sensor/Observation
pattern and define Forecasting/Forecaster/Forecast
classes.
Describing a plan for some actuation or observation in the future is not covered by this specification.
This section is non-normative.
The result of an sosa:Observation
or an sosa:Actuation
can be a quantity value with a numeric value and a unit of measure.
It is not in the scope of this specification to recommend any particular way of modeling results as quantity values. There exists external vocabularies that are specifically designed for modeling quantity values as OWL individuals. Examples
include the Quantities, Units, Dimensions and Data Types Ontologies (QUDT, [QUDT]) and the Ontology of Units of Measure (OM, [Rijgersberg-et-al-2013]).
With QUDT 1.1, a sosa:Result
would be a qudt:QuantityValue
.
With OM 2, a sosa:Result
would be a om:Measure
or om:Point
.
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
@prefix qudt-1-1: <http://qudt.org/1.1/schema/qudt#> .
@prefix qudt-unit-1-1: <http://qudt.org/1.1/vocab/unit#> .
<Observation/234534> a sosa:Observation ;
rdfs:comment "Observation of the difference between
the outside temperature and the inside temperature."@en ;
sosa:hasFeatureOfInterest <apartment/134> ;
sosa:hasResult [
a qudt-1-1:QuantityValue ;
qudt-1-1:unit qudt-unit-1-1:DegreeCelsius ;
qudt-1-1:numericValue "-29.9"^^xsd:double ] .
<Observation/83985> a sosa:Observation ;
rdfs:comment "Observation of the temperature inside apartment #134."@en ;
sosa:hasFeatureOfInterest <apartment/134> ;
sosa:hasResult [
a qudt-1-1:QuantityValue ;
qudt-1-1:unit qudt-unit-1-1:DegreeCelsius ;
qudt-1-1:numericValue "22.4"^^xsd:double ] .
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
@prefix om: <http://www.ontology-of-units-of-measure.org/resource/om-2/> .
<Observation/234534> a sosa:Observation ;
rdfs:comment "Observation of the difference between
the outside temperature and the inside temperature."@en ;
sosa:hasFeatureOfInterest <apartment/134> ;
sosa:hasResult [
a om:Measure ;
om:hasUnit om:degreeCelsius ;
om:hasNumericalValue "-29.9"^^xsd:double ] .
<Observation/83985> a sosa:Observation ;
rdfs:comment "Observation of the temperature inside apartment #134."@en ;
sosa:hasFeatureOfInterest <apartment/134> ;
sosa:hasResult [
a om:Point ;
om:hasScale om:CelsiusScale ;
om:hasNumericalValue "22.4"^^xsd:double ] .
Other means to represent quantity values as literals are reported, but not in the scope of this specification. This solution would require the use of some custom datatype whose value space is some set of quantity values. Such a datatype should be supported by RDF and SPARQL engines to support the comparison of quantity values. On the other hand, this approach is not compatible with the OWL specifications, that restrict the set of datatypes that can be used. See sec. 5.2 in [owl2-syntax] for more details.
@prefix cdt: <http://w3id.org/lindt/custom_datatypes#> .
@prefix sosa: <http://www.w3.org/ns/sosa/> .
<observation/123> a sosa:Observation ;
sosa:hasSimpleResult "12.4 m"^^cdt:length .
This section is non-normative.
This specification does not specify whether an instance of ssn:Property
should be generic to all features of interest (e.g., ex:Temperature
,
ex:OnOffStatus
), or specific to a single feature of interest (e.g., <myBodyTemperature>
, <LightStatus>
). Implementers are free to choose one way of modeling things or the other.
On the other hand, one SHOULD NOT use OWL punning to make ex:Temperature
denote both a subclass of
ssn:Property
and an instance of ssn:Property
. In fact, merging the two examples below in a single RDF Graph would make an OWL reasoner infer that ex:Temperature
,
<office/1/temperature>
, and
<office/2/temperature>
, denote the same individual.
This also holds for subclasses of ssn:Property
: sosa:ObservableProperty
, and sosa:ActuatableProperty
.
This first example is modeling instances of ssn:Property
as generic to all features of interest:
ex:Temperature a ssn:Property .
<office/1> a sosa:FeatureOfInterest;
ssn:hasProperty ex:Temperature .
<Observation/1> a sosa:Observation ;
sosa:observedProperty ex:Temperature ;
sosa:hasFeatureOfInterest <office/1> .
<office/2> a sosa:FeatureOfInterest;
ssn:hasProperty ex:Temperature .
<Observation/1> a sosa:Observation ;
sosa:observedProperty ex:Temperature ;
sosa:hasFeatureOfInterest <office/2> .
This second example is modeling instances of ssn:Property
as specific to a features of interest:
ex:Temperature a owl:Class ;
rdfs:subClassOf ssn:Property .
<office/1> a sosa:FeatureOfInterest;
ssn:hasProperty <office/1/temperature> .
<office/1/temperature> a ex:Temperature , ssn:Property .
<Observation/1> a sosa:Observation ;
sosa:observedProperty <office/1/temperature> ;
sosa:hasFeatureOfInterest <office/1> .
<office/2> a sosa:FeatureOfInterest;
ssn:hasProperty <office/2/temperature> .
<office/2/temperature> a ex:Temperature , ssn:Property .
<Observation/1> a sosa:Observation ;
sosa:observedProperty <office/2/temperature> ;
sosa:hasFeatureOfInterest <office/2> .
This section is non-normative.
This specification does not specify whether an instance of ssn:System
should be generic (e.g., ex:TemperatureSensor
,
ex:LightActuator
), or specific to a single feature of interest (e.g., <temperatureSensor/84>
, <light/112>
). Implementers are free to choose one way of modeling things or the other.
On the other hand, one SHOULD NOT use OWL punning to make ex:Temperature
denote both a subclass of
ssn:Property
and an instance of ssn:Property. In fact, merging the two examples below in a single RDF Graph would make an OWL reasoner infer that ex:TemperatureSensor
, <TemperatureSensor/1>
,
and
<TemperatureSensor/2>
, denote the same individual.
This also holds for subclasses of ssn:System
: sosa:Sensor
, sosa:Actuator
, and sosa:Sampler
.
This first example is modeling instances of ssn:System
as generic:
ex:TemperatureSensor a ssn:System .
<Observation/1> a sosa:Observation ;
sosa:madeBySensor ex:TemperatureSensor .
<Observation/2> a sosa:Observation ;
sosa:madeBySensor ex:TemperatureSensor .
# describing the system capabilities and operating/survival range can be done generically
# with this modeling choice:
ex:TemperatureSensor ssn-system:hasOperatingRange ex:TemperatureSensorOperatingRange .
ex:TemperatureSensorOperatingRange a ssn-system:OperatingRange ;
ssn-system:inCondition ex:NormalTemperatureCondition , ex:NormalHumidityCondition .
This second example is modeling instances of ssn:System
as specific:
ex:TemperatureSensor a owl:Class ;
rdfs:subClassOf ssn:System .
<TemperatureSensor/1> a ex:TemperatureSensor , ssn:System .
<Observation/1> a sosa:Observation ;
sosa:madeBySensor <TemperatureSensor/1> .
<TemperatureSensor/2> a ex:TemperatureSensor , ssn:System .
<Observation/2> a sosa:Observation ;
sosa:madeBySensor <TemperatureSensor/2> .
# describing the system capabilities and operating/survival range can be done at the level of
# the class or at the level of each instance with this modeling choice:
ex:TemperatureSensor rdfs:subClassOf [
owl:onProperty ssn-system:hasOperatingRange ;
owl:hasValue ex:TemperatureSensorOperatingRange ] .
<TemperatureSensor/1>
ssn-system:hasOperatingRange ex:TemperatureSensorOperatingRange ; # this axiom can be inferred
ssn-system:hasOperatingRange <moreSpecificTemperatureSensorOperatingRange> .
<moreSpecificTemperatureSensorOperatingRange> a ssn-system:OperatingRange ;
ssn-system:inCondition <modeSpecificTemperatureCondition> , <modeSpecificHumidityCondition> .
Results of the wide review of SOSA and SSN is summarized here.
An RDF file containing a graph corresponding to this example is available.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix time: <http://www.w3.org/2006/time#>.
@prefix qudt-1-1: <http://qudt.org/1.1/schema/qudt#> .
@prefix qudt-unit-1-1: <http://qudt.org/1.1/vocab/unit#> .
@prefix cdt: <http://w3id.org/lindt/custom_datatypes#> .
@base <http://example.org/data/> .
# The barometric readings from a Bosch Sensortec BMP282 sensor in an Apple IPhone 7
# observed on June 6 2017 using only the SOSA core for modelling.
<earthAtmosphere> rdf:type sosa:FeatureOfInterest ;
rdfs:label "Atmosphere of Earth"@en .
# An iPhone 7 as the Platform that hosts several sensors,
# among others the Bosch Sensortec BMP282 atmospheric pressure sensor.
<iphone7/35-207306-844818-0> a sosa:Platform ;
rdfs:label "IPhone 7 - IMEI 35-207306-844818-0"@en ;
rdfs:comment "IPhone 7 - IMEI 35-207306-844818-0 - John Doe"@en ;
sosa:hosts <sensor/35-207306-844818-0/BMP282> .
<sensor/35-207306-844818-0/BMP282> rdf:type sosa:Sensor ;
rdfs:label "Bosch Sensortec BMP282"@en ;
sosa:observes <sensor/35-207306-844818-0/BMP282/atmosphericPressure> .
# An observation made by the BMP282 atmospheric pressure sensor.
<Observation/346344> rdf:type sosa:Observation ;
sosa:observedProperty <sensor/35-207306-844818-0/BMP282/atmosphericPressure> ;
sosa:hasFeatureOfInterest <earthAtmosphere> ;
sosa:madeBySensor <sensor/35-207306-844818-0/BMP282> ;
sosa:hasSimpleResult "1021.45 hPa"^^cdt:ucum ;
sosa:resultTime "2017-06-06T12:36:12Z"^^xsd:dateTime .
# Another observation made a second later by the BMP282 atmospheric pressure sensor
# using the QUDT Ontology for the Units of Measurement
# and the Time Ontology for the instant.
<Observation/346345> rdf:type sosa:Observation ;
sosa:observedProperty <sensor/35-207306-844818-0/BMP282/atmosphericPressure> ;
sosa:hasFeatureOfInterest <earthAtmosphere> ;
sosa:madeBySensor <sensor/35-207306-844818-0/BMP282> ;
sosa:hasResult [
rdf:type qudt-1-1:QuantityValue ;
qudt-1-1:numericValue "101936"^^xsd:double ;
qudt-1-1:unit qudt-unit-1-1:Pascal ] ;
sosa:resultTime [
rdf:type time:Instant ;
time:inXSDDateTimeStamp "2017-06-06T12:36:13+00:00"^^xsd:dateTimeStamp ] .
An RDF file containing a graph corresponding to this example is available.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sosa: <http://www.w3.org/ns/sosa#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix cdt: <http://w3id.org/lindt/custom_datatypes#>.
@base <http://example.org/data/> .
<IDEA> a owl:Ontology ;
owl:imports <http://www.w3.org/ns/sosa> .
<COPR> a sosa:FeatureOfInterest ;
sosa:hasSample <COPR_SL> ;
rdfs:comment "Coal Oil Point Reserve: UC Santa Barbara Natural Reserve System"@en ;
rdfs:label "Coal Oil Point Reserve"@en .
<COPR_Station_Location> a sosa:Sample ;
rdfs:comment "."@en ;
rdfs:label "Air around COPR Station"@en ;
sosa:isSampleOf <COPR> .
<COPR_Station> a sosa:Platform ;
rdfs:comment "Station at Coal Oil Point Reserve, CA (see http://www.geog.ucsb.edu/ideas/COPR.html for details)"@en ;
rdfs:label "Coal Oil Point Reserve Wx Station"@en ;
rdfs:seeAlso <http://www.geog.ucsb.edu/ideas/COPR.html> ;
sosa:hosts <COPR-HMP45C-L> .
<COPR-HMP45C-L> a sosa:Platform ;
rdfs:label "HMP45C-L Temperature and Relative Humidity Probe at Coal Oil Point, UCSB, CA"@en ;
sosa:hosts <HUMICAP-H> ;
sosa:isHostedBy <COPR_Station> .
<HUMICAP-H> a sosa:Sensor ;
rdfs:label "Vaisala HUMICAP H-chip"@en ;
sosa:isHostedBy <COPR-HMP45C-L> .
<RelativeHumidity> a sosa:ObservableProperty ;
rdfs:comment "Humidity is a measure of the moisture content of air."@en ;
rdfs:label "Relative Humidity"@en .
<MeasuringRelativeHumidity> a sosa:Procedure ;
rdfs:comment "Instructions for measuring relative humidity"@en .
<RH_avg_1_COPR_15min_201706020300PM> a sosa:Observation ;
rdfs:comment "Relative humidity as averaged over 15min at COPR."@en ;
rdfs:label "Relative humidity, AVG, 15min, COPR, 06.02.2017, 3:00 PM"@en ;
sosa:madeBySensor <HUMICAP-H> ;
sosa:hasFeatureOfInterest <COPR_Station_Location> ;
sosa:hasSimpleResult "92.5 %"^^cdt:ucum ;
sosa:resultTime "2017-06-02-T03:00:00-7:00"^^xsd:dateTime ;
sosa:observedProperty <RelativeHumidity> ;
sosa:usedProcedure <MeasuringRelativeHumidity> .
An RDF file containing a graph corresponding to this example is available.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix time: <http://www.w3.org/2006/time#>.
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix ssn: <http://www.w3.org/ns/ssn/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix qudt-1-1: <http://qudt.org/1.1/schema/qudt#> .
@prefix qudt-unit-1-1: <http://qudt.org/1.1/vocab/unit#> .
@base <http://example.org/data/> .
# The electric consumption of apartment #134 on April 15 2017 was 22.4 kWh as
# observed by sensor #926. The result was available 12 seconds later.
<Observation/235714> rdf:type sosa:Observation ;
sosa:observedProperty <apartment/134/electricConsumption> ;
sosa:madeBySensor <sensor/926> ;
sosa:hasResult [
rdf:type qudt-1-1:QuantityValue ;
qudt-1-1:numericValue "22.4"^^xsd:double ;
qudt-1-1:unit qudt-unit-1-1:Kilowatthour ] ;
sosa:phenomenonTime [
rdf:type time:Interval ;
time:hasBeginning [
rdf:type time:Instant ;
time:inXSDDateTimeStamp "2017-04-15T00:00:00+00:00"^^xsd:dateTimeStamp ] ;
time:hasEnd [
rdf:type time:Instant ;
time:inXSDDateTimeStamp "2017-04-16T00:00:00+00:00"^^xsd:dateTimeStamp ] ] ;
sosa:resultTime "2017-04-16T00:00:12+00:00"^^xsd:dateTimeStamp .
# Sensor #926 observes the electric consumption of apartment #134, and we know that
# it made some observations.
<sensor/926> rdf:type sosa:Sensor ;
sosa:observes <apartment/134/electricConsumption> ;
sosa:madeObservation <Observation/235714>, <Observation/235715>, <Observation/235716> .
# mobile sensor tempSensor #23 observes the temperature in its surroundings, and we know
# that it made some observations.
<tempSensor/23> rdf:type sosa:Sensor ;
sosa:observes <tempSensor/23#temperature> ;
sosa:madeObservation <tempSensor/23/4572>, <tempSensor/23/4573>, <tempSensor/23/4574> .
# Sensor #926 observes the electric consumption of apartment #134
<sensor/926> rdf:type sosa:Sensor ;
sosa:observes <apartment/134/electricConsumption> .
# This is equivalent to saying that the electric consumption of apartment #134 is
# observed by Sensor #926
<apartment/134/electricConsumption> rdf:type sosa:ObservableProperty ;
sosa:isObservedBy <sensor/926> .
# Sensor #926 made observations identified by <Observation/235714> and <Observation/235715>.
<sensor/926> rdf:type sosa:Sensor ;
sosa:madeObservation <Observation/235714>, <Observation/235715> .
# This is equivalent to saying that these observations have been made by sensor #926.
<Observation/235714> rdf:type sosa:Observation ;
sosa:madeBySensor <sensor/926> .
<Observation/235754> rdf:type sosa:Observation ;
sosa:madeBySensor <sensor/926> .
# the window opening state is an ActuatableProperty.
# SSN allows to explicitly say that <window/104#state> is a property of <window>
<window> rdf:type sosa:FeatureOfInterest ;
ssn:hasProperty <window/104#state> .
<window/104#state> rdf:type sosa:ActuatableProperty ;
sosa:isActedOnBy <actuation/188> .
# WindowCloser #987 made actuation #188
# SSN allows to explicitly say that <windowCloser/987> is designed to automatically open and close window #104.
<windowCloser/987> rdf:type sosa:Actuator ;
sosa:madeActuation <actuation/188> ;
ssn:forProperty <window/104#state> .
# Actuation #188 acted on the state of window #104 and returned 'true'.
<actuation/188> rdf:type sosa:Actuation ;
sosa:actsOnProperty <window/104#state> ;
sosa:actuationMadeBy <windowCloser/987> ;
sosa:hasSimplResult true ;
sosa:resultTime "2017-04-18T17:24:00+02:00"^^xsd:dateTimeStamp .
An RDF file containing a graph corresponding to this example is available.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix ssn: <http://www.w3.org/ns/ssn/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix qudt-1-1: <http://qudt.org/1.1/schema/qudt#> .
@prefix qudt-unit-1-1: <http://qudt.org/1.1/vocab/unit#> .
@base <http://example.org/data/> .
# rangefinder #30 is a laser range finder sensor that was used
# to observe the height of tree #124 and #125.
<rangefinder/30> rdf:type sosa:Sensor ;
rdfs:label "rangefinder #30"@en ;
rdfs:comment "rangefinder #30 is a laser range finder sensor."@en .
# rangefinder #30 made observation #1087 of the height of tree #124.
<observation/1087> rdf:type sosa:Observation ;
rdfs:label "observation #1087"@en ;
sosa:hasFeatureOfInterest <tree/124> ;
sosa:observedProperty <tree/124/height> ;
sosa:madeBySensor <rangefinder/30> ;
sosa:hasResult [
qudt-1-1:unit qudt-unit-1-1:Meter ;
qudt-1-1:numericalValue "15.3"^^xsd:double ] .
# using SSN, one can explicitly link a property and its feature of interest.
<tree/124> rdf:type sosa:FeatureOfInterest ;
rdfs:label "tree #124"@en ;
ssn:hasProperty <tree/124#height> .
<tree/124#height> rdf:type sosa:ObservableProperty , ssn:Property ;
rdfs:label "the height of tree #124"@en ;
ssn:isPropertyOf <tree/124> .
# rangefinder #30 made observation #1088 of the height of tree #125.
<observation/1088> rdf:type sosa:Observation ;
rdfs:label "observation #1088"@en ;
sosa:hasFeatureOfInterest <tree/125> ;
sosa:observedProperty <tree/125/height> ;
sosa:madeBySensor <rangefinder/30> ;
sosa:hasResult [
qudt-1-1:numericValue "23.0"^^xsd:double ;
qudt-1-1:unit qudt-unit-1-1:Meter ] .
# using SSN, one can explicitly link a property and its feature of interest.
<tree/125> rdf:type sosa:FeatureOfInterest ;
rdfs:label "tree #125"@en ;
ssn:hasProperty <tree/125#height> .
<tree/125#height> rdf:type sosa:ObservableProperty , ssn:Property ;
rdfs:label "the height of tree #125"@en ;
ssn:isPropertyOf <tree/124> .
An RDF file containing a graph corresponding to this example is available.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix ssn: <http://www.w3.org/ns/ssn/> .
@prefix geo: <http://www.w3.org/2003/01/geo/wgs84_pos#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix qudt-1-1: <http://qudt.org/1.1/schema/qudt#> .
@prefix qudt-unit-1-1: <http://qudt.org/1.1/vocab/unit#> .
@base <http://example.org/data/> .
# Observation #358 of seismograph VCAB DP1 BP 40 (Vineyard Canyon, Parkfield, Ca) measured
# a earth displacement speed of 0.000500 cm/sec at 8:23 am on April 18, 2017, Pacific
# Daylight Time.
<earth> rdf:type sosa:FeatureOfInterest ;
rdfs:label "earth"@en .
<VCAB-DP1-BP-40> rdf:type sosa:Sensor ;
rdfs:label "seismograph VCAB DP1 BP 40 (Vineyard Canyon, Parkfield, Ca)"@en ;
rdfs:seeAlso <https://earthquake.usgs.gov/monitoring/seismograms/153> ;
sosa:observes <VCAB-DP1-BP-40#groundDisplacementSpeed> .
<VCAB-DP1-BP-40#location> rdf:type sosa:FeatureOfInterest ;
rdfs:label "location of VCAB-DP1-BP-40"@en ;
geo:lat 35.8648067 ;
geo:long -120.6195831 ;
geo:alt 12.75 ;
sosa:isSampleOf <earth> .
<VCAB-DP1-BP-40#groundDisplacementSpeed> rdf:type sosa:ObservableProperty , ssn:Property ;
rdfs:label "the ground displacement speed at location of VCAB-DP1-BP-40"@en ;
sosa:isObservedBy <VCAB-DP1-BP-40> .
<VCAB-DP1-BP-40?t=2017-04-18T08%3A23%3A00-07%3A00> rdf:type sosa:Observation ;
sosa:madeBySensor <VCAB-DP1-BP-40> ;
sosa:hasFeatureOfInterest <VCAB-DP1-BP-40#location> ;
sosa:observedProperty <VCAB-DP1-BP-40#groundDisplacementSpeed> ;
sosa:hasResult [
rdf:type qudt-1-1:QuantityValue ;
qudt-1-1:numericValue "5e-4"^^xsd:double ;
qudt-1-1:unit qudt-unit-1-1:CentimeterPerSecond ] ;
sosa:resultTime "2017-04-18T08:23:00-07:00"^^xsd:dateTimeStamp .
# using SSN one can explicitly state that <VCAB-DP1-BP-40#groundDisplacementSpeed> is the property of <VCAB-DP1-BP-40#location> .
<VCAB-DP1-BP-40#location> ssn:hasProperty <VCAB-DP1-BP-40#groundDisplacementSpeed> ;
An RDF file containing a graph corresponding to this example is available.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix time: <http://www.w3.org/2006/time#>.
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@base <http://example.org/data/> .
# The result of an observation of the sunspot number is available a few minutes
# after the phenomenon time, due to the light travel duration.
<Observation/7536> rdf:type sosa:Observation ;
sosa:observedProperty <Sun#sunspotNumber> ;
sosa:hasSimpleResult 66 ;
sosa:phenomenonTime [
rdf:type time:Instant ;
time:inXSDDateTimeStamp "2017-03-31T11:51:42+00:00"^^xsd:dateTimeStamp ] ;
sosa:resultTime "2017-03-31T12:00:00+00:00"^^xsd:dateTimeStamp .
An RDF file containing a graph corresponding to this example is available.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix ssn: <http://www.w3.org/ns/ssn/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@base <http://example.org/data/> .
# movements of spinning cups on wind sensor #14 serves as proxies for the wind speed
# at the location of the wind sensor.
<windSensor/14> rdf:type sosa:Sensor ;
sosa:observes <location/4687#windSpeed> .
# wind sensor #14 detected some movement of spinning cups, from which originated the
# observations #147 and #148.
<windSensor/14> rdf:type sosa:Sensor ;
sosa:madeObservation <observation/147> , <observation/148> ;
ssn:detects <observation/147#spinningCupsMovement> , <observation/148#spinningCupsMovement> .
# observation #147 was originated by the movement of the spinning cups of sensor #14.
# the result of observations #147 and #148 is using some custom datatype that encodes the unit of measure.
<observation/147> rdf:type sosa:Observation ;
sosa:observedProperty <location/4687#windSpeed> ;
sosa:madeBySensor <windSensor/14> ;
ssn:wasOriginatedBy <observation/147#spinningCupsMovement> ;
sosa:resultTime "2017-04-12T12:00:00Z"^^xsd:dateTime ;
sosa:hasSimpleResult "47 km/h"^^<speed> .
<observation/147#spinningCupsMovement> rdf:type ssn:Stimulus ;
ssn:isProxyFor <location/4687#windSpeed> .
<observation/148> rdf:type sosa:Observation ;
sosa:observedProperty <location/4687#windSpeed> ;
sosa:madeBySensor <windSensor/14> ;
ssn:wasOriginatedBy <observation/148#spinningCupsMovement> ;
sosa:resultTime "2017-04-12T12:01:00Z"^^xsd:dateTime ;
sosa:hasSimpleResult "43 km/h"^^<speed> .
<observation/148#spinningCupsMovement> rdf:type ssn:Stimulus ;
ssn:isProxyFor <location/4687#windSpeed> .
In order to characterize a thing with a large extent, or which is not directly accessible, the usual observational strategy is to obtain one or more samples. Observations may then be made more conveniently on the samples, with the intention
of characterizing the larger thing. This intentionality is captured using the property sosa:isSampleOf
.
In the following example, the ice core is a sample of the Antarctic ice sheet, and observations are made on the ice core.
A convenient side effect of this feature is that all observations related to the larger thing (the ice sheet) can be found, and then potentially joined together in a meta-analysis in order to characterize that.
An RDF file containing a graph corresponding to this example is available.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix time: <http://www.w3.org/2006/time#>.
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix ssn: <http://www.w3.org/ns/ssn/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix geo: <http://www.w3.org/2003/01/geo/wgs84_pos#>.
@base <http://example.org/data/> .
# The CO2 level observed in an ice core is 240 parts per million.
# the ice core is a sample of the polar ice sheet of Antarctica.
<http://dbpedia.org/resource/Antarctic_ice_sheet> a sosa:FeatureOfInterest ;
sosa:hasSample <iceCore/12>, <iceCore/13>, <iceCore/14> .
<iceCore/12> rdf:type sosa:Sample ;
sosa:isSampleOf <http://dbpedia.org/resource/Antarctic_ice_sheet> ;
sosa:isResultOf <WellDrilling/4578> ;
sosa:madeBySampler <thermalDrill/2> .
<WellDrilling/4578> a sosa:Sampling ;
geo:lat -73.35 ;
geo:long 9.32 ;
sosa:hasResult <iceCore/12> ;
sosa:madeBySampler <thermalDrill/2> ;
sosa:resultTime "2017-04-03T11:12:00Z"^^xsd:dateTime ;
sosa:hasFeatureOfInterest <http://dbpedia.org/resource/Antarctic_ice_sheet> .
<iceCore/12#observation> a sosa:Observation ;
sosa:observedProperty <iceCore/12#CO2> ;
sosa:hasSimpleResult 240 .
# using SSN one can explicitly state that <iceCore/12#CO2> is the property of <iceCore/12> .
<iceCore/12#CO2> ssn:isPropertyOf <iceCore/12> .
An RDF file containing a graph corresponding to this example is available.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix qudt-1-1: <http://qudt.org/1.1/schema/qudt#> .
@prefix qudt-unit-1-1: <http://qudt.org/1.1/vocab/unit#> .
@prefix schema: <http://schema.org/>.
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix ssn: <http://www.w3.org/ns/ssn/> .
@prefix ssn-system: <http://www.w3.org/ns/ssn/systems/> .
@prefix rdfp: <https://w3id.org/rdfp/>.
@base <http://example.org/data/> .
<DHT22#Procedure> a sosa:Procedure ;
ssn:hasOutput <DHT22#output> .
<DHT22#output> a ssn:Output , rdfp:GraphDescription ;
rdfs:comment "The output is a RDF Graph that describes both the temperature and the humidity. It can be validated by a SHACL shapes graph."@en ;
rdfp:presentedBy [
a rdfp:GraphDescription ;
rdfp:validationRule <shacl_shapes_graph> ;
] .
<DHT22/4578> a ssn:System ;
rdfs:comment "DHT22 sensor #4578 contains a humidity and a temperature sensor."@en ;
rdfs:seeAlso <https://www.sparkfun.com/datasheets/Sensors/Temperature/DHT22.pdf> ;
ssn:hasSubSystem <DHT22/4578#TemperatureSensor>, <DHT22/4578#HumiditySensor> .
<DHT22/4578#TemperatureSensor> a sosa:Sensor , ssn:System ;
rdfs:comment "The embedded temperature sensor, a specific instance of temperature sensor."@en ;
ssn-system:hasOperatingRange <DHT22/4578#TemperatureSensorOperatingRange> ;
ssn-system:hasSystemCapability <DHT22/4578#TemperatureSensorCapability> ;
ssn:implements <DHT22#Procedure> .
<DHT22/4578#HumiditySensor> a sosa:Sensor , ssn:System ;
rdfs:comment "The embedded humidity sensor, a specific instance of humidity sensor."@en ;
ssn-system:hasOperatingRange <DHT22/4578#HumiditySensorOperatingRange> ;
ssn:implements <DHT22#Procedure> .
<DHT22/4578#TemperatureSensorOperatingRange> a ssn-system:OperatingRange ;
rdfs:comment "The conditions in which the DHT22 temperature sensor is expected to operate."@en ;
ssn-system:inCondition <NormalTemperatureCondition> , <NormalHumidityCondition> .
<DHT22/4578#HumiditySensorOperatingRange> a ssn-system:OperatingRange ;
rdfs:comment "The conditions in which the DHT22 humidity sensor is expected to operate."@en ;
ssn-system:inCondition <NormalTemperatureCondition> , <NormalHumidityCondition> .
<NormalOperatingCondition> a ssn-system:Condition , schema:PropertyValue ;
rdfs:comment "A temperature range of -40 to 80 Celsius."@en ;
schema:minValue -40.0 ;
schema:maxValue 80.0 ;
schema:unitCode qudt-unit-1-1:DegreeCelsius .
<NormalHumidityCondition> a ssn-system:Condition , schema:PropertyValue ;
rdfs:comment "A relative humidity range of 5 to 85 %."@en ;
schema:minValue 5.0 ;
schema:maxValue 85.0 ;
schema:unitCode qudt-unit-1-1:Percent .
<DHT22/4578#TemperatureSensorCapability> a ssn:Property , ssn-system:SystemCapability , schema:PropertyValue ;
rdfs:comment "The capabilities of the temperature sensor in normal temperature and humidity conditions." ;
ssn-system:inCondition <NormalTemperatureCondition> , <NormalHumidityCondition> ;
ssn-system:hasSystemProperty <DHT22/4578#TemperatureSensorAccuracy> , <DHT22/4578#TemperatureSensorSensitivity> , <DHT22/4578#TemperatureSensorRepeatability> , <DHT22/4578#TemperatureSensorFrequency> .
<DHT22/4578#TemperatureSensorAccuracy> a ssn:Property , ssn-system:Accuracy , schema:PropertyValue ;
rdfs:comment "The accuracy of the temperature sensor is +-0.5 °C in normal temperature and humidity conditions."@en ;
schema:minValue -0.5 ;
schema:maxValue 0.5 ;
schema:unitCode qudt-unit-1-1:DegreeCelsius .
<DHT22/4578#TemperatureSensorSensitivity> a ssn:Property , ssn-system:Sensitivity , ssn-system:Resolution , schema:PropertyValue ;
rdfs:comment "The sensitivity and resolution of the temperature sensor is 0.1 °C in normal temperature and humidity conditions."@en ;
schema:value 0.1 ;
schema:unitCode qudt-unit-1-1:DegreeCelsius .
<DHT22/4578#TemperatureSensorPrecision> a ssn:Property , ssn-system:Precision , schema:PropertyValue ;
rdfs:comment "The precision (= repeatability) of the temperature sensor is +-0.2 °C in normal temperature and humidity conditions."@en ;
schema:minValue 0.2 ;
schema:maxValue 0.2 ;
schema:unitCode qudt-unit-1-1:DegreeCelsius .
<DHT22/4578#TemperatureSensorFrequency> a ssn:Property , ssn-system:Frequency , schema:PropertyValue ;
rdfs:comment "The smallest possible time between one observation and the next is 2 s on average."@en ;
schema:value 2 ;
schema:unitCode qudt-unit-1-1:Second .
<observation/1087> rdf:type sosa:Observation ;
sosa:madeBySensor <DHT22/4578#TemperatureSensor> ;
sosa:usedProcedure <DHT22#Procedure> ;
ssn-system:qualityOfObservation <observation/1087#quality> ;
# one may classify the quality of observation using some class:
<observation/1087#quality> rdf:type ex:FairQuality .
# one may use some other ontology to further qualify this quality.
<observation/1087#quality>
ex:evaluatedBy <Tom> ;
ex:confidenceValue "6"^^xsd:integer;
rdfs:comment """Tom gave a confidence value of 6 out of 10 on this observation."""@en .
# one may use some quantity ontology.
@prefix qudt-1-1: <http://qudt.org/1.1/schema/qudt#> .
@prefix qudt-unit-1-1: <http://qudt.org/1.1/vocab/unit#> .
<observation/1087#quality> rdf:type qudt-1-1:Quantity ;
qudt-1-1:quantityValue [
rdf:type qudt-1-1:QuantityValue ;
qudt-1-1:numericValue "98.4"^^xsd:double ;
qudt-1-1:unit qudt-unit-1-1:Percent ] .
This example shows how the conditions (temperature and humidity) in a room may be measured using one or more sensors. Each sensor observes the conditions in its immediate vicinity, and the values are then used to characterize the room.
In Room 145 one of the walls is external in the building, so there is expected to be a temperature gradient across the room, and there are two sensors on different walls. In room 245 there is one sensor on the south wall. Each of these
locations corresponds to a sosa:Sample
of the entire room. The wall also serves as a sosa:Platform
on which the sensors are mounted.
An RDF file containing a graph corresponding to this example is available.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix qudt-1-1: <http://qudt.org/1.1/schema/qudt#> .
@prefix qudt-unit-1-1: <http://qudt.org/1.1/vocab/unit#> .
@prefix schema: <http://schema.org/>.
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix ssn: <http://www.w3.org/ns/ssn/> .
@prefix ssn-system: <http://www.w3.org/ns/ssn/systems/> .
@base <http://example.org/data/> .
<Room145> a sosa:FeatureOfInterest ;
rdfs:label "Room #145"@en ;
sosa:hasSample <Room145/east> ;
sosa:hasSample <Room145/south> .
<Room145/east> a sosa:Sample , sosa:FeatureOfInterest , sosa:Platform ;
rdfs:label "East wall of room #145."@en ;
rdfs:comment "This wall hosts PCB Board 1 with DHT22 temperature and humidity sensor #4578."@en ;
sosa:hosts <PCBBoard1> .
<Room145/south> a sosa:Sample , sosa:FeatureOfInterest , sosa:Platform ;
rdfs:label "South wall of room #145."@en ;
rdfs:comment "This wall hosts PCB Board 2 with DHT22 temperature and humidity sensor #4579."@en ;
sosa:hosts <PCBBoard2> .
<Room245> a sosa:FeatureOfInterest ;
rdfs:label "Room #245"@en ;
sosa:hasProperty <Room245#temperature> , <Room245#humidity> ;
sosa:hasSample <Room245/south> .
<Room245/south> a sosa:Sample , sosa:FeatureOfInterest , sosa:Platform ;
rdfs:label "South wall of room #245."@en ;
sosa:hosts <PCBBoard3> .
<PCBBoard1> a ssn:System , sosa:Platform ;
rdfs:label "PCB Board 1"@en ;
rdfs:comment "PCB Board 1 hosts DHT22 temperature and humidity sensor #4578 permanently, one can say it has it as one of its subsystems."@en ;
sosa:hosts <DHT22/4578> ;
ssn:hasSubSystem <DHT22/4578> .
<DHT22/4578> a ssn:System ;
rdfs:label "DHT22 sensor #4578"@en ;
sosa:isHostedBy <PCBBoard1> .
<PCBBoard2> a ssn:System , sosa:Platform ;
rdfs:label "PCB Board 2"@en ;
rdfs:comment "PCB Board 2 hosts DHT22 temperature and humidity sensor #4579 permanently, one can say it has it as one of its subsystems."@en ;
sosa:hosts <DHT22/4578> ;
ssn:hasSubSystem <DHT22/4578> .
<DHT22/4579> a ssn:System ;
rdfs:label "DHT22 sensor #4579."@en ;
sosa:isHostedBy <PCBBoard2> .
<PCBBoard3> a ssn:System , sosa:Platform ;
rdfs:label "PCB Board 3"@en ;
rdfs:comment "PCB Board 3 hosts DHT22 temperature and humidity sensor #4580 permanently, one can say it has it as one of its subsystems."@en ;
sosa:hosts <DHT22/4578> ;
ssn:hasSubSystem <DHT22/4578> .
<DHT22/4580> a ssn:System ;
rdfs:label "DHT22 sensor #4580."@en ;
sosa:isHostedBy <PCBBoard3> .
<Room245Deployment> a ssn:Deployment ;
rdfs:comment "Deployment of PCB Board 3 on the south wall of room #245 for the purpose of observing the temperature and humidity of room #245."@en ;
ssn:deployedOnPlatform <Room245/south> ;
ssn:deployedSystem <PCBBoard3> ;
ssn:forProperty <Room245#temperature> , <Room245#humidity> .
<Room145Deployment> a ssn:Deployment ;
rdfs:comment "Deployment of PCB Board 1 and 2 on the east and south wall of room #145, respectively, for the purpose of observing the temperature and humidity of room #145."@en ;
ssn:deployedOnPlatform <Room245/east> , <Room245/south> ;
ssn:deployedSystem <PCBBoard1> , <PCBBoard2> ;
ssn:forProperty <Room145#temperature> , <Room145#humidity> .
This example describes the IP68 Smart Sensor that and some of its capabilities and operating ranges. A specific IP68 Smart Sensor observes the air temperature, and its own battery state.
An RDF file containing a graph corresponding to this example is available.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix geo: <http://www.w3.org/2003/01/geo/wgs84_pos#> .
@prefix gr: <http://purl.org/goodrelations/v1#> .
@prefix org: <http://www.w3.org/ns/org#> .
@prefix schema: <http://schema.org/> .
@prefix sosa: <http://www.w3.org/ns/sosa/> .
@prefix ssn: <http://www.w3.org/ns/ssn/> .
@prefix ssn-system: <http://www.w3.org/ns/ssn/systems/> .
@prefix qudt-unit-1-1: <http://qudt.org/vocab/unit#> .
@prefix prov: <http://www.w3.org/ns/prov#>.
@prefix owl: <http://www.w3.org/2002/07/owl#>.
@prefix seas: <https://w3id.org/seas/>.
@prefix cdt: <http://w3id.org/lindt/custom_datatypes#>.
@base <https://data.grandlyon.com/> .
<Organization/1> a org:Organization ;
owl:sameAs <http://dbpedia.org/page/Metropolis_of_Lyon> .
<Air> a sosa:FeatureOfInterest ;
rdfs:label "The air."@en .
<IP68_Outdoor_Temperature_Sensor> a owl:Class , gr:ProductOrServiceModel ;
gr:name "IP68 Outdoor Temperature Sensor"@en ;
rdfs:label "IP68 Outdoor Temperature Sensor"@en ;
rdfs:subClassOf [
owl:onProperty ssn-system:hasOperatingRange ;
owl:hasValue <IP68_Outdoor_Temperature_Sensor#operatingRange> ] ;
rdfs:subClassOf [
owl:onProperty ssn-system:hasSystemCapability ;
owl:hasValue <IP68_Outdoor_Temperature_Sensor#systemCapability> ] .
<IP68_Outdoor_Temperature_Sensor#operatingRange> a ssn-system:OperatingRange , ssn:Property ;
ssn-system:inCondition <IP68_Outdoor_Temperature_Sensor#normalOperatingCondition> .
<IP68_Outdoor_Temperature_Sensor#normalOperatingCondition> a ssn-system:Condition , schema:PropertyValue ;
rdfs:comment "A temperature range of -20 to 70 Celsius."@en ;
schema:minValue -20.0 ;
schema:maxValue 70.0 ;
schema:unitCode qudt-unit-1-1:DegreeCelsius .
<IP68_Outdoor_Temperature_Sensor#systemCapability> a ssn:Property , ssn-system:SystemCapability ;
rdfs:comment "The sensor capability in normal operating conditions."@en ;
ssn-system:hasSystemProperty <IP68_Outdoor_Temperature_Sensor#RFSensitivity> , <IP68_Outdoor_Temperature_Sensor#TemperatureAccuracy> , <IP68_Outdoor_Temperature_Sensor#TemperatureResolution> , <IP68_Outdoor_Temperature_Sensor#BatteryAccuracy> , <IP68_Outdoor_Temperature_Sensor#BatteryResolution> ;
ssn-system:inCondition <IP68_Outdoor_Temperature_Sensor#normalOperatingCondition> .
<IP68_Outdoor_Temperature_Sensor#RFSensitivity> a ssn:Property , ssn-system:Sensitivity , schema:PropertyValue ;
schema:value -137 ;
schema:unitCode qudt-unit-1-1:DecibelReferredToOneMilliwatt .
<IP68_Outdoor_Temperature_Sensor#TemperatureAccuracy> a ssn:Property , ssn-system:Accuracy , schema:PropertyValue ;
ssn:forProperty <Air?lat=45.75&long=4.85#temperature> ;
schema:minValue -0.2 ;
schema:maxValue 0.2 ;
schema:unitCode qudt-unit-1-1:DegreeCelsius .
<IP68_Outdoor_Temperature_Sensor#TemperatureResolution> a ssn:Property , ssn-system:Resolution , schema:PropertyValue ;
ssn:forProperty <Air?lat=45.75&long=4.85#temperature> ;
schema:value 0.0625 ;
schema:unitCode qudt-unit-1-1:DegreeCelsius .
<IP68_Outdoor_Temperature_Sensor#BatteryResolution> a ssn:Property , ssn-system:Resolution , schema:PropertyValue ;
ssn:forProperty <Sensor/SL-T-P1#battery> ;
schema:value 3.937e-3 ;
schema:unitCode qudt-unit-1-1:Percent .
<Air?lat=45.75&long=4.85> a sosa:Sample ;
rdfs:label "The air at lat 45.75 and long 4.85."@en ;
sosa:isSampleOf <Air> ;
ssn:hasProperty <Air?lat=45.75&long=4.85#temperature> .
<Air?lat=45.75&long=4.85#temperature> a ssn:Property , sosa:ObservableProperty ;
ssn:isPropertyOf <Air?lat=45.75&long=4.85> .
<Sensor/SL-T-P1> a gr:ProductOrService, sosa:Sensor , seas:LoRaCommunicationDevice , <IP68_Outdoor_Temperature_Sensor> ;
gr:hasBrand [ a gr:Brand ; gr:name "Sensing Labs"@en ] ;
geo:alt 100.0 ;
geo:lat 45.75 ;
geo:lon 4.85 ;
ssn:implements <IP68_Outdoor_Temperature_Sensor#temperatureSensingProcedure> ;
ssn:implements <IP68_Outdoor_Temperature_Sensor#batterySensingProcedure> ;
ssn:observes <Sensor/SL-T-P1#battery> ;
ssn:observes <Air?lat=45.75&long=4.85#temperature> .
<Deployment/SL-T-P1/2017-06-06> a ssn:Deployment ;
ssn:deployedSystem <Sensor/SL-T-P1> ;
prov:startedAtTime "2017-06-06"^^xsd:date ;
prov:wasAssociatedWith <Organization/1> ;
ssn:deployedOnPlatform <Tree/1> .
<Observation/5872357#temperature> a sosa:Observation ;
sosa:hasSimpleResult "64.5244681928429 Cel"^^cdt:ucum ;
sosa:madeBySensor <Sensor/SL-T-P1> ;
sosa:hasFeatureOfInterest <Air?lat=45.75&long=4.85> ;
sosa:observedProperty <Air?lat=45.75&long=4.85#temperature> ;
sosa:resultTime "2017-06-20T21:49:18+00:00"^^xsd:dateTime .
<Observation/5872357#battery> a sosa:Observation ;
sosa:hasSimpleResult "73.2 %"^^cdt:ucum ;
sosa:madeBySensor <Sensor/SL-T-P1> ;
sosa:hasFeatureOfInterest <Sensor/SL-T-P1> ;
sosa:observedProperty <Sensor/SL-T-P1#battery> ;
sosa:resultTime "2017-06-20T21:49:18+00:00"^^xsd:dateTime .
An XML implementation of the Observations and Measurements specification is available from OGC [OandM], known as [OMXML]. Annex C in that document contains a large set of examples. To assist users of O&M to understand SOSA/SSN, and potentially to migrate services based on OMXML to SOSA/SSN, an RDF file containing a graph corresponding to the OMXML examples is provided.
Note that in some cases the information contained in the OMXML examples goes beyond what is supported directly by SOSA/SSN, so the examples use terms from some other well known RDF vocabularies, such as [GeoSPARQL], [QUDT], [owl-time], and [prov-o], as well as the sample relations module. In some cases these only approximate the semantics of the OMXML examples. This is indicated in editorial notes embedded in the RDF file. In a few places where there was no well-known RDF implementation matching the requirements, the details have been omitted.
A full change-log is available on GitHub.