remove some WFS refs

bp/BP-implementation-report-00004.md

@@ -4,7 +4,7 @@
 Ordnance Survey Names API
 
 ## Documentation root
-[https://apidocs.os.uk/docs/os-names-overview](https://apidocs.os.uk/docs/os-names-overview)
+[https://apidocs.os.uk/docs/os-names-overview](https://osdatahub.os.uk/docs/names/overview)
 
 ## Description of service
 OS Names API provides a geocoding convienience API for the discovery or identification of named places in Great Britain. The API can locate a feature using just its name, or it can find the closest location to a given point.
@@ -249,7 +249,14 @@ The two resources within the API are operations performing a geocoding search, b
 #### To-do
 None.
 
-### [Best Practice 13: Include spatial metadata in dataset metadata](https://www.w3.org/TR/sdw-bp/#spatial-info-dataset-metadata)
+### [Best Practice 13: Support requesting and returning geometries in a specific CRS] (https://w3c.github.io/sdw/bp/#request-return-crs)
+
+#### Conformance statement
+- Does not conform
+
+OS Names API only operates in British National Grid (EPSG::27700)
+
+### [Best Practice 14: Include spatial metadata in dataset metadata](https://www.w3.org/TR/sdw-bp/#spatial-info-dataset-metadata)
 
 #### Conformance statement 
  - Conforms, but could be improved 
@@ -265,16 +272,17 @@ The API itself is purely machine to machine, however the links within it resolve
 #### To-do
 The metadata included the API response could included a human readable description.
 
-### [Best Practice 14: Describe the positional accuracy of spatial data](https://www.w3.org/TR/sdw-bp/#desc-accuracy)
+### [Best Practice 15: Describe the positional accuracy of spatial data](https://www.w3.org/TR/sdw-bp/#desc-accuracy)
 
 #### Conformance statement 
- - Does not conform 
+ - Conforms, but could be improved
 
 Test | Conforms?
 ---|---
-Check if the metadata contains at least one human and machine readable statement regarding positional accuracy | <ul><li>- [ ] </li></ul>
+Check if the metadata contains at least one human and machine readable statement regarding positional accuracy | <ul><li>- [x] </li></ul>
 Check that the kind of statement is relevant to the kind of data, e.g. not an absolute positional accuracy measure for Atlantis | <ul><li>- [ ] </li></ul>
 Checking whether the accuracy statement is actually correct is beyond the scope of this best practice. | <ul><li>- [ ] </li></ul>
 
 #### How-to
-No data is published regarding the positional accuracy in the reference dataset.
+The positional accuracy is expressed in the metadata of the dataset, not that of the service. It is expressed as an equivalent scale (1:25,000) which gives an implied positional accuracy.
+See https://osmetadata.astuntechnology.com/geonetwork/srv/eng/catalog.search#/metadata/d442b64c-c8c8-11e4-8731-1681e6b88ec1

bp/bpconfig.js

@@ -18,10 +18,16 @@ var respecConfig = {
       company: "Geonovum",
       companyURL: "https://www.geonovum.nl/"
     }, {
-			name: "Payam Barnaghi",
-			company: "University of Surrey",
-			companyURL: "https://www.surrey.ac.uk/"
-		}],
+	name: "Payam Barnaghi",
+	company: "University of Surrey",
+	companyURL: "https://www.surrey.ac.uk/"
+    }, {
+      name: "Timo Homburg",
+      company: "Hochschule Mainz University Of Applied Sciences",
+      companyURL: "https://www.hs-mainz.de/",
+      orcid: "0000-0002-9499-5840"
+    }, 
+    ],
     otherLinks: [
     {
       key: "Contributors",
@@ -33,6 +39,7 @@ var respecConfig = {
         { value: "Simon Cox" },
         { value: "François Daoust" },
         { value: "Andreas Harth" },
+        { value: "Iza Hurst" },
         { value: "Bart van Leeuwen" },
         { value: "Josh Lieberman" },
         { value: "Chris Little" },
@@ -45,7 +52,8 @@ var respecConfig = {
         { value: "Lars G. Svensson" },
         { value: "Kerry Taylor" },
         { value: "Erik Wilde" },
-	{ value: "Rob Atkinson" }
+	{ value: "Rob Atkinson" },
+	{ value: "Edward Lewis" }      
       ]
     }, {
       key: "OGC Document Number",
@@ -92,6 +100,12 @@ var respecConfig = {
         authors: ["Howard Butler", "Martin Daly", "Allan Doyle", "Sean Gillies", "Tim Schaub", "Christopher Schmidt"],
         date: "16 June 2008"
       },
+      "GeoPackage":{
+        href:"http://www.opengis.net/doc/IS/geopackage/1.3",
+        publisher:"OGC",
+	title:"OGC® GeoPackage Encoding Standard",	
+        date: "16 November 2021"
+      },	      
       "SIMPLE-FEATURES":{
         href:"http://www.opengeospatial.org/standards/sfa",
         publisher:"OGC",
@@ -280,7 +294,24 @@ var respecConfig = {
         "title":"FAIR Data Maturity Model. Specification and Guidelines (1.0)",
         "date": "2020"
       },
-
+      "OAEDR": {
+        "href":"https://docs.ogc.org/is/19-086r5/19-086r5.html",
+        "publisher": "OGC",
+        "title":"OGC API - Environmental Data Retrieval Standard",
+        "date": "2022"
+      },
+      "COG": {
+        "href":"https://www.cogeo.org/",
+        "publisher": "COG Geo",
+        "title":"Cloud Optimized GeoTIFF",
+        "date": "2021"
+      },
+      "ZARR": {
+        "href":"https://zarr.dev/",
+        "publisher": "Zarr community",
+        "title":"Zarr",
+        "date": "2022"
+      },
 // ALREADY IN SPECREF
 
 /*
@@ -353,15 +384,16 @@ var respecConfig = {
         date:"1 February 2006"
       },
 */
-/*
-      "ISO-19123": {
-        href:"https://www.iso.org/standard/40121.html",
-        title:"ISO 19123:2005 Geographic information -- Schema for coverage geometry and functions",
+
+      "ISO-19123-1:2022": {
+        href:"https://www.iso.org/standard/70743.html",
+        title:"ISO 19123:2022 Geographic information — Schema for coverage geometry and functions — Part 1: Fundamentals",
         authors:["ISO/TC 211"],
         publisher:"ISO",
-        date:"15 August 2005"
+        date:"2022",
+        status: "FDIS"
       },
-*/
+
 /*
       "ISO-19109": {
         href:"https://www.iso.org/standard/59193.html",