From adc757c43be0be28dd1af0eca7dd763e91c185a1 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Wed, 9 Oct 2024 10:30:41 +0100 Subject: [PATCH 1/4] Update .gitignore Added vscode folder to.gitignore --- .gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index 3ecd8a2..f88c9bf 100644 --- a/.gitignore +++ b/.gitignore @@ -2,3 +2,4 @@ docs/*.html pending/ .github/workflows/*.yml +/.vscode From 3165dd3d782c22f6aa5863e200acd5b3b628feb6 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Wed, 9 Oct 2024 10:31:21 +0100 Subject: [PATCH 2/4] Update limitationsonpublicaccess.asciidoc Clarified guidance note 7 on Limitations on Public Access as per discussion on https://github.com/agiorguk/gemini/issues/61 --- docs/partials/limitationsonpublicaccess.asciidoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/partials/limitationsonpublicaccess.asciidoc b/docs/partials/limitationsonpublicaccess.asciidoc index 7659b03..3995679 100644 --- a/docs/partials/limitationsonpublicaccess.asciidoc +++ b/docs/partials/limitationsonpublicaccess.asciidoc @@ -49,7 +49,9 @@ https://www.legislation.gov.uk/uksi/2009/3157/regulation/9[Regulation 9(5)(g) of + Each has an entry with the full text, in the INSPIRE registry, http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess -. At least one limitation on public access shall give an INSPIRE reason +. At least one limitation on public access shall give an INSPIRE reason. +. If there is no applicable limitation listed in Article 13, then the closest limitation should be chosen, and +a second limitations on public access element should be used to provide further information. |Comment |Limitations on public access are different from Use constraints which are warnings about its suitability for particular From f5cfe93d6b7c3ff89e9f9e7ed22b580c277f88d7 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Wed, 9 Oct 2024 10:40:01 +0100 Subject: [PATCH 3/4] Update limitationsonpublicaccess.asciidoc Update revision date --- docs/partials/limitationsonpublicaccess.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/limitationsonpublicaccess.asciidoc b/docs/partials/limitationsonpublicaccess.asciidoc index 3995679..12031af 100644 --- a/docs/partials/limitationsonpublicaccess.asciidoc +++ b/docs/partials/limitationsonpublicaccess.asciidoc @@ -59,7 +59,7 @@ types of usage, or constraints on the use that can be made of the data. |Examples |No restriction on public access. -|Revision date |June 2021 +|Revision date |October 2024 |=== .Corresponding element in other standards... From 460a3c1bfcdbd738815d5e56f645c6a3d71dcde5 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Wed, 9 Oct 2024 10:50:14 +0100 Subject: [PATCH 4/4] Update limitationsonpublicaccess.asciidoc Incorporates suggested wording change from "should" to "shall" --- docs/partials/limitationsonpublicaccess.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/partials/limitationsonpublicaccess.asciidoc b/docs/partials/limitationsonpublicaccess.asciidoc index 12031af..ea123a9 100644 --- a/docs/partials/limitationsonpublicaccess.asciidoc +++ b/docs/partials/limitationsonpublicaccess.asciidoc @@ -50,7 +50,7 @@ https://www.legislation.gov.uk/uksi/2009/3157/regulation/9[Regulation 9(5)(g) of Each has an entry with the full text, in the INSPIRE registry, http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess . At least one limitation on public access shall give an INSPIRE reason. -. If there is no applicable limitation listed in Article 13, then the closest limitation should be chosen, and +. If there is no applicable limitation listed in Article 13, then the closest limitation shall be chosen, and a second limitations on public access element should be used to provide further information. |Comment |Limitations on public access are different from Use