fix DWBP reference

w3c · Jun 13, 2017 · 5aea7e1 · 5aea7e1
1 parent 9515866
commit 5aea7e1
Showing 1 changed file with 1 addition and 2 deletions.
diff --git a/coverage-json/index.html b/coverage-json/index.html
@@ -89,7 +89,6 @@
     <section>
       <h2>Known issues with this document</h2>
       <ul>
-        <li>Need to tidy up and check references (e.g link to DW-BP)</li>
         <li>TimeseriesML section requires fact-checking/expansion by a TimeseriesML expert</li>
       </ul>
     </section>
@@ -112,7 +111,7 @@ <h3>Existing Coverage representations</h3>
 
       <section id="motivation">
         <h3>Motivation and objectives</h3>
-        <p>This document describes the CoverageJSON format and explains how it is well-suited to representation of spatial data on the Web: with a number of advantages for use in a web context, in comparison to alternative established approaches for serialisation of coverage data. It is a good match to the Use Case Requirements  [[SDW-UCR]] and Best Practices [[SDW-BP]] of the Spatial Data on the Web working group. It has been informed also by the Data on the Web Best Practices [[DW-BP]]."</p>
+        <p>This document describes the CoverageJSON format and explains how it is well-suited to representation of spatial data on the Web: with a number of advantages for use in a web context, in comparison to alternative established approaches for serialisation of coverage data. It is a good match to the Use Case Requirements  [[SDW-UCR]] and Best Practices [[SDW-BP]] of the Spatial Data on the Web working group. It has been informed also by the Data on the Web Best Practices [[DWBP]]."</p>
 <p>Serialisations (i.e. data formats) based upon community-specific binary formats and complex XML schemas provide usability challenges for the development of web applications. Javascript libraries do not always exist for these formats, and the formats are complex, requiring specialist knowledge on the part of the web developer. Our overall aim is to <strong>make it easier for web developers to consume coverage data in their applications</strong>, minimising the need for prior knowledge about community-specific data formats.</p>
         <p>Therefore our objective in this work was to develop a well-structured, consistent and easy-to-use JSON format for coverage data that fulfils the following criteria:</p>
         <ul>