fixes to requirements cross-reference table

BillSwirrl · BillSwirrl · commit eb7f26b8ea1f · 2016-12-12T16:12:08.000Z
diff --git a/coverage-json/index.html b/coverage-json/index.html
@@ -369,13 +369,12 @@ <h3>Other data models</h3>
 
     <section  id="mappingToUCR">
       <h2>Mapping to Use Cases and Requirements Document</h2>
-      The Spatial Data on the Web Working Group has created a <a href="https://www.w3.org/TR/sdw-ucr/">Use Cases and Requirements Document</a>. A subset of the requirements are relevant to Coverage data. This section describes how CoverageJSON addresses relevant requirements.
+      <p>The Spatial Data on the Web Working Group has created a <a href="https://www.w3.org/TR/sdw-ucr/">Use Cases and Requirements Document</a>. A subset of the requirements are relevant to Coverage data. This section describes how CoverageJSON addresses relevant requirements.</p>
       <table id="table_covjson_ucr_xref">
 	     <caption>How CoverageJSON relates to the Spatial Data on the Web Use Cases and Requirements Document</caption>
-	     <thead>
+	     <tr>
 	     	<th>Requirement</th><th>CoverageJSON approach</th>
-	     </thead>
-	     <tbody>
+	     </tr>
 		  <tr>
 		  	 <td><a href="https://www.w3.org/TR/sdw-ucr/#4DModelSpaceTime">4D model of space-time</td><td>CoverageJSON has a <a href="https://covjson.org/domain-types/#trajectory">'trajectory'</a> option in the way it specifies the type of a domain.</td>
 		  </tr>
@@ -419,7 +418,7 @@ <h2>Mapping to Use Cases and Requirements Document</h2>
 		  	 <td><a href="https://www.w3.org/TR/sdw-ucr/#MultilingualSupport">Multilingual support</a></td><td>CoverageJSON supports <a href="https://covjson.org/spec/#i18n-objects">multi-language labels</a></td>
 		  </tr>
 		  <tr>
-		  	 <td><a href="https://www.w3.org/TR/sdw-ucr/#ObservedPropertyInCoverage">Observed property in coverage</a></td><td></td>
+		  	 <td><a href="https://www.w3.org/TR/sdw-ucr/#ObservedPropertyInCoverage">Observed property in coverage</a></td><td>See the CoverageJSON approach to describing <a href="https://covjson.org/spec/#parameter-objects">parameters</a></td>
 		  </tr>
 		  <tr>
 		  	 <td><a href="https://www.w3.org/TR/sdw-ucr/#Provenance">Provenance</a></td><td>CoverageJSON does not specify particular ways to describe provenance, but as with other metadata, should be compatible with established approaches of describing provenance. </td>
@@ -437,7 +436,7 @@ <h2>Mapping to Use Cases and Requirements Document</h2>
             </td>
 		  </tr>
 		  <tr>
-		  	 <td><a href="https://www.w3.org/TR/sdw-ucr/#SensingProcedure">Sensing procedure</a></td><td></td>
+		  	 <td><a href="https://www.w3.org/TR/sdw-ucr/#SensingProcedure">Sensing procedure</a></td><td>It is possible to provide a text description of a <a href="https://covjson.org/spec/#parameter-objects">parameter</a>, which could potentially contain a description of the sensing method.</td>
 		  </tr>
 		  <tr>
 		  	 <td><a href="https://www.w3.org/TR/sdw-ucr/#SpatialVagueness">Spatial vagueness</a></td><td>Coverage data in general may not be suitable for representing data at vague locations.  An external connection could be made between a vaguely expressed location and a precisely defined region that might approximate it, for example a bounding box.  The coverage format should then be able to deliver data relating to that region of interest.</td>
@@ -449,13 +448,12 @@ <h2>Mapping to Use Cases and Requirements Document</h2>
 		  	 <td><a href="https://www.w3.org/TR/sdw-ucr/#3DSupport">Support for 3D</a></td><td>CoverageJSON's <a href="https://covjson.org/spec/#domain-objects">approach to specifying spatial domains</a> supports 3D.</td>
 		  </tr>
 		  <tr>
-		  	 <td><a href="https://www.w3.org/TR/sdw-ucr/#TilingSupport">Support for tiling</td><td></td>
+		  	 <td><a href="https://www.w3.org/TR/sdw-ucr/#TilingSupport">Support for tiling</td><td>CoverageJSON supports <a href="https://covjson.org/spec/#tiledndarray-objects">tiling</a>.</td>
 		  </tr>
 		  <tr>
 		  	 <td><a href="https://www.w3.org/TR/sdw-ucr/#UseInComputationalModels">Use in computational models</a></td><td>Different computational models will have their own requirements for input and output data and any single format for coverage data will not match all models.  However, a reasonable requirement for a coverage data format would be to deliver data in an easy to process format, and to have flexible options for delivering extracts of the data in different dimensions.  CoverageJSON satisfies those general requirements.</td>
 		  </tr>
 		
-		 </tbody>
 	
 	  </table>
     </section>
