Merge branch 'gh-pages' into minor-edits-usage

Author: dr-shorthair

ssn/chapters/CompleteExamples.html

@@ -3,96 +3,3 @@ <h2>Extended Examples</h2>
 <p>
     A set of extended examples of instances using the SSN ontology are available in the <a href="https://github.com/w3c/sdw-sosa-ssn/blob/gh-pages/ssn/rdf/examples">examples folder</a>.
 </p>
-
-
-<!---
-
-<section id="tree-height">
-    <h3>Tree height measurement</h3>
-    <p>An RDF file containing a <a href="https://github.com/w3c/sdw-sosa-ssn/blob/gh-pages/sdw-sosa-ssn/ssn/rdf/examples/tree-height.ttl">graph
-            corresponding to this example is available</a>. </p>
-    <pre class="example turtle" data-include="./rdf/examples/tree-height.ttl" data-include-format="text"></pre>
-</section>
-
-<section id="sunspots">
-    <h3>Number of sunspots</h3>
-    <p>An RDF file containing a <a href="https://github.com/w3c/sdw/blob/gh-pages/sdw-sosa-ssn/ssn/rdf/examples/sunspots.ttl">graph
-            corresponding to
-            this example is available</a>. </p>
-    <pre class="example turtle" data-include="./rdf/examples/sunspots.ttl" data-include-format="text"></pre>
-</section>
-
-<section id="seismograph">
-    <h3>Seismograph measuring ground displacement speed</h3>
-    <p>An RDF file containing a <a href="https://github.com/w3c/sdw/blob/gh-pages/sdw-sosa-ssn/ssn/rdf/examples/seismograph.ttl">graph
-            corresponding to this example is available</a>. </p>
-    <pre class="example turtle" data-include="./rdf/examples/seismograph.ttl" data-include-format="text"></pre>
-</section>
-
-<section id="iphone_barometer-sosa">
-    <h3>iPhone Barometer</h3>
-    <p>An RDF file containing a <a href="https://github.com/w3c/sdw/blob/gh-pages/sdw-sosa-ssn/ssn/rdf/examples/iphone_barometer-sosa.ttl">graph
-            corresponding to this example is available</a>. </p>
-    <pre class="example turtle" data-include="./rdf/examples/iphone_barometer-sosa.ttl" data-include-format="text"></pre>
-</section>
-
-<section id="coal_oil_plant-sosa">
-    <h3>Temperature and Humidity at Coal Oil Point Reserve</h3>
-    <p>An RDF file containing a <a href="https://github.com/w3c/sdw/blob/gh-pages/sdw-sosa-ssn/ssn/rdf/examples/IDEAS.ttl">graph
-            corresponding to this example is available</a>. </p>
-    <pre class="example turtle" data-include="./rdf/examples/IDEAS.ttl" data-include-format="text"></pre>
-</section>
-
-<section id="apartment-134">
-    <h3>Electricity consumption of apartment #134</h3>
-    <p>An RDF file containing a <a href="https://github.com/w3c/sdw/blob/gh-pages/sdw-sosa-ssn/ssn/rdf/examples/apartment-134.ttl">graph
-            corresponding to this example is available</a>. </p>
-    <pre class="example turtle" data-include="./rdf/examples/apartment-134.ttl" data-include-format="text"></pre>
-</section>
-
-<section id="spinning-cups">
-    <h3>Wind sensor spinning cups</h3>
-    <p>An RDF file containing a <a href="https://github.com/w3c/sdw/blob/gh-pages/sdw-sosa-ssn/ssn/rdf/examples/spinning-cups.ttl">graph
-            corresponding to this example is available</a>. </p>
-    <pre class="example turtle" data-include="./rdf/examples/spinning-cups.ttl" data-include-format="text"></pre>
-</section>
-
-<section id="dht22-description">
-    <h3>Complex sensor capabilities &mdash; DHT22</h3>
-    <div class="ssn">
-        <p>An RDF file containing a <a href="https://github.com/w3c/sdw/blob/gh-pages/sdw-sosa-ssn/ssn/rdf/examples/dht22.ttl">graph
-                corresponding to this example is available</a>. </p>
-        <pre class="example turtle" data-include="./rdf/examples/dht22.ttl" data-include-format="text"></pre>
-    </div>
-</section>
-
-<section id="dht22-deployment">
-    <h3>DHT22 Deployment</h3>
-    <div class="ssn">
-        <p>This example shows how the conditions (temperature and humidity) in a room can 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. </p>
-        <p>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. </p>
-        <p>An RDF file containing a <a href="https://github.com/w3c/sdw/blob/gh-pages/sdw-sosa-ssn/ssn/rdf/examples/dht22-deployment.ttl">graph
-                corresponding to this example is available</a>. </p>
-        <pre class="example turtle" data-include="./rdf/examples/dht22-deployment.ttl" data-include-format="text"></pre>
-    </div>
-</section>
-
-<section id="ip68-smart-sensor">
-    <h3>IP68 Smart Sensor</h3>
-    <div>
-        <p>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.</p>
-        <p>An RDF file containing a <a href="https://github.com/w3c/sdw/blob/gh-pages/sdw-sosa-ssn/ssn/rdf/examples/ip68.ttl">graph
-                corresponding to this example is available</a>. </p>
-        <pre class="example turtle" data-include="./rdf/examples/ip68.ttl" data-include-format="text"></pre>
-    </div>
-</section>
-
--->

