diff --git a/ogc-web-api-guidelines/OGC API EDR Part 1 Core Checklist V1.2 b/ogc-web-api-guidelines/OGC API EDR Part 1 Core Checklist V1.2
deleted file mode 100644
index 4ad9675a3..000000000
--- a/ogc-web-api-guidelines/OGC API EDR Part 1 Core Checklist V1.2	
+++ /dev/null
@@ -1,68 +0,0 @@
-## OGC API - Environmental Data Retrieval Part 1: Core Version 1.2
-
-To comply with [Policy Directive 50](https://portal.ogc.org/public_ogc/directives/directives.php#50), the following should be completed.
-
-See an example in the [OGC API - Common - Part 1: Core Standard](https://docs.ogc.org/is/19-072/19-072.html#_c483b499-4a80-4d7d-997e-100e0d89a0b3).
-
-
-
-| # | Principle | Discussion
-| -- | -- | --
-|	1	|	Don’t reinvent	|	
-|	2	|	Keep it simple and intuitive	|	
-|	3	|	Use well-known resource types	|	
-|	4	|	Construct consistent URIs	|	
-|	5	|	Use HTTP methods consistent with RFC 7231	|	
-|	6	|	Put selection criteria behind the ‘?’	|	
-|	7	|	Error handling and use of HTTP status codes	|	
-|	8	|	Use explicit list of HTTP status codes	|	
-|	9	|	Use of HTTP header	|	
-|	10	|	Allow flexible content negotiation	|	
-|	11	|	Pagination	|	
-|	12	|	Processing resources	|	
-|	13	|	Support metadata	|	
-|	14	|	Consider your security needs	|	
-|	15	|	API description	|	
-|	16	|	Use well-known identifiers	|	
-|	17	|	Use explicit relations	|	
-|	18	|	Support W3C cross-origin resource sharing	|	
-|	19	|	Resource encodings	|	
-|	20	|	Good APIs are testable from the beginning	|	
-|	21	|	Specify whether operations are safe and/or idempotent	|	
-|	22	|	Make resources discoverable	|	
-|	23	|	Make default behavior explicit	|	
-
-
-## OGC API - Environmental Data Retrieval - Part 2: Publish-Subscribe Workflows (version-number)
-
-To comply with [Policy Directive 50](https://portal.ogc.org/public_ogc/directives/directives.php#50), the following should be completed.
-
-See an example on the [OGC-Web-API-Guidelines](https://github.com/opengeospatial/OGC-Web-API-Guidelines/blob/master/Examples/API-Common-Core_api_guidelines.adoc) repo.
-
-
-| # | Principle | Discussion
-| -- | -- | --
-|	1	|	Don’t reinvent	|	
-|	2	|	Keep it simple and intuitive	|	
-|	3	|	Use well-known resource types	|	
-|	4	|	Construct consistent URIs	|	
-|	5	|	Use HTTP methods consistent with RFC 7231	|	
-|	6	|	Put selection criteria behind the ‘?’	|	
-|	7	|	Error handling and use of HTTP status codes	|	
-|	8	|	Use explicit list of HTTP status codes	|	
-|	9	|	Use of HTTP header	|	
-|	10	|	Allow flexible content negotiation	|	
-|	11	|	Pagination	|	
-|	12	|	Processing resources	|	
-|	13	|	Support metadata	|	
-|	14	|	Consider your security needs	|	
-|	15	|	API description	|	
-|	16	|	Use well-known identifiers	|	
-|	17	|	Use explicit relations	|	
-|	18	|	Support W3C cross-origin resource sharing	|	
-|	19	|	Resource encodings	|	
-|	20	|	Good APIs are testable from the beginning	|	
-|	21	|	Specify whether operations are safe and/or idempotent	|	
-|	22	|	Make resources discoverable	|	
-|	23	|	Make default behavior explicit	|	
-