-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #261 from w3c/251-collections-documentation
251 collections documentation
- Loading branch information
Showing
20 changed files
with
329 additions
and
148 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| <h3>Forecasts</h3> | ||
| <p>One MAY also represent forecasts as observations if the value of <code>sosa:phenomenonTime</code> is later in | ||
| time than the <code>sosa:resultTime</code>. | ||
| Given the definition of these terms, it means that: <em>The time when the Observation act was completed is | ||
| before the time that the Result of the observation applies to the FeatureOfInterest.</em></p> | ||
| <p class="note"> Other means to represent forecasts are reported, but not in the scope of this specification. | ||
| For example [[Lefrancois-et-al-2017]] derives the SSN <code>Sensing/Sensor/Observation</code> | ||
| pattern and define <code>Forecasting/Forecaster/Forecast</code> classes.</p> | ||
| <p class="note">Describing a plan for some actuation or observation in the future is not covered by this | ||
| specification.</p> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| <h3>Homogeneous collections and data-cubes</h3> | ||
|
|
||
| <p> | ||
| A homogeneous collection of observations shares a common value for one or more of the characteristic observation | ||
| properties. | ||
| For example: | ||
| </p> | ||
|
|
||
| <p>For example, <a href="#fig-observation-collection-3" class="fig-ref"></a> describes a collection of remote sensing | ||
| observations using the same sensor on different scenes, while <a href="#fig-observation-collection-4" | ||
| class="fig-ref"></a> is a series of the same scene on different days. </p> | ||
|
|
||
| <figure id="fig-observation-collection-3"> | ||
| <img alt="Collections of observations 3" src="./images/OC-instance-3.png" style="width:90%" /> | ||
| <figcaption>A set of remote sensing observations of different scenes on the same day</figcaption> | ||
| </figure> | ||
|
|
||
| <figure id="fig-observation-collection-4"> | ||
| <img alt="Collections of observations 4" src="./images/OC-instance-4.png" style="width:90%" /> | ||
| <figcaption>A series of remote sensing observations of the same scene on the different days</figcaption> | ||
| </figure> | ||
|
|
||
| <p> | ||
| Collections may be nested. | ||
| For example, an outer observation-collection might share the observed-property, procedure and sensor, and contain | ||
| inner observation-collections at different phenomenon-times, each of which contain a set of observations on | ||
| different features-of-interest (<a href="#fig-observation-collection-1" class="fig-ref"></a>). | ||
| </p> | ||
|
|
||
| <figure id="fig-observation-collection-1"> | ||
| <img alt="Nested collections of observations 1" src="./images/OC-instance-1.png" style="width:90%" /> | ||
| <figcaption>Example of a set of nested collections of four observations of the same property of two | ||
| features-of-interest at two different times.</figcaption> | ||
| </figure> | ||
|
|
||
| <p> | ||
| Observations can be factored into collections in more than one way, so more than one set of nested | ||
| observation-collections can collect the same set of atomic results. | ||
| For example, the same outer collection may contain inner collections concerning different features-of-interests, each | ||
| containing a set of observations at different phenomenon-times (<a href="#fig-observation-collection-2" | ||
| class="fig-ref"></a>). | ||
| </p> | ||
|
|
||
| <figure id="fig-observation-collection-2"> | ||
| <img alt="Nested collections of observations 2" src="./images/OC-instance-2.png" style="width:90%" /> | ||
| <figcaption>Alternative set of nested collections with the same results of the same property of two | ||
| features-of-interest at two different times.</figcaption> | ||
| </figure> | ||
|
|
||
| <p> | ||
| Effectively, the results of each observation-collection correspond to a <i>slice</i> in a data-cube which is | ||
| composed of the results of the complete set of observations. | ||
| </p> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| <h3>Location</h3> | ||
| <p>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]]. </p> | ||
| <p>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.</p> | ||
| <p>For example, if observations are made of the atmosphere at a specific location, it might be described as a | ||
| Sample using the following pattern:</p> | ||
| <pre class="example" data-include="./rdf/examples/2023ex1.ttl" data-include-format="text"></pre> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| <h3>Generic or Specific Instances of sosa:Property</h3> | ||
| <p>The previous version of SOSA/SSN left an ambiguity on whether an instance of <a | ||
| href="#SOSAProperty"><code>sosa:Property</code></a> should be generic to all features of interest (e.g., | ||
| <code>ex:Temperature</code>, | ||
| <code>ex:OnOffStatus</code>), or specific to a single feature of interest (e.g., | ||
| <code><myBodyTemperature></code>, <code><LightStatus></code>). This version solves the ambiguity by | ||
| differentiating: | ||
| </p> | ||
| <ul> | ||
| <li><a href="#SOSAProperty"><code>sosa:Property</code></a> for the former case</li> | ||
| <li><a href="#SOSAPropertyOfInterest"><code>sosa:PropertyOfInterest</code></a> for the latter case.</li> | ||
| </ul> |
Oops, something went wrong.