ssn/chapters/Introduction.html

@@ -6,9 +6,9 @@ <h3>Context</h3>
   Sensors are a major source of data available on the Web today.
   However, searching, reusing, integrating, and interpreting sensor data requires more than just the result of an act of
   sensing.
-  For proper interpretation of these values, knowledge of the feature of interest, such as a river, the observed
-  property, such as flow velocity, the sampling strategy, such as the specific locations and times at which the velocity
-  was measured, and a variety of other information are required.
+  For proper interpretation of these values, knowledge of the feature of interest (such as a river), the observed
+  property (such as flow velocity), the sampling strategy (such as the specific locations and times at which the
+  velocity was measured), and a variety of other information are required.
 </p>
 
 <p>
@@ -20,9 +20,10 @@ <h3>Context</h3>
 </p>
 
 <p>
-  OGC's Sensor Web Enablement standards [[SWE]], [[SensorML]], [[OandM]], [[OMS]], [[STA]] provide
+  OGC's Sensor Web Enablement [[SWE]] Standards — [[SensorML]], [[OandM]], [[OMS]], and [[STA]] — provide
   conceptual models and some encodings for the annotation of sensors and their observations.
-  [[OMS]] provides a comprehensive description of the characteristics of observations and samples.
+  Observations, Measurements, and Samples ([[OMS]]) provides a comprehensive description of the characteristics of
+  observations and samples.
   Integration and alignment of these with W3C Semantic Web technologies and Linked Data embeds this in a global and
   densely interconnected graph of data.
 </p>
@@ -38,7 +39,7 @@ <h3>Context</h3>
 <h3>Scope</h3>
 
 <p>
-  This recommendation defines the Semantic Sensor Network Ontology (<b>SSN</b>).
+  This document is a W3C Recommendation and OGC Standard that defines the Semantic Sensor Network Ontology (<b>SSN</b>).
   SSN provides flexible but coherent perspectives for representing the entities, relations, and activities involved in
   actuation, observation, and sampling, including the procedures executed, and the systems that implement the
   procedures.
@@ -50,19 +51,19 @@ <h3>Scope</h3>
 <p>
   A lightweight core module, known as <b>SOSA</b> (Sensor, Observation, Sample, and Actuator) aims to broaden the
   audience and application areas that do not need the full capabilities of Semantic Web ontologies.
-  SOSA acts as minimal interoperability fall-back level, i.e., it defines terms (classes and properties) with which
-  data can be safely exchanged across all uses of SSN, its modules, and SOSA.
+  SOSA acts as minimal interoperability fallback level, i.e., it defines terms (classes and properties) with which data
+  can be safely exchanged across all uses of SSN, its modules, and SOSA.
   Basic subclass and subproperty relationships are included.
 </p>
 
 <p>
-  The full SSN Ontology has additional axiomatizations that may be useful in richer semantic web applications.
+  The full SSN Ontology has additional axioms that may be useful in richer semantic web applications.
 </p>
 
 <h3>2023 Edition</h3>
 
 <p>
-  The previous edition of the SSN Ontology [[vocab-ssn-20171019]] harmonised prior work from OGC ([[OandM]]) and W3C
+  The previous edition of the SSN Ontology [[vocab-ssn-20171019]] harmonized prior work from OGC ([[OandM]]) and W3C
   ([[SSNX]]).
   A new edition of the OGC/ISO standard [[iso-19156-2023]],[[[OMS]]] has updated [[OandM]] with a number of additional
   features arising from more than 10 years implementation experience.
@@ -99,14 +100,13 @@ <h3>2023 Edition</h3>
 </p>
 <p>
   A <a href="#changes">change log</a> is provided in an Annex of this document.
-  This describes the changes since the 2017 edition [[vocab-ssn-20171019]].
+  The Annex describes the changes since the previous edition [[vocab-ssn-20171019]].
   Backward compatibility is maintained since descriptions of Actuations, Observations, Samplings, and Samples using the
-  SSN Ontology from the 2017 edition are compatible with the SSN Ontology provided by this 2023 Edition.
+  SSN Ontology from the previous edition are compatible with the SSN Ontology provided by this 2023 Edition.
 </p>
 <p class="note">
   A brief account of the <a href="#Origins">Origins of SSN and SOSA</a> through various OGC and W3C initiatives is
-  provided
-  in an Appendix to this document.
+  provided in an Appendix to this document.
 </p>
 <p>
   The RDF files of the 2017 edition remain available at their permanent version IRI, which is obtained by substituting

ssn/chapters/Inverse-properties.html

@@ -1,17 +1,18 @@
 <h3>Tabulation of properties and their inverses</h3>
 
 <p>
-    Inverses are named for all SSN object properties, in order to support interoperability across a range of
-    applications.
+  To support interoperability across a range of applications, inverses are named for all SSN object properties.
 </p>
 
 <p class="note">
-    Terms added in the 2023 Edition are indicated with an asterisk*.
+  Terms added in the 2023 Edition are indicated with an asterisk*.
 </p>
 <p class="note">
-  This section uses a combination of [[Description-Logics]] notation (see also the [[Description-Logics-Home-Page]]) and the Manchester Syntax [[owl2-manchester-syntax]].
+  This section uses a combination of [[Description-Logics]] notation (see also the [[Description-Logics-Home-Page]]) and
+  the Manchester Syntax [[owl2-manchester-syntax]].
   <br>
-  The expression <code>OP1 <span class="logic">≡ inverse</span> OP2</code> indicates that the properties <code>OP1</code> and <code>OP2</code> are inverses of each other.
+  The expression <code>OP1 <span class="logic">≡ inverse</span> OP2</code> indicates that the properties
+  <code>OP1</code> and <code>OP2</code> are inverses of each other.
 </p>
 
 <ul class="align-on-symbol" data-sortable="true">
@@ -197,7 +198,7 @@ <h3>Tabulation of properties and their inverses</h3>
     </li>
 </ul>
 <p>
-    The following properties are datatype properties, and have therefore no inverses.
+  The following properties are datatype properties, and have therefore no inverses.
 </p>
 
 <ul class="align-on-symbol" data-sortable="true">

ssn/chapters/ModelPropertyDefinition.html

@@ -19,27 +19,33 @@ <h4>Catalogues of properties</h4>
 </p>
 <h4>New property definitions</h4>
 <p>
-    Alternatively, the <a href="https://w3id.org/env/puv">Parameter Usage Vocabulary</a> or
-    <a href="https://doi.org/10.15497/RDA00071">I-ADOPT</a> may be used to define a new observable or actuatable
-    property.
-    For example, using the I-ADOPT terminology, the property <a href="http://qudt.org/vocab/quantitykind/Temperature">Temperature</a> may be specialized to apply to a sick
-    child as follows:
+    Alternatively, the <a href="https://w3id.org/env/puv">Parameter Usage Vocabulary</a> or <a href="https://w3id.org/iadopt/ont/">I-ADOPT</a> [[I-ADOPT]] may be used to define a new <a>sosa:Property</a>.
+    For example, integrating I-ADOPT Variables may resolve legacy inconsistencies by decomposing complex properties into explicit, interoperable atomic components.
+    This may enrich SOSA observables with reusable, machine-actionable semantics, lowering barriers to cross-system data comparison and sharing.
+    <a href="#Fig-AgeOfAir"></a> and <a href="#Fig-CO2-Concentration"></a> show the application of the I-ADOPT ontology for the properties used in two initial observations to provide input-values for the final observation (cmp. <a href="#example-20"></a>).
 </p>
-<figure id="Fig-Temperature-i-adopt">
-    <embed alt="Constrained temperature definition" src="./images/Temperature-i-adopt.svg" style="width:90%" />
+<figure id="Fig-AgeOfAir">
+    <embed alt="Property definition based on I-ADOPT" src="./images/AgeOfAir-i-adopt.svg" style="width:90%" />
     <figcaption>
-        Definition of a constrained temperature property for a sick child, using the I-ADOPT vocabulary.
+        Definition of an observation with an I-ADOPT Variable: The age of air in ice core, determined by radiocarbon dating, expressed relative to a datum of AD 1950.
         <br>
         <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
     </figcaption>
 </figure>
-<pre class="example turtle" data-include="./rdf/examples/Temperature-i-adopt.ttl" data-include-format="text"></pre>
+<pre class="example turtle" data-include="./rdf/examples/AgeOfAir-i-adopt.ttl" data-include-format="text"></pre>
+As demonstrated, the I-ADOPT Variable remains strictly decoupled from procedural metadata and value expressions. Methodological details, such as Radiocarbon (C-14) dating, are explicitly captured via the observation's measurement procedure (sosa:usedProcedure), preserving the reusable, context-independent structure of the variable itself.
+<figure id="Fig-CO2-Concentration">
+    <embed alt="Property definition based on I-ADOPT" src="./images/CO2InAir-i-adopt.svg" style="width:90%" />
+    <figcaption>
+        Definition of an observation with an I-ADOPT Variable: Concentration of carbon dioxide in air.
+        <br>
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
+    </figcaption>
+</figure>
+<pre class="example turtle" data-include="./rdf/examples/CO2InAir-i-adopt.ttl" data-include-format="text"></pre>
 <p>
-    The key point is that an individual property, whether taken from a catalogue or defined using a specialist
-    vocabaulary, is denoted by a URI.
-    This URI can then be used as the value of the
-    <a>sosa:actsOnProperty</a> or
-    <a>sosa:observedProperty</a> of an Execution.
+    The primary objective of the I-ADOPT framework is to represent a variable as an identifiable and reusable concept that is decomposed into its atomic components. By assigning specific descriptive roles, such as Object of Interest, Matrix, or Context Object, and mapping each component to URIs from domain-specific vocabularies, I-ADOPT ensures full semantic clarity.
+    The variable URI can then be used as the value of the <a>sosa:actsOnProperty</a> or <a>sosa:observedProperty</a> of an Execution.
 </p>
 <h4>Feature-specific properties</h4>
 <p>

ssn/chapters/Origins.html

@@ -3,7 +3,7 @@ <h3>Origins of SSN and SOSA</h3>
 <h4>OGC Sensor Web Enablement</h4>
 
 <p>
-    Starting in 2002, the OGC's Sensor Web Enablement initiative [[SWE]] developed a generic framework for delivering
+    Beginning in 2002, the OGC's Sensor Web Enablement initiative [[SWE]] developed a generic framework for delivering
     sensor data, dealing with remote-sensing, moving platforms, and in-situ monitoring and sensing.
     In particular, the key standards SensorML and O&amp;M provided complementary viewpoints:</p>
 <ol>
@@ -58,7 +58,7 @@ <h4>New editions</h4>
     Section 7 of [[OMS]] provides a comprehensive description of the characteristics of observations and samples.
 </p>
 
-<p class="note">OMS was published as ISO 19156:2023 [[iso-19156-2023]], but is freely available as OGC Abstract
+<p class="note">OMS was published as ISO 19156:2023 [[iso-19156-2023]] but is freely available as OGC Abstract
     Specification &mdash; Topic 20 [[OMS]].</p>
 
 <p>

ssn/chapters/README.md

@@ -1,3 +1,3 @@
-# Individual chapters from the Semantic Sensor Network Ontology recommendation
+# Individual chapters from the Semantic Sensor Network Ontology Recommendation
 
 This folder contains chapters from the **2023 edition** of the **Semantic Sensor Network Ontology** (SSN). 

ssn/chapters/System-capabilities.html

@@ -304,7 +304,7 @@ <h4>Guidance on System Capability properties and ranges</h4>
 
         <p>The System Capabilities Module also introduced a <a href="#SOSABattery">Battery</a> class to represent power
             supply requirements for mobile sensors.
-            The illustrative <a href="#SOSACAPBatteryLifetime"><code>sosa-cap:BatteryLifetime</code></a> system
+            The illustrative  <a href="#SOSACAPBatteryLifetime"><code>sosa-cap:BatteryLifetime</code></a> system
             capability property allows to record expected battery
             utilization either on a nominal basis or within different operating conditions.
         </p>
@@ -776,4 +776,4 @@ <h6>Sample vocabulary of properties about the system environment</h6>
         </div>
     </section>
 
-</section>
+</section>