Broken links (#277)

* Fix some borken links and missing diagrams * Missing diagram * adjust diagram sizes * Missing diagram and missing ids on figures * Missing figure IDs * Missing refs for bibliography * Diagrams widths and colours * Diagram colours * Diagram colours * Diagram widths * Make appendices non-normative * mark appendices 'informative' * Revert "mark appendices 'informative'" This reverts commit 35ef6c1. * Revert "Make appendices non-normative" This reverts commit c60de01. * Incorrect tag
w3c · Mar 5, 2025 · 712d190 · 712d190
1 parent b93f84d
commit 712d190
Show file tree

Hide file tree

Showing 61 changed files with 391 additions and 3,850 deletions.
diff --git a/ssn/chapters/Actuation.html b/ssn/chapters/Actuation.html
@@ -5,10 +5,10 @@ <h4>Overview</h4>
     <p>The following figure provides an overview of the core classes
         and properties that are specifically related to modeling Actuations.
     </p>
-    <figure>
+    <figure id="Actuation">
         <embed
             alt="Actuation diagram; showing Actuation, ActuationCollection, Procedure, Actuator, ActuatableProperty, FeatureOfInterest"
-            src="images/Actuation.svg">
+            src="images/Actuation.svg" style="width:100%" />
         <figcaption>
             Classes and relationships involved in Actuation
             <br>

diff --git a/ssn/chapters/Common.html b/ssn/chapters/Common.html
@@ -31,10 +31,10 @@ <h5>Overview</h5>
                 The following figure provides an overview of the classes and properties related to modeling Features of
                 Interest and Properties.
             </p>
-            <figure>
+            <figure id="FeatureOfInterest">
                 <embed
                     alt="Features of Interest and Properties; showing Property, PropertyOfInterest, FeatureOfInterest, Execution"
-                    src="images/FeatureOfInterest.svg">
+                    src="images/FeatureOfInterest.svg" style="width: 100%;" />
                 <figcaption>
                     Classes and relationships related to features of interest and properties
                     <br>
@@ -605,9 +605,9 @@ <h5>Overview</h5>
             <p>
                 The following figure provides an overview of the classes and properties related to modeling Procedures.
             </p>
-            <figure>
+            <figure id="Procedure">
                 <embed alt="Procedure diagram; showing Procedure, Execution, Property, System"
-                    src="images/Procedure.svg">
+                    src="images/Procedure.svg" style="width: 100%;" />
                 <figcaption>Classes and relationships related to procedures
                     <br>
                     <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
@@ -1114,9 +1114,9 @@ <h5>Overview</h5>
                 The following figure provides an overview of the classes and properties related to modeling Execution of
                 Procedures.
             </p>
-            <figure>
+            <figure id="Execution">
                 <embed alt="Execution of Procedures diagram; showing Execution, System, FeatureOfInterest, Procedure"
-                    src="images/Execution.svg">
+                    src="images/Execution.svg" style="width: 100%;" />
                 <figcaption>Classes and relationships related to execution of procedures
                     <br>
                     <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
@@ -2542,10 +2542,10 @@ <h5>Overview</h5>
             <p>The following figure provides an overview of the classes
                 and properties that are specifically related to modeling systems and their deployment.
             </p>
-            <figure>
+            <figure id="System">
                 <embed
                     alt="Systems and deployment diagram; showing System, Deployment, Platform, Property, Procedure, Execution"
-                    src="images/System.svg">
+                    src="images/System.svg" style="width: 100%;" />
                 <figcaption>Classes and relationships related to systems and deployments
                     <br>
                     <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
@@ -3258,8 +3258,7 @@ <h6><a href="#SOSAinDeployment">sosa:inDeployment</a></h6>
                 <em property="rdfs:label">in deployment</em> -
                 <span property="skos:definition">Relation between a <a href="#SOSAPlatform">Platform</a> and a
                     <a href="#SOSADeployment">Deployment</a>, meaning that the
-                    <a href="#SOSAdeployedSystems">deployedSystems</a> of
-                    the
+                    <a href="#SOSAdeployedSystem">deployedSystems</a> of the
                     <a href="#SOSADeployment">Deployment</a> are hosted on the <a
                         href="#SOSAPlatform">Platform</a>.</span>
             </p>
@@ -3550,7 +3549,7 @@ <h5>Overview</h5>
                 related to describing collections of executions or of samples.
             </p>
             <figure class="sosa">
-                <embed alt="Collections of Executions or Samples" src="images/Collections.svg">
+                <embed alt="Collections of Executions or Samples" src="images/Collections.svg" style="width: 100%;" />
                 <figcaption>Classes and relationships related to collections of executions or samples
                     <br>
                     <em>See <a href="#Class-diagram">explanation of the notation used in class diagrams</a></em>.

diff --git a/ssn/chapters/ModelDomainTypes.html b/ssn/chapters/ModelDomainTypes.html
@@ -111,7 +111,7 @@ <h4>FeatureOfInterest in SSN</h4>
     <figcaption>
         A feature classified using a domain ontology.
         <br>
-        <em><a href="#class-diagram">Explanation of the notation used in class diagrams</a></em>.
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
     </figcaption>
 </figure>
 <pre>
@@ -125,7 +125,7 @@ <h4>FeatureOfInterest in SSN</h4>
     <figcaption>
         An observation on a feature previously classified using a domain ontology.
         <br>
-        <em><a href="#class-diagram">Explanation of the notation used in class diagrams</a></em>.
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
     </figcaption>
 </figure>
 

diff --git a/ssn/chapters/ModelFOI.html b/ssn/chapters/ModelFOI.html
@@ -31,7 +31,7 @@ <h3>Proximate and Ultimate feature of interest</h3>
     property</a>.
 </p>
 <figure id="obs-sample-foi">
-    <embed alt="Observation feature-of-interest patterns" data="./images/obs-sample-foi.svg" style="width:75%" />
+    <embed alt="Observation feature-of-interest patterns" src="./images/obs-sample-foi.svg" style="width:75%" />
     <figcaption>
         The observation is on a sample of the ultimate feature of interest.
         <br>

diff --git a/ssn/chapters/ModelLocation.html b/ssn/chapters/ModelLocation.html
@@ -32,9 +32,9 @@ <h5>Systems, Platforms, Deployments</h5>
     described as follows:
 </p>
 <figure id="LocatedSensor">
-    <embed alt="sensor location - direct" src="./images/LocatedSensor.svg" style="width:50%" />
+    <embed alt="sensor location - direct" src="./images/LocatedSensor.svg" style="width:60%" />
     <figcaption>System location - direct description <br>
-        <em><a href="#class-diagram">Explanation of the notation used in class diagrams</a></em>.
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
     </figcaption>
 </figure>
 <pre class="example" data-include="./rdf/examples/LocatedSensor.ttl" data-include-format="text"></pre>
@@ -43,10 +43,10 @@ <h5>Systems, Platforms, Deployments</h5>
     Alternatively, the location may be associated with a Platform, which then might also host other Systems:
 </p>
 <figure id="LocatedPlatform">
-    <embed alt="sensor location - on a platform" src="./images/LocatedPlatform.svg" style="width:60%" />
+    <embed alt="sensor location - on a platform" src="./images/LocatedPlatform.svg" style="width:75%" />
     <figcaption>System location - on Platform
         <br>
-        <em><a href="#class-diagram">Explanation of the notation used in class diagrams</a></em>.
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
     </figcaption>
 </figure>
 <pre class="example" data-include="./rdf/examples/LocatedPlatform.ttl" data-include-format="text"></pre>
@@ -55,9 +55,9 @@ <h5>Systems, Platforms, Deployments</h5>
     If this Sensor location is not permanent, then it may be characterized as a Deployment:
 </p>
 <figure id="LocatedDeployment">
-    <embed alt="sensor location - in a deployment" src="./images/LocatedDeployment.svg" style="width:60%" />
+    <embed alt="sensor location - in a deployment" src="./images/LocatedDeployment.svg" style="width:75%" />
     <figcaption>System location - in a Deployment <br>
-        <em><a href="#class-diagram">Explanation of the notation used in class diagrams</a></em>.
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
     </figcaption>
 </figure>
 <pre class="example" data-include="./rdf/examples/LocatedDeployment.ttl" data-include-format="text"></pre>
@@ -72,9 +72,9 @@ <h5>Samples, Features</h5>
     The location of an air Sample might be recorded directly using the following pattern:
 </p>
 <figure id="LocatedSample">
-    <embed alt="Location of a Sample" src="./images/LocatedSample.svg" style="width:60%" />
+    <embed alt="Location of a Sample" src="./images/LocatedSample.svg" style="width:75%" />
     <figcaption>Sample location - direct descriptions <br>
-        <em><a href="#class-diagram">Explanation of the notation used in class diagrams</a></em>.
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
     </figcaption>
 </figure>
 <pre class="example" data-include="./rdf/examples/LocatedSample.ttl" data-include-format="text"></pre>
@@ -89,9 +89,9 @@ <h5>Samples, Features</h5>
     The location could also be provided as a parameter to the act of Sampling that generated the Sample:
 </p>
 <figure id="LocatedSampling">
-    <embed alt="Location of a Sampling" src="./images/LocatedSampling.svg" style="width:60%" />
+    <embed alt="Location of a Sampling" src="./images/LocatedSampling.svg" style="width:75%" />
     <figcaption>Sample location - indirect descriptions <br>
-        <em><a href="#class-diagram">Explanation of the notation used in class diagrams</a></em>.
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
     </figcaption>
 </figure>
 <pre class="example" data-include="./rdf/examples/LocatedSampling.ttl" data-include-format="text"></pre>

diff --git a/ssn/chapters/ModelSampleChains.html b/ssn/chapters/ModelSampleChains.html
@@ -17,7 +17,7 @@ <h3>Sample chains</h3>
     <embed alt="Provenance of sample from ice core" src="./images/bubble-provenance.svg" style="width:90%"/>
     <figcaption>Sequence of two acts of sampling to recover a gas bubble from an ice sheet.
         <br>
-        <em><a href="#class-diagram">Explanation of the notation used in class diagrams</a></em>.
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
     </figcaption>
 </figure>
 <pre class="example" data-include="./rdf/examples/bubble-provenance.ttl" data-include-format="text"></pre>

diff --git a/ssn/chapters/ModelTimes.html b/ssn/chapters/ModelTimes.html
@@ -16,7 +16,7 @@ <h3>Temporal properties</h3>
     Different kinds of executions have different relationships between these times.
 </p>
 
-<h4>Forecast</h4>
+<h4>Forecasts</h4>
 <p>
     A forecast may be represented as an observation where the value of <code>sosa:phenomenonTime</code> is later in
     time than the <code>sosa:resultTime</code>.
@@ -28,7 +28,7 @@ <h4>Forecast</h4>
     <figcaption>Temperature grid forecast, modeled as an Observation in which the result time is before the phenomenon
         time, which is when the result applies to the feature of interest.
         <br>
-        <em><a href="#class-diagram">Explanation of the notation used in class diagrams</a></em>.
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
     </figcaption>
 </figure>
 
@@ -52,34 +52,37 @@ <h5>Serialised in JSON-LD</h5>
 <h4>Historical observations</h4>
 <p>
     Observations in historical sciences, including geology and archeology, may be made to determine the state of the
-    world in the remote past.
+    world in the past.
 </p>
-<p>
-    A simple case is encoding an observation transcribed from a historical record, such as a logbook:
-</p>
-<!--
-<figure id="historical-airtemp">
-    <img alt="Observation transcribed from a historical record" src="./images/historical-airtemp.png" />
-    <figcaption>Observation with phenomemon-time in the deep past.
-    </figcaption>
-</figure>
--->
-<pre class="example" data-include="./rdf/examples/historical-airtemp.ttl" data-include-format="text"></pre>
-
 
+<h5>Historical observations - simple cases</h5>
 <p>
-    For a more complex example, consider a determination of the diet of past communities by examination of middens and
-    other archaeological features (<a href="#diet"></a>)
+    Consider a determination of the diet of past communities by examination of middens and other archaeological features
+    (<a href="#diet"></a>)
 </p>
-
 <figure id="diet">
     <embed alt="Observation with phenomemon-time in the deep past - paleo diet" src="./images/diet.svg"
         style="width:90%" />
     <figcaption>Observation with phenomemon-time in the deep past.
+        <br>
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
     </figcaption>
 </figure>
 <pre class="example" data-include="./rdf/examples/diet.ttl" data-include-format="text"></pre>
+<p>
+    An observation transcribed from a historical record, such as a logbook, might be encoded as follows:
+</p>
+<figure id="historical-airtemp">
+    <embed alt="Observation transcribed from a historical record" src="./images/historical-airtemp.svg"
+        style="width:100%" />
+    <figcaption>Observation with phenomenon-time in the past.
+        <br>
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
+    </figcaption>
+</figure>
+<pre class="example" data-include="./rdf/examples/historical-airtemp.ttl" data-include-format="text"></pre>
 
+<h5>Historical observation - from combination of separate observation of time and property</h5>
 <p>
     The concentration of CO<sub>2</sub> can be measured in bubbles in ice-cores that are assumed to sample the
     atmosphere at some past time.
@@ -89,9 +92,11 @@ <h4>Historical observations</h4>
 </p>
 <figure id="paleo-atmosphere">
     <embed alt="Observation with phenomemon-time in the deep past - atmospheric CO2" src="./images/paleo-atmosphere.svg"
-        style="width:90%" />
-    <figcaption>Observation with phenomemon-time in the deep past, constructed from the output of two primitive
-        observations.
+        style="width:100%" />
+    <figcaption>Observation with phenomenon-time in the deep past,
+        constructed from the output of two primitive observations.
+        <br>
+        <em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
     </figcaption>
 </figure>
 <pre class="example" data-include="./rdf/examples/paleo-atmosphere.ttl" data-include-format="text"></pre>

diff --git a/ssn/chapters/Notation.html b/ssn/chapters/Notation.html
@@ -3,7 +3,7 @@ <h2>Notation</h2>
 <section id="RDF-notation">
     <h3>RDF notation</h3>
     <p>
-        The SSN Ontology is defined using RDFS [[rdf-schema]] and OWL [[owl2-overview]] using its RDF representation
+        The SSN Ontology is defined using RDFS [[[rdf-schema]]] and OWL [[[owl2-overview]]] using its RDF representation
         [[owl2-rdf-based-semantics]].
     </p>
     <p>
@@ -29,7 +29,7 @@ <h4>Module diagrams</h4>
         </figure>
 
         <p>
-            Module diagrams use a notation similar to UML Package Diagrams [[uml]],
+            Module diagrams use a notation similar to UML Package Diagrams [[[uml]]],
             with folders for modules, and dashed directed connectors for dependencies.
             However the module diagrams MUST NOT be interpreted according to strict UML rules.
         </p>
@@ -50,7 +50,7 @@ <h4>Class and property diagrams</h4>
         </figure>
 
         <p>
-            Class and property diagrams use a notation similar to UML Class Diagrams [[uml]],
+            Class and property diagrams use a notation similar to UML Class Diagrams [[[uml]]],
             with boxes for classes and individuals,
             and labelled directed connectors (associations) or class attributes for properties.
             However the class diagrams MUST NOT be interpreted according to strict UML rules.
@@ -72,7 +72,8 @@ <h4>Class and property diagrams</h4>
         </p>
         <p>
             Connectors with open arrowheads indicate sub-class relationships,
-            however it should be noted that these are not defined in the SOSA modules.
+            however it should be noted that these are not defined in the <a href="#sosa-module">SOSA modules</a>
+            &mdash; see <a href="#expressivity">Expressivity</a> for more explanation.
         </p>
         <p>
             The purpose of the diagrams is primarily to orient the reader as to how SSN properties are related to the
@@ -101,4 +102,4 @@ <h3>JSON-LD serialization</h3>
     </p>
 </section>
 
-</section>
+</section>
diff --git a/ssn/chapters/OBOE-alignment.html b/ssn/chapters/OBOE-alignment.html
@@ -53,7 +53,8 @@ <h4>Class Alignments</h4>
     <a href="#SOSAhasFeatureOfInterest">sosa:hasFeatureOfInterest</a>.
   </p>
   <figure id="oboe-implementation">
-    <embed alt="OBOE core aligned to SOSA Observation and ObservationCollection" src="./images/OBOE-alignment.svg">
+    <embed alt="OBOE core aligned to SOSA Observation and ObservationCollection" src="./images/OBOE-alignment.svg"
+      style="width:100%" />
     <figcaption>
       The OBOE core model (left), shown alongside the SOSA model including two levels of
       <a href="#SOSAObservationCollection">ObservationCollection</a> (right) with matching classes and properties