From 8eb7c3f9907c7cbdfa531ef58683cb7dbcdf54e3 Mon Sep 17 00:00:00 2001
From: Simon Cox Custom datatypes are not strictly compatible with OWL, which restricts the set of datatypes that can be used. See sec. 5.2 in [[owl2-syntax]] for more details. 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, with the core classes
-and properties defined using minimal axiomatization in a graph called SOSA (Sensor, Observation, Sample, and Actuator)
-supplemented with additional axiomatization and terms in further graphs.
-These allow SSN 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.
- The namespace for the core terms is
- http://www.w3.org/ns/sosa/. The suggested prefix for the SOSA namespace is sosa.
- The SOSA graph containing the core definitions is available at http://www.w3.org/ns/sosa/.
- 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. 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 interpreting 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. Ontology modularization is commonly used
- to segment an ontology to provide users with the knowledge
- they require, reducing the scope as much as possible to what is strictly
- necessary in a given use case. The SSN Ontology is distributed through several modules or graphs that use Vertical modules build upon each other, i.e., they directionally In particular,
- The SSN Ontology is distributed through several modules or graphs that use Vertical modules build upon each other, i.e., they directionally In particular,
+ Quantity Values and Unit of Measures
sosa:Result
would be a qudt:QuantityValue
sosa:Result
would be a om:Measure
or om:Point
sosa:hasSimpleResult
may be structured to match cdt:ucum
which encodes the unit-of-measure using UCUM (UCUM, [[UCUM]])sosa:hasSimpleResult
may alternatively be structured such that the datatype indicates a qudt:Unit
- The SSN graph with the full axiomatization of the core terms is available at http://www.w3.org/ns/ssn/.
-
- Introduction
- Modularization
-
- owl:imports
- statements.
- We distinguish two methods depending on the
- directionality of the segmentation: a vertical segmentation and a
- horizontal segmentation.
-
TODO: re-draw to include SOSA-OMS, SSN-OMS
- Vertical Segmentation
- owl:import
- lower level modules. Lower level modules are independent of their higher
- level modules and logically consistent on their own.
-
owl:imports
+ statements.
+ We distinguish two methods depending on the
+ directionality of the segmentation: a vertical segmentation and a
+ horizontal segmentation.
+
TODO: re-draw to include SOSA-OMS, SSN-OMS
+ Vertical Segmentation
+ owl:import
+ lower level modules. Lower level modules are independent of their higher
+ level modules and logically consistent on their own.
+
+
SOSA as the core, does not + import any other ontologies, so it is 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. + Two horizontal modules that are dependent on the SOSA and SSN ontologies are + presented in this specification, +
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.
SOSA as the core, does not - import any other ontologies, so it is 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. - Two horizontal modules that are dependent on the SOSA and SSN ontologies are - presented in this specification, -
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 the RDF implementation of the Semantic Sensor Network Ontology as SOSA.
- -- The namespace for the core terms is http://www.w3.org/ns/sosa/. - -
-- - The suggested prefix for the SOSA namespace is sosa. -
- -
- The SOSA and SSN Ontologies are distributed in several graphs, each packaged as an RDF file.
- Within each graph, where further information (axioms and annotations) is added to an existing term, rdfs:isDefinedBy
indicates the graph where the term was originally defined.
-
- The SOSA graph contains the basic definitions of the core terms with minimal axiomatization - only rdf:type
and owl:inverseOf
- together with key annotations rdfs:label
, skos:definition
, schema:domainIncludes
, schema:rangeIncludes
, plus other annotations as required.
-
- The SOSA graph is available at http://www.w3.org/ns/sosa/. -
-
- The SSN graph contains the full axiomatization of the core terms, importing SOSA and using rdfs:subClassOf
, rdfs:subPropertyOf
, owl:Restriction
with the various associated RDFS and OWL structures.
-
- The SSN graph is available at http://www.w3.org/ns/ssn/. -
-- The SSN-System graph imports SOSA and SSN and contains additional definitions associated with the composition and deployment of systems. -
-- The SSN-System graph is available at http://www.w3.org/ns/ssn-system/. -
-- The Sample-Relations graph imports SOSA and contains additional definitions associated with relationships between samples. -
-- The Sample-Relations graph is available at http://www.w3.org/ns/sosa/sampling/. -
-- The SOSA-OMS graph describes the alignment of SOSA to ISO 19156:2023 [[OMS]] using annotations to link SOSA terms to specific requirements in [[OMS]]. SOSA-OMS imports SOSA and declares additional terms required for OMS. This graph is the canonical RDF implementation of OMS. -
-- The SOSA-OMS graph is available at http://www.w3.org/ns/sosa-oms/. -
-- The SSN-OMS graph describes the alignment of SSN to ISO 19156:2023 [[OMS]] with RDFS/OWL axiomatization. This graph imports SSN and SOSA-OMS. This graph is the canonical OWL implementation of OMS. -
-- The SSN-OMS graph is available at http://www.w3.org/ns/ssn-oms/. -
-
+ The SOSA and SSN Ontologies are distributed in several graphs, each packaged as an RDF file.
+ Within each graph, where further information (axioms and annotations) is added to an existing term,
+ rdfs:isDefinedBy
indicates the graph where the term was originally defined.
+
+ The SOSA graph contains the basic definitions of the core terms with minimal axiomatization - only
+ rdf:type
and owl:inverseOf
- together with key annotations rdfs:label
,
+ skos:definition
, schema:domainIncludes
, schema:rangeIncludes
, plus
+ other annotations as required.
+
+ The SOSA graph is available at http://www.w3.org/ns/sosa/. +
+
+ The SSN graph contains the full axiomatization of the core terms, importing SOSA and using
+ rdfs:subClassOf
, rdfs:subPropertyOf
, owl:Restriction
with the various
+ associated RDFS and OWL structures.
+
+ The SSN graph is available at http://www.w3.org/ns/ssn/. +
++ The SSN-System graph imports SOSA and SSN and contains additional definitions associated with the composition + and deployment of systems. +
++ The SSN-System graph is available at http://www.w3.org/ns/ssn-system/. +
++ The Sample-Relations graph imports SOSA and contains additional definitions associated with relationships + between samples. +
++ The Sample-Relations graph is available at http://www.w3.org/ns/sosa/sampling/. +
++ The SOSA-OMS graph describes the alignment of SOSA to ISO 19156:2023 [[OMS]] using annotations to link SOSA + terms to specific requirements in [[OMS]]. SOSA-OMS imports SOSA and declares additional terms required for OMS. + This graph is the canonical RDF implementation of OMS. +
++ The SOSA-OMS graph is available at http://www.w3.org/ns/sosa-oms/. +
++ The SSN-OMS graph describes the alignment of SSN to ISO 19156:2023 [[OMS]] with RDFS/OWL axiomatization. This + graph imports SSN and SOSA-OMS. This graph is the canonical OWL implementation of OMS. +
++ The SSN-OMS graph is available at http://www.w3.org/ns/ssn-oms/. +
+Classes: - sosa:ActuatableProperty - , sosa:Actuation - , sosa:Actuator - , sosa:Deployment - , sosa:FeatureOfInterest - , sosa:Input - , sosa:ObservableProperty - , sosa:Observation - , sosa:Output - , sosa:Platform - , sosa:Property - , sosa:Procedure - , sosa:Result - , sosa:Sample - , sosa:Sampler - , sosa:Sampling - , sosa:Sensor - , sosa:Stimulus - , sosa:System -
- -Object Properties: - sosa:actsOnProperty - , sosa:madeByActuator - , sosa:deployedOnPlatform - , sosa:deployedSystem - , sosa:detects - , sosa:forProperty - , sosa:hasDeployment - , sosa:hasFeatureOfInterest - , sosa:hasInput - , sosa:hasOutput - , sosa:hasProperty - , sosa:hasResult - - , sosa:hasSample - , sosa:hasSubSystem - , sosa:hosts - , sosa:implementedBy - , sosa:implements - , sosa:inDeployment - , sosa:isActedOnBy - , sosa:isFeatureOfInterestOf - , sosa:isHostedBy - , sosa:isObservedBy - , sosa:isPropertyOf - , sosa:isProxyFor - , sosa:isResultOf - , sosa:isSampleOf - - , sosa:madeActuation - , sosa:madeBySampler - , sosa:madeBySensor - , sosa:madeObservation - , sosa:madeSampling - , sosa:observedProperty - , sosa:observes - , sosa:phenomenonTime - , sosa:usedProcedure - , sosa:wasOriginatedBy -
- -Datatype Properties: - sosa:hasSimpleResult - , sosa:resultTime -
+Classes: + sosa:ActuatableProperty + , sosa:Actuation + , sosa:Actuator + , sosa:Deployment + , sosa:FeatureOfInterest + , sosa:Input + , sosa:ObservableProperty + , sosa:Observation + , sosa:Output + , sosa:Platform + , sosa:Property + , sosa:Procedure + , sosa:Result + , sosa:Sample + , sosa:Sampler + , sosa:Sampling + , sosa:Sensor + , sosa:Stimulus + , sosa:System +
+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. -
-Object Properties: + sosa:actsOnProperty + , sosa:madeByActuator + , sosa:deployedOnPlatform + , sosa:deployedSystem + , sosa:detects + , sosa:forProperty + , sosa:hasDeployment + , sosa:hasFeatureOfInterest + , sosa:hasInput + , sosa:hasOutput + , sosa:hasProperty + , sosa:hasResult + + , sosa:hasSample + , sosa:hasSubSystem + , sosa:hosts + , sosa:implementedBy + , sosa:implements + , sosa:inDeployment + , sosa:isActedOnBy + , sosa:isFeatureOfInterestOf + , sosa:isHostedBy + , sosa:isObservedBy + , sosa:isPropertyOf + , sosa:isProxyFor + , sosa:isResultOf + , sosa:isSampleOf + + , sosa:madeActuation + , sosa:madeBySampler + , sosa:madeBySensor + , sosa:madeObservation + , sosa:madeSampling + , sosa:observedProperty + , sosa:observes + , sosa:phenomenonTime + , sosa:usedProcedure + , sosa: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. +
+The following figure provides an overview of the core classes - and properties that are specifically related to modeling Observations. + and properties that are specifically related to modeling Observations. SOSA axioms are shown in green, while SSN-only axioms are shown in blue.
IRI: http://www.w3.org/ns/sosa/Sensor
+a OWL Class
-IRI: http://www.w3.org/ns/sosa/detects
-an 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/sosa/ - | -
---|
Procedure
. 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 | ++ sosa:System + | +
Restrictions | +
+
+
+ sosa:implements
+ MIN 1
+ + + + sosa:observes + ONLY sosa:ObservableProperty + + + + sosa:detects + ONLY sosa:Stimulus + + + + sosa:madeObservation + ONLY sosa:Observation + |
+
The following figure provides an overview of the core classes - and properties that are specifically related to modeling Actuations. - SOSA axioms are shown in green, while SSN-only axioms are shown in blue. -
- - - -IRI: http://www.w3.org/ns/sosa/observes
+an OWL Object Property
-The following example illustrate how the terms related to Actuations can be used:
-Sensor
+ 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 | ++ sosa:forProperty + | +
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 | -- sosa:Property - | -
Restriction | -- - - sosa:isActedOnBy - ONLY sosa:Actuation - | -
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
IRI: http://www.w3.org/ns/sosa/isObservedBy
+an OWL Object Property
-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. |
-
---|---|
Sub class of | -- sosa:ProcedureExecution - | -
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 - |
-
ObservableProperty
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/actsOnProperty
-an 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 | -
The following examples illustrate how the terms related to Samplings can be used:
+The following example illustrate how the terms related to Actuations 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 + sosa:ActuatableProperty, + sosa:Actuation, + sosa:actsOnProperty, + sosa:isActedOnBy, + sosa:Actuator, + sosa:madeActuation, + sosa:madeByActuator
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 - - - - sosa:hasOriginalSample - ONLY sosa:Sample - - - - sosa:hasSampledFeature - ONLY sosa:FeatureOfInterest - - - - sosa:isResultOfMadeBySampler - ONLY sosa:Sampler - - - - sosa:isResultOfUsedProcedure - ONLY sosa:Procedure - - |
-
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
IRI: http://www.w3.org/ns/sosa/hasSample
-an 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/ActuatableProperty
+a OWL Class
-IRI: http://www.w3.org/ns/sosa/isSampleOf
-an OWL Object Property
- - is sample of - - Relation from aSample
to the FeatureOfInterest
that it is intended to be representative of. Domain Includes | -sosa:Sample, sosa:SampleCollection | -
---|---|
Range Includes | -sosa:FeatureOfInterest | -
Inverse property of | -- sosa:hasSample | -
is Functional | -
FeatureOfInterest
. 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 | ++ sosa:Property + | +
Restriction | ++ + + sosa:isActedOnBy + ONLY sosa:Actuation + | +
is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
IRI: http://www.w3.org/ns/sosa/hasOriginalSample
-an OWL Object Property
-Term added in 2024 update.
+IRI: http://www.w3.org/ns/sosa/Actuation
+a OWL Class
- has original sample - - Relation from aSample
or SampleCollection
to the original Sample
collected from the ultimate feature of interest. Actuation
carries
+ out an (Actuation) Procedure
to change the state of the world
+ using an Actuator
. Domain Includes | -sosa:Sample, sosa:SampleCollection | -||
---|---|---|---|
Range Includes | -sosa:Sample | +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. |
IRI: http://www.w3.org/ns/sosa/hasSampledFeature
-an OWL Object Property
- -Term added in 2024 update.
- - has ultimate sampled feature - - Relation from aSample
or SampleCollection
to the ultimate FeatureOfInterest
that it is intended to be representative of - i.e. the end of a chain of isSampleOf relations. Domain Includes | -sosa:Sample, sosa:SampleCollection | -
---|---|
Range Includes | -sosa:FeatureOfInterest | -
IRI: http://www.w3.org/ns/sosa/isResultOfMadeBySampler
-an OWL Object Property
- -Term added in 2024 update.
- - is a result of made by sampler - - Relation from aSample
or SampleCollection
to the Sampler
(sampling device or entity) that made it. Domain Includes | -sosa:Sample, sosa:SampleCollection | -
---|---|
Range Includes | -sosa:Sampler | -
Sub property of Chain | -- - sosa:isResultOf o - - sosa:madeBySampler - - | -
IRI: http://www.w3.org/ns/sosa/isResultOfUsedProcedure
-an OWL Object Property
- -Term added in 2024 update.
- - is a result of used procedure - - Relation from aSample
or SampleCollection
to the Procedure
(plan) used to make it. Domain Includes | -sosa:Sample, sosa:SampleCollection | -
---|---|
Range Includes | -sosa:Procedure | -
Sub property of Chain | -- - sosa:isResultOf o - - sosa:usedProcedure - - | -
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. - |
-
---|---|
Sub class of | -- sosa:ProcedureExecution - | -
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 | -- sosa:System - | -
Restrictions | -
-
-
- sosa:implements
- MIN 1
- - - - sosa:madeSampling - ONLY sosa:Sampling - |
-
IRI: http://www.w3.org/ns/sosa/madeSampling
-an 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
-an 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, sosa:SampleCollection | -
---|---|
Range Includes | -sosa:Sampler | -
Inverse property of | -- sosa:madeSampling | -
The following figure provides an overview of the core classes - and properties that are specifically 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:hasUltimateFeatureOfInterest, - sosa:isFeatureOfInterestOf, - sosa:Property, - sosa:hasProperty, - sosa:isPropertyOf, - sosa: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 | -
-
- sosa:hasProperty
- ONLY sosa:Property
- - - sosa: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
-an 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:ObservationCollection, sosa:Actuation, sosa:Sampling | -
Range Includes | -sosa:FeatureOfInterest, sosa:Sample | -
Inverse property of | -- sosa:isFeatureOfInterestOf | -
IRI: http://www.w3.org/ns/sosa/hasUltimateFeatureOfInterest
+IRI: http://www.w3.org/ns/sosa/actsOnProperty
an OWL Object Property
-Term added in 2024 update.
- - has ultimate feature of interest - - Link to the ultimate feature of interest of an observation or act of sampling. This is useful when the proximate feature of interest is a sample of the ultimate feature of interest, directly or transitively. - A relation between anObservation
and the ultimate entity whose quality was observed, or between an Actuation
and the ultimate entity whose property was modified, or between an act of Sampling
and the ultimate entity that was sampled.
+ acts on property -
+ Relation between an Actuation
and the property of a FeatureOfInterest
it is acting upon. Note | -This is useful when the proximate feature of interest is a sample of the ultimate feature of interest, directly or transitively. | +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:Observation, sosa:Actuation, sosa:Sampling | +sosa:Actuation | |
Range Includes | -sosa:FeatureOfInterest, sosa:Sample | +sosa:ActuatableProperty | +|
Inverse property of | ++ sosa:isActedOnBy + |
IRI: http://www.w3.org/ns/sosa/isFeatureOfInterestOf
-an 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/sosa/Property
-a OWL Class
- Property - - An identifiable quality of a
FeatureOfInterest that can be observed or acted upon. A property can apply to different features of interest.
+
+ IRI: http://www.w3.org/ns/sosa/isActedOnBy
+an OWL Object Property
+ + is acted on by - + Relation between anActuatableProperty
of a FeatureOfInterest
and an Actuation
changing its state. Example | -Cars (a feature type) all have a characteristic colour, where "colour" is a property. | +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. |
|
---|---|---|---|
Note | -Concepts from existing code lists, vocabularies, and taxonomies, may be used as instances of Property . |
+ Domain Includes | +sosa:ActuatableProperty |
is Defined By | +Range Includes | +sosa:Actuation | +|
Inverse property of | - http://www.w3.org/ns/sosa/ + sosa:actsOnProperty |
IRI: http://www.w3.org/ns/sosa/PropertyOfInterest
-a OWL Class
- Property Of Interest - - An identifiable quality of aFeatureOfInterest
that can be observed or acted upon. A property of interest is specific to a FeatureOfInterest
. It is inherent to and cannot exist without that feature of interest.
+
+ 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 | -Abby's car has the colour red, where "colour red" is a property of interest of the car. | -|
---|---|---|
Note | -Properties of interest need not always be explicitly identified. It depends on the use case. | +A window actuator for automatic window control, i.e., opening or + closing the window. |
Restrictions: | +||
Sub class of |
-
-
- sosa:isPropertyOf
- ONLY sosa:FeatureOfInterest
- - - - sosa:isPropertyOf - EXACTLY 1 + sosa:System |
|
is Defined By | +||
Restrictions |
- http://www.w3.org/ns/sosa/
+
+
+ sosa:implements
+ MIN 1
+ + + + sosa:forProperty + ONLY sosa:ActuatableProperty + + + + sosa:madeActuation + ONLY sosa:Actuation |
IRI: http://www.w3.org/ns/sosa/hasProperty
-an OWL Object Property
- - has property - - Relation between an entity and aProperty
of that entity.
- Inverse property of | -- sosa:isPropertyOf - | -
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
IRI: http://www.w3.org/ns/sosa/isPropertyOf
-an OWL Object Property
- is property of - - Relation between aProperty
and the entity it belongs to.
- Inverse property of | -- sosa:hasProperty - | -
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
IRI: http://www.w3.org/ns/sosa/forProperty
-an 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/sosa/ - | -
The following figure provides an overview of the core classes - and properties that are specifically 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:
-- sosa:Result, - sosa:hasResult, - sosa:isResultOf, - sosa:hasSimpleResult, - sosa:resultTime -
-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
-an 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:ObservationCollection, sosa:Sampling | -
---|---|
Range Includes | -sosa:Result, sosa:Sample | -
Inverse property of | -- sosa:isResultOf | -
IRI: http://www.w3.org/ns/sosa/isResultOf
-an 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:ObservationCollection, 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:ObservationCollection, sosa:Sampling | -
---|---|
Range | -xsd:dateTime | -
The following figure provides an overview of the core classes - and properties that are specifically 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:ProcedureExecution, - sosa:usedProcedure, - sosa:implements, - sosa:implementedBy, - sosa:hasInput, - sosa:hasOutput, - sosa:Input, - sosa: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 | -
-
-
- sosa:hasInput
- ONLY sosa:Input
- - - - sosa:hasOutput - ONLY sosa:Output - - - - sosa:implementedBy - ONLY sosa:System - |
-
IRI: http://www.w3.org/ns/sosa/usedProcedure
-an 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:ObservationCollection, sosa:Sampling, sosa:SampleCollection | -
---|---|
Range Includes | -sosa:Procedure | -
Sub property of Chain | -
-
- sosa:madeBySensor o
-
- sosa:implements
-
- - - sosa:madeByActuator o - - sosa:implements - - - - sosa:madeBySampler o - - sosa:implements - - |
-
IRI: http://www.w3.org/ns/sosa/implements
-an 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 | -- sosa:implementedBy - | -
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
IRI: http://www.w3.org/ns/sosa/implementedBy
-an 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 | -- sosa:implements - | -
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
IRI: http://www.w3.org/ns/sosa/hasInput
-an OWL Object Property
+IRI: http://www.w3.org/ns/sosa/madeActuation
+an OWL Object Property
- has Input - - Relation between aProcedure
and an Input
to it.
- is Defined By | -- http://www.w3.org/ns/sosa/ - | -
---|
Actuator
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/Input
-a OWL Class
- - Input - - Any information that is provided to aProcedure
for its use.
- Restrictions | -
-
-
-
- inverse Of sosa:hasInput
- ONLY sosa:Procedure
- - - - - inverse Of sosa:hasInput - MIN 1 - |
-
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
IRI: http://www.w3.org/ns/sosa/hasOutput
-an OWL Object Property
- - has Output - - Relation between aProcedure
and an Output
of it.
- is Defined By | -- http://www.w3.org/ns/sosa/ - | -
---|
IRI: http://www.w3.org/ns/sosa/Output
-a OWL Class
- - Output - - Any information that is reported from aProcedure
.
- Restrictions | -
-
-
-
- inverse Of sosa:hasOutput
- ONLY sosa:Procedure
- - - - - inverse Of sosa:hasOutput - MIN 1 - |
-
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
IRI: http://www.w3.org/ns/sosa/ProcedureExecution
-a OWL Class
+IRI: http://www.w3.org/ns/sosa/madeByActuator
+an OWL Object Property
- Procedure Execution - - Act of carrying out aProcedure
. This class generalizes the Observation
, Actuation
, and Sampling
classes. Actuation
to the Actuator
+ that made that Actuation
.
+ is Defined By | +Domain Includes | +sosa:Actuation | +
---|---|---|
Range Includes | +sosa:Actuator | +|
Inverse property of | - http://www.w3.org/ns/sosa/ + sosa:madeActuation |
The following figure provides an overview of the core classes - and properties that are specifically 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, - sosa:System, - sosa:hasSubSystem, - sosa:Deployment, - sosa:deployedSystem, - sosa:hasDeployment, - sosa:deployedOnPlatform, - sosa:inDeployment -
- +The following figure provides an overview of the core classes + and properties that are specifically related to modeling Samplings. + SOSA axioms are shown in green, while SSN-only axioms are shown in blue. +
+ -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 sosa:System
- - - - sosa:inDeployment - ONLY sosa:Deployment - |
-
IRI: http://www.w3.org/ns/sosa/hosts
-an 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 | -- - sosa:inDeployment o - - sosa:deployedSystem - - | -
IRI: http://www.w3.org/ns/sosa/isHostedBy
-an 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/sosa/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
- - - - sosa:implements - ONLY sosa:Procedure - - - - sosa:hasSubSystem - ONLY sosa:System - - - - inverse Of sosa:hasSubSystem - ONLY sosa:System - - - - sosa:hasDeployment - ONLY sosa:Deployment - |
-
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
IRI: http://www.w3.org/ns/sosa/hasSubSystem
-an OWL Object Property
- - has subsystem - - Relation between aSystem
and its component parts.
- is Defined By | -- http://www.w3.org/ns/sosa/ - | -
---|
IRI: http://www.w3.org/ns/sosa/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 | -
-
-
- sosa:deployedSystem
- ONLY sosa:System
- - - - sosa:deployedOnPlatform - ONLY sosa:Platform - - - - sosa:forProperty - ONLY sosa:Property - |
-
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
IRI: http://www.w3.org/ns/sosa/deployedSystem
-an OWL Object Property
- - deployed system - - Relation between aDeployment
and a deployed System
.
- Inverse property of | -- sosa:hasDeployment - | -
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
IRI: http://www.w3.org/ns/sosa/hasDeployment
-an OWL Object Property
- - has deployment - - Relation between aSystem
and a Deployment
, recording that the System
is deployed in that Deployment
.
- Inverse property of | -- sosa:deployedSystem - | -
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
IRI: http://www.w3.org/ns/sosa/deployedOnPlatform
-an OWL Object Property
- - deployed on platform - - Relation between aDeployment
and the Platform
on which the Systems are deployed. Inverse property of | -- sosa:inDeployment - | -
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/ - | -
The following examples illustrate how the terms related to Samplings can be used:
+Collections added in the 2024 Update
-Observations may be packaged in collections, for management and analysis. - A summary of the range of values for properties of the member observations may be recorded as properties of the collection - for example, the set of features of interest for a suite of observations.
-- Collections of observations that are useful for analysis will typically be homogeneous with respect to one or more observation properties - for example, of the same observed-property on the same feature of interest at a series of different times. - Shared properties might be conveniently recorded as properties of the collection as a whole, and these properties can then be omitted on the descriptions of the individual member observations. -
-Similarly, samples are often grouped in collections, for example a set of samples of the same feature or entity.
-The results of collections of observations are often packaged in a 'data cube' whose axes define the range of properties of the set of observations.
-Two classes representing collections of Observations or of Samples are provided: -
The following figure provides an overview of the core classes - and properties that are specifically related to describing collections of observations or of samples. -
-The following examples illustrate how the terms related to SCollections can be used:
- -This section introduces the following classes and properties:
- sosa:ObservationCollection, - sosa:SampleCollection, - sosa:hasMember, + sosa:Sample, + sosa:hasSample, + sosa:isSampleOf, + sosa:Sampling, + sosa:Sampler, + sosa:madeSampling, + sosa:madeBySampler
-IRI: http://www.w3.org/ns/sosa/ObservationCollection
-a OWL Class
- Observation Collection - - AObservationCollection
is a collection of one or more Observations
or ObservationCollections
, i.e. collections may be nested.
- Observation
properties may appear in an ObservationCollection
:
- hasFeatureOfInterest
,
- hasUltimateFeatureOfInterest
,
- usedProcedure
,
- madeBySensor
,
- madeOnPlatform
,
- observedProperty
,
- phenomenonTime
,
- resultTime
,
- validTime
,
- hasResult
,
- hasSimpleResult
,
- observationType
,
- resultQuality
.
- If they are present, the values of these properties summarize the values of the matching properties of the member observations, where membership is either direct or transitive through one or more member observation collections.
- ObservationCollection
omits a property, a member Observation
(direct or transitive) MAY have any value for that property.ObservationCollection
has a single value for a property, each member Observation
(direct or transitive) MUST have that same value for that property - i.e. the collection is homogeneous in that property. That property MAY be omitted in any member Observation
or ObservationCollection
.ObservationCollection
has more than one value for a property, each member Observation
(direct or transitive) MUST have a value for that property that matches one of the values for the property in the collection.ObservationCollection
has a value for a property that is a range or interval, each member Observation
(direct or transitive) MUST have a value for that property that matches or falls within that range or interval.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 | -... TODO ... | +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 | - rdf:Bag + sosa:FeatureOfInterest, sosa:Result | |
Disjoint with | +Restrictions |
- sosa:SampleCollection
+
+
+ sosa:isResultOf
+ ONLY sosa:Sampling
+ + + + sosa:isResultOf + MIN 1 sosa:Sampling + + + + sosa:isSampleOf + ONLY sosa:FeatureOfInterest + + + + sosa:isSampleOf + MIN 1 + + + + sosa:hasOriginalSample + ONLY + sosa:Sample + + + + sosa:hasSampledFeature + ONLY sosa:FeatureOfInterest + + + + sosa:isResultOfMadeBySampler + ONLY sosa:Sampler + + + + sosa:isResultOfUsedProcedure + ONLY sosa:Procedure + |
Restrictions | +||
is Defined By | - - - sosa:hasMember - ONLY (sosa:Observation OR sosa:ObservationCollection ) + http://www.w3.org/ns/sosa/ |
IRI: http://www.w3.org/ns/sosa/SampleCollection
-a OWL Class
- Sample Collection - - ASampleCollection
is a collection of one or more Samples
or SampleCollections
, i.e. collections may be nested.
- Sample
properties may appear in a SampleCollection
:
- hasOriginalSample
,
- hasSampledFeature
,
- isSampleOf
,
- isResultOfUsedProcedure
,
- isResultOfMadeBySampler
.
- If it is present, the values of a property summarizes the values of the matching properties of the member samples, where membership is either direct or transitive through onw or more member sample collections.
- SampleCollection
omits a property, a member Sample
(direct or transitive) MAY have any value for that property.SampleCollection
has a single value for a property, each member Sample
(direct or transitive) MUST have that same value for that property - i.e. the collection is homogeneous in that property. That property MAY be omitted in any member Sample
or SampleCollection
.SampleCollection
has more than one value for a property, each member Sample
(direct or transitive) MUST have a value for that property that matches one of the values for the property in the collection.SampleCollection
has a value for a property that is a range or interval, each member Sample
(direct or transitive) MUST have a value for that property that matches or falls within that range or interval.IRI: http://www.w3.org/ns/sosa/hasSample
+an OWL Object Property
+ has sample - + Relation between aFeatureOfInterest
and the Sample
used to represent it.
+ Example | -... TODO ... | +Domain Includes | +sosa:FeatureOfInterest |
---|---|---|---|
Sub class of | -- rdf:Bag + | ||
Range Includes | +sosa:Sample | ||
Disjoint with | +|||
Inverse property of | - sosa:ObservationCollection + sosa:isSampleOf | ||
Restrictions | -- - - sosa:hasMember - ONLY (sosa:Sample OR sosa:SampleCollection ) - | +is Inverse-Functional + |
IRI: http://www.w3.org/ns/sosa/hasMember
-an OWL Object Property
- has member of collection - - Link to a member within a collection of (samples
or observations
) or (collection of samples
or collection of observations
) which may share a value for one or more of the characteristic properties.
- rules for the consistency of values of properties of collections and properties of their members are given for each collection type.
- Note that there is a single `member` property. OWL or SHACL constraints may limit the range depending on the context of different collection types.
+ IRI: http://www.w3.org/ns/sosa/isSampleOf
+an OWL Object Property
+ + is sample of - + Relation from aSample
to
+ the FeatureOfInterest
that it is intended to be
+ representative of. Example | -... TODO ... | -|
---|---|---|
Inverse property of | -- sosa:isMemberOf - | -|
Domain Includes | -sosa:ObservationCollection , sosa:SampleCollection | +sosa:Sample, sosa:SampleCollection + |
Range Includes | -sosa:Observation , sosa:ObservationCollection , sosa:Sample , sosa:SampleCollection | +sosa:FeatureOfInterest |
is Defined By | +Inverse property of | - http://www.w3.org/ns/sosa/ + sosa:hasSample |
is Functional | +
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.
- -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/sosa/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/sosa/ - | -
IRI: http://www.w3.org/ns/ssn/systems/inCondition
-an 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 | -- sosa:Property - | -
is Defined By | -- http://www.w3.org/ns/ssn/systems/ - | -
IRI: http://www.w3.org/ns/ssn/systems/hasSystemCapability
-an OWL Object Property
- - has system capability - - Relation from aSystem
to a SystemCapability
describing the capabilities of the System
under certain Conditions
.
- Sub property of | -- sosa: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 | -- sosa:Property - | -
---|---|
Restrictions | -
-
-
- sosa:forProperty
- ONLY sosa: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 sosa:System - |
-
is Defined By | -- http://www.w3.org/ns/ssn/systems/ - | -
IRI: http://www.w3.org/ns/ssn/systems/hasSystemProperty
-an OWL Object Property
- - has system property - - Relation from anSystemCapability
of a System
to a SystemProperty
describing the capabilities of the System
.
- Sub property of | -- sosa: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 | -- sosa: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
-an OWL Object Property
- - has operating range - - Relation from aSystem
to an OperatingRange
describing the normal operating environment of the System
.
- Sub property of | -- sosa: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 | -- sosa: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 sosa:System - |
-
is Defined By | -- http://www.w3.org/ns/ssn/systems/ - | -
IRI: http://www.w3.org/ns/ssn/systems/hasOperatingProperty
-an 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 | -- sosa: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 | -- sosa: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
-an OWL Object Property
- - has survival range - - Relation from aSystem
to a SurvivalRange
.
- Sub property of | -- sosa: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 | -- sosa: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 sosa:System - |
-
is Defined By | -- http://www.w3.org/ns/ssn/systems/ - | -
IRI: http://www.w3.org/ns/ssn/systems/hasSurvivalProperty
-an 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 | -- sosa: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 | -- sosa: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
-an 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 | -- sosa:hasProperty - | -
---|---|
is Defined By | -- http://www.w3.org/ns/ssn/systems/ - | -
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/hasOriginalSample
+an OWL Object Property
-IRI: http://www.w3.org/ns/sosa/sampling/RelationshipNature
-a OWL Class
+Term added in 2024 update.
- 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 + | Domain Includes | +sosa:Sample, sosa:SampleCollection |
---|---|---|---|
is Defined By | -- http://www.w3.org/ns/sosa/sampling/ + | Range Includes | +sosa:Sample |
IRI: http://www.w3.org/ns/sosa/hasSampledFeature
+an OWL Object Property
-IRI: http://www.w3.org/ns/sosa/sampling/SampleRelationship
-a OWL Class
+Term added in 2024 update.
- Sample relationship - - Members of this class represent a relationship between aSample
and another.
- is Defined By | -- http://www.w3.org/ns/sosa/sampling/ + | Domain Includes | +sosa:Sample, sosa:SampleCollection |
---|
IRI: http://www.w3.org/ns/sosa/isResultOfMadeBySampler
+an OWL Object Property
-IRI: http://www.w3.org/ns/sosa/sampling/hasSampleRelationship
-an OWL Object Property
+Term added in 2024 update.
- has sample relationship - - Links a sample to aSample Relationship
(which links to a related Sample
).
- Domain Includes | -sosa:Sample | +sosa:Sample, sosa:SampleCollection + |
---|---|---|
Range Includes | -sampling:SampleRelationship | +sosa:Sampler |
is Defined By | +||
Sub property of Chain | - http://www.w3.org/ns/sosa/sampling/ + + sosa:isResultOf o + + sosa:madeBySampler + |
IRI: http://www.w3.org/ns/sosa/sampling/natureOfRelationship
-an OWL Object Property
+IRI: http://www.w3.org/ns/sosa/isResultOfUsedProcedure
+an OWL Object Property
- nature of (sample) relationship - - Links aSample Relationship
to an indication of the nature of the relationship.
- Domain Includes | -sampling:SampleRelationship | +sosa:Sample, sosa:SampleCollection + |
---|---|---|
Range Includes | -sampling:SampleRelationship | +sosa:Procedure |
is Defined By | -- http://www.w3.org/ns/sosa/sampling/ - | -
IRI: http://www.w3.org/ns/sosa/Sampling
+a OWL Class
-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 introduces the alignment of SOSA and SSN to Observations, measurements and samples [[OMS]]. OMS is the latest edition of the OGC and ISO standard previously known as Observations and Measurements [[OandM]], which was a key influence and input in the development of SSN. - This module serves to provide a detailed mapping of SOSA terms to discrete requirements in [[OMS]] thus explaining how SOSA and SSN provide an RDF and OWL/RDFS implementation of OMS (repectively).
-- Note that [[OMS]] is formalized using UML, which does not provide accessible global identifiers for terms in the - structure model. - However, each UML element (class or property) satisfies a formal requirement, which are each individually - denoted - by a URI in the [[OMS]] specification. - For example, the conceptual Observation class in OMS corresponds to the requirement -
http://www.opengis.net/spec/om/3.0/req/obs-cpt/Observation/Observation-sem. - So here we use the requirement URI to denote the corresponding UML class or property. -
Within the RDF representation of the alignment, we use the predicate ogc-ms:implements
to link a
- SOSA term to the corresponding OMS class or property, defined as follows:
-
ogc-ms:implements a owl:ObjectProperty ; - rdfs:subPropertyOf dcterms:source , prov:wasDerivedFrom , doap:implements .- -
The following namespace prefixes are used in the alignment of SOSA - and SSN to OMS
-Prefix | -Namespace | -
---|---|
sosa: | -http://www.w3.org/ns/sosa/ - | -
sosa-oms: | -http://www.w3.org/ns/sosa/oms/ - | -
ogc-ms: | -http://www.opengis.net/def/ont/modspec/ - | -
obs-cpt: | -http://www.opengis.net/spec/om/3.0/req/obs-cpt/ - | -
obs-core: | -http://www.opengis.net/spec/om/3.0/req/obs-core/ - | -
sam-cpt: | -http://www.opengis.net/spec/om/3.0/req/sam-cpt/ - | -
sam-basic: | -http://www.opengis.net/spec/om/3.0/req/sam-basic/ - | -
- A number of terms in OMS do not have matches in the SSN Ontology. -
-This section introduces the following classes and properties:
-- sosa-oms:SpatialSample - , sosa-oms:MaterialSample - , sosa-oms:StatisticalSample - , sosa-oms:ObservingProcedure - , sosa-oms:ActuationProcedure - , sosa-oms:SamplingProcedure - , sosa-oms:PreparationProcedure - , sosa-oms:PreparationStep - , sosa-oms:hasPreparationStep - , sosa-oms:madeOnPlatform - , sosa-oms:metadata - , sosa-oms:observationType - , sosa-oms:preparedSample - , sosa-oms:processingDetails - , sosa-oms:relatedObservation - , sosa-oms:relatedSampling - , sosa-oms:resultQuality - , sosa-oms:samplePreparationStep - , sosa-oms:validTime -
-IRI: http://www.w3.org/ns/sosa/oms/SpatialSample
-a OWL Class
- - Spatial Sample - - A SpatialSample is a geospatial Sample. When observations are made to estimate properties of a geospatial feature, in particular where the value of a property varies within the scope of the feature, a SpatialSample is used. -Sub class of | -- sosa:Sample - | -
---|
Examples | +Example |
- borehole
- , interval
- , flightline
- , lidar cloud
- , map horizon
- , microscope slide
- , mine level
- , mine
- , observation well
- , profile
- , quadrat
- , scene
- , section
- , spot
- , station
- , swath
- , trajectory
- , traverse
+ 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. |
---|---|---|
Note | +||
Sub class of | - Depending on accessibility and on the nature of the expected property variation, the SpatialSample may be extensive in one, two or three spatial dimensions. + sosa:ProcedureExecution | |
is Defined By | +||
Restrictions |
- http://www.w3.org/ns/sosa/oms/
+
+
+ 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/oms/MaterialSample
-a OWL Class
- Material Sample - - A MaterialSample is a physical, tangible Sample. -Sub class of | -- sosa:Sample - | -
---|
Examples | -- A piece of rock - , a blood sample - , a water sample - | +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. |
---|---|---|---|
Note | +|||
Sub class of |
- MaterialSamples that are curated and preserved are sometimes known as 'specimens'.
- - MaterialSamples may be destroyed in connexion with the observation act or a subsequent preparation step. + sosa:System |
||
is Defined By | +|||
Restrictions |
- http://www.w3.org/ns/sosa/oms/
+
+
+ sosa:implements
+ MIN 1
+ + + + sosa:madeSampling + ONLY sosa:Sampling |
IRI: http://www.w3.org/ns/sosa/oms/StatisticalSample
-a OWL Class
+IRI: http://www.w3.org/ns/sosa/madeSampling
+an OWL Object Property
- Statistical Sample - - A StatisticalSample is a statistical subset of a feature-of-interest, defined for the purpose of creating Observation(s). -Sub class of | -- sosa:Sample - | -
---|
Examples | -- The male or female subset of a population. - | +Domain Includes | +sosa:Sampler |
---|---|---|---|
Note | -- StatisticalSamples usually apply to populations or other sets, of which certain subset may be of specific interest. - | +Range Includes | +sosa:Sampling |
is Defined By | +Inverse property of | - http://www.w3.org/ns/sosa/oms/ + sosa:madeBySampler |
IRI: http://www.w3.org/ns/sosa/oms/ObservingProcedure
-a OWL Class
+IRI: http://www.w3.org/ns/sosa/madeBySampler
+an OWL Object Property
- Observing Procedure - - The description of steps performed in order to determine the value of an ObservableProperty by an Observer. -Sub class of | -- sosa:Procedure - | -||
---|---|---|---|
Examples | -- A workflow, protocol, plan, algorithm, or computational method specifying how to make an observation; the description of the process utilized by an observer. This could be a chemical analysis method, a protocol for measuring an object, but could also be a checklist utilized by a human observer during a biodiversity campaign. - | -
Note | -- The observing procedure cannot describe a sensor instance, but it can describe the sensor type. + | Domain Includes | +sosa:Sampling, sosa:SampleCollection |
---|---|---|---|
is Defined By | -- http://www.w3.org/ns/sosa/oms/ - | -
IRI: http://www.w3.org/ns/sosa/oms/ActuationProcedure
-a OWL Class
- - Actuation Procedure - - The description of steps performed by an Actuator to change the ActuableProperty. -Note | -- ActuationProcedure is not mentioned in OMS, which does not address Actuation. It is added here since it is trivially symmetric with the other procedure classes. - | -||
---|---|---|---|
Sub class of | -- sosa:Procedure - | +Range Includes | +sosa:Sampler |
is Defined By | +Inverse property of | - http://www.w3.org/ns/sosa/oms/ + sosa:madeSampling |
IRI: http://www.w3.org/ns/sosa/oms/SamplingProcedure
-a OWL Class
- Sampling Procedure - - The description of steps performed by a Sampler in order to extract a Sample from its sampled Feature in the frame of a Sampling. -Sub class of | -- sosa:Procedure - | -
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/oms/ - | -
The following figure provides an overview of the core classes + and properties that are specifically 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:hasUltimateFeatureOfInterest, + sosa:isFeatureOfInterestOf, + sosa:Property, + sosa:hasProperty, + sosa:isPropertyOf, + sosa:forProperty +
+ +IRI: http://www.w3.org/ns/sosa/oms/PreparationProcedure
-a OWL Class
+IRI: http://www.w3.org/ns/sosa/FeatureOfInterest
+a OWL Class
- Preparation Procedure - - The description of preparation steps performed on a Sample. -Sub class of | + Feature Of Interest - + The thing whose property is being estimated or calculated in the + course of an
---|
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 |
- sosa:Procedure
+
+ sosa:hasProperty
+ ONLY sosa:Property
+ + + sosa:hasProperty + MIN 1 + + + sosa:hasSample + ONLY sosa:Sample + |
|
is Defined By | -- http://www.w3.org/ns/sosa/oms/ + | http://www.w3.org/ns/sosa/ |
IRI: http://www.w3.org/ns/sosa/oms/PreparationStep
-a OWL Class
+IRI: http://www.w3.org/ns/sosa/hasFeatureOfInterest
+an OWL Object Property
- Preparation Step - - A PreparationStep is an individual step pertaining to a Sample PreparationProcedure. -is Defined By | +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:ObservationCollection, sosa:Actuation, sosa:Sampling | +|
Range Includes | +sosa:FeatureOfInterest, sosa:Sample | +|
Inverse property of | - http://www.w3.org/ns/sosa/oms/ + sosa:isFeatureOfInterestOf |
IRI: http://www.w3.org/ns/sosa/hasUltimateFeatureOfInterest
+an OWL Object Property
- -Term added in 2024 update.
+ has ultimate feature of interest - + Link to the ultimate feature of interest of an observation or + act of sampling. This is useful when the proximate feature of interest is a sample of the ultimate feature + of interest, directly or transitively. + A relation between anObservation
and the ultimate entity whose
+ quality was observed, or between an Actuation
and the ultimate
+ entity whose property was modified, or between an act of Sampling
+ and the ultimate entity that was sampled.
+ Note | +This is useful when the proximate feature of interest is a sample of the + ultimate feature of interest, directly or transitively. | +
---|---|
Domain Includes | +sosa:Observation, sosa:Actuation, sosa:Sampling | +
Range Includes | +sosa:FeatureOfInterest, sosa:Sample | +
IRI: http://www.w3.org/ns/sosa/oms/hasPreparationStep
-an OWL Object Property
+IRI: http://www.w3.org/ns/sosa/isFeatureOfInterestOf
+an OWL Object Property
- has preparation step - - Link to a preparation step used to prepare the sample -Domain Includes | -- sosa:Sample - | -
---|---|
Range Includes | -- sosa-oms:PreparationStep - | -
is Defined By | -- http://www.w3.org/ns/sosa/oms/ - | -
IRI: http://www.w3.org/ns/sosa/oms/madeOnPlatform
-an OWL Object Property
- - made on platform - - Relation between an Observation and the Platform the Sensor was attached to at the time the observation was made. -Domain Includes | -- sosa:Observation - , sosa:ObservationCollection - | -
---|---|
Range Includes | -- sosa:Platform - | -
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/sosa/Property
+a OWL Class
+ + Property - + An identifiable quality of a
FeatureOfInterest that can be observed or acted
+ upon. A property can apply to different features of interest.
+ Example | +Cars (a feature type) all have a characteristic + colour, where "colour" is a property. | +
---|---|
Note | +Concepts from existing code lists, vocabularies,
+ and taxonomies, may be used as instances of Property . |
+
is Defined By | - http://www.w3.org/ns/sosa/oms/ + http://www.w3.org/ns/sosa/ |
IRI: http://www.w3.org/ns/sosa/PropertyOfInterest
+a OWL Class
-IRI: http://www.w3.org/ns/sosa/oms/metadata
-an OWL Object Property
- - metadata - - Links an individual to a metadata description -Domain Includes | -- sosa:FeatureOfInterest , - sosa:ObservableProperty , - sosa:Observation , - sosa:ObservationCollection , - sosa:Sample , - sosa:SampleCollection , - sosa:Sampling , - sosa-oms:PreparationStep , - sosa:Procedure , - sosa:Sensor , - sosa:Platform , - sosa:Deployment - | -
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/oms/ - | -
IRI: http://www.w3.org/ns/sosa/oms/observationType
-an OWL Object Property
- - observation type - - Information providing further detail on the type of Observations. -Domain Includes | -- sosa:Observation - | -
---|---|
is Defined By | -- http://www.w3.org/ns/sosa/oms/ - | -
IRI: http://www.w3.org/ns/sosa/oms/preparedSample
-an OWL Object Property
- - prepared sample - - The Sample on which the PreparationProcedure is performed. -Domain Includes | -- sosa-oms:PreparationStep - | -
---|---|
Range Includes | -- sosa:Sample - | -
Example | +Abby's car has the colour red, where + "colour red" is a property of interest of the car. | +
---|---|
Note | +Properties of interest need not always be + explicitly identified. It depends on the use case. | +
Restrictions: | +
+
+
+ sosa:isPropertyOf
+ ONLY sosa:FeatureOfInterest
+ + + + sosa:isPropertyOf + EXACTLY 1 + |
+
is Defined By | - http://www.w3.org/ns/sosa/oms/ - | -
IRI: http://www.w3.org/ns/sosa/oms/processingDetails
-an OWL Object Property
- - processing details - - The PreparationProcedure used by the PreparationStep. -Domain Includes | -- sosa-oms:PreparationStep - | -
---|---|
Range Includes | -- sosa-oms:PreparationProcedure - | -
IRI: http://www.w3.org/ns/sosa/hasProperty
+an OWL Object Property
+ + has property - + Relation between an entity and aProperty
of that entity.
+ Inverse property of | ++ sosa:isPropertyOf + | +
---|---|
is Defined By | - http://www.w3.org/ns/sosa/oms/ - | -
IRI: http://www.w3.org/ns/sosa/isPropertyOf
+an OWL Object Property
+ is property of - + Relation between aProperty
and the entity it belongs to.
+ Inverse property of | ++ sosa:hasProperty + | +
---|---|
is Defined By | - http://www.w3.org/ns/sosa/oms/ - | -
IRI: http://www.w3.org/ns/sosa/forProperty
+an 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/sosa/oms/ + http://www.w3.org/ns/sosa/ |
IRI: http://www.w3.org/ns/sosa/oms/resultQuality
-an OWL Object Property
- - observation result quality - - Information pertaining to the data quality of the result. -Note | -
- This instance-specific description complements the description of the observation Procedure, which provides information concerning the quality of all observations using this procedure.
- - The quality of a result can be assessed following the procedures in the ISO 19157 series. Multiple measures can be provided. - - dqv:hasQualityMeasurement from the Data Quality Vocabulary is equivalent - |
-
---|---|
Domain Includes | -- sosa:Observation - , sosa:ObservationCollection - | -
is Defined By | -- http://www.w3.org/ns/sosa/oms/ - | -
IRI: http://www.w3.org/ns/sosa/oms/samplePreparationStep
-an OWL Object Property
- -sample preparation step - -A PreparationStep that uses the PreparationProcedure. -Domain Includes | -- sosa-oms:PreparationProcedure - | -
---|---|
Range Includes | -- sosa-oms:PreparationStep - | -
is Defined By | --http://www.w3.org/ns/sosa/oms/ - | -
IRI: http://www.w3.org/ns/sosa/oms/validTime
-an OWL Object Property
- - valid time - - The time interval during which the result is assumed to be applicable for use. -Domain Includes | -- sosa:Observation - , sosa:Sampling - | -
---|---|
Range Includes | -- time:Interval - , dcterms:PeriodOfTime - | -
is Defined By | -- http://www.w3.org/ns/sosa/oms/ - | -
The following classes used in SOSA can be aligned as follows.
-sosa:Deployment | -ogc-ms:implements | -obs-cpt:Deployment | -
sosa-oms:MaterialSample | -ogc-ms:implements | -sam-basic:MaterialSample | -
sosa:ObservableProperty | -ogc-ms:implements | -obs-cpt:ObservableProperty | -
sosa:Observation | -ogc-ms:implements | -obs-cpt:Observation | -
sosa:ObservationCollection | -ogc-ms:implements | -obs-core:AbstractObservationCollection | -
sosa-oms:ObservingProcedure | -ogc-ms:implements | -obs-cpt:ObservingProcedure | -
sosa:Platform | -ogc-ms:implements | -obs-cpt:Host | -
sosa-oms:PreparationProcedure | -ogc-ms:implements | -sam-cpt:PreparationProcedure | -
sosa-oms:PreparationStep | -ogc-ms:implements | -sam-cpt:PreparationStep | -
sosa:Procedure | -ogc-ms:implements | -obs-cpt:Procedure | -
sosa:Sample | -ogc-ms:implements | -sam-cpt:Sample | -
sosa:SampleCollection | -ogc-ms:implements | -sam-basic:SampleCollection | -
sosa:Sampler | -ogc-ms:implements | -sam-cpt:Sampler | -
sosa:Sampling | -ogc-ms:implements | -sam-cpt:Sampling | -
sosa-oms:SamplingProcedure | -ogc-ms:implements | -sam-cpt:SamplingProcedure | -
sosa:Sensor | -ogc-ms:implements | -obs-cpt:Observer | -
sosa-oms:SpatialSample | -ogc-ms:implements | -sam-basic:SpatialSample | -
sosa-oms:StatisticalSample | -ogc-ms:implements | -sam-basic:StatisticalSample | -
The following figure provides an overview of the core classes + and properties that are specifically 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:
+ +The following properties used in SOSA can be aligned as follows.
-sosa:deployedOnPlatform | -ogc-ms:implements | -obs-cpt:Deployment/host-sem | -|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sosa:deployedSystem | -ogc-ms:implements | -obs-cpt:Deployment/observer-sem | -|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sosa:hasDeployment | -ogc-ms:implements | -obs-cpt:Observer/deployment-sem | -|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sosa:hasFeatureOfInterest | -ogc-ms:implements | - obs-cpt:Observation/featureOfInterest-sem , obs-core:AbstractObservationCharacteristics/pFoI-sem , sam-cpt:Sampling/featureOfInterest-sem |
- |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sosa:hasMember | -ogc-ms:implements | - sam-basic:SampleCollection/member-sem , obs-core:AbstractObservationCollection/member-sem |
- |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sosa-oms:hasPreparationStep | -ogc-ms:implements | -sam-cpt:Sample/preparationStep-sem | -|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sosa:hasResult | -ogc-ms:implements | - obs-cpt:Observation/result-sem , sam-cpt:Sampling/sample-sem |
- |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sosa:hasSampledFeature | -ogc-ms:implements | -sam-cpt:Sample/sampledFeature-sem | -|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sosa:hasSimpleResult | -ogc-ms:implements | -obs-cpt:Observation/result-sem | -|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sosa:hasUltimateFeatureOfInterest | -ogc-ms:implements | -obs-core:AbstractObservationCharacteristics/uFoI-sem | -|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sosa:implementedBy | -ogc-ms:implements | - obs-cpt:ObservingProcedure/observer-sem , sam-cpt:SamplingProcedure/sampler-sem |
- |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sosa:implements | +
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
+an 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:ObservationCollection, sosa:Sampling | +
---|---|
Range Includes | +sosa:Result, sosa:Sample | +
Inverse property of | ++ sosa:isResultOf + | +
IRI: http://www.w3.org/ns/sosa/isResultOf
+an 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:ObservationCollection, 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:ObservationCollection, sosa:Sampling | +
---|---|
Range | +xsd:dateTime | +
The following figure provides an overview of the core classes + and properties that are specifically 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:ProcedureExecution, + sosa:usedProcedure, + sosa:implements, + sosa:implementedBy, + sosa:hasInput, + sosa:hasOutput, + sosa:Input, + sosa: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 | +
+
+
+ sosa:hasInput
+ ONLY sosa:Input
+ + + + sosa:hasOutput + ONLY sosa:Output + + + + sosa:implementedBy + ONLY sosa:System + |
+
IRI: http://www.w3.org/ns/sosa/usedProcedure
+an 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:ObservationCollection, sosa:Sampling, sosa:SampleCollection + | +
---|---|
Range Includes | +sosa:Procedure | +
Sub property of Chain | +
+
+ sosa:madeBySensor o
+
+ sosa:implements
+
+ + + sosa:madeByActuator o + + sosa:implements + + + + sosa:madeBySampler o + + sosa:implements + + |
+
IRI: http://www.w3.org/ns/sosa/implements
+an 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 | ++ sosa:implementedBy + | +
---|---|
is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
IRI: http://www.w3.org/ns/sosa/implementedBy
+an 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 | ++ sosa:implements + | +
---|---|
is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
IRI: http://www.w3.org/ns/sosa/hasInput
+an OWL Object Property
+ + has Input - + Relation between aProcedure
and an Input
to
+ it.
+ is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
---|
IRI: http://www.w3.org/ns/sosa/Input
+a OWL Class
+ + Input - + Any information that is provided to aProcedure
for its use.
+ Restrictions | +
+
+
+
+ inverse Of
+ sosa:hasInput
+ ONLY sosa:Procedure
+ + + + + inverse Of + sosa:hasInput + MIN 1 + |
+
---|---|
is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
IRI: http://www.w3.org/ns/sosa/hasOutput
+an OWL Object Property
+ + has Output - + Relation between aProcedure
and an Output
of
+ it.
+ is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
---|
IRI: http://www.w3.org/ns/sosa/Output
+a OWL Class
+ + Output - + Any information that is reported from aProcedure
.
+ Restrictions | +
+
+
+
+ inverse Of
+ sosa:hasOutput
+ ONLY sosa:Procedure
+ + + + + inverse Of + sosa:hasOutput + MIN 1 + |
+
---|---|
is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
IRI: http://www.w3.org/ns/sosa/ProcedureExecution
+a OWL Class
+ + Procedure Execution - + Act of carrying out aProcedure
. This class generalizes the Observation
, Actuation
,
+ and Sampling
classes. is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
---|
The following figure provides an overview of the core classes + and properties that are specifically 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, + sosa:System, + sosa:hasSubSystem, + sosa:Deployment, + sosa:deployedSystem, + sosa:hasDeployment, + sosa:deployedOnPlatform, + sosa: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 sosa:System
+ + + + sosa:inDeployment + ONLY sosa:Deployment + |
+
IRI: http://www.w3.org/ns/sosa/hosts
+an 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 | ++ + sosa:inDeployment o + + sosa:deployedSystem + + | +
IRI: http://www.w3.org/ns/sosa/isHostedBy
+an 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/sosa/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
+ + + + sosa:implements + ONLY + sosa:Procedure + + + + sosa:hasSubSystem + ONLY sosa:System + + + + inverse Of + sosa:hasSubSystem + ONLY sosa:System + + + + sosa:hasDeployment + ONLY + sosa:Deployment + |
+
---|---|
is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
IRI: http://www.w3.org/ns/sosa/hasSubSystem
+an OWL Object Property
+ + has subsystem - + Relation between aSystem
+ and its component parts.
+ is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
---|
IRI: http://www.w3.org/ns/sosa/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 | +
+
+
+ sosa:deployedSystem
+ ONLY sosa:System
+ + + + sosa:deployedOnPlatform + ONLY sosa:Platform + + + + sosa:forProperty + ONLY sosa:Property + |
+
is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
IRI: http://www.w3.org/ns/sosa/deployedSystem
+an OWL Object Property
+ + deployed system - + Relation between aDeployment
and a deployed System
.
+ Inverse property of | ++ sosa:hasDeployment + | +
---|---|
is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
IRI: http://www.w3.org/ns/sosa/hasDeployment
+an OWL Object Property
+ + has deployment - + Relation between aSystem
+ and a Deployment
, recording that the System
is deployed in that Deployment
.
+ Inverse property of | ++ sosa:deployedSystem + | +
---|---|
is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
IRI: http://www.w3.org/ns/sosa/deployedOnPlatform
+an OWL Object Property
+ + deployed on platform - + Relation between aDeployment
and the Platform
on which the Systems are deployed. Inverse property of | ++ sosa:inDeployment + | +
---|---|
is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
IRI: http://www.w3.org/ns/sosa/inDeployment
+an 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 | ++ sosa:deployedOnPlatform + | +
is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
Collections added in the 2024 Update
+Observations may be packaged in collections, for management and analysis. + A summary of the range of values for properties of the member observations may be recorded as properties of + the collection - for example, the set of features of interest for a suite of observations.
++ Collections of observations that are useful for analysis will typically be homogeneous with respect to one or + more observation properties - for example, of the same observed-property on the same feature of interest at a + series of different times. + Shared properties might be conveniently recorded as properties of the collection as a whole, and these + properties can then be omitted on the descriptions of the individual member observations. +
+Similarly, samples are often grouped in collections, for example a set of samples of the same feature or + entity.
+The results of collections of observations are often packaged in a 'data cube' whose axes define the range of + properties of the set of observations.
+Two classes representing collections of Observations or of Samples are provided: +
The following figure provides an overview of the core classes + and properties that are specifically related to describing collections of observations or of samples. +
+The following examples illustrate how the terms related to SCollections can be used:
+ +This section introduces the following classes and properties:
++ sosa:ObservationCollection, + sosa:SampleCollection, + sosa:hasMember, +
+ +IRI: http://www.w3.org/ns/sosa/ObservationCollection
+a OWL Class
+ + Observation Collection - + AObservationCollection
+ is a collection of one or more Observations
or ObservationCollections
, i.e. collections may be nested.
+ Observation
properties may appear in an ObservationCollection
:
+ hasFeatureOfInterest
,
+ hasUltimateFeatureOfInterest
,
+ usedProcedure
,
+ madeBySensor
,
+ madeOnPlatform
,
+ observedProperty
,
+ phenomenonTime
,
+ resultTime
,
+ validTime
,
+ hasResult
,
+ hasSimpleResult
,
+ observationType
,
+ resultQuality
.
+ If they are present, the values of these properties summarize the values of the matching properties of the
+ member observations, where membership is either direct or transitive through one or more member observation
+ collections.
+ ObservationCollection
+ omits a property, a member Observation
(direct or
+ transitive) MAY have any value for that property.ObservationCollection
has
+ a single value for a property, each member Observation
(direct or transitive) MUST have that same value
+ for that property - i.e. the collection is homogeneous in that property. That property MAY be omitted in
+ any member Observation
or ObservationCollection
.ObservationCollection
has
+ more than one value for a property, each member Observation
(direct or transitive) MUST have a value for that
+ property that matches one of the values for the property in the collection.ObservationCollection
has
+ a value for a property that is a range or interval, each member Observation
(direct or transitive) MUST have a value for that
+ property that matches or falls within that range or interval.Example | +... TODO ... | +
---|---|
Sub class of | ++ rdf:Bag + | +
Disjoint with | ++ sosa:SampleCollection + | +
Restrictions | ++ + + sosa:hasMember + ONLY (sosa:Observation OR sosa:ObservationCollection ) + | +
IRI: http://www.w3.org/ns/sosa/SampleCollection
+a OWL Class
+ + Sample Collection - + ASampleCollection
is a
+ collection of one or more Samples
or SampleCollections
, i.e. collections may be nested.
+ Sample
properties may appear in a SampleCollection
:
+ hasOriginalSample
,
+ hasSampledFeature
,
+ isSampleOf
,
+ isResultOfUsedProcedure
,
+ isResultOfMadeBySampler
.
+ If it is present, the values of a property summarizes the values of the matching properties of the member
+ samples, where membership is either direct or transitive through onw or more member sample collections.
+ SampleCollection
omits a
+ property, a member Sample
(direct or transitive) MAY have
+ any value for that property.SampleCollection
has a single
+ value for a property, each member Sample
(direct or
+ transitive) MUST have that same value for that property - i.e. the collection is homogeneous in that
+ property. That property MAY be omitted in any member Sample
or SampleCollection
.SampleCollection
has more than
+ one value for a property, each member Sample
(direct or
+ transitive) MUST have a value for that property that matches one of the values for the property in the
+ collection.SampleCollection
has a value
+ for a property that is a range or interval, each member Sample
(direct or transitive) MUST have a value for that property
+ that matches or falls within that range or interval.Example | +... TODO ... | +
---|---|
Sub class of | ++ rdf:Bag + | +
Disjoint with | ++ sosa:ObservationCollection + | +
Restrictions | ++ + + sosa:hasMember + ONLY (sosa:Sample OR sosa:SampleCollection ) + | +
IRI: http://www.w3.org/ns/sosa/hasMember
+an OWL Object Property
+ + has member of collection - + Link to a member within a collection of (samples
or observations
)
+ or (collection of samples
or collection of observations
) which may share a value for
+ one or more of the characteristic properties.
+ rules for the consistency of values of properties of collections and
+ properties of their members are given for each collection type.
+ Note that there is a single `member` property. OWL or SHACL constraints may limit
+ the range depending on the context of different collection types.
+ Example | +... TODO ... | +
---|---|
Inverse property of | ++ sosa:isMemberOf + | +
Domain Includes | +sosa:ObservationCollection , sosa:SampleCollection | +
Range Includes | +sosa:Observation , sosa:ObservationCollection , sosa:Sample , + sosa:SampleCollection | +
is Defined By | ++ http://www.w3.org/ns/sosa/ + | +
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.
+ +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/sosa/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/sosa/ + | +
IRI: http://www.w3.org/ns/ssn/systems/inCondition
+an 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 | ++ sosa:Property + | +
is Defined By | ++ http://www.w3.org/ns/ssn/systems/ + | +
IRI: http://www.w3.org/ns/ssn/systems/hasSystemCapability
+an OWL Object Property
+ + has system capability - + Relation from aSystem
to
+ a SystemCapability
describing the capabilities of the
+ System
under certain Conditions
.
+ Sub property of | ++ sosa: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 | ++ sosa:Property + | +
---|---|
Restrictions | +
+
+
+ sosa:forProperty
+ ONLY sosa: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 sosa:System + |
+
is Defined By | ++ http://www.w3.org/ns/ssn/systems/ + | +
IRI: http://www.w3.org/ns/ssn/systems/hasSystemProperty
+an OWL Object Property
+ + has system property - + Relation from anSystemCapability
of a System
to a SystemProperty
describing the capabilities of the System
.
+ Sub property of | ++ sosa: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 | ++ sosa: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
+an OWL Object Property
+ + has operating range - + Relation from aSystem
to
+ an OperatingRange
describing the normal operating
+ environment of the System
.
+ Sub property of | ++ sosa: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 | ++ sosa: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 sosa:System + |
+
is Defined By | ++ http://www.w3.org/ns/ssn/systems/ + | +
IRI: http://www.w3.org/ns/ssn/systems/hasOperatingProperty
+an 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 | ++ sosa: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 | ++ sosa: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
+an OWL Object Property
+ + has survival range - + Relation from aSystem
to
+ a SurvivalRange
.
+ Sub property of | ++ sosa: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 | ++ sosa: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 sosa:System + |
+
is Defined By | ++ http://www.w3.org/ns/ssn/systems/ + | +
IRI: http://www.w3.org/ns/ssn/systems/hasSurvivalProperty
+an 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 | ++ sosa: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 the +System
'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 | ++ sosa: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
+an 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 | ++ sosa:hasProperty + | +
---|---|
is Defined By | ++ http://www.w3.org/ns/ssn/systems/ + | +
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
+an 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
+an 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 introduces the alignment of SOSA and SSN to Observations, measurements and samples [[OMS]]. OMS is + the latest edition of the OGC and ISO standard previously known as Observations and Measurements [[OandM]], + which was a key influence and input in the development of SSN. + This module serves to provide a detailed mapping of SOSA terms to discrete requirements in [[OMS]] thus + explaining how SOSA and SSN provide an RDF and OWL/RDFS implementation of OMS (repectively).
++ Note that [[OMS]] is formalized using UML, which does not provide accessible global identifiers for terms in the + structure model. + However, each UML element (class or property) satisfies a formal requirement, which are each individually + denoted + by a URI in the [[OMS]] specification. + For example, the conceptual Observation class in OMS corresponds to the requirement +
http://www.opengis.net/spec/om/3.0/req/obs-cpt/Observation/Observation-sem. + So here we use the requirement URI to denote the corresponding UML class or property. +
Within the RDF representation of the alignment, we use the predicate ogc-ms:implements
to link a
+ SOSA term to the corresponding OMS class or property, defined as follows:
+
ogc-ms:implements a owl:ObjectProperty ; + rdfs:subPropertyOf dcterms:source , prov:wasDerivedFrom , doap:implements .+ +
The following namespace prefixes are used in the alignment of SOSA + and SSN to OMS
+Prefix | +Namespace | +
---|---|
sosa: | +http://www.w3.org/ns/sosa/ + | +
sosa-oms: | +http://www.w3.org/ns/sosa/oms/ + | +
ogc-ms: | +http://www.opengis.net/def/ont/modspec/ + | +
obs-cpt: | +http://www.opengis.net/spec/om/3.0/req/obs-cpt/ + | +
obs-core: | +http://www.opengis.net/spec/om/3.0/req/obs-core/ + | +
sam-cpt: | +http://www.opengis.net/spec/om/3.0/req/sam-cpt/ + | +
sam-basic: | +http://www.opengis.net/spec/om/3.0/req/sam-basic/ + | +
+ A number of terms in OMS do not have matches in the SSN Ontology. +
+This section introduces the following classes and properties:
++ sosa-oms:SpatialSample + , sosa-oms:MaterialSample + , sosa-oms:StatisticalSample + , sosa-oms:ObservingProcedure + , sosa-oms:ActuationProcedure + , sosa-oms:SamplingProcedure + , sosa-oms:PreparationProcedure + , sosa-oms:PreparationStep + , sosa-oms:hasPreparationStep + , sosa-oms:madeOnPlatform + , sosa-oms:metadata + , sosa-oms:observationType + , sosa-oms:preparedSample + , sosa-oms:processingDetails + , sosa-oms:relatedObservation + , sosa-oms:relatedSampling + , sosa-oms:resultQuality + , sosa-oms:samplePreparationStep + , sosa-oms:validTime +
+IRI: http://www.w3.org/ns/sosa/oms/SpatialSample
+a OWL Class
+ + Spatial Sample - + A SpatialSample is a geospatial Sample. When observations are + made to estimate properties of a geospatial feature, in particular where the value of a property varies + within the scope of the feature, a SpatialSample is used. +Sub class of | ++ sosa:Sample + | +
---|---|
Examples | ++ borehole + , interval + , flightline + , lidar cloud + , map horizon + , microscope slide + , mine level + , mine + , observation well + , profile + , quadrat + , scene + , section + , spot + , station + , swath + , trajectory + , traverse + | +
Note | ++ Depending on accessibility and on the nature of the expected property + variation, the SpatialSample may be extensive in one, two or three spatial dimensions. + | +
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/MaterialSample
+a OWL Class
+ + Material Sample - + A MaterialSample is a physical, tangible Sample. +Sub class of | ++ sosa:Sample + | +
---|---|
Examples | ++ A piece of rock + , a blood sample + , a water sample + | +
Note | +
+ MaterialSamples that are curated and preserved are sometimes known as
+ 'specimens'.
+ + MaterialSamples may be destroyed in connexion with the observation act or a + subsequent preparation step. + |
+
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/StatisticalSample
+a OWL Class
+ + Statistical Sample - + A StatisticalSample is a statistical subset of a + feature-of-interest, defined for the purpose of creating Observation(s). +Sub class of | ++ sosa:Sample + | +
---|---|
Examples | ++ The male or female subset of a population. + | +
Note | ++ StatisticalSamples usually apply to populations or other sets, of which + certain subset may be of specific interest. + | +
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/ObservingProcedure
+a OWL Class
+ + Observing Procedure - + The description of steps performed in order to determine the + value of an ObservableProperty by an Observer. +Sub class of | ++ sosa:Procedure + | +
---|---|
Examples | ++ A workflow, protocol, plan, algorithm, or computational method + specifying how to make an observation; the description of the process utilized by an observer. This + could be a chemical analysis method, a protocol for measuring an object, but could also be a + checklist utilized by a human observer during a biodiversity campaign. + | +
Note | ++ The observing procedure cannot describe a sensor instance, but it can + describe the sensor type. + | +
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/ActuationProcedure
+a OWL Class
+ + Actuation Procedure - + The description of steps performed by an Actuator to change the + ActuableProperty. +Note | ++ ActuationProcedure is not mentioned in OMS, which does not address + Actuation. It is added here since it is trivially symmetric with the other procedure classes. + | +
---|---|
Sub class of | ++ sosa:Procedure + | +
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/SamplingProcedure
+a OWL Class
+ + Sampling Procedure - + The description of steps performed by a Sampler in order to + extract a Sample from its sampled Feature in the frame of a Sampling. +Sub class of | ++ sosa:Procedure + | +
---|---|
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/PreparationProcedure
+a OWL Class
+ + Preparation Procedure - + The description of preparation steps performed on a + Sample. +Sub class of | ++ sosa:Procedure + | +
---|---|
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/PreparationStep
+a OWL Class
+ + Preparation Step - + A PreparationStep is an individual step pertaining to a Sample + PreparationProcedure. +is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
---|
IRI: http://www.w3.org/ns/sosa/oms/hasPreparationStep
+an OWL Object Property
+ + has preparation step - + Link to a preparation step used to prepare the sample +Domain Includes | ++ sosa:Sample + | +
---|---|
Range Includes | ++ sosa-oms:PreparationStep + | +
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/madeOnPlatform
+an OWL Object Property
+ + made on platform - + Relation between an Observation and the Platform the Sensor was + attached to at the time the observation was made. +Domain Includes | ++ sosa:Observation + , sosa:ObservationCollection + | +
---|---|
Range Includes | ++ sosa:Platform + | +
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/metadata
+an OWL Object Property
+ + metadata - + Links an individual to a metadata description +Domain Includes | ++ sosa:FeatureOfInterest , + sosa:ObservableProperty , + sosa:Observation , + sosa:ObservationCollection , + sosa:Sample + , + sosa:SampleCollection , + sosa:Sampling , + sosa-oms:PreparationStep , + sosa:Procedure , + sosa:Sensor + , + sosa:Platform , + sosa:Deployment + | +
---|---|
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/observationType
+an OWL Object Property
+ + observation type - + Information providing further detail on the type of + Observations. +Domain Includes | ++ sosa:Observation + | +
---|---|
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/preparedSample
+an OWL Object Property
+ + prepared sample - + The Sample on which the PreparationProcedure is + performed. +Domain Includes | ++ sosa-oms:PreparationStep + | +
---|---|
Range Includes | ++ sosa:Sample + | +
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/processingDetails
+an OWL Object Property
+ + processing details - + The PreparationProcedure used by the PreparationStep. +Domain Includes | ++ sosa-oms:PreparationStep + | +
---|---|
Range Includes | ++ sosa-oms:PreparationProcedure + | +
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/resultQuality
+an OWL Object Property
+ + observation result quality - + Information pertaining to the data quality of the result. +Note | +
+ This instance-specific description complements the description of the
+ observation Procedure, which provides information concerning the quality of all observations using
+ this procedure.
+ + The quality of a result can be assessed following the procedures in the ISO + 19157 series. Multiple measures can be provided. + + dqv:hasQualityMeasurement + from the Data Quality Vocabulary is equivalent + |
+
---|---|
Domain Includes | ++ sosa:Observation + , sosa:ObservationCollection + | +
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/samplePreparationStep
+an OWL Object Property
+ + sample preparation step - + A PreparationStep that uses the PreparationProcedure. +Domain Includes | ++ sosa-oms:PreparationProcedure + | +
---|---|
Range Includes | ++ sosa-oms:PreparationStep + | +
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
IRI: http://www.w3.org/ns/sosa/oms/validTime
+an OWL Object Property
+ + valid time - + The time interval during which the result is assumed to be + applicable for use. +Domain Includes | ++ sosa:Observation + , sosa:Sampling + | +
---|---|
Range Includes | ++ time:Interval + , dcterms:PeriodOfTime + | +
is Defined By | ++ http://www.w3.org/ns/sosa/oms/ + | +
The following classes used in SOSA can be aligned as follows.
+sosa:Deployment | +ogc-ms:implements | +obs-cpt:Deployment | +
sosa-oms:MaterialSample | +ogc-ms:implements | +sam-basic:MaterialSample | +
sosa:ObservableProperty | +ogc-ms:implements | +obs-cpt:ObservableProperty | +
sosa:Observation | +ogc-ms:implements | +obs-cpt:Observation | +
sosa:ObservationCollection | +ogc-ms:implements | +obs-core:AbstractObservationCollection | +
sosa-oms:ObservingProcedure | +ogc-ms:implements | +obs-cpt:ObservingProcedure | +
sosa:Platform | +ogc-ms:implements | +obs-cpt:Host | +
sosa-oms:PreparationProcedure | +ogc-ms:implements | +sam-cpt:PreparationProcedure | +
sosa-oms:PreparationStep | +ogc-ms:implements | +sam-cpt:PreparationStep | +
sosa:Procedure | +ogc-ms:implements | +obs-cpt:Procedure | +
sosa:Sample | +ogc-ms:implements | +sam-cpt:Sample | +
sosa:SampleCollection | +ogc-ms:implements | +sam-basic:SampleCollection | +
sosa:Sampler | +ogc-ms:implements | +sam-cpt:Sampler | +
sosa:Sampling | +ogc-ms:implements | +sam-cpt:Sampling | +
sosa-oms:SamplingProcedure | +ogc-ms:implements | +sam-cpt:SamplingProcedure | +
sosa:Sensor | +ogc-ms:implements | +obs-cpt:Observer | +
sosa-oms:SpatialSample | +ogc-ms:implements | +sam-basic:SpatialSample | +
sosa-oms:StatisticalSample | +ogc-ms:implements | +sam-basic:StatisticalSample | +
The following properties used in SOSA can be aligned as follows.
+sosa:deployedOnPlatform | +ogc-ms:implements | +obs-cpt:Deployment/host-sem | +|
sosa:deployedSystem | +ogc-ms:implements | +obs-cpt:Deployment/observer-sem | +|
sosa:hasDeployment | +ogc-ms:implements | +obs-cpt:Observer/deployment-sem | +|
sosa:hasFeatureOfInterest | +ogc-ms:implements | + obs-cpt:Observation/featureOfInterest-sem , + obs-core:AbstractObservationCharacteristics/pFoI-sem , sam-cpt:Sampling/featureOfInterest-sem + |
+ |
sosa:hasMember | +ogc-ms:implements | + sam-basic:SampleCollection/member-sem , obs-core:AbstractObservationCollection/member-sem |
+ |
sosa-oms:hasPreparationStep | +ogc-ms:implements | +sam-cpt:Sample/preparationStep-sem | +|
sosa:hasResult | +ogc-ms:implements | + obs-cpt:Observation/result-sem , sam-cpt:Sampling/sample-sem |
+ |
sosa:hasSampledFeature | +ogc-ms:implements | +sam-cpt:Sample/sampledFeature-sem | +|
sosa:hasSimpleResult | +ogc-ms:implements | +obs-cpt:Observation/result-sem | +|
sosa:hasUltimateFeatureOfInterest | +ogc-ms:implements | +obs-core:AbstractObservationCharacteristics/uFoI-sem | +|
sosa:implementedBy | +ogc-ms:implements | + obs-cpt:ObservingProcedure/observer-sem , sam-cpt:SamplingProcedure/sampler-sem |
+ |
sosa:implements | ogc-ms:implements | - obs-cpt:Observer/observingProcedure-sem , sam-cpt:Sampling/samplingProcedure-sem , sam-cpt:PreparationStep/processingDetails-sem |
+ obs-cpt:Observer/observingProcedure-sem , sam-cpt:Sampling/samplingProcedure-sem , + sam-cpt:PreparationStep/processingDetails-sem |
sosa:inDeployment | @@ -6178,7 +7650,7 @@|||
sosa:usedProcedure | ogc-ms:implements | - obs-cpt:Observation/observingProcedure-sem , sam-cpt:Sampling/samplingProcedure-sem |
+ obs-cpt:Observation/observingProcedure-sem , sam-cpt:Sampling/samplingProcedure-sem |
sosa-oms:validTime | @@ -6188,13 +7660,17 @@
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 +
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. + 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.The following namespace prefixes are used in the alignment to SOSA @@ -6217,7 +7693,8 @@
sosa:Result | -subclass of | -owl:unionOf ( dul:Region dul:Object ) | -
(not (oldsosa:Observation)) and (old-sosa:observationResult some owl:Thing) | -subclass of | -sosa:Observation | -sosa:Result | +subclass of | +owl:unionOf ( dul:Region dul:Object ) | + +
(not (oldsosa:Observation)) and (old-sosa:observationResult some owl:Thing) | +subclass of | +sosa:Observation | +
Additional alignments from SOSA/SSN to DUL properties are defined as + follows.
+sosa:hasProperty | +sub-property of | +dul:hasQuality | +
sosa:isPropertyOf | +sub-property of | +dul:isQualityOf | +
sosa:hosts | +sub-property of | +dul:isLocationOf | +
sosa:isHostedBy | +sub-property of | +dul:hasLocation | +
sosa:implementedBy | +sub-property of | +dul:describes | +
sosa: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 | +
sosa:hasSubSystem | +sub-property of | +dul:hasPart | +
sosa:deployedOnPlatform | +sub-property of | +dul:associatedWith | +
sosa:deployedSystem | +sub-property of | +dul:associatedWith | +
sosa:hasDeployment | +sub-property of | +dul:associatedWith | +
sosa:inDeployment | +sub-property of | +dul:associatedWith | +
Additional alignments from SOSA/SSN to DUL properties are defined as - follows.
-sosa:hasProperty | -sub-property of | -dul:hasQuality | -
sosa:isPropertyOf | -sub-property of | -dul:isQualityOf | -
sosa:hosts | -sub-property of | -dul:isLocationOf | -
sosa:isHostedBy | -sub-property of | -dul:hasLocation | -
sosa:implementedBy | -sub-property of | -dul:describes | -
sosa: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 | -
sosa:hasSubSystem | -sub-property of | -dul:hasPart | -
sosa:deployedOnPlatform | -sub-property of | -dul:associatedWith | -
sosa:deployedSystem | -sub-property of | -dul:associatedWith | -
sosa:hasDeployment | -sub-property of | -dul:associatedWith | -
sosa:inDeployment | -sub-property of | -dul:associatedWith | -
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/. + 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.
The following classes in SOSA and SSN are interpreted as superclasses of the corresponding ones in SSN-XG.
+The following classes in SOSA and SSN are interpreted as superclasses of the corresponding ones in SSN-XG. +
subclass of | ssn-system:Selectivity |
The more complex aligments of SSN-XG classes are expressed as combinations of axiomatic statements as follows.
- +The more complex aligments of SSN-XG classes are expressed as combinations of axiomatic statements as + follows.
+[ a owl:Restriction ; owl:onProperty oldsosa:isProducedBy ; owl:someValuesFrom oldsosa:Sensor ] | |||||||||||||||||||||||
oldsosa:ObservationValue | subclass of | sosa:Result | @@ -6705,7 +8185,7 @@subclass of | [ a owl:Restriction ; owl:onProperty dul:isRegionFor ; owl:someValuesFrom oldsosa:SensorOutput ] | |||||||||||||||||||
oldsosa:Deployment | equivalent class | @@ -6848,12 +8328,12 @@equivalent property | sosa:observedProperty | ||||||||||||||||||||
oldsosa:detects | equivalent property | sosa:detects | |||||||||||||||||||||
oldsosa:isProxyFor | equivalent property | sosa:isProxyFor | @@ -6893,7 +8373,7 @@equivalent property | sosa:hasDeployment | |||||||||||||||||||
oldsosa:inDeployment | equivalent property | sosa:inDeployment | @@ -6934,17 +8414,17 @@
oldsosa:hasValue | -sub-property of | -sosa:hasResult | -||
oldsosa:observationResult | -sub-property of | -sosa:hasResult | -||
oldsosa:hasValue | +sub-property of | +sosa:hasResult | +||
oldsosa:observationResult | +sub-property of | +sosa:hasResult | +||
oldsosa:hasMeasurementCapability | sub-property of | ssn-system:hasSystemCapability | @@ -6954,7 +8434,7 @@sub-property of | ssn-system:hasSystemProperty |
oldsosa:hasSurvivalRange | sub-property of | @@ -6978,7 +8458,7 @@property chain axiom | ( oldsosa:madeObservation oldsosa:observedProperty ) |
The primary classes from [[OBOE]] are aligned with SOSA classes as @@ -7124,257 +8606,282 @@
An RDF file containing a graph
+ An RDF file containing a graph
corresponding to this alignment is available.
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.
-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.
- -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/ - | -
The primary classes from SOSA are aligned with the PROV classes as - follows.
+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.
+ +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/ + | +
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 | -
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 | -
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 | -
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 | +
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:
+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 | -
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 ] | -
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.
+An RDF file containing a graph corresponding to this + alignment is available.
+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.
+For example, if observations are made of the atmosphere at a specific location, it might be described as a + Sample using the following pattern:
+ +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.
-For example, if observations are made of the atmosphere at a specific location, it might be described as a Sample using the following pattern:
- - -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.
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
@@ -7382,595 +8889,728 @@
Describing a plan for some actuation or observation in the future is not covered by this specification.
-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 expressing results as quantity values. - There exist external vocabularies that are specifically designed for modeling quantity values as OWL individuals, or as datatypes. - Examples include the Quantities, Units, Dimensions and Data Types Ontologies (QUDT, [[QUDT]]) the Ontology of Units of Measure (OM, [[Rijgersberg-et-al-2013]]), and the St Etienne School of Mines Custom Datatypes (CDT, [[CDT]]).
-sosa:Result
would be a qudt:QuantityValue
sosa:Result
would be a om:Measure
or om:Point
sosa:hasSimpleResult
may be structured to match cdt:ucum
which encodes the unit-of-measure using UCUM (UCUM, [[UCUM]])sosa:hasSimpleResult
may alternatively be structured such that the datatype indicates a qudt:Unit
Custom datatypes are not strictly compatible with OWL, which restricts the set of datatypes that can be used. See sec. 5.2 in [[owl2-syntax]] for more details.
- - - - -The previous version of SOSA/SSN left an ambiguity on whether an instance of sosa: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>
). This version solves the ambiguity by differentiating:
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 expressing + results as quantity values. + There exist external vocabularies that are specifically designed for modeling quantity values as OWL + individuals, or as datatypes. + Examples include the Quantities, Units, Dimensions and Data Types Ontologies (QUDT, [[QUDT]]) the Ontology of + Units of Measure (OM, [[Rijgersberg-et-al-2013]]), and the St Etienne School of Mines Custom Datatypes + (CDT, [[CDT]]).
+sosa:Result
would be a qudt:QuantityValue
sosa:Result
would be a om:Measure
or om:Point
sosa:hasSimpleResult
may be
+ structured to match cdt:ucum
which
+ encodes the unit-of-measure using UCUM (UCUM, [[UCUM]])sosa:hasSimpleResult
may alternatively be
+ structured such that the datatype indicates a qudt:Unit
Custom datatypes are not strictly compatible with OWL, which restricts the set of datatypes that + can be used. See sec. 5.2 in [[owl2-syntax]] for more details.
+ + + + +The previous version of SOSA/SSN left an ambiguity on whether an instance of sosa: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>
). This version solves the ambiguity
+ by differentiating:
+
sosa:Property
for the former casesosa:PropertyOfInterest
for the latter case.This specification does not specify whether an instance of sosa: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
- sosa:Property
and an instance of sosa: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 sosa:System
: sosa:Sensor
, sosa:Actuator
, and sosa:Sampler
.
This first example is modeling instances of sosa:System
as generic:
This second example is modeling instances of sosa:System
as specific:
This specification does not specify whether an instance of sosa: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
+ sosa:Property
and an instance of sosa: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 sosa:System
: sosa:Sensor
, sosa:Actuator
, and
+ sosa:Sampler
.
This first example is modeling instances of sosa:System
as generic:
+
This second example is modeling instances of sosa:System
as specific:
+
Results of the wide review of SOSA and SSN is summarized here.
- -An RDF file containing a graph corresponding to this example is available.
- +Results of the wide review of SOSA and SSN is summarized here.
+ + + +An RDF file containing a graph + corresponding to this example is available.
+An RDF file containing a graph corresponding to this example is available.
- + +An RDF file containing a graph corresponding to + this example is available.
+An RDF file containing a graph corresponding to this example is available.
- -An RDF file containing a graph corresponding to this example is available.
- -An RDF file containing a graph corresponding to this example is available.
- -An RDF file containing a graph corresponding to this example is available.
- -An RDF file containing a graph corresponding to this example is available.
- -An RDF file containing a graph + corresponding to this example is available.
+ +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.
- -An RDF file containing a graph + corresponding to this example is available.
+ +An RDF file containing a graph corresponding to this example is available.
- -An RDF file containing a graph + corresponding to this example is available.
+ +An RDF file containing a graph corresponding to + this example is available.
+ +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.
- -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.
- -An RDF file containing a graph + corresponding to this example is available.
+ +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.
+ +An RDF file containing a graph corresponding to + this example is available.
+ +A full change-log is available on GitHub.
-;
with a .
sosa:hosts
and sosa:hasSubSystem
in DHT Deployment exampleactsOnProperty
and isActedOnBy
in actuation diagramssosa:hasSimplResult
syntax errors in apartment 134 examplessosa:actuationMadeBy
by sosa:madeByActuator
in apartment 134 exampleoldsosa:FeatureOfInterest
is a sub-class of sosa:FeatureOfInterest
(instead of equivalent)oldsosa:hasValue
is a sub-property of sosa:hasResult
(instead of equivalent)oldsosa:observationResult
is a sub-property of sosa:hasResult
(instead of equivalent)sosa:FeatureOfInterest
is a sub-class of dul:Entity
qudt-1-1:numericalValue
by qudt-1-1:numericValue
in tree height measurement exampleThis 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.
+ +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.
+ +A full change-log is available on GitHub.
+;
with a .
sosa:hosts
and sosa:hasSubSystem
in DHT Deployment exampleactsOnProperty
and isActedOnBy
in actuation diagramssosa:hasSimplResult
syntax errors in apartment 134 examplessosa:actuationMadeBy
by sosa:madeByActuator
in apartment 134
+ exampleoldsosa:FeatureOfInterest
is a sub-class of sosa:FeatureOfInterest
(instead of
+ equivalent)oldsosa:hasValue
is a sub-property of sosa:hasResult
(instead of equivalent)
+ oldsosa:observationResult
is a sub-property of sosa:hasResult
(instead of
+ equivalent)sosa:FeatureOfInterest
is a sub-class of dul:Entity
qudt-1-1:numericalValue
by qudt-1-1:numericValue
in tree
+ height measurement example