From a9d4593e31f5dc9c291027a006cf0fc0ef60a15d Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Mon, 7 Nov 2022 15:26:07 +0000 Subject: [PATCH 01/54] Update README.md A test commit to the dev branch --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index bd43e39..af723d0 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,4 +1,4 @@ -# Gemini documentation +# Gemini documentation- dev branch Gemini web pages, converted from html to asciidoc, and back again! From 2a88355b9d4beb063aed89035dfdb128db699c3f Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Mon, 7 Nov 2022 15:53:21 +0000 Subject: [PATCH 02/54] Update README.md Force a change to dev branch --- docs/README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/README.md b/docs/README.md index af723d0..312e03a 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,7 +1,5 @@ # Gemini documentation- dev branch -Gemini web pages, converted from html to asciidoc, and back again! - * [Services](https://agiorguk.github.io/gemini/services.html) * [Datasets](https://agiorguk.github.io/gemini/datasets.html) From 062acd532ae29ecbf9acd6eb800ad0c8171dd434 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Mon, 7 Nov 2022 17:03:06 +0000 Subject: [PATCH 03/54] Update datasets.adoc Forcing a change to datasets.adoc to test dev workflow --- docs/datasets.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/datasets.adoc b/docs/datasets.adoc index ff86c59..e82c10b 100644 --- a/docs/datasets.adoc +++ b/docs/datasets.adoc @@ -1,4 +1,4 @@ -== [[top]]UK GEMINI 2.3 2020-04-07 dataset or series +== [[top]]UK GEMINI 2.3 2020-04-07 dataset or series dev version include::includes/attributes.asciidoc[] @@ -177,4 +177,4 @@ include::./partials/dataquality.asciidoc[] include::./partials/maintenanceinformation.asciidoc[] -Go to <> \ No newline at end of file +Go to <> From 9ddf0f8c82b0da0409e83b2177c9640ff070806a Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Tue, 8 Nov 2022 09:38:29 +0000 Subject: [PATCH 04/54] Clearly state "DEV BRANCH" in Readme --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 608c06f..843e498 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# gemini +# gemini DEV BRANCH Resources relating to the UK Gemini metadata profile The published version of GEMINI 2.3 lives at https://www.agi.org.uk/gemini/1037-uk-gemini-standard-and-inspire-implementing-rules/ From c3470c207dfae8f32677ad7253254af801d4bcfd Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Tue, 8 Nov 2022 10:53:27 +0000 Subject: [PATCH 05/54] Try floating the menu To bring the content nearer the top --- docs/datasets.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/datasets.adoc b/docs/datasets.adoc index e82c10b..bbce04b 100644 --- a/docs/datasets.adoc +++ b/docs/datasets.adoc @@ -4,7 +4,7 @@ include::includes/attributes.asciidoc[] == Contents -[width="100%",cols="50%,50%",options="header",] +[width="50%",cols="50%,50%",options="header",float="right",] |=== |Metadata about the metadata record |Metadata about the resource |<<45, File Identifier>> From 6701cd1507355692c1040475fbb0ff8da0d638a4 Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Tue, 8 Nov 2022 16:04:55 +0000 Subject: [PATCH 06/54] Update README.md Remove the misleading stuff --- README.md | 32 +------------------------------- 1 file changed, 1 insertion(+), 31 deletions(-) diff --git a/README.md b/README.md index 843e498..63fede4 100644 --- a/README.md +++ b/README.md @@ -3,34 +3,4 @@ Resources relating to the UK Gemini metadata profile The published version of GEMINI 2.3 lives at https://www.agi.org.uk/gemini/1037-uk-gemini-standard-and-inspire-implementing-rules/ -This is the place to raise and manage issues - -This repository does not contain the GEMINI Schematron and sample files, which are at https://github.com/agiorguk/gemini-schematron - -Contact gemini@agi.org.uk, or just raise an issue here. - -Meeting notes & actions - on https://github.com/agiorguk/gemini/wiki - -# guide to our labels -This is how we use the labels: - -| Label | Meaning | -| ----- | ------- | -|Guidance|We reckon this issue only affects informative parts of GEMINI| -|Breaking|We expect the solution to this issue to mean that previously valid instances will no longer be valid| -|documentation|We reckon this issue only affects documentation around GEMINI, not the actual elements| -|enhancement|We see this issue as a request for something extra| -|discussion|Probably a status - intended to mean 'the suggested solution requires more discussion'| -|Elements|This issue refers to one or more specific GEMINI elements| -|bug|it looks like somethings definitely broken; we're advising people to do something that is invalid| -|help wanted|whoever raised this issue is asking for help, not (yet) specifically saying something is wrong| -|Encoding|This issue primarily refers to the (XML) encoding of a GEMINI record| -|invalid|something that's wrong but probably not causing people to create invalid records| -|samples|This issue relates to the XML sample files (in the GEMINI-schematron repository)| - -Note: overlaps between "Guidance" and "documentation", "bug" and "invalid" - -Note: we have not firmly defined which parts of GEMINI are normative & which are informative. Roughly, the normative parts are: -- for each element: the GEMINI id, name, definition, "purpose and meaning", obligation, occurence, data type, and domain -- the general Encoding Guidance page: sections 2.2, 2.3, 2.4 -The rest are informative +This branch is for trying out solutions to issues From 11765bf84dafb825e97c3a1f4070341d7187c12a Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Tue, 8 Nov 2022 16:09:50 +0000 Subject: [PATCH 07/54] Update README.md Use relative links so that they go to files in the same repository --- docs/README.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/README.md b/docs/README.md index 312e03a..af25093 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,18 +1,18 @@ # Gemini documentation- dev branch -* [Services](https://agiorguk.github.io/gemini/services.html) -* [Datasets](https://agiorguk.github.io/gemini/datasets.html) +* [Services](services.html) +* [Datasets](datasets.html) The files below have been converted but have not been altered to work using the new workflow. Consequently internal links will go to the agi website and there may be other errors. -* [1037-uk-gemini-standard-and-inspire-implementing-rules](https://agiorguk.github.io/gemini/1037-uk-gemini-standard-and-inspire-implementing-rules.html) -* [1048-uk-gemini-encoding-guidance](https://agiorguk.github.io/gemini/1048-uk-gemini-encoding-guidance.html) -* [1049-metadata-guidelines-for-geospatial-data-resources-part-2](https://agiorguk.github.io/gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2.html) -* [1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources](https://agiorguk.github.io/gemini/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html) -* [1052-metadata-guidelines-for-geospatial-data-resources-part-1](https://agiorguk.github.io/gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1.html) -* [1053-common-metadata-errors-uk-location-discovery-metadata-service](https://agiorguk.github.io/gemini/1053-common-metadata-errors-uk-location-discovery-metadata-service.html) -* [1054-operational-guide](https://agiorguk.github.io/gemini/1054-operational-guide.html) -* [1055-uk-gemini-major-changes-since-1-0](https://agiorguk.github.io/gemini/1055-uk-gemini-major-changes-since-1-0.html) -* [1056-glossary](https://agiorguk.github.io/gemini/1056-glossary.html) +* [1037-uk-gemini-standard-and-inspire-implementing-rules](1037-uk-gemini-standard-and-inspire-implementing-rules.html) +* [1048-uk-gemini-encoding-guidance](1048-uk-gemini-encoding-guidance.html) +* [1049-metadata-guidelines-for-geospatial-data-resources-part-2](1049-metadata-guidelines-for-geospatial-data-resources-part-2.html) +* [1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources](1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html) +* [1052-metadata-guidelines-for-geospatial-data-resources-part-1](1052-metadata-guidelines-for-geospatial-data-resources-part-1.html) +* [1053-common-metadata-errors-uk-location-discovery-metadata-service](1053-common-metadata-errors-uk-location-discovery-metadata-service.html) +* [1054-operational-guide](1054-operational-guide.html) +* [1055-uk-gemini-major-changes-since-1-0](1055-uk-gemini-major-changes-since-1-0.html) +* [1056-glossary](1056-glossary.html) ## Services and Datasets workflow @@ -37,4 +37,4 @@ docker run --rm -v $(pwd):/documents/ asciidoctor/docker-asciidoctor asciidoctor ## Styling -All files share a common attributes file, which indicates the basic attributes to be used when processing. This includes a linked reference to the asciidoc html stylesheet rather than the default embedding. Work has begun to integrate the styling from [Gemini.css](https://github.com/archaeogeek/gemini/blob/main/docs/Gemini.css) into [asciidoctor.css](https://github.com/archaeogeek/gemini/blob/main/docs/assets/asciidoctor.css) but this is far from complete. +All files share a common attributes file, which indicates the basic attributes to be used when processing. This includes a linked reference to the asciidoc html stylesheet rather than the default embedding. Work has begun to integrate the styling from [Gemini.css](blob/main/docs/Gemini.css) into [asciidoctor.css](blob/main/docs/assets/asciidoctor.css) but this is far from complete. From 16f1c55c217ceb5151499ceec79fea90adc98841 Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Tue, 8 Nov 2022 16:16:37 +0000 Subject: [PATCH 08/54] Link to the GitPages Allows developer to see what they have achieved! --- docs/README.md | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/docs/README.md b/docs/README.md index af25093..3b2ce00 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,19 +1,20 @@ # Gemini documentation- dev branch -* [Services](services.html) -* [Datasets](datasets.html) +* [Services](https://archaeogeek.github.io/gemini-dev/services.html) +* [Datasets](https://archaeogeek.github.io/gemini-dev/datasets.html) The files below have been converted but have not been altered to work using the new workflow. Consequently internal links will go to the agi website and there may be other errors. -* [1037-uk-gemini-standard-and-inspire-implementing-rules](1037-uk-gemini-standard-and-inspire-implementing-rules.html) -* [1048-uk-gemini-encoding-guidance](1048-uk-gemini-encoding-guidance.html) -* [1049-metadata-guidelines-for-geospatial-data-resources-part-2](1049-metadata-guidelines-for-geospatial-data-resources-part-2.html) -* [1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources](1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html) -* [1052-metadata-guidelines-for-geospatial-data-resources-part-1](1052-metadata-guidelines-for-geospatial-data-resources-part-1.html) -* [1053-common-metadata-errors-uk-location-discovery-metadata-service](1053-common-metadata-errors-uk-location-discovery-metadata-service.html) -* [1054-operational-guide](1054-operational-guide.html) -* [1055-uk-gemini-major-changes-since-1-0](1055-uk-gemini-major-changes-since-1-0.html) -* [1056-glossary](1056-glossary.html) - +* [1037-uk-gemini-standard-and-inspire-implementing-rules](https://archaeogeek.github.io/gemini-dev/1037-uk-gemini-standard-and-inspire-implementing-rules.html) +* [1048-uk-gemini-encoding-guidance](https://archaeogeek.github.io/gemini-dev/1048-uk-gemini-encoding-guidance.html) +* [1049-metadata-guidelines-for-geospatial-data-resources-part-2](https://archaeogeek.github.io/gemini-dev/1049-metadata-guidelines-for-geospatial-data-resources-part-2.html) +* [1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources](https://archaeogeek.github.io/gemini-dev/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html) +* [1052-metadata-guidelines-for-geospatial-data-resources-part-1](https://archaeogeek.github.io/gemini-dev/1052-metadata-guidelines-for-geospatial-data-resources-part-1.html) +* [1053-common-metadata-errors-uk-location-discovery-metadata-service](https://archaeogeek.github.io/gemini-dev/1053-common-metadata-errors-uk-location-discovery-metadata-service.html) +* [1054-operational-guide](https://archaeogeek.github.io/gemini-dev/1054-operational-guide.html) +* [1055-uk-gemini-major-changes-since-1-0](https://archaeogeek.github.io/gemini-dev/1055-uk-gemini-major-changes-since-1-0.html) +* [1056-glossary](https://archaeogeek.github.io/gemini-dev/1056-glossary.html) + +Links above this are to the Gitpages published in https://archaeogeek.github.io/gemini-dev/ ## Services and Datasets workflow * These files are generated from [include files](https://docs.asciidoctor.org/asciidoc/latest/directives/include/), one per element, in the [docs/partials](https://github.com/archaeogeek/gemini/tree/main/docs/partials) folder. From c9b931e7663b340602393bc9fd476849ef0b3f39 Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Tue, 8 Nov 2022 16:22:44 +0000 Subject: [PATCH 09/54] Update abstract.asciidoc https://docs.asciidoctor.org/asciidoc/latest/blocks/collapsible/ suggests that we can provide our own 'clickable text' instead of the default "Details". I have only done that to this element as an experiment to check it works. --- docs/partials/abstract.asciidoc | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/docs/partials/abstract.asciidoc b/docs/partials/abstract.asciidoc index d8367af..5e32934 100644 --- a/docs/partials/abstract.asciidoc +++ b/docs/partials/abstract.asciidoc @@ -54,8 +54,7 @@ the United Kingdom as at February 2017. |Revision date |March 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -80,8 +79,7 @@ Change history... [[history4]] -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -101,9 +99,8 @@ endif::[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available -==== \ No newline at end of file +==== From 8cbac120317c6bb0fd855b3f29021a00ce464c97 Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Tue, 8 Nov 2022 16:27:25 +0000 Subject: [PATCH 10/54] Update README.md Link to where you should see the output of changes --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 63fede4..2b0e8fb 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,8 @@ # gemini DEV BRANCH Resources relating to the UK Gemini metadata profile +Pull requests accepted to this branch get published to the GitPages repository at https://archaeogeek.github.io/gemini-dev/ + The published version of GEMINI 2.3 lives at https://www.agi.org.uk/gemini/1037-uk-gemini-standard-and-inspire-implementing-rules/ This branch is for trying out solutions to issues From 1cb0effa844ac2df3a5ffe78b1d67d69f50227f0 Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Mon, 28 Nov 2022 15:49:52 +0000 Subject: [PATCH 11/54] Reducing size of Index table Remove "float" trial; make as two cells, like in the current GEMINI --- docs/datasets.adoc | 122 ++++++++++++++------------------------------- 1 file changed, 38 insertions(+), 84 deletions(-) diff --git a/docs/datasets.adoc b/docs/datasets.adoc index bbce04b..f19bef9 100644 --- a/docs/datasets.adoc +++ b/docs/datasets.adoc @@ -4,92 +4,46 @@ include::includes/attributes.asciidoc[] == Contents -[width="50%",cols="50%,50%",options="header",float="right",] +[width="50%",cols="50%,50%",options="header",] |=== |Metadata about the metadata record |Metadata about the resource -|<<45, File Identifier>> -|<<4, Abstract>> - -|<<47, Hierarchy level name>> -|<<27, Additional information>> - -|<<30, Metadata date>> -|<<2, Alternative title>> - -|<<33, Metadata language>> -|<<44, Bounding box>> - -|<<35, Metadata point of contact>> -|<<51, Character encoding>> - -|<<54, Metadata standard name>> -|<<41, Conformity>> - -|<<55, Metadata standard version>> -|<<21, Data format>> - -|<<49, Parent identifier>> -|<<52, Data quality>> - -|<<39, Resource type>> -|<<3, Dataset language>> - -| -|<<8, Dataset reference date>> - -| -|<<43, Equivalent scale>> - -| -|<<15, Extent>> - -| -|<<6, Keyword>> - -| -|<<25, Limitations on public access>> - -| -|<<10, Lineage>> - -| -|<<53, Maintenance information>> - -| -|<<48, Quality scope>> - -| -|<<36, Resource identifier>> - -| -|<<19, Resource locator>> - -| -|<<23, Responsible organisation>> - -| -|<<17, Spatial reference system>> - -| -|<<50, Spatial representation type>> - -| -|<<18, Spatial resolution>> - -| -|<<7, Temporal extent>> - -| -|<<1, Title>> - -| -|<<5, Topic Category>> - -| -|<<26, Use constraints>> - -| -|<<16, Vertical extent information>> +|<<45, File Identifier>> + +<<47, Hierarchy level name>> + +<<30, Metadata date>> + +<<33, Metadata language>> + +<<35, Metadata point of contact>> + +<<54, Metadata standard name>> + +<<55, Metadata standard version>> + +<<49, Parent identifier>> + +<<39, Resource type>> + +|<<4, Abstract>> + +<<27, Additional information>> + +<<2, Alternative title>> + +<<44, Bounding box>> + +<<51, Character encoding>> + +<<41, Conformity>> + +<<21, Data format>> + +<<52, Data quality>> + +<<3, Dataset language>> + +<<8, Dataset reference date>> + +<<43, Equivalent scale>> + +<<15, Extent>> + +<<6, Keyword>> + +<<25, Limitations on public access>> + +<<10, Lineage>> + +<<53, Maintenance information>> + +<<48, Quality scope>> + +<<36, Resource identifier>> + +<<19, Resource locator>> + +<<23, Responsible organisation>> + +<<17, Spatial reference system>> + +<<50, Spatial representation type>> + +<<18, Spatial resolution>> + +<<7, Temporal extent>> + +<<1, Title>> + +<<5, Topic Category>> + +<<26, Use constraints>> + +<<16, Vertical extent information>> + |=== Return to link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI From bdcaae95c49eea4c1e7f349b56432d165460aa4b Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Tue, 20 Dec 2022 14:51:36 +0000 Subject: [PATCH 12/54] Update README.md Changed title to say this is the dev branch, while working through step by step guide to editing in place --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index bd43e39..bc35ec7 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,4 +1,4 @@ -# Gemini documentation +# Gemini documentation DEV branch Gemini web pages, converted from html to asciidoc, and back again! From f2a7864a5990e411667a600845c8692011a9a3c2 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Tue, 20 Dec 2022 14:58:48 +0000 Subject: [PATCH 13/54] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2b0e8fb..3f2e71b 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ # gemini DEV BRANCH Resources relating to the UK Gemini metadata profile -Pull requests accepted to this branch get published to the GitPages repository at https://archaeogeek.github.io/gemini-dev/ +Pull requests accepted to this branch get published to the GitPages repository at https://agiorguk.github.io/gemini-dev/ The published version of GEMINI 2.3 lives at https://www.agi.org.uk/gemini/1037-uk-gemini-standard-and-inspire-implementing-rules/ From 89dfed0b26a4f64d47d7d537ead58c48b66f17bc Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Tue, 20 Dec 2022 15:32:04 +0000 Subject: [PATCH 14/54] Update README.md Changed the two absolute URLs to the correct domain --- docs/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/README.md b/docs/README.md index 229b6ca..214bd97 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,8 +1,8 @@ # Gemini documentation DEV branch -* [Services](https://archaeogeek.github.io/gemini-dev/services.html) -* [Datasets](https://archaeogeek.github.io/gemini-dev/datasets.html) +* [Services](https://agiorguk.github.io/gemini-dev/services.html) +* [Datasets](https://agiorguk.github.io/gemini-dev/datasets.html) The files below have been converted but have not been altered to work using the new workflow. Consequently internal links will go to the agi website and there may be other errors. * [1037-uk-gemini-standard-and-inspire-implementing-rules](https://archaeogeek.github.io/gemini-dev/1037-uk-gemini-standard-and-inspire-implementing-rules.html) From 8e3f394c4fa3bbe00ad4d6a0e0124a3e115af8c2 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Tue, 20 Dec 2022 15:35:16 +0000 Subject: [PATCH 15/54] Update dev-build.yml --- .github/workflows/dev-build.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/dev-build.yml b/.github/workflows/dev-build.yml index aa15a38..66d7dd2 100644 --- a/.github/workflows/dev-build.yml +++ b/.github/workflows/dev-build.yml @@ -27,7 +27,7 @@ jobs: uses: peaceiris/actions-gh-pages@v3 with: personal_token: ${{ secrets.API_TOKEN_GITHUB }} - external_repository: archaeogeek/gemini-dev + external_repository: agiorguk/gemini-dev publish_branch: gh-pages publish_dir: ./docs/ enable_jekyll: true From 0fd811eb7b370ab97996dab6e7d1dafbf3ee5141 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Mon, 16 Jan 2023 11:20:31 +0000 Subject: [PATCH 16/54] Changed gemini css to handle asciidoc collapsible blocks more like links, and changed the metadatadate partial to show how it works --- docs/assets/gemini.css | 11 ++++++++++- docs/partials/metadatadate.asciidoc | 12 ++++-------- 2 files changed, 14 insertions(+), 9 deletions(-) diff --git a/docs/assets/gemini.css b/docs/assets/gemini.css index d2e73c9..e8502d3 100644 --- a/docs/assets/gemini.css +++ b/docs/assets/gemini.css @@ -17,6 +17,15 @@ table th, table td { } table { - border: 1px solid #f2f2f2; + border: 1px solid #f2f2​f2; } +details { + color: rgb(40,158,197); + cursor: pointer; + list-style: disclosure-closed inside; +} + +details .content { + color: rgb(103, 97, 97); +} \ No newline at end of file diff --git a/docs/partials/metadatadate.asciidoc b/docs/partials/metadatadate.asciidoc index 7af6ddf..820fb49 100644 --- a/docs/partials/metadatadate.asciidoc +++ b/docs/partials/metadatadate.asciidoc @@ -42,8 +42,7 @@ date when it was created. |Revision date |May 2018 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -54,15 +53,13 @@ Corresponding element in other standards... |=== ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: Change of name from Date of last update of metadata ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -86,8 +83,7 @@ include::../snippets/metadatadatetime.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== |=== From 0b14611e1e57a52e0281cac52c9eebd279359589 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Mon, 16 Jan 2023 12:18:38 +0000 Subject: [PATCH 17/54] Update 1055-uk-gemini-major-changes-since-1-0.asciidoc Added a colon to make the list styling more consistent throughout --- docs/1055-uk-gemini-major-changes-since-1-0.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/1055-uk-gemini-major-changes-since-1-0.asciidoc b/docs/1055-uk-gemini-major-changes-since-1-0.asciidoc index ff53491..77c3eb3 100644 --- a/docs/1055-uk-gemini-major-changes-since-1-0.asciidoc +++ b/docs/1055-uk-gemini-major-changes-since-1-0.asciidoc @@ -25,7 +25,7 @@ elements, which were already required to encode the record: * There are two additional conditional elements: ** Character encoding ** Data quality -* Four elements have been made mandatory +* Four elements have been made mandatory: ** Conformity ** Dataset language ** Data format @@ -408,4 +408,4 @@ http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/ Commons Licence]] + This work is licensed under a{nbsp}http://creativecommons.org/licenses/by/4.0/[Creative Commons -Attribution 4.0 International License] \ No newline at end of file +Attribution 4.0 International License] From d75f3010517140f9d123d6a2f1178f7d1575cf2d Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Mon, 16 Jan 2023 13:28:23 +0000 Subject: [PATCH 18/54] Updated static URLs in docs readme --- docs/README.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/README.md b/docs/README.md index 214bd97..43df92a 100644 --- a/docs/README.md +++ b/docs/README.md @@ -5,20 +5,20 @@ * [Datasets](https://agiorguk.github.io/gemini-dev/datasets.html) The files below have been converted but have not been altered to work using the new workflow. Consequently internal links will go to the agi website and there may be other errors. -* [1037-uk-gemini-standard-and-inspire-implementing-rules](https://archaeogeek.github.io/gemini-dev/1037-uk-gemini-standard-and-inspire-implementing-rules.html) -* [1048-uk-gemini-encoding-guidance](https://archaeogeek.github.io/gemini-dev/1048-uk-gemini-encoding-guidance.html) -* [1049-metadata-guidelines-for-geospatial-data-resources-part-2](https://archaeogeek.github.io/gemini-dev/1049-metadata-guidelines-for-geospatial-data-resources-part-2.html) -* [1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources](https://archaeogeek.github.io/gemini-dev/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html) -* [1052-metadata-guidelines-for-geospatial-data-resources-part-1](https://archaeogeek.github.io/gemini-dev/1052-metadata-guidelines-for-geospatial-data-resources-part-1.html) -* [1053-common-metadata-errors-uk-location-discovery-metadata-service](https://archaeogeek.github.io/gemini-dev/1053-common-metadata-errors-uk-location-discovery-metadata-service.html) -* [1054-operational-guide](https://archaeogeek.github.io/gemini-dev/1054-operational-guide.html) -* [1055-uk-gemini-major-changes-since-1-0](https://archaeogeek.github.io/gemini-dev/1055-uk-gemini-major-changes-since-1-0.html) -* [1056-glossary](https://archaeogeek.github.io/gemini-dev/1056-glossary.html) - -Links above this are to the Gitpages published in https://archaeogeek.github.io/gemini-dev/ +* [1037-uk-gemini-standard-and-inspire-implementing-rules](https://agiorguk.github.io/gemini-dev/1037-uk-gemini-standard-and-inspire-implementing-rules.html) +* [1048-uk-gemini-encoding-guidance](https://agiorguk.github.io/gemini-dev/1048-uk-gemini-encoding-guidance.html) +* [1049-metadata-guidelines-for-geospatial-data-resources-part-2](https://agiorguk.github.io/gemini-dev/1049-metadata-guidelines-for-geospatial-data-resources-part-2.html) +* [1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources](https://agiorguk.github.io/gemini-dev/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html) +* [1052-metadata-guidelines-for-geospatial-data-resources-part-1](https://agiorguk.github.io/gemini-dev/1052-metadata-guidelines-for-geospatial-data-resources-part-1.html) +* [1053-common-metadata-errors-uk-location-discovery-metadata-service](https://agiorguk.github.io/gemini-dev/1053-common-metadata-errors-uk-location-discovery-metadata-service.html) +* [1054-operational-guide](https://agiorguk.github.io/gemini-dev/1054-operational-guide.html) +* [1055-uk-gemini-major-changes-since-1-0](https://agiorguk.github.io/gemini-dev/1055-uk-gemini-major-changes-since-1-0.html) +* [1056-glossary](https://agiorguk.github.io/gemini-dev/1056-glossary.html) + +Links above this are to the Gitpages published in https://agiorguk.github.io/gemini-dev/ ## Services and Datasets workflow -* These files are generated from [include files](https://docs.asciidoctor.org/asciidoc/latest/directives/include/), one per element, in the [docs/partials](https://github.com/archaeogeek/gemini/tree/main/docs/partials) folder. +* These files are generated from [include files](https://docs.asciidoctor.org/asciidoc/latest/directives/include/), one per element, in the [docs/partials](https://github.com/agiorguk/gemini/tree/main/docs/partials) folder. * The xml snippets are in the docs/snippets folder. * The naming convention for the element files is {element name in lower case without spaces}.asciidoc * The naming convention for the xml snippets is {optional dataset or service prefix}-{element name in lower case without spaces}-{optional specific example}.xml From 36c6a5181cf43aa17775619f48301842c95b9a5d Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Mon, 16 Jan 2023 13:54:38 +0000 Subject: [PATCH 19/54] Updated all the partials asciidoc files with the new style for the collapsible elements --- docs/partials/additionalinformation.asciidoc | 12 ++++-------- docs/partials/alternatetitle.asciidoc | 11 ++++------- docs/partials/boundingbox.asciidoc | 12 ++++-------- docs/partials/characterencoding.asciidoc | 12 ++++-------- docs/partials/conformity.asciidoc | 12 ++++-------- docs/partials/coupledresource.asciidoc | 12 ++++-------- docs/partials/dataformat.asciidoc | 12 ++++-------- docs/partials/dataquality.asciidoc | 12 ++++-------- docs/partials/datasetlanguage.asciidoc | 12 ++++-------- docs/partials/datasetreferencedate.asciidoc | 12 ++++-------- docs/partials/equivalentscale.asciidoc | 12 ++++-------- docs/partials/extent.asciidoc | 12 ++++-------- docs/partials/fileidentifier.asciidoc | 12 ++++-------- docs/partials/hierarchylevelname.asciidoc | 9 +++------ docs/partials/keyword.asciidoc | 12 ++++-------- docs/partials/limitationsonpublicaccess.asciidoc | 12 ++++-------- docs/partials/lineage.asciidoc | 12 ++++-------- docs/partials/maintenanceinformation.asciidoc | 12 ++++-------- docs/partials/metadatalanguage.asciidoc | 12 ++++-------- docs/partials/metadatapointofcontact.asciidoc | 12 ++++-------- docs/partials/metadatastandardname.asciidoc | 12 ++++-------- docs/partials/metadatastandardversion.asciidoc | 12 ++++-------- docs/partials/parentidentifier.asciidoc | 12 ++++-------- docs/partials/qualityscope.asciidoc | 12 ++++-------- docs/partials/resourceidentifier.asciidoc | 12 ++++-------- docs/partials/resourcelocator.asciidoc | 12 ++++-------- docs/partials/resourcetype.asciidoc | 12 ++++-------- docs/partials/responsibleorganisation.asciidoc | 12 ++++-------- docs/partials/spatialdataservicetype.asciidoc | 12 ++++-------- docs/partials/spatialreferencesystem.asciidoc | 12 ++++-------- docs/partials/spatialrepresentationtype.asciidoc | 12 ++++-------- docs/partials/spatialresolution.asciidoc | 12 ++++-------- docs/partials/temporalextent.asciidoc | 12 ++++-------- docs/partials/title.asciidoc | 9 +++------ docs/partials/topiccategory.asciidoc | 9 +++------ docs/partials/useconstraints.asciidoc | 9 +++------ docs/partials/verticalextent.asciidoc | 12 ++++-------- 37 files changed, 144 insertions(+), 287 deletions(-) diff --git a/docs/partials/additionalinformation.asciidoc b/docs/partials/additionalinformation.asciidoc index 26fcfcd..bc69d03 100644 --- a/docs/partials/additionalinformation.asciidoc +++ b/docs/partials/additionalinformation.asciidoc @@ -37,8 +37,7 @@ link which is given in this element. |Revision date |June 2021 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -55,8 +54,7 @@ MD_DataIdentification.supplementalInformation |Equivalent |=== ==== -Change history... - +.Change history... [%collapsible] ==== * GEMINI 2.3 20181031 Rename 'Additional information source' to @@ -64,8 +62,7 @@ Change history... * GEMINI 2.3 June 2021 fixed typo (XML syntax error) in example 2 ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== [width="100%",cols="50%,50%",] @@ -88,8 +85,7 @@ include::../snippets/additionalinformation-anchor.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/alternatetitle.asciidoc b/docs/partials/alternatetitle.asciidoc index 647ad04..26e0238 100644 --- a/docs/partials/alternatetitle.asciidoc +++ b/docs/partials/alternatetitle.asciidoc @@ -39,8 +39,7 @@ different data resource). |Revision date |May 2021 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -63,9 +62,8 @@ endif::[] |=== ==== -Change history... - -Encoding guidelines... +.Change history... +[%collapsible]ncoding guidelines... [%collapsible] ==== @@ -96,8 +94,7 @@ endif::[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/boundingbox.asciidoc b/docs/partials/boundingbox.asciidoc index 5b53a50..a13c081 100644 --- a/docs/partials/boundingbox.asciidoc +++ b/docs/partials/boundingbox.asciidoc @@ -69,8 +69,7 @@ related to the area covered by the resource. |Revision date |December 2012 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -95,8 +94,7 @@ endif::[] |=== ==== -Change history... - +.Change history... [%collapsible] ==== * GEMINI 1 to 2.0: Slight change of name of each element @@ -104,8 +102,7 @@ Change history... Bounding box, which was made multiple ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -147,8 +144,7 @@ endif::[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== |=== diff --git a/docs/partials/characterencoding.asciidoc b/docs/partials/characterencoding.asciidoc index 3893ad5..a2909e7 100644 --- a/docs/partials/characterencoding.asciidoc +++ b/docs/partials/characterencoding.asciidoc @@ -32,8 +32,7 @@ guidance as interoperability metadata for datasets and dataset series |Revision date |May 2018 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -51,15 +50,13 @@ references: B.5.10 MD_CharacterSetCode CodeList |Equivalent |=== ==== -Change history... - +.Change history... [%collapsible] ==== New element in GEMINI 2.3 ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -75,8 +72,7 @@ include::../snippets/characterencoding.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/conformity.asciidoc b/docs/partials/conformity.asciidoc index 06d74e3..814e8c8 100644 --- a/docs/partials/conformity.asciidoc +++ b/docs/partials/conformity.asciidoc @@ -96,8 +96,7 @@ and would give a publication date of 2010-12-08 |Revision date |April 2020 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -114,8 +113,7 @@ DQ_ConformanceResult |Equivalent |=== ==== -Change history... - +.Change history... [%collapsible] ==== * GEMINI 1 to 2.0: New element @@ -123,8 +121,7 @@ Change history... been tested against the relevant INSPIRE specification ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== [width="100%",cols="50%,50%",] @@ -180,8 +177,7 @@ endif::[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== |=== diff --git a/docs/partials/coupledresource.asciidoc b/docs/partials/coupledresource.asciidoc index af85645..eb04801 100644 --- a/docs/partials/coupledresource.asciidoc +++ b/docs/partials/coupledresource.asciidoc @@ -34,8 +34,7 @@ This may be: |Revision date |March 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -51,15 +50,13 @@ Corresponding element in other standards... |=== ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: New element, required for INSPIRE ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -144,8 +141,7 @@ element of the dataset metadata record, like below |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== |=== diff --git a/docs/partials/dataformat.asciidoc b/docs/partials/dataformat.asciidoc index e25fb56..2d91377 100644 --- a/docs/partials/dataformat.asciidoc +++ b/docs/partials/dataformat.asciidoc @@ -42,8 +42,7 @@ versioned, a nil reason attribute shall be specified with either |Revision date |March 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -58,16 +57,14 @@ Corresponding element in other standards... |=== ==== -Change history... - +.Change history... [%collapsible] ==== . GEMINI 1 to 2.0: made optional . GEMINI 2.2 to 2.3: made mandatory, but removed from services ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -90,8 +87,7 @@ include::../snippets/dataformat-name-unknownversion.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== |=== diff --git a/docs/partials/dataquality.asciidoc b/docs/partials/dataquality.asciidoc index 3c6375d..e14a93e 100644 --- a/docs/partials/dataquality.asciidoc +++ b/docs/partials/dataquality.asciidoc @@ -228,8 +228,7 @@ guidance as interoperability metadata for datasets and dataset series |Revision date |May 2018 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -249,15 +248,13 @@ Other types are specified in the data specifications | |=== ==== -Change history... - +.Change history... [%collapsible] ==== New element in GEMINI 2.3 ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -311,8 +308,7 @@ include::../snippets/dataquality-topo-quantitative.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/datasetlanguage.asciidoc b/docs/partials/datasetlanguage.asciidoc index 346fc68..47aa9c3 100644 --- a/docs/partials/datasetlanguage.asciidoc +++ b/docs/partials/datasetlanguage.asciidoc @@ -53,8 +53,7 @@ content; not applicable" shall be used. |Revision date |September 2018 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -71,16 +70,14 @@ Corresponding element in other standards... |=== ==== -Change history... - +.Change history... [%collapsible] ==== . GEMINI 1 to 2: Obligation changed from mandatory . GEMINI 2 to 2.2: Obligation changed (back) to mandatory ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== [width="100%",cols="50%,50%",] @@ -109,8 +106,7 @@ include::../snippets/datasetlanguage.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/datasetreferencedate.asciidoc b/docs/partials/datasetreferencedate.asciidoc index 0e8981a..1834048 100644 --- a/docs/partials/datasetreferencedate.asciidoc +++ b/docs/partials/datasetreferencedate.asciidoc @@ -76,8 +76,7 @@ should be reported for spatial datasets |Revision date |March 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -101,15 +100,13 @@ endif::[] ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: Addition of date type ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -154,8 +151,7 @@ endif::[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== |=== diff --git a/docs/partials/equivalentscale.asciidoc b/docs/partials/equivalentscale.asciidoc index 6f459b0..ce9d8b9 100644 --- a/docs/partials/equivalentscale.asciidoc +++ b/docs/partials/equivalentscale.asciidoc @@ -32,8 +32,7 @@ distance cannot be determined. |Revision date |July 2009 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -56,15 +55,13 @@ endif::[] |=== ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: New element ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -90,8 +87,7 @@ endif::[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/extent.asciidoc b/docs/partials/extent.asciidoc index a93dc57..cb9a900 100644 --- a/docs/partials/extent.asciidoc +++ b/docs/partials/extent.asciidoc @@ -54,8 +54,7 @@ NERC Vocabulary "C64, United Kingdom Charting Progress 2 sea regions" |Revision date |August 2010 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -84,15 +83,13 @@ endif::[] ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: Made optional ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -155,8 +152,7 @@ endif::[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/fileidentifier.asciidoc b/docs/partials/fileidentifier.asciidoc index f80d53c..9f40bff 100644 --- a/docs/partials/fileidentifier.asciidoc +++ b/docs/partials/fileidentifier.asciidoc @@ -46,8 +46,7 @@ resource being described. + |Revision date |March 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -58,16 +57,14 @@ Corresponding element in other standards... |=== ==== -Change history... - +.Change history... [%collapsible] ==== * introduced in the UK Location application profile and XML encoding * New element in GEMINI 2.3 ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -90,8 +87,7 @@ include::../snippets/fileidentifier.xml[] [%collapsible] ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== |=== diff --git a/docs/partials/hierarchylevelname.asciidoc b/docs/partials/hierarchylevelname.asciidoc index d5df3cd..cd7214e 100644 --- a/docs/partials/hierarchylevelname.asciidoc +++ b/docs/partials/hierarchylevelname.asciidoc @@ -33,8 +33,7 @@ hierarchyLevel) is not "dataset". |Revision date |April 2020 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -49,15 +48,13 @@ series |Equivalent |=== ==== -Change history... - +.Change history... [%collapsible] ==== New element in GEMINI 2.3 ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== diff --git a/docs/partials/keyword.asciidoc b/docs/partials/keyword.asciidoc index 3930fd5..c06a992 100644 --- a/docs/partials/keyword.asciidoc +++ b/docs/partials/keyword.asciidoc @@ -83,8 +83,7 @@ broader range of values. |Revision date |May 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -107,8 +106,7 @@ endif::[] |=== ==== -Change history... - +.Change history... [%collapsible] ==== . GEMINI 1 to 2.0: Change of name from 'Subject' @@ -116,8 +114,7 @@ Change history... controlled vocabulary ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -209,8 +206,7 @@ endif::[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== |=== diff --git a/docs/partials/limitationsonpublicaccess.asciidoc b/docs/partials/limitationsonpublicaccess.asciidoc index c5b8934..23ae226 100644 --- a/docs/partials/limitationsonpublicaccess.asciidoc +++ b/docs/partials/limitationsonpublicaccess.asciidoc @@ -52,8 +52,7 @@ types of usage, or constraints on the use that can be made of the data. |Revision date |June 2021 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -76,8 +75,7 @@ endif::[] |=== ==== -Change history... - +.Change history... [%collapsible] ==== . GEMINI 1 to 2.0: Change of name from 'access constraint', and @@ -89,8 +87,7 @@ accessConstraint making domain free text. . GEMINI 2.3 June 2021 fixed typo in Guidance 6 (a) and (f) ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== [width="100%",cols="50%,50%",] @@ -142,8 +139,7 @@ include::../snippets/limitationsonpublicaccess-twolimitations.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== |=== diff --git a/docs/partials/lineage.asciidoc b/docs/partials/lineage.asciidoc index 783de35..6951e72 100644 --- a/docs/partials/lineage.asciidoc +++ b/docs/partials/lineage.asciidoc @@ -47,8 +47,7 @@ addresses on the map and visually checking for errors. |Revision date |March 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -65,16 +64,14 @@ Corresponding element in other standards... |=== ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: Made mandatory for datasets and dataset series to conform to INSPIRE ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -97,8 +94,7 @@ include::../snippets/lineage.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/maintenanceinformation.asciidoc b/docs/partials/maintenanceinformation.asciidoc index a8ef409..82ca392 100644 --- a/docs/partials/maintenanceinformation.asciidoc +++ b/docs/partials/maintenanceinformation.asciidoc @@ -58,8 +58,7 @@ theme specific information |Revision date |April 2020 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -76,15 +75,13 @@ more than one resourceMaintenance |=== ==== -Change history... - +.Change history... [%collapsible] ==== New element in GEMINI 2.3 ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -99,8 +96,7 @@ include::../snippets/maintenanceinformation.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/metadatalanguage.asciidoc b/docs/partials/metadatalanguage.asciidoc index a63ebbb..2df2bba 100644 --- a/docs/partials/metadatalanguage.asciidoc +++ b/docs/partials/metadatalanguage.asciidoc @@ -55,8 +55,7 @@ official European languages, such as English or Irish. |Revision date |September 2018 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -71,16 +70,14 @@ Corresponding element in other standards... |=== ==== -Change history... - +.Change history... [%collapsible] ==== [[history33]] GEMINI 1 to 2.0: New element ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== [width="100%",cols="50%,50%",] @@ -97,8 +94,7 @@ include::../snippets/metadatadate.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== [width="100%",cols="50%,50%",] diff --git a/docs/partials/metadatapointofcontact.asciidoc b/docs/partials/metadatapointofcontact.asciidoc index 81ae3f9..7a2fead 100644 --- a/docs/partials/metadatapointofcontact.asciidoc +++ b/docs/partials/metadatapointofcontact.asciidoc @@ -30,8 +30,7 @@ as described under Responsible party. |Revision date |July 2009 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -46,15 +45,13 @@ has a general class |=== ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: New element ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -78,8 +75,7 @@ include::../snippets/metadatapointofcontact.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/metadatastandardname.asciidoc b/docs/partials/metadatastandardname.asciidoc index 7533891..475890d 100644 --- a/docs/partials/metadatastandardname.asciidoc +++ b/docs/partials/metadatastandardname.asciidoc @@ -36,8 +36,7 @@ NERC vocab server, contact GEMINI at AGI |Revision date |January 2020 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -52,16 +51,14 @@ guidance |=== ==== -Change history... - +.Change history... [%collapsible] ==== * GEMINI 1 to 2.0: deleted * GEMINI 2.3 September 2020: reinstated ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -88,8 +85,7 @@ include::../snippets/metadatastandardname-medin.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/metadatastandardversion.asciidoc b/docs/partials/metadatastandardversion.asciidoc index d4e905d..e4674ea 100644 --- a/docs/partials/metadatastandardversion.asciidoc +++ b/docs/partials/metadatastandardversion.asciidoc @@ -33,8 +33,7 @@ metadata system to another. |Revision date |June 2021 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -49,8 +48,7 @@ guidance |=== ==== -Change history... - +.Change history... [%collapsible] ==== * GEMINI 1 to 2.0: deleted @@ -59,8 +57,7 @@ Change history... link:#54[Metadata standard name] ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -76,8 +73,7 @@ include::../snippets/metadatastandardversion.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/parentidentifier.asciidoc b/docs/partials/parentidentifier.asciidoc index ab73749..8f25fb3 100644 --- a/docs/partials/parentidentifier.asciidoc +++ b/docs/partials/parentidentifier.asciidoc @@ -36,8 +36,7 @@ endif::[] |Revision date |May 2018 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -47,15 +46,13 @@ Corresponding element in other standards... |=== ==== -Change history... - +.Change history... [%collapsible] ==== New element in GEMINI 2.3 ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -70,8 +67,7 @@ include::../snippets/parentidentifier.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/qualityscope.asciidoc b/docs/partials/qualityscope.asciidoc index a23c2cb..39ffd95 100644 --- a/docs/partials/qualityscope.asciidoc +++ b/docs/partials/qualityscope.asciidoc @@ -46,8 +46,7 @@ endif::[] |Revision date |March 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -73,15 +72,13 @@ endif::[] |=== ==== -Change history... - +.Change history... [%collapsible] ==== New element in GEMINI 2.3 ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -122,8 +119,7 @@ endif::[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== ifdef::variant-dataset[] diff --git a/docs/partials/resourceidentifier.asciidoc b/docs/partials/resourceidentifier.asciidoc index d826d91..19e9409 100644 --- a/docs/partials/resourceidentifier.asciidoc +++ b/docs/partials/resourceidentifier.asciidoc @@ -81,8 +81,7 @@ element. |Revision date |May 2018 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -99,8 +98,7 @@ Corresponding element in other standards... |=== ==== -Change history... - +.Change history... [%collapsible] ==== . GEMINI 1 to 2.0: New item 'Unique resource identifier', required for @@ -109,8 +107,7 @@ INSPIRE reduce confusion with W3C URI ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -153,8 +150,7 @@ include::../snippets/resourceidentifier-anchor.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/resourcelocator.asciidoc b/docs/partials/resourcelocator.asciidoc index 1693ba1..65f9603 100644 --- a/docs/partials/resourcelocator.asciidoc +++ b/docs/partials/resourcelocator.asciidoc @@ -102,8 +102,7 @@ http://myserver/INSPIREWM/MapServer/WMSServer?service=WMS&request=GetCapabilitie endif::[] |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -120,15 +119,13 @@ CI_OnlineResource.linkage |Equivalent |=== ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: Modification of Online resource ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -252,8 +249,7 @@ include::../snippets/service-resourcelocator-function-invocable.xml[] endif::[] ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== |=== diff --git a/docs/partials/resourcetype.asciidoc b/docs/partials/resourcetype.asciidoc index 6f2eb02..fcc7156 100644 --- a/docs/partials/resourcetype.asciidoc +++ b/docs/partials/resourcetype.asciidoc @@ -34,8 +34,7 @@ series are: |Revision date |July 2009 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -46,15 +45,13 @@ Corresponding element in other standards... |=== ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: New element, required for INSPIRE ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -69,8 +66,7 @@ include::../snippets/resourcetype.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/responsibleorganisation.asciidoc b/docs/partials/responsibleorganisation.asciidoc index 28c8e09..448dd86 100644 --- a/docs/partials/responsibleorganisation.asciidoc +++ b/docs/partials/responsibleorganisation.asciidoc @@ -112,8 +112,7 @@ acting as distributor, publisher, author, etc. !distributor |Revision date |July 2009 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -137,8 +136,7 @@ ifdef::variant-service[] endif::[] ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: This has been generalised from Distributor (and @@ -147,8 +145,7 @@ Originator) to cover a range of possible roles, by the addition of corrected. ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -181,8 +178,7 @@ endif::[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/spatialdataservicetype.asciidoc b/docs/partials/spatialdataservicetype.asciidoc index 0c39fa4..7d66732 100644 --- a/docs/partials/spatialdataservicetype.asciidoc +++ b/docs/partials/spatialdataservicetype.asciidoc @@ -39,8 +39,7 @@ guidance] link:component/content/article?id=1047[[9]]. |Revision date |July 2009 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -56,15 +55,13 @@ Corresponding element in other standards... |=== ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: New element ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -91,8 +88,7 @@ include::../snippets/spatialdataservicetype.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/spatialreferencesystem.asciidoc b/docs/partials/spatialreferencesystem.asciidoc index 7d4b2c3..4873b44 100644 --- a/docs/partials/spatialreferencesystem.asciidoc +++ b/docs/partials/spatialreferencesystem.asciidoc @@ -64,8 +64,7 @@ reference systems in addition to that in which it is recorded. |Revision date |March 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -86,15 +85,13 @@ RS_Identifier.code |Equivalent |=== ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: Changed from enumerated list ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -133,8 +130,7 @@ include::../snippets/spatialreferencesystem-identifiers.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/spatialrepresentationtype.asciidoc b/docs/partials/spatialrepresentationtype.asciidoc index 5dbcfbd..517e174 100644 --- a/docs/partials/spatialrepresentationtype.asciidoc +++ b/docs/partials/spatialrepresentationtype.asciidoc @@ -44,8 +44,7 @@ guidance as interoperability metadata for datasets and dataset series |Revision date |May 2018 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -64,16 +63,14 @@ is a superset of values used by INSPIRE |=== ==== -Change history... - +.Change history... [%collapsible] ==== * In original GEMINI, but removed in 2 * Reintroduced in GEMINI 2.3 ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -89,8 +86,7 @@ include::../snippets/spatialrepresentationtype.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/spatialresolution.asciidoc b/docs/partials/spatialresolution.asciidoc index a4a819d..76f557e 100644 --- a/docs/partials/spatialresolution.asciidoc +++ b/docs/partials/spatialresolution.asciidoc @@ -46,8 +46,7 @@ the building, i.e. about 10 metres. |Revision date |March 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -70,15 +69,13 @@ endif::[] ==== -Change history... - +.Change history... [%collapsible] ==== GEMINI 1 to 2.0: made conditional ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -116,8 +113,7 @@ include::../snippets/spatialresolution.xml[] endif::[] ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/temporalextent.asciidoc b/docs/partials/temporalextent.asciidoc index 161024b..5d1465e 100644 --- a/docs/partials/temporalextent.asciidoc +++ b/docs/partials/temporalextent.asciidoc @@ -60,8 +60,7 @@ following year. |Revision date |May 2018 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -84,8 +83,7 @@ endif::[] |=== ==== -Change history... - +.Change history... [%collapsible] ==== . GEMINI 1 to 2.0: Name changed from Date @@ -93,8 +91,7 @@ Change history... 'year' ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -222,8 +219,7 @@ endif::[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available diff --git a/docs/partials/title.asciidoc b/docs/partials/title.asciidoc index 79938ea..1405b69 100644 --- a/docs/partials/title.asciidoc +++ b/docs/partials/title.asciidoc @@ -40,8 +40,7 @@ in the abstract or Alternative Title. |Revision date |March 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -56,13 +55,11 @@ Corresponding element in other standards... |=== ==== -Change history... - +.Change history... [%collapsible] ==== ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== diff --git a/docs/partials/topiccategory.asciidoc b/docs/partials/topiccategory.asciidoc index 11e3f5b..8347847 100644 --- a/docs/partials/topiccategory.asciidoc +++ b/docs/partials/topiccategory.asciidoc @@ -117,8 +117,7 @@ link:#6[Keyword] |Revision date |March 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -138,8 +137,7 @@ Change history... [[history5]] -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -164,8 +162,7 @@ include::../snippets/topiccategory.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== |=== diff --git a/docs/partials/useconstraints.asciidoc b/docs/partials/useconstraints.asciidoc index 74eea37..6926346 100644 --- a/docs/partials/useconstraints.asciidoc +++ b/docs/partials/useconstraints.asciidoc @@ -65,8 +65,7 @@ endif::[] |=== ==== -Change history... - +.Change history... [%collapsible] ==== * GEMINI 1 to 2.0: Change to free text field from enumerated list, and @@ -74,8 +73,7 @@ making mandatory to conform with INSPIRE. * GEMINI 2.2 to 2.3: Change of encoding ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -131,8 +129,7 @@ include::../snippets/useconstraints-noconditions.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== [width="100%",cols="50%,50%",] diff --git a/docs/partials/verticalextent.asciidoc b/docs/partials/verticalextent.asciidoc index a622d6f..33df265 100644 --- a/docs/partials/verticalextent.asciidoc +++ b/docs/partials/verticalextent.asciidoc @@ -63,8 +63,7 @@ significant, e.g. in geology, mining, meteorology etc. |Revision date |March 2019 |=== -Corresponding element in other standards... - +.Corresponding element in other standards... [%collapsible] ==== |=== @@ -91,8 +90,7 @@ EX_VerticalExtent |Identical endif::[] ==== -Change history... - +.Change history... [%collapsible] ==== * GEMINI 1 to 2.0: made optional; + @@ -102,8 +100,7 @@ description of class EX_VerticalExtent changed to match change to ISO * GEMINI 2.1 to 2.2: made multiple again ==== -Encoding guidelines... - +.Encoding guidelines... [%collapsible] ==== |=== @@ -176,8 +173,7 @@ include::../snippets/extent-verticalcrs-unknown.xml[] |=== ==== -Metadata errors observed... - +.Metadata errors observed... [%collapsible] ==== No error information available From 189758c793e80d85e9dba3e0caf484647f2d27b6 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Tue, 17 Jan 2023 12:24:45 +0000 Subject: [PATCH 20/54] Update README.md Made a minor change to the readme to check that the updated personal access token works correctly --- docs/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index 43df92a..3411357 100644 --- a/docs/README.md +++ b/docs/README.md @@ -15,7 +15,8 @@ The files below have been converted but have not been altered to work using the * [1055-uk-gemini-major-changes-since-1-0](https://agiorguk.github.io/gemini-dev/1055-uk-gemini-major-changes-since-1-0.html) * [1056-glossary](https://agiorguk.github.io/gemini-dev/1056-glossary.html) -Links above this are to the Gitpages published in https://agiorguk.github.io/gemini-dev/ +Links above this are to the GitHub pages published in https://agiorguk.github.io/gemini-dev/ + ## Services and Datasets workflow * These files are generated from [include files](https://docs.asciidoctor.org/asciidoc/latest/directives/include/), one per element, in the [docs/partials](https://github.com/agiorguk/gemini/tree/main/docs/partials) folder. From 7f146bede5332cfd061968e8fa5138167075eea5 Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Wed, 8 Mar 2023 16:32:54 +0000 Subject: [PATCH 21/54] Update 1048-uk-gemini-encoding-guidance.asciidoc Some minor corrections: section numbering leads to duplication of table of contents; I removed the "manual" one - on preview, this loses both, so I'll have to wait to see what happens on publication (to dev) According to https://github.com/agiorguk/gemini/issues/2, the sample links should already have been to GitHub, although as of 2023-03-08, that is only true of one of each link on the live site. To save migrating the invalid XML samples from the live site (!), I've changed the second of each pair of links to point to GitHub (and removed the 'series' example link). Need to migrate 1046-xml-order, or remove a lot of links to it (as it is no longer possible to automatically generate it as we could with the old "massive XML -> HTML" process.) Fixed "end note" links to go directly to the relevant page (i.e. not [4] -> page 1047 "bibliography" under a different name -> an old edition of GEMINI!) - in fact, I removed that link as basically circular! The source (live) page included a duplicate of "Figure 2" and the following explanatory paragraph; the duplicate figure had been migrated (but not the following paragraph). I've removed it. Similarly for the explanation of Figure 22a. Corrected 2.4.2 reference to "Figure 23" to the correct Figure 25. How to avoid URI namespace identifiers being converted to links in ASCII Doc? Fortunately, some of them have landing pages... Manually numbered the "figures". They (the code fragments) look good in preview, less good in HTML) --- .../1048-uk-gemini-encoding-guidance.asciidoc | 179 +++++------------- 1 file changed, 52 insertions(+), 127 deletions(-) diff --git a/docs/1048-uk-gemini-encoding-guidance.asciidoc b/docs/1048-uk-gemini-encoding-guidance.asciidoc index e126652..7eeefab 100644 --- a/docs/1048-uk-gemini-encoding-guidance.asciidoc +++ b/docs/1048-uk-gemini-encoding-guidance.asciidoc @@ -1,50 +1,17 @@ = UK GEMINI Encoding Guidance include::./includes/attributes.asciidoc[] -:sectnums!: -== Technical guidance on the encoding of UK GEMINI +Technical guidance on the encoding of UK GEMINI -Return -to link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI -2.3 home page] - -<<_introduction, Introduction>> - -<<_purpose_of_guidelines, Purpose of guidelines>> - -<<_scope, Scope>> - -<<_assumed_knowledge, Assumed knowledge>> - -<<_terminology, Terminology>> - -<<1.5, Structure of document>> - -<<1.6, XML fragments>> - -<<2, Encoding Guidelines>> - -<<2.1, Schemas>> - -<<2.2, Common concepts>> - -<<2.3, Metadata for datasets and dataset series>> - -<<2.4, Metadata for services>> +Return to link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI 2.3 home page] Appendices -https://www.agi.org.uk/40-gemini/1046-xml-element-order[XML Element -Order] +link:1046-xml-element-order[XML Element Order] -https://www.agi.org.uk/40-gemini/1044-dataset-metadata-instance-example[Dataset -metadata instance example] - -https://www.agi.org.uk/40-gemini/1043-series-metadata-example-old[Series -metadata instance example] +https://github.com/AGIuk/Schematron/blob/master/samples/1044-ds.xml[Dataset metadata instance example] -https://www.agi.org.uk/40-gemini/1042-service-metadata-instance-example[Service -metadata instance example] +https://github.com/AGIuk/Schematron/blob/master/samples/1042-sv.xml[Service metadata instance example] :sectnums: :sectnumlevels: 3 @@ -62,17 +29,12 @@ The encoding of all types is covered. === Scope -The scope of these guidelines is the encoding of UK GEMINI -[https://www.agi.org.uk/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[4]]according -to ISO 19139, ISO 19119 and ISO 19136, in a way that adheres to the -INSPIRE technical guidelines -[https://www.agi.org.uk/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[9]] -for encoding metadata. +The scope of these guidelines is the encoding of UK GEMINI according +to ISO 19139, ISO 19119 and ISO 19136, in a way that adheres to the https://github.com/INSPIRE-MIF/technical-guidelines/blob/main/metadata/metadata-iso19139/metadata-iso19139.adoc[INSPIRE technical guidelines for encoding metadata]. Outside the scope of this document is the description of GEMINI2 metadata items, their content, obligation and meaning. Readers seeking -this information should consult the GEMINI2 standard -[https://www.agi.org.uk/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[4]]. +this information should consult the GEMINI2 standard. === Assumed knowledge @@ -90,7 +52,7 @@ W3Schools XML Schema tutorial: === Terminology A Glossary is -provided https://www.agi.org.uk/40-gemini/1056-glossary[here]. +provided link:1056-glossary.html[here]. === Structure of document @@ -112,7 +74,7 @@ the requirements for each type of metadata. The 'Metadata for datasets and dataset series' and 'Metadata for services' sections list metadata items from GEMINI2 in the order that they appear in GEMINI2. XML elements in an XML document must follow -the https://www.agi.org.uk/40-gemini/1046-xml-element-order[order ]expressed +the link:1046-xml-element-order.html[order ]expressed in the XSD schema to which the XML document conforms. The order of XML element expressed by the XSD schema will not be the same as the order of metadata items in GEMINI2. @@ -143,7 +105,7 @@ text wrapping) * Missing XML content, removed while forming the fragment, shall be represented by an ellipsis (...) -.XML fragment – tabbing +*Figure 1 - XML fragment – tabbing* [source, xml] ---- @@ -168,17 +130,17 @@ Also deliberately omitted from XML fragments is: * XML namespace identifiers In the example in Figure 1 CharacterString is an XML element in the -namespace gco. It has the start-tag and the -end-tag . The -string 98e25be5-388d-4be3-bc5f-ba07ef6009b2 is the element’s content. +namespace gco. It has the start-tag `` and the +end-tag ``. The +string _98e25be5-388d-4be3-bc5f-ba07ef6009b2_ is the element’s content. The CharacterString element forms the content of another element: -fileIdentifier. Its start-tag is and its end-tag -is . In the example -below gml:id and codeSpace are XML attributes. XML attributes are +fileIdentifier. Its start-tag is `` and its end-tag +is ``. In the example +below `gml:id` and `codeSpace` are XML attributes. XML attributes are encoded in the start-tag of an element with the form [namespace]:[attributeName]="[content]". -.XML attributes +*Figure 2 - XML attributes* [source, xml] ---- ... @@ -194,7 +156,7 @@ each XML element on a new line other than to aid humans in reading raw XML. XML parsers, on the other hand, would have no problem reading the XML were it encoded without carriage returns as shown in Figure 3. -.XML fragment - no tabbing +*Figure 3 - XML fragment - no tabbing* [source, xml] ---- 98e25be5-388d-4be3-bc5f-ba07ef6009b2 @@ -202,23 +164,11 @@ XML were it encoded without carriage returns as shown in Figure 3. The UK Location Information Infrastructure will accept any valid XML document that conforms to these guidelines. This includes -canonical XML encodings -[https://www.agi.org.uk/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[5]] +http://www.w3.org/TR/xml-c14n[canonical XML encodings] and files laid out with additional white space for human readability, and other variants in between. Similarly, XML attribute values could be delimited using single or double quotes. -.XML attributes -[source, xml] ----- -... - - information applies to the dataset - dataset - -... ----- - == Encoding Guidelines === Schemas @@ -305,7 +255,7 @@ An XML declaration may include a “standalone” attribute. However, this attribute is only relevant if an XML document is using a DTD. Metadata instances of GEMINI2 shall not use a DTD so it is out of scope. -.XML declaration +*Figure 4 - XML declaration* [source, xml] ---- @@ -325,7 +275,7 @@ An example is shown in Figure 5. Subsequent examples omit the namespace references for brevity. An ellipsis is used to indicate that required content has been omitted. -.Root Element +*Figure 5 - Root Element* [source, xml] ---- @@ -381,7 +331,7 @@ metadata instance, the attribute contains a space separated sequence of namespace / schema pairs. The xsi:schemaLocation attribute is not required in a GEMINI2 metadata instance. -.Using the xsi:schemaLocation attribute +*Figure 6 - Using the xsi:schemaLocation attribute* [source, xml] ---- @@ -427,14 +377,14 @@ XML elements in a metadata instance must follow the order in which the elements are defined in an XSD schema. Failure to do so will result in schema validation errors. The order of XML elements and their corresponding GEMINI2 metadata items is -shown https://www.agi.org.uk/40-gemini/1046-xml-element-order[here]. +shown link:1046-xml-element-order[here]. ==== Patterns for multiple instances Some metadata items, such as alternative title, have cardinalities for more than one. This means that more than one instance of the item can be encoded in metadata instances. The general approach in ISO 19139 XML is -that an XML element expressing the property, in Figure7 +that an XML element expressing the property, in Figure 7 gmd:alternateTitle, contains an XML element which expresses the data type and contains the value, in this case gco:CharacterString. Note that more than one alternative title is expressed by repeating the @@ -443,7 +393,7 @@ gmd:alternateTitle XML element, not the gco:CharacterString XML element throughout ISO 19139 XML including for XML elements that have complex content, such as gmd:identificationInfo (Figure 9). -.Multiple alternative title elements +*Figure 7 - Multiple alternative title elements* [source, xml] ---- @@ -457,10 +407,9 @@ content, such as gmd:identificationInfo (Figure 9). ... ---- -.Multiple alternative title elements - invalid encoding +*Figure 8 - Multiple alternative title elements - invalid encoding* [source, xml] ---- - ... Digital Geological Map Data of Great Britain - 625k @@ -469,10 +418,9 @@ content, such as gmd:identificationInfo (Figure 9). ... ---- -.Multiple identification information elements +*Figure 9 - Multiple identification information elements* [source, xml] ---- - ... @@ -494,18 +442,15 @@ content, such as gmd:identificationInfo (Figure 9). The first XML child element of any GEMINI2 metadata instance shall be gmd:fileIdentifier. The content of this XML element is the identifier of the metadata instance. File identifier is not to be confused with the -metadata -item https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#36[Resource -Identifier]. +metadata item link:datasets.htm#36[Resource Identifier]. The content of the XML element shall be a unique managed identifier, such as a system generated UUID. Once the identifier has been set for a metadata instance it shall not change. -.File Identifier +*Figure 10 - File Identifier* [source, xml] ---- - 98e25be5-388d-4be3-bc5f-ba07ef6009b2 @@ -536,10 +481,9 @@ In any one citation there may be more than one date. However, there shall be only one date with a date type of ‘creation’ and there shall be only one date with type 'revision'. -.CI_Citation structure +*Figure 11 - CI_Citation structure* [source, xml] ---- - ... @@ -561,10 +505,9 @@ only one date with type 'revision'. ==== Responsible party -.CI_ResponsibleParty structure +*Figure 12 - CI_ResponsibleParty structure* [source, xml] ---- - ... @@ -663,17 +606,16 @@ The value of the code list value attribute (gmd:codeListValue) shall be a valid entry from the specified code list dictionary. The element value (i.e. in Figure -13 dataset) is human +13 `*dataset*`) is human readable text. It can be omitted or given a value different from that of the attribute codeListValue (e.g. Dataset). Developers of GEMINI aware applications should note that reliance should not be placed on the element value of code list elements but rather on the value of the attribute gmd:codeListValue. -.Code list +*Figure 13 - Code list* [source, xml] ---- - dataset ---- @@ -681,10 +623,9 @@ codeListValue="dataset">dataset Figure 14 shows a fragment of the code list catalogue with the entries of MD_ScopeCode that are relevant to GEMINI2 metadata. -.Fragment of the code list catalogue +*Figure 14 - Fragment of the code list catalogue* [source, xml] ---- - ---- -.Vertical CRS by value +*Figure 17 - Vertical CRS by value* [source, xml] ---- @@ -836,11 +776,9 @@ items shall be implemented _by value_. ... ---- -.Coupled resource by reference - +*Figure 18 - Coupled resource by reference* [source, xml] ---- - @@ -858,8 +796,7 @@ for namespaces, so it cannot appear in an identifier. XML names may not include any whitespace including spaces and carriage returns. All names beginning with the letters XML (in uppercase, lowercase or any mixture thereof) are reserved (see -[https://www.agi.org.uk/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[11]] -pages 18 and 19). +https://www.w3schools.com/xml/xml_elements.asp). XML names may only start with letters, ideograms and the underscore character. Consequently, care must be taken when using the value of a @@ -893,7 +830,7 @@ For example the encoding of an identifier/code value should be done with gmx:Anchor as in Figure 19, rather than gco:CharacterString (Figure 20), when the unique resource identifier is referenceable, -.Non-empty free text, with gmx:Anchor +*Figure 19 - Non-empty free text, with gmx:Anchor* [source, xml] ---- @@ -910,7 +847,7 @@ when the unique resource identifier is referenceable, .... ---- -.Non-empty free text, with gco:CharacterString +*Figure 20 - Non-empty free text, with gco:CharacterString* [source, xml] ---- @@ -964,11 +901,9 @@ Three examples: Figure 21 describes a commercial product, not available to the public for IPR reasons, and with a web page describing licences -.OS licence - +*Figure 21 - OS licence* [source, xml] ---- - .... @@ -1005,14 +940,9 @@ Figure 22a describes an open data product, with no limitations on public access, the Open Government Licence referenced, and summarised in plain text. -Figure 22a describes an open data product, with no limitations on public -access, the Open Government Licence referenced, and summarised in plain -text. - -.INSPIRE no limitations; OGL +*Figure 22a - INSPIRE no limitations; OGL* [source, xml] ---- - .... @@ -1028,7 +958,6 @@ text. - @@ -1048,10 +977,9 @@ text. Figure 22b describes an open data product, with no limitations on public access, but plain text conditions of use. -.INSPIRE no limitations on access; constraint on use +*Figure 22b - INSPIRE no limitations on access; constraint on use* [source, xml] ---- - .... @@ -1102,7 +1030,7 @@ hierarchyLevel element shall be set to “dataset” or “series”. For a series, ISO 19115 hierarchyLevelName element must also be set, to "dataset" or "series" as appropriate. -.Metadata for datasets using the gmd:MD_DataIdentification type +*Figure 23 - Metadata for datasets using the gmd:MD_DataIdentification type* [source, xml] ---- @@ -1124,8 +1052,7 @@ series, ISO 19115 hierarchyLevelName element must also be set, to ==== Detailed guidance for each metadata element -* https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series[Datasets -and series] +link:datasets.htm[Datasets] === Metadata for services @@ -1142,7 +1069,7 @@ srv:SV_ServiceIdentification. The ISO 19115 hierarchyLevel element shall be set to “service”, ISO 19115 hierarchyLevelName element must also be set, to "service". -.Metadata for services using the srv:SV_ServiceIdentification type +*Figure 24 - Metadata for services using the srv:SV_ServiceIdentification type* [source, xml] ---- @@ -1170,9 +1097,9 @@ set, to "service". The ISO 19119 class SV_ServiceIdentification includes two mandatory properties that are out of scope of GEMINI2 metadata. These are srv:couplingType and srv:containsOperations. Both shall be implemented -with null values with the nil reason being missing (Figure 23). +with null values with the nil reason being missing (Figure 25). -.Coupling Type and Contains Operations – Null values* +*Figure 25 - Coupling Type and Contains Operations – Null values* [source, xml] ---- @@ -1192,12 +1119,10 @@ with null values with the nil reason being missing (Figure 23). ==== Detailed guidance for each metadata element -* https://www.agi.org.uk/40-gemini/1063-gemini-services[Services] +link:services.htm[Services] _Last technical update: March 2019_ http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative Commons Licence]] -This work is licensed under -a http://creativecommons.org/licenses/by/4.0/[Creative Commons -Attribution 4.0 International License] \ No newline at end of file +This work is licensed under a http://creativecommons.org/licenses/by/4.0/[Creative Commons Attribution 4.0 International License] From 29a50d7d5ec8aad4d2cb20e1ec52ed6c23825fef Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Thu, 9 Mar 2023 11:54:15 +0000 Subject: [PATCH 22/54] internal links should be to .html, not .htm! --- docs/1048-uk-gemini-encoding-guidance.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/1048-uk-gemini-encoding-guidance.asciidoc b/docs/1048-uk-gemini-encoding-guidance.asciidoc index 7eeefab..3502657 100644 --- a/docs/1048-uk-gemini-encoding-guidance.asciidoc +++ b/docs/1048-uk-gemini-encoding-guidance.asciidoc @@ -442,7 +442,7 @@ content, such as gmd:identificationInfo (Figure 9). The first XML child element of any GEMINI2 metadata instance shall be gmd:fileIdentifier. The content of this XML element is the identifier of the metadata instance. File identifier is not to be confused with the -metadata item link:datasets.htm#36[Resource Identifier]. +metadata item link:datasets.html#36[Resource Identifier]. The content of the XML element shall be a unique managed identifier, such as a system generated UUID. Once the identifier has been set for a @@ -1052,7 +1052,7 @@ series, ISO 19115 hierarchyLevelName element must also be set, to ==== Detailed guidance for each metadata element -link:datasets.htm[Datasets] +link:datasets.html[Datasets] === Metadata for services @@ -1119,7 +1119,7 @@ with null values with the nil reason being missing (Figure 25). ==== Detailed guidance for each metadata element -link:services.htm[Services] +link:services.html[Services] _Last technical update: March 2019_ From 3ee750b63980efa9aa59b79b7649de062486d722 Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Mon, 13 Mar 2023 11:08:53 +0000 Subject: [PATCH 23/54] Update 1049-metadata-guidelines-for-geospatial-data-resources-part-2.asciidoc Fix links mainly (including bizarre one which has for a long time pointed out to a quite different page on AGI's site & one which was pointing to 1244 but should have been to 1051!) Also fixed headings and removed quite a few instances of {nbsp} --- ...-geospatial-data-resources-part-2.asciidoc | 153 +++++++----------- 1 file changed, 61 insertions(+), 92 deletions(-) diff --git a/docs/1049-metadata-guidelines-for-geospatial-data-resources-part-2.asciidoc b/docs/1049-metadata-guidelines-for-geospatial-data-resources-part-2.asciidoc index 42f7320..7a52cb7 100644 --- a/docs/1049-metadata-guidelines-for-geospatial-data-resources-part-2.asciidoc +++ b/docs/1049-metadata-guidelines-for-geospatial-data-resources-part-2.asciidoc @@ -1,47 +1,15 @@ -== Metadata Guidelines for Geospatial Data Resources Part 2 += Metadata Guidelines for Geospatial Data Resources Part 2 include::./includes/attributes.asciidoc[] -=== Creating metadata using UK GEMINI (v2.3) May 2018 -{nbsp}_being revised_ +Creating metadata using UK GEMINI (v2.3) May 2018 -{nbsp}_being revised_ -Return -to{nbsp}https://www.agi.org.uk/gemini/40-gemini/1037-uk-gemini-standard-and-inspire-implementing-rules[GEMINI -2.3 home page] +Return to link:1037-uk-gemini-standard-and-inspire-implementing-rules[GEMINI 2.3 home page] -https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2#Intro[1. -Introduction] +:sectnums: +:sectnumlevels: 3 -https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2#gemini[2. -GEMINI2] - -https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2#2.1[2.1 -Metadata elements] - -https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2#2.2[2.2 -Additional metadata elements] - -https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2#2.3[2.3 -Extension code lists] - -https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2#errors[3. -Possible metadata errors] - -https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2#3.1[3.1 -Impact of metadata errors] - -https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2#3.2[3.2 -Effect on searches] - -https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2#3.3[3.3 -Prevention and correction of errors] - -https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2#3.4[3.4 -Common errors] - -https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2#guidance[4. -Guidance for individual metadata elements] - -=== Preface +*Preface* This is the second part of a set of guidelines for metadata for geospatial data resources. These metadata guidelines are primarily @@ -59,11 +27,10 @@ providers of metadata services and general data users. They include guidance on quality management such that they could be used in the context of a national metadata service. -https://www.agi.org.uk/gemini/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1[Part -1 of the Guidelines{nbsp}]covers the basics of metadata and provides an +link:1052-metadata-guidelines-for-geospatial-data-resources-part-1[Part +1 of the Guidelines] covers the basics of metadata and provides an introduction to the other two parts. It includes a glossary of terms and -set of references. Part 3 -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[3]] +set of references. https://www.agi.org.uk/wp-content/uploads/2020/12/METADATAGUIDELINESPART32015-04.pdf[Part 3] deals with metadata quality and covers quality evaluation and quality management of metadata including guidance on establishing acceptable quality levels. This Part of the Guidelines provides a set of detailed @@ -72,9 +39,9 @@ correspond to version 2.3 of UK GEMINI. Any comments on these guidelines or on the UK GEMINI2 metadata standard should be sent -to{nbsp}gemini@agi.org.uk. +to mailto:gemini@agi.org.uk[gemini@agi.org.uk]. -=== [#intro]##{nbsp}1. Introduction +== Introduction UK GEMINI2 defines a core set of metadata elements for discovery of data resources and other essential purposes. It provides details of what @@ -86,11 +53,10 @@ content. This includes datasets that relate to a limited geographic area. The data resources may be graphical or textual (tabular or free text), hardcopy or digital. -This part of the{nbsp}_Metadata Guidelines for Geospatial Data -Resources_{nbsp}provides detailed guidance for the application of UK GEMINI2. +This part of the _Metadata Guidelines for Geospatial Data Resources_ provides detailed guidance for the application of UK GEMINI2. It is aimed at those creating metadata conforming to UK GEMINI2. This expands on existing guidance given in the UK GEMINI2 -specification[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[4]]. +specification. It also describes possible errors that might occur in such metadata and suggests actions to guard against them. It explains how to expand the metadata elements in addition to those in UK GEMINI2 if required, and @@ -99,40 +65,35 @@ how to extend code lists of allowable values. This Part should be read in conjunction with the other parts of these guidelines. -=== [#gemini]##{nbsp}2. GEMINI2 +== GEMINI2 -==== *_[#2.1]####2.1 Metadata elements_* +=== Metadata elements UK GEMINI2 specifies a set of metadata elements for describing geospatial data resources. These resources may be a dataset, data set series (collection of datasets with a common specification) or data service. The type of resource is identified in the element Resource Type -(39). The metadata elements are summarised -in{nbsp}https://www.agi.org.uk/gemini/40-gemini/1250-element-summary[element -summary]. +(39). The metadata elements are summarised in link:1250-element-summary[element summary]. Detailed guidance on how to create each of these elements can be found here: -https://www.agi.org.uk/gemini/40-gemini/1027-citizens-as-sensors-a-solution-to-pollution[GEMINI -- Datasets and data series] +link:datasets.html[GEMINI - Datasets and data series] -GEMINI - Services +link:services.html[GEMINI - Services] -==== *_[#2.2]####2.2 Additional metadata elements_* +=== Additional metadata elements In many organisations, there is a need to record additional items of metadata to meet specific local requirements. This may be to incorporate particular characteristics of the data resources, or for particular applications. Additional metadata elements may be included in a metadata -implementation. These elements should be taken from ISO -19115{nbsp}_Geographic information - -Metadata{nbsp}_[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[18]], +implementation. These elements should be taken from ISO 19115:2003 _Geographic information - Metadata_, which includes a comprehensive collection of metadata elements for geographic information. An example would be Dataset character set and Metadata character set where non-standard characters are used. -==== *_[#2.3]####2.3 Extension of code lists_* +=== Extension of code lists Several of the metadata elements specified in UK GEMINI2 use enumerated code lists. These are pre-defined sets of values identified by codes. @@ -153,7 +114,7 @@ created as follows: Such code extensions may be either specific to a metadata implementation in an organisation or sector, or for general usage. In the latter case, proposed new codes should be submitted -(to{nbsp}mailto:standards@agi.org[gemini@agi.org.uk) +(to mailto:standards@agi.org[gemini@agi.org.uk]) for inclusion in the next version of UK GEMINI2. It is expected that future editions of UK GEMINI will incorporate such modified code lists. @@ -161,9 +122,9 @@ future editions of UK GEMINI will incorporate such modified code lists. service until incorporated in the Standard, neither will they be valid for the purposes of INSPIRE.* -=== [#errors]##{nbsp}3. Possible metadata errors +== Possible metadata errors -==== *_[#3.1]####3.1 Impact of metadata errors_* +=== Impact of metadata errors Errors having the greatest impact are likely to be those that affect searches based on: @@ -180,7 +141,7 @@ Inconsistencies in the capture or updating of metadata, such as the categorisation of data subject or topic, will further erode the quality of the discovery service. -==== *_[#3.2]####3.2 Effect on searches_* +=== Effect on searches Having discovered a number of candidate data resources, the discovery service user then assesses the likelihood that any of these meet their @@ -197,7 +158,7 @@ about the data resource and how they can obtain that resource. It is not uncommon for this to be out-of-date or have incorrect URLs or contact details. -==== *_[#3.3]####3.3 Prevention and correction of errors_* +=== Prevention and correction of errors Prevention and correction of these errors is usually a combination of: @@ -216,11 +177,9 @@ users; * Overall quality assurance process which reviews procedures in the light of experience and aims to improve overall metadata quality. -Further guidance on how to prevent and correct errors is given in Part 3 -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[3]]{nbsp}of -these Guidelines. +Further guidance on how to prevent and correct errors is given in https://www.agi.org.uk/wp-content/uploads/2020/12/METADATAGUIDELINESPART32015-04.pdf[Part 3] of these Guidelines. -==== *_[#3.4]####3.4 Common errors_* +=== Common errors Some common errors that lead to inconsistent results when searching across metadatasets are: @@ -254,15 +213,17 @@ and dates documented using one metadata record. a| Have clear guidance on the “chunking” of data resources for individual -documentation[See{nbsp}https://www.agi.org.uk/gemini/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1[Part -1 of these Guidelines]] based on: +documentation (See link:1052-metadata-guidelines-for-geospatial-data-resources-part-1[Part +1 of these Guidelines]) based on: . how the data is used (stand-alone or as part of wider set); . continuity and extent of coverage; . date of capture or maintenance; . topics or subjects covered, and . uniformity of specification within data resource. - +++++ +
+++++ Introduce checks to ensure consistency of approach across all metadata. |Extent over-generalised |This particularly applies when extent is @@ -281,7 +242,9 @@ the coverage of data resources and guidelines on the types of extents to be used. Where named extents form part of a nesting hierarchy (e.g. administrative areas) then any guidance should cover the possible need for inclusion of levels in the hierarchy. - +++++ +
+++++ Introduce checks to ensure consistency of approach across all metadata. |Subjects and topic categories under-reported |This particularly applies @@ -292,16 +255,22 @@ boundaries, elevation, inland waters, structure, and transportation as topics. a| Use guidance on the recording of topics or themes to promote consistency. - +++++ +
+++++ Use closed lists wherever possible and discourage the use of free text. - +++++ +
+++++ Introduce checks to ensure consistency of approach across all metadata. |Incorrect or inconsistent date entries a| There is often confusion between the date that the data was current, the date when the data was captured or last updated and the date when the data resource was released, published or made available. - +++++ +
+++++ There can be further inconsistencies between the frequency of update and the recorded currency of the data resource. This can lead to {nbsp} false returns for searches based on dates. @@ -313,7 +282,9 @@ years ago. a| Use guidance on the recording of different dates to promote consistency. - +++++ +
+++++ Introduce checks, preferably by software, to ensure that the ordering of dates is consistent. @@ -323,7 +294,9 @@ metadatasets. This may lead to inconsistent results or, more frequently misinterpretation of results. |National Grid, British National Grid, National Grid of Great Britain. a| Include frequently used standard names in any internal guidance. - +++++ +
+++++ Introduce checks to ensure consistency of approach across all metadata. |Missing values |Omission of values relating to extent, date or topic @@ -371,7 +344,9 @@ against the wrong metadata element. a| a| Use guidance on the definition and use of the metadata elements especially those most commonly confused (see examples). - +++++ +
+++++ Introduce training and checks to ensure correct use of elements. |Values incorrect, incomplete or inaccurate |This can apply to both @@ -398,25 +373,19 @@ user. |Use guidance and checklists for compiling entries e.g. abstracts. |=== -=== [#guidance]####4. Guidance for individual metadata elements +== Guidance for individual metadata elements Detailed guidance on how to create each of these elements can be found here: -https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series/[GEMINI -- Datasets and data series] +link:datasets.html[GEMINI - Datasets and data series] -https://www.agi.org.uk/gemini/40-gemini/1063-gemini-services/[GEMINI - -Services] +link:services.html[GEMINI - Services] -Each metadata element is listed{nbsp}separately, as described -in{nbsp}https://www.agi.org.uk/gemini/40-gemini/1244-uk-gemini-introduction#4.3[UK -GEMINI Introduction]. +Each metadata element is listed separately, as described +in link:1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html#4.3[UK GEMINI Introduction]. _Last updated: May 2018_ -http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative -Commons Licence]] + -This work is licensed under -a{nbsp}http://creativecommons.org/licenses/by/4.0/[Creative Commons -Attribution 4.0 International License] +http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative Commons Licence]] + +This work is licensed under a http://creativecommons.org/licenses/by/4.0/[Creative Commons Attribution 4.0 International License] From 1e09319eaccf56755c1bb8056ee852e2504d0727 Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Thu, 16 Mar 2023 12:27:25 +0000 Subject: [PATCH 24/54] Check & update 1051 Fixed links e.g. to be relative, to avoid going via the 'bibliography' Removed link to 1040 (see https://github.com/agiorguk/gemini/issues/64#issuecomment-893499559) Fix the two links which said they were to 1250-summary-table but weren't (even in the live page!) Removed {nbsp}s, some of which were preventing ASCIIdoc "constrained bold" formatting See https://github.com/agiorguk/gemini/issues/96 - there's some duplication between this page & 1051. --- ...metadata-for-geospatial-resources.asciidoc | 160 ++++++------------ 1 file changed, 55 insertions(+), 105 deletions(-) diff --git a/docs/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.asciidoc b/docs/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.asciidoc index 7200940..cf0d8fd 100644 --- a/docs/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.asciidoc +++ b/docs/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.asciidoc @@ -1,43 +1,13 @@ == UK GEMINI v2-2 Specification for Discovery Metadata for Geospatial Resources include::./includes/attributes.asciidoc[] -Return -to{nbsp}https://www.agi.org.uk/gemini/40-gemini/1037-uk-gemini-standard-and-inspire-implementing-rules[GEMINI +Return to https://www.agi.org.uk/gemini/40-gemini/1037-uk-gemini-standard-and-inspire-implementing-rules[GEMINI 2.3 home page] -https://www.agi.org.uk/gemini/40-gemini/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources#Intro[Introduction] +:sectnums: +:sectnumlevels: 3 -https://www.agi.org.uk/gemini/40-gemini/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources#scope[1. -Scope] - -https://www.agi.org.uk/gemini/40-gemini/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources#normative_ref[2. -Normative Reference] - -https://www.agi.org.uk/gemini/40-gemini/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources#terms[3. -Terms and Definitions] - -https://www.agi.org.uk/gemini/40-gemini/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources#requirements[4. -Requirements] - -https://www.agi.org.uk/gemini/40-gemini/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources#4.1[4.1 -Datasets and dataset series] - -https://www.agi.org.uk/gemini/40-gemini/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources#4.2[4.2 -Services] - -https://www.agi.org.uk/gemini/40-gemini/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources#4.3[4.3 -Element details] - -https://www.agi.org.uk/gemini/40-gemini/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources#extended[5. -Extended metadata] - -https://www.agi.org.uk/gemini/40-gemini/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources#5.1[5.1 -Additional metadata elements] - -https://www.agi.org.uk/gemini/40-gemini/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources#5.2[5.2 -Extension of code lists] - -=== Foreword +== Foreword UK GEMINI was originally produced in 2004 by collaboration between the Association for Geographic Information (AGI), the (then) e-Government @@ -86,10 +56,10 @@ Programme Metadata Working Group. In 2018, changes were made that had been requested by various user communities as well as the revised metadata technical guidance from -INSPIRE. {nbsp}This updated version is known as UK GEMINI2.3. +INSPIRE. This updated version is known as UK GEMINI2.3. Further details of all these changes are -given{nbsp}https://www.agi.org.uk/40-gemini/1055-uk-gemini-major-changes-since-1-0[here]. +given link:1055-uk-gemini-major-changes-since-1-0[here]. A set of guidelines for metadata for geospatial datasets was originally produced in 2006. The Guidelines were in three parts: @@ -100,22 +70,18 @@ produced in 2006. The Guidelines were in three parts: These Guidelines were intended for general use in the UK geographic information environment, and particularly in support of the national -geospatial metadata service,{nbsp}_gigateway_. They were developed within the +geospatial metadata service, _gigateway_. They were developed within the context of a national geospatial metadata service, and UK GEMINI. These Guidelines have now been updated to incorporate the changes made in the revised version of UK GEMINI, 2.3, and their content made available on -the AGI -website:{nbsp}https://www.agi.org.uk/gemini/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1[Introduction -to Metadata]; parts -of{nbsp}https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2[Creating -metadata using GEMINI]; material in Part 2 which was specific to -particular elements has been moved to the element descriptions. +the AGI website: link:1052-metadata-guidelines-for-geospatial-data-resources-part-1[Introduction to Metadata]; +parts of link:1049-metadata-guidelines-for-geospatial-data-resources-part-2[Creating metadata using GEMINI]; +material in Part 2 which was specific to particular elements has been moved to the element descriptions. This Standard is maintained by the AGI Standards Committee. Any feedback -on it should be sent -to{nbsp}mailto:standards@agi.org.uk[gemini@agi.org.uk] +on it should be sent to mailto:standards@agi.org.uk[gemini@agi.org.uk] -=== [#Intro]####Introduction +== Introduction Geospatial data is data containing a locational element relative to the Earth. Many datasets that at first sight do not appear to be geospatial @@ -141,17 +107,16 @@ There are many metadata standards in existence. These have been produced at different times by different bodies for different purposes. The main one that is relevant to geospatial datasets is: -* **ISO 19115,{nbsp}**the International Standard which describes all aspects +* *ISO 19115*, the International Standard which describes all aspects of geospatial metadata and provides a comprehensive set of metadata elements that are widely used as the basis for geospatial metadata services. -The{nbsp}https://inspire.ec.europa.eu/about-inspire/563[EU INSPIRE -Directive]{nbsp}[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[7]]{nbsp}mandates +The https://inspire.ec.europa.eu/about-inspire/563[EU INSPIRE Directive] mandates the collection of metadata for use in Europe. Implementing Rules define the requirements for metadata for discovery purposes. These are based on ISO 19115, and -outlined{nbsp}https://www.agi.org.uk/40-gemini/1055-uk-gemini-major-changes-since-1-0[here]. +outlined link:1055-uk-gemini-major-changes-since-1-0[here]. The aim of UK GEMINI is to provide a core set of metadata elements for use in a UK geospatial metadata service, that are compatible with the @@ -163,35 +128,30 @@ In this document the term ‘data resource’ is used, in preference to ‘dataset’. This is to allow UK GEMINI to be applied to resources in addition to datasets, such as services supplying data. -=== [#scope]##{nbsp}1. Scope +== Scope This Standard specifies a set of metadata elements for describing geographic information resources. These resources may be datasets, dataset series, services delivering geographic data, or any other information resource with a geospatial content. This includes datasets -that relate to a limited geographic area -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[1]]. +that relate to a limited geographic area. The data resources may be graphical or textual (tabular or free text), hardcopy or digital. The metadata elements are intended for use in a metadata service for discovering what data resources exist. The elements include the -mandatory core set defined in ISO 19115 Geographic information – -Metadata, and comply with -the{nbsp}https://inspire.ec.europa.eu/metadata/6541[INSPIRE Implementing -Rules for -Metadata]{nbsp}[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[7]]. +mandatory core set defined in ISO 19115 Geographic information – Metadata, +and comply with the https://inspire.ec.europa.eu/metadata/6541[INSPIRE Implementing Rules for Metadata]. In any implementation or community, it is likely that additional metadata elements will be included for other purposes, such as data management, and a method for specifying such elements is defined. The UK specific guidance is designed to ensure that the metadata records work correctly with the national -catalogue,{nbsp}https://data.gov.uk/[https://data.gov.uk] +catalogue, https://data.gov.uk/[https://data.gov.uk] Guidance on transferring metadata records to the national catalogue are given -at{nbsp}https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide[Operational -Guide]. +at link:1054-operational-guide[Operational Guide]. This Standard is applicable to data creators, data owners, data publishers and suppliers of metadata services. Although it is primarily @@ -199,7 +159,7 @@ designed for data resources held within the UK on a national basis, by following the principles and structures of ISO 19115, it is also applicable within an organisation, user community or nation. -=== [#normative_ref]##{nbsp}2. Normative References +== Normative References The following referenced documents are indispensable to the application of this document. For dated references, only the edition cited applies. @@ -222,20 +182,19 @@ ISO 19119:2005 Geographic information – Services https://inspire.ec.europa.eu/Technical-Guidelines2/Metadata/6541[The INSPIRE Metadata Technical Guidance], v2.0.1, published 2017-03-02 -=== [#terms]##{nbsp}3. Terms and Definitions +== Terms and Definitions -See the{nbsp}https://www.agi.org.uk/gemini/40-gemini/1056-glossary[Glossary]. +See the link:1056-glossary[Glossary]. -=== [#requirements]##{nbsp}4. Requirements +== Requirements -==== *_[#4.1]####4.1 Datasets and dataset series_* +=== Datasets and dataset series UK GEMINI specifies a set of metadata elements for use when describing geographic information resources. The metadata elements are listed in -the{nbsp}https://www.agi.org.uk/40-gemini/1055-uk-gemini-major-changes-since-1-0[summary -table], which shows the metadata element names, their GEMINI element id +the link:1250-element-summary[summary table], which shows the metadata element names, their GEMINI element id (consistent with element numbers in previous versions of GEMINI), the obligation (whether their inclusion is mandatory, optional or conditional, and the number of possible occurrences of the element @@ -250,10 +209,9 @@ by an organisation. For metadata to conform to this Standard, it is necessary that all mandatory elements are provided, and that all conditional elements are provided when the stated condition is met. Optional elements should be -provided where they are applicable. A checklist for conformity is -given{nbsp}https://www.agi.org.uk/gemini/40-gemini/1040-checklist-for-conformity2[here]. +provided where they are applicable. -==== {nbsp}*_[#4.2]####4.2 Services_* +=== Services The INSPIRE Implementing Rules apply not only to datasets and datasets series, but also to (data) services. These are external applications @@ -267,78 +225,73 @@ Note that services are not described in ISO 19115, but in ISO 19119 of approach regarding the way that metadata is recorded for services. Some of the other metadata elements may not apply to particular types of service. The UK GEMINI metadata elements for services are identified in -the{nbsp}https://www.agi.org.uk/40-gemini/1055-uk-gemini-major-changes-since-1-0[summary -table]. +the link:1250-element-summary[summary table]. -==== *_[#4.3]####4.3 Element details_* +=== Element details Details of the metadata elements are given in : -https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series[GEMINI -- Datasets and dataset series] +link:datasets.html[GEMINI - Datasets and dataset series] -https://www.agi.org.uk/gemini/40-gemini/1063-gemini-services[GEMINI - -Services] +link:services.html[GEMINI - Services] -Each element listed{nbsp}separately, with the following information: +Each element listed separately, with the following information: --{nbsp}*Metadata element name*{nbsp}– the name of the UK GEMINI element; +-*Metadata element name* – the name of the UK GEMINI element; --{nbsp}*UK GEMINI id{nbsp}*– the identifier of the UK GEMINI element; note: these +- *UK GEMINI id* – the identifier of the UK GEMINI element; note: these do not change between versions of GEMINI; ids of deleted elements are not re-used. --{nbsp}*Definition*{nbsp}– the formal definition of the element; +- *Definition* – the formal definition of the element; --{nbsp}*Purpose and meaning*{nbsp}- an explanation of what the element is, and why +- *Purpose and meaning* - an explanation of what the element is, and why it is required --{nbsp}*Obligation*{nbsp}– whether the element is mandatory, optional or +- *Obligation* – whether the element is mandatory, optional or conditional (where the element must be supplied when stated conditions apply); --{nbsp}*Occurrence*{nbsp}– whether the element is single-valued or can have +- *Occurrence* – whether the element is single-valued or can have multiple values; --{nbsp}*Data type*{nbsp}– the form of the entry, whether it is a character string +- *Data type* – the form of the entry, whether it is a character string (CharacterString), real number (real), integer, code or other class. Where the data type is another class, it is described as a set of sub-elements. Examples are Distributor and Vertical extent; --{nbsp}*Domain*{nbsp}– the allowable set of values; +- *Domain* – the allowable set of values; --{nbsp}*Guidance*{nbsp}– advice on how to complete the entry -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[2]]; +- *Guidance* – advice on how to complete the entry --{nbsp}*Comment*{nbsp}– other other information of relevance; +- *Comment* – other other information of relevance; --{nbsp}*Examples* +- *Examples* --**{nbsp}Corresponding element in{nbsp}**INSPIRE Metadata, ISO 19115:2003, ISO +- Corresponding element** in INSPIRE Metadata, ISO 19115:2003, ISO 19139:2007 --{nbsp}*Change history*{nbsp}– how the element has changed from v1.0 of the +- *Change history* – how the element has changed from v1.0 of the Standard; --*{nbsp}Encoding guidelines & example*{nbsp}- how to create an XML instance of +- *Encoding guidelines & example* - how to create an XML instance of this element --{nbsp}*Errors observed*{nbsp}- observations on errors noted with each element +- *Errors observed* - observations on errors noted with each element -=== [#extended]##{nbsp}5. Extended metadata +== Extended metadata -==== *_[#5.1]####5.1 Additional metadata elements_* +=== Additional metadata elements In many organisations, there is a need to record additional items of metadata to meet specific local requirements. This may be to incorporate particular characteristics of the data resources, or for particular applications. Additional metadata elements may be included in a metadata -implementation. These elements should be taken from ISO 19115 -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[18]], +implementation. These elements should be taken from ISO 19115, which includes a comprehensive collection of metadata elements for geographic information, and also allows for further extensions. -==== *_[#5.2]####5.2 Extension of code lists_* +=== Extension of code lists Several metadata elements specified in UK GEMINI use enumerated code lists. These are pre-defined sets of values identified by codes. They @@ -369,8 +322,5 @@ the purposes of INSPIRE.* _Last updated: May 2018_ -http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative -Commons Licence]] + -This work is licensed under -a{nbsp}http://creativecommons.org/licenses/by/4.0/[Creative Commons -Attribution 4.0 International License] \ No newline at end of file +http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative Commons Licence]] + +This work is licensed under a http://creativecommons.org/licenses/by/4.0/[Creative Commons Attribution 4.0 International License] From e2e5fa79168620bf0056a8b0c990c5c238ed1da1 Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Thu, 16 Mar 2023 14:57:04 +0000 Subject: [PATCH 25/54] Update 1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.asciidoc Remove odd link that claimed to be to some summary of INSPIRE IRs, but never has been. And one formatting issue. I don't know why the "sectnums" bit doesn't work; it looks the same pas page 1049, where it does! --- ...-for-discovery-metadata-for-geospatial-resources.asciidoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.asciidoc b/docs/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.asciidoc index cf0d8fd..413b9c1 100644 --- a/docs/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.asciidoc +++ b/docs/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.asciidoc @@ -115,8 +115,7 @@ services. The https://inspire.ec.europa.eu/about-inspire/563[EU INSPIRE Directive] mandates the collection of metadata for use in Europe. Implementing Rules define the requirements for metadata for discovery purposes. These are based on -ISO 19115, and -outlined link:1055-uk-gemini-major-changes-since-1-0[here]. +ISO 19115. The aim of UK GEMINI is to provide a core set of metadata elements for use in a UK geospatial metadata service, that are compatible with the @@ -268,7 +267,7 @@ sub-elements. Examples are Distributor and Vertical extent; - *Examples* -- Corresponding element** in INSPIRE Metadata, ISO 19115:2003, ISO +- *Corresponding element* in INSPIRE Metadata, ISO 19115:2003, ISO 19139:2007 - *Change history* – how the element has changed from v1.0 of the From 4b8fb14d22059a1098a91fc6d4a2947ec53fd8c3 Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Thu, 16 Mar 2023 14:57:35 +0000 Subject: [PATCH 26/54] tidying --- ...guidelines-for-geospatial-data-resources-part-2.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/1049-metadata-guidelines-for-geospatial-data-resources-part-2.asciidoc b/docs/1049-metadata-guidelines-for-geospatial-data-resources-part-2.asciidoc index 7a52cb7..a5c8394 100644 --- a/docs/1049-metadata-guidelines-for-geospatial-data-resources-part-2.asciidoc +++ b/docs/1049-metadata-guidelines-for-geospatial-data-resources-part-2.asciidoc @@ -129,10 +129,10 @@ for the purposes of INSPIRE.* Errors having the greatest impact are likely to be those that affect searches based on: -* *Where?*{nbsp}- geographical extent expressed in latitude and longitude or +* *Where?* - geographical extent expressed in latitude and longitude or some named standard area (e.g. administrative area, postcode, country); -* *What?*{nbsp}- theme, subject or topic; -* *When?*{nbsp}- date when data resource was current. +* *What?* - theme, subject or topic; +* *When?* - date when data resource was current. Errors in the metadata elements used by these searches will result in over- or under-selection of data resources and will degrade the quality From e5ef7f71268c1b7929dd7f3a58e19c03d781e8c2 Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Thu, 16 Mar 2023 15:20:27 +0000 Subject: [PATCH 27/54] Update 1052-metadata-guidelines-for-geospatial-data-resources-part-1.asciidoc Change internal links to link:, and manually full-URL index to sectnums Fix data.gov.uk CSW link - now at ckan.publishing.service.gov.uk Tidy heading styles Remove mention of bibliography on the assumption we won't migrate it (see https://github.com/agiorguk/gemini/issues/64#issuecomment-893499559) Fix link to "Part 3", which had gone to the bibliography - even in the live pages! --- ...-geospatial-data-resources-part-1.asciidoc | 144 +++++------------- 1 file changed, 40 insertions(+), 104 deletions(-) diff --git a/docs/1052-metadata-guidelines-for-geospatial-data-resources-part-1.asciidoc b/docs/1052-metadata-guidelines-for-geospatial-data-resources-part-1.asciidoc index fb4b144..dbf2847 100644 --- a/docs/1052-metadata-guidelines-for-geospatial-data-resources-part-1.asciidoc +++ b/docs/1052-metadata-guidelines-for-geospatial-data-resources-part-1.asciidoc @@ -1,77 +1,21 @@ -== Introduction to Metadata += Introduction to Metadata include::./includes/attributes.asciidoc[] -=== July 2018 +*July 2018* -Return -to{nbsp}https://www.agi.org.uk/gemini/40-gemini/1037-uk-gemini-standard-and-inspire-implementing-rules[GEMINI -2.3 home page] +Return to link:1037-uk-gemini-standard-and-inspire-implementing-rules[GEMINI 2.3 home page] -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#Intro[1. -Introduction] +:sectnums: +:sectnumlevels: 3 -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#fundamentals[2. -Fundamentals of Metadata] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#2.1[2.1 -The nature of metadata] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#2.2[2.2 -Metadata services] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#2.3[2.3 -Metadata as a business process] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#2.4[2.4 -Metadata roles] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#2.5[2.5 -Metadata standards] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#principles[3. -General principles of Metadata] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#3.1[3.1 -Introduction] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#3.2[3.2 -Free text] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#3.3[3.3 -Obligation] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#3.4[3.4 -Element domains] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#3.5[3.5 -Spatial references] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#3.6[3.6 -Date fields] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#scope[4. -Data resources in Scope] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#4.1[4.1 -What is stated in UK GEMINI2] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#4.2[4.2 -Characteristics of data resources in scope] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#4.3[4.3 -Applicability of UK GEMINI2] - -https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1#4.4[4.4 -Levels of data resources for documentation] - -=== Preface +== Preface These guidelines cover the basics of metadata for geospatial data resources and services. They are intended for general use in the UK geographic information environment and serve as a preamble to the more -detailed and specific -guidelines{nbsp}https://www.agi.org.uk/gemini/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2[Metadata -Guidelines for Geospatial Data Resources - Part 2]. They are primarily +detailed and specific guidelines +link:1049-metadata-guidelines-for-geospatial-data-resources-part-2[Metadata Guidelines for Geospatial Data Resources - Part 2]. +They are primarily concerned with geospatial data (i.e. that which references data to a location on the surface of the Earth), and which has a limited geographic extent (i.e. is restricted to a defined territory). Services @@ -88,7 +32,7 @@ guidance on quality management such that they could be used in the context of a national metadata service. A UK discovery metadata service forms part of data.gov.uk. As well as the human usable portal, this has a machine readable OGC “Catalogue Services for the Web” interface -(http://csw.data.gov.uk/geonetwork/srv/en/csw?service=CSW&version=2.0.2&request=GetCapabilities[OGC +(https://ckan.publishing.service.gov.uk/csw?request=GetCapabilities&service=CSW&version=2.0.2[OGC Capabilities document link]). The Guidelines have been revised during 2018 in the light of other @@ -96,7 +40,7 @@ developments, including revisions to UK GEMINI2. Any comments on these Guidelines or on UK GEMINI2 should be sent to{nbsp}gemini@agi.org.uk. -=== [#Intro]####1.{nbsp} Introduction +== Introduction These guidelines for the creation, maintenance and quality management of metadata for geospatial data resources, including the services which @@ -159,12 +103,11 @@ metadata, and in particular the UK GEMINI2 metadata set designed for discovery metadata services, the principles are equally applicable to internal metadata. -A glossary of terms is provided -in{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary[here]. +A glossary of terms is provided in link:1056-glossary[here]. -=== [#fundamentals]####2.{nbsp} Fundamentals of metadata +== Fundamentals of metadata -==== *_[#2.1]####2.1 The nature of metadata_* +=== The nature of metadata There are a range of uses for metadata, for discovery, for evaluation and for use: @@ -182,7 +125,7 @@ candidate resource is fit for the intended purpose. * *use*: the user has selected a candidate resource, but needs to access it and to configure a system or software to process it. -==== *_[#2.2]####2.2 Metadata services_* +=== Metadata services Metadata services provide one of the fundamental parts of a Spatial Data Infrastructure (SDI). They are used within organisations as part of the @@ -192,7 +135,7 @@ parameters such as Topic Category and Extent, to carry out a search to discover data resources that might be suitable and return information about their source, content and availability. -==== *_[#2.3]####2.3 Metadata as a business process_* +=== Metadata as a business process A simple process model is presented at Figure 1 and shows the flow from metadata creation through to metadata query with quality related @@ -225,7 +168,7 @@ finally picked up, it may well be assigned to someone who has no knowledge of the data resource and no interest in the quality of the metadata. -==== *_[#2.4]####2.4 Metadata roles_* +=== Metadata roles Three generic roles in the metadata process can be recognised, these are illustrated above: @@ -248,7 +191,7 @@ criteria matching their requirements, performs the searches and finds data resources meeting their requirements or, at least, meriting further investigation. -==== *_[#2.5]####2.5 Metadata standards_* +=== Metadata standards There are many metadata standards in existence. These have been produced at different times by different bodies for different purposes. The main @@ -303,19 +246,15 @@ their GeoDCAT Application Profile. At present, GEMINI makes no direct use of DCAT or GeoDCAT, but it does share some of the Dublin Core vocabulary. -Formal references for these standards and implementing rules are given -in -the{nbsp}https://www.agi.org.uk/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[Bibliography]. - -=== [#principles]####3.{nbsp} General principles of metadata +== General principles of metadata -==== *_[#3.1]####3.1 Introduction_* +=== Introduction This section describes some general high-level rules that apply to the creation of metadata. Whilst primarily applying to UK GEMINI2, they are also relevant to other metadata specifications. -==== *_[#3.2]####3.2 Free text_* +=== Free text The aim of a discovery metadata such as specified in UK GEMINI2 is to define metadata in a form that provides easily understood information @@ -332,7 +271,7 @@ the theme of the dataset, and the nearest option should be chosen. Where code lists are used, input and output facilities in a metadata service should identify the corresponding element value. -==== *_[#3.3]####3.3 Obligation_* +=== Obligation As with other data specifications, elements in UK GEMINI2 are given as mandatory, conditional or optional. Mandatory elements must be @@ -347,18 +286,18 @@ and there is a set of circumstances in which a value should be given, roughly corresponding to “is it relevant?” and “is its value known?” Optional elements should not be ignored. -==== *_[#3.4]####3.4 Element domains_* +=== Element domains Each metadata element has a range of allowable values, called its domain. These may be values in a given range (e.g. positive integers) or a set of code values chosen from a list. Specifying the domain helps with both the initial creation of data and quality checking [For further details on quality checking, -see{nbsp}https://www.agi.org.uk/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[Part -3{nbsp}]of these Guidelines]. In some cases, default values may be used, for +see https://www.agi.org.uk/wp-content/uploads/2020/11/METADATAGUIDELINESPART32015-04.pdf[Part 3] of these Guidelines]. +In some cases, default values may be used, for example for elements relating to the metadata itself. -==== *_[#3.5]####3.5 Spatial references_* +=== Spatial references By definition, geographic data contains some form of spatial reference. The spatial reference identifies the position of the object of interest @@ -372,7 +311,7 @@ data resource in the world (e.g. data for Scotland). A consistent set of spatial references enables spatial searches to be made for datasets in a metadata service. -==== *_[#3.6]####3.6 Date fields_* +=== Date fields Metadata can contain a multitude of dates identifying the different stages in the life cycle of the data. Key dates are included in @@ -380,21 +319,21 @@ metadata. To enable searches to be carried out (e.g. date relating to the period 1990 to 1999), these dates need to be recorded in standardised form. Unfortunately, different standards are used in different places. Here it is recommended that the extended format -defined in{nbsp}https://www.iso.org/iso-8601-date-and-time-format.html[ISO -8601]{nbsp}(YYYY-MM-DD) is used. +defined in https://www.iso.org/iso-8601-date-and-time-format.html[ISO +8601] (YYYY-MM-DD) is used. -=== [#scope]####4.{nbsp} Data resources in scope +== Data resources in scope -==== *_[#4.1]####4.1 What is stated in{nbsp}__UK GEMINI2_* +=== What is stated in{nbsp}__UK GEMINI2_* The purpose of this section is to provide guidance on -{empty}(i) what types of geospatial data can be documented using UK +(i) what types of geospatial data can be documented using UK GEMINI2, -{empty}(ii) the applicability of UK GEMINI2 and +(ii) the applicability of UK GEMINI2 and -{empty}(iii) how to find an appropriate level for the individual +(iii) how to find an appropriate level for the individual documentation of data resources. UK GEMINI2 “specifies a set of metadata elements for describing @@ -409,7 +348,7 @@ it be an individual map or the whole map series? There is no simple answer to these questions; it is likely to be a compromise. However, some general guidance can be given. -==== *_[#4.2]####4.2 Characteristics of data resources in scope_* +=== Characteristics of data resources in scope The general nature of geospatial data and access services is described in the Introduction. As is emphasised there, many data resources that at @@ -429,13 +368,13 @@ video form. All these types can be documented using UK GEMINI2. -==== *_[#4.3]####4.3 Applicability of{nbsp}__UK GEMINI2_* +=== Applicability of UK GEMINI2 The primary purpose of UK GEMINI2 is to provide the requirements for documenting data resources within the United Kingdom that conforms with the INSPIRE Metadata Implementing Rules. -==== *_[#4.4]####4.4 Levels of data resources for documentation_* +=== Levels of data resources for documentation There are no absolute rules for deciding on an appropriate level for the individual documentation of a data resource. The overriding @@ -563,10 +502,7 @@ if feasible. |=== -_{nbsp}Last updated: July 2018_ +_Last updated: July 2018_ -http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative -Commons Licence]] + -This work is licensed under -a{nbsp}http://creativecommons.org/licenses/by/4.0/[Creative Commons -Attribution 4.0 International License] +http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative Commons Licence]] + +This work is licensed under a http://creativecommons.org/licenses/by/4.0/[Creative Commons Attribution 4.0 International License] From df303103a560d4e6ddcb655399e144c3b3fa8d35 Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Sat, 18 Mar 2023 11:25:53 +0000 Subject: [PATCH 28/54] Update 1052 - fixed one heading w/ migrated format --- ...ata-guidelines-for-geospatial-data-resources-part-1.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/1052-metadata-guidelines-for-geospatial-data-resources-part-1.asciidoc b/docs/1052-metadata-guidelines-for-geospatial-data-resources-part-1.asciidoc index dbf2847..a231dff 100644 --- a/docs/1052-metadata-guidelines-for-geospatial-data-resources-part-1.asciidoc +++ b/docs/1052-metadata-guidelines-for-geospatial-data-resources-part-1.asciidoc @@ -324,7 +324,7 @@ defined in https://www.iso.org/iso-8601-date-and-time-format.html[ISO == Data resources in scope -=== What is stated in{nbsp}__UK GEMINI2_* +=== What is stated in UK GEMINI2 The purpose of this section is to provide guidance on From 6278ac5bb799e0e916455795d60c86ec410ec8cd Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Mon, 20 Mar 2023 17:52:16 +0000 Subject: [PATCH 29/54] WIP PR to address discussion issue https://github.com/agiorguk/gemini/discussions/91#discussion-4945524 around how to better style code fragments. This branch uses pygments for code highlighting, with some styling overrides in assets/gemini.css. It's not perfect but at least demonstrates how to get the styling to work. So far, abstract, additionalinformation, boundingbox, characterencoding and metadatadate have been done --- docs/assets/gemini.css | 17 +++++++- docs/datasets.adoc | 5 +-- docs/includes/attributes.asciidoc | 9 ++--- docs/partials/abstract.asciidoc | 17 ++++---- docs/partials/additionalinformation.asciidoc | 25 ++++++------ docs/partials/alternatetitle.asciidoc | 40 +++++++++++-------- docs/partials/boundingbox.asciidoc | 17 ++++---- docs/partials/characterencoding.asciidoc | 14 +++---- .../includes/partials-attributes.adoc | 8 ++-- docs/partials/metadatadate.asciidoc | 25 ++++++------ 10 files changed, 95 insertions(+), 82 deletions(-) diff --git a/docs/assets/gemini.css b/docs/assets/gemini.css index e8502d3..653126e 100644 --- a/docs/assets/gemini.css +++ b/docs/assets/gemini.css @@ -17,7 +17,7 @@ table th, table td { } table { - border: 1px solid #f2f2​f2; + border: 1px solid #f2f2f2; } details { @@ -28,4 +28,17 @@ details { details .content { color: rgb(103, 97, 97); -} \ No newline at end of file +} + +/*.highlight pre { + background-color: transparent !important; + white-space: normal; +} */ + +code[data-lang="xml"] { + font-size: 0.75em !important; + white-space: pre !important; + line-height: 1.0 !important; + background-color: transparent !important; +} + diff --git a/docs/datasets.adoc b/docs/datasets.adoc index f19bef9..013c881 100644 --- a/docs/datasets.adoc +++ b/docs/datasets.adoc @@ -1,6 +1,5 @@ -== [[top]]UK GEMINI 2.3 2020-04-07 dataset or series dev version - -include::includes/attributes.asciidoc[] += [[top]]UK GEMINI 2.3 2020-04-07 dataset or series dev version +include::./includes/attributes.asciidoc[] == Contents diff --git a/docs/includes/attributes.asciidoc b/docs/includes/attributes.asciidoc index f6d997e..436b0f7 100644 --- a/docs/includes/attributes.asciidoc +++ b/docs/includes/attributes.asciidoc @@ -1,13 +1,10 @@ :assetdir: ./assets :stylesdir: {assetdir} :figure-caption: Figure -:toc: left :docinfo: shared -:safe-mode-unsafe: :iconfont-remote!: :stylesheet: gemini.css :scriptsdir: {assetdir} -:linkcss: :data-uri: :iconfont-name: font-awesome.min :imagesdir: media @@ -15,6 +12,6 @@ :sectnumlevels: 3 :sectlinks: :sectanchors: -:experimental: -:stem: -:toclevels: 4 \ No newline at end of file +:toclevels: 4 +:source-highlighter: pygments +:pygments-style: default diff --git a/docs/partials/abstract.asciidoc b/docs/partials/abstract.asciidoc index 5e32934..0439674 100644 --- a/docs/partials/abstract.asciidoc +++ b/docs/partials/abstract.asciidoc @@ -1,4 +1,4 @@ -= Abstract +== Abstract include::includes/partials-attributes.adoc[] [#4] @@ -82,20 +82,19 @@ Change history... .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines |Cannot be empty - -|Example a| - -.... +| Guidelines | Cannot be empty +| Example +| +[source,xml] +---- ifdef::variant-dataset[] include::../snippets/dataset-abstract.xml[] -endif::[] ifdef::variant-service[] include::../snippets/service-abstract.xml[] endif::[] -.... - +---- |=== ==== diff --git a/docs/partials/additionalinformation.asciidoc b/docs/partials/additionalinformation.asciidoc index bc69d03..68590b9 100644 --- a/docs/partials/additionalinformation.asciidoc +++ b/docs/partials/additionalinformation.asciidoc @@ -1,4 +1,4 @@ -= Additional information +== Additional information include::includes/partials-attributes.adoc[] [#27] @@ -65,23 +65,22 @@ MD_DataIdentification.supplementalInformation |Equivalent .Encoding guidelines... [%collapsible] ==== -[width="100%",cols="50%,50%",] +[cols="a,a"] |=== |Guidelines |No specific rules for this metadata element - -|Example a| -Example one - -.... +|Example One +| +[source,xml] +---- include::../snippets/additionalinformation-characterstring.xml[] -.... - -Example two - a link, using gmx:Anchor - -.... +---- +|Example two - a link, using gmx:Anchor +| +[source,xml] +---- include::../snippets/additionalinformation-anchor.xml[] .... - +---- |=== ==== diff --git a/docs/partials/alternatetitle.asciidoc b/docs/partials/alternatetitle.asciidoc index 26e0238..de7e2cb 100644 --- a/docs/partials/alternatetitle.asciidoc +++ b/docs/partials/alternatetitle.asciidoc @@ -1,4 +1,4 @@ -= Alternative title +== Alternative title include::includes/partials-attributes.adoc[] [#2] @@ -63,35 +63,43 @@ endif::[] ==== .Change history... -[%collapsible]ncoding guidelines... +[%collapsible] +==== +==== +.Encoding guidelines... [%collapsible] ==== -[width="100%",cols="50%,50%",] +[cols="a,a"] |=== |Guidelines |Note that more than one alternative title may be presented, as shown in the example below. - -|Example a| +|Example ifdef::variant-dataset[] -Example one -.... +| +|Example one +| +[source,xml] +---- include::../snippets/dataset-alternatetitle-multi.xml[] -.... - -Example two - -.... +---- +|Example two +| +[source,xml] +---- include::../snippets/dataset-alternatetitle-multi.xml[] -.... +---- +|=== endif::[] ifdef::variant-service[] -.... +| +[source,xml] +---- include::../snippets/service-alternatetitle-multi.xml[] .... -endif::[] - +---- |=== +endif::[] ==== .Metadata errors observed... diff --git a/docs/partials/boundingbox.asciidoc b/docs/partials/boundingbox.asciidoc index a13c081..70ec692 100644 --- a/docs/partials/boundingbox.asciidoc +++ b/docs/partials/boundingbox.asciidoc @@ -1,4 +1,4 @@ -= Bounding box +== Bounding box include::includes/partials-attributes.adoc[] [#44] @@ -105,8 +105,10 @@ Bounding box, which was made multiple .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| . The encoding example for geographic bounding box for datasets is shown in the example . Note that the extent XML element is in the gmd namespace. This differs @@ -129,18 +131,17 @@ property of MD_DataIdentification (ISO 19115) and SV_ServiceIdentification (ISO 19119/Amd 1:2008), not a property of the parent MD_Identification. endif::[] - -|Example a| - -.... +|Example +| +[source,xml] +---- ifdef::variant-dataset[] include::../snippets/dataset-boundingbox.xml[] endif::[] ifdef::variant-service[] include::../snippets/service-boundingbox.xml[] endif::[] -.... - +---- |=== ==== diff --git a/docs/partials/characterencoding.asciidoc b/docs/partials/characterencoding.asciidoc index a2909e7..3c74364 100644 --- a/docs/partials/characterencoding.asciidoc +++ b/docs/partials/characterencoding.asciidoc @@ -1,4 +1,4 @@ -= Character encoding +== Character encoding include::includes/partials-attributes.adoc[] [#51] @@ -59,16 +59,16 @@ New element in GEMINI 2.3 .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== |Guidelines |Only the codeListValue is required, the codeList and the free text content are optional and informative only - -|Example a| - -.... +|Example +| +[source,xml] +---- include::../snippets/characterencoding.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/includes/partials-attributes.adoc b/docs/partials/includes/partials-attributes.adoc index f3f8d29..f0e9c13 100644 --- a/docs/partials/includes/partials-attributes.adoc +++ b/docs/partials/includes/partials-attributes.adoc @@ -5,11 +5,9 @@ :docinfo: shared :docinfodir: {assetdir} :docinfosubs: attributes -:safe-mode-unsafe: :iconfont-remote!: -:stylesheet: ../assets/gemini.css +:stylesheet: gemini.css :scriptsdir: {assetdir} -:linkcss: :data-uri: :iconfont-name: font-awesome.min :imagesdir: media @@ -17,5 +15,5 @@ :sectnumlevels: 3 :sectlinks: :sectanchors: -:experimental: -:stem: \ No newline at end of file +:source-highlighter: pygments +:pygments-style: default \ No newline at end of file diff --git a/docs/partials/metadatadate.asciidoc b/docs/partials/metadatadate.asciidoc index 820fb49..cf87d83 100644 --- a/docs/partials/metadatadate.asciidoc +++ b/docs/partials/metadatadate.asciidoc @@ -1,4 +1,4 @@ -= Metadata Date +== Metadata Date include::includes/partials-attributes.adoc[] [#30] @@ -62,24 +62,23 @@ GEMINI 1 to 2.0: Change of name from Date of last update of metadata .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== |Guidelines |The encoding example for metadata date is shown in Example One. Note that it is possible to record the date and time of the metadata instance using the encoding shown in Example Two. - -|Example a| -`Example One - -.... +|Example One +| +[source,xml] +---- include::../snippets/metadatadate.xml[] -.... - -Example Two (date and time) - -.... +---- +|Example Two (date and time) +| +[source,xml] +---- include::../snippets/metadatadatetime.xml[] -.... - +---- |=== ==== From c15fb00d6061c9860b865edef2eb1d6938b99154 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Mon, 20 Mar 2023 17:54:17 +0000 Subject: [PATCH 30/54] added pygments-default.css to the WIP patch-styling-branch --- docs/assets/pygments-default.css | 69 ++++++++++++++++++++++++++++++++ 1 file changed, 69 insertions(+) create mode 100644 docs/assets/pygments-default.css diff --git a/docs/assets/pygments-default.css b/docs/assets/pygments-default.css new file mode 100644 index 0000000..089a2d2 --- /dev/null +++ b/docs/assets/pygments-default.css @@ -0,0 +1,69 @@ +pre.pygments .hll { background-color: #ffffcc } +pre.pygments { background: #f8f8f8; } +pre.pygments .tok-c { color: #408080; font-style: italic } /* Comment */ +pre.pygments .tok-err { border: 1px solid #FF0000 } /* Error */ +pre.pygments .tok-k { color: #008000; font-weight: bold } /* Keyword */ +pre.pygments .tok-o { color: #666666 } /* Operator */ +pre.pygments .tok-ch { color: #408080; font-style: italic } /* Comment.Hashbang */ +pre.pygments .tok-cm { color: #408080; font-style: italic } /* Comment.Multiline */ +pre.pygments .tok-cp { color: #BC7A00 } /* Comment.Preproc */ +pre.pygments .tok-cpf { color: #408080; font-style: italic } /* Comment.PreprocFile */ +pre.pygments .tok-c1 { color: #408080; font-style: italic } /* Comment.Single */ +pre.pygments .tok-cs { color: #408080; font-style: italic } /* Comment.Special */ +pre.pygments .tok-gd { color: #A00000 } /* Generic.Deleted */ +pre.pygments .tok-ge { font-style: italic } /* Generic.Emph */ +pre.pygments .tok-gr { color: #FF0000 } /* Generic.Error */ +pre.pygments .tok-gh { color: #000080; font-weight: bold } /* Generic.Heading */ +pre.pygments .tok-gi { color: #00A000 } /* Generic.Inserted */ +pre.pygments .tok-go { color: #888888 } /* Generic.Output */ +pre.pygments .tok-gp { color: #000080; font-weight: bold } /* Generic.Prompt */ +pre.pygments .tok-gs { font-weight: bold } /* Generic.Strong */ +pre.pygments .tok-gu { color: #800080; font-weight: bold } /* Generic.Subheading */ +pre.pygments .tok-gt { color: #0044DD } /* Generic.Traceback */ +pre.pygments .tok-kc { color: #008000; font-weight: bold } /* Keyword.Constant */ +pre.pygments .tok-kd { color: #008000; font-weight: bold } /* Keyword.Declaration */ +pre.pygments .tok-kn { color: #008000; font-weight: bold } /* Keyword.Namespace */ +pre.pygments .tok-kp { color: #008000 } /* Keyword.Pseudo */ +pre.pygments .tok-kr { color: #008000; font-weight: bold } /* Keyword.Reserved */ +pre.pygments .tok-kt { color: #B00040 } /* Keyword.Type */ +pre.pygments .tok-m { color: #666666 } /* Literal.Number */ +pre.pygments .tok-s { color: #BA2121 } /* Literal.String */ +pre.pygments .tok-na { color: #7D9029 } /* Name.Attribute */ +pre.pygments .tok-nb { color: #008000 } /* Name.Builtin */ +pre.pygments .tok-nc { color: #0000FF; font-weight: bold } /* Name.Class */ +pre.pygments .tok-no { color: #880000 } /* Name.Constant */ +pre.pygments .tok-nd { color: #AA22FF } /* Name.Decorator */ +pre.pygments .tok-ni { color: #999999; font-weight: bold } /* Name.Entity */ +pre.pygments .tok-ne { color: #D2413A; font-weight: bold } /* Name.Exception */ +pre.pygments .tok-nf { color: #0000FF } /* Name.Function */ +pre.pygments .tok-nl { color: #A0A000 } /* Name.Label */ +pre.pygments .tok-nn { color: #0000FF; font-weight: bold } /* Name.Namespace */ +pre.pygments .tok-nt { color: #008000; font-weight: bold } /* Name.Tag */ +pre.pygments .tok-nv { color: #19177C } /* Name.Variable */ +pre.pygments .tok-ow { color: #AA22FF; font-weight: bold } /* Operator.Word */ +pre.pygments .tok-w { color: #bbbbbb } /* Text.Whitespace */ +pre.pygments .tok-mb { color: #666666 } /* Literal.Number.Bin */ +pre.pygments .tok-mf { color: #666666 } /* Literal.Number.Float */ +pre.pygments .tok-mh { color: #666666 } /* Literal.Number.Hex */ +pre.pygments .tok-mi { color: #666666 } /* Literal.Number.Integer */ +pre.pygments .tok-mo { color: #666666 } /* Literal.Number.Oct */ +pre.pygments .tok-sa { color: #BA2121 } /* Literal.String.Affix */ +pre.pygments .tok-sb { color: #BA2121 } /* Literal.String.Backtick */ +pre.pygments .tok-sc { color: #BA2121 } /* Literal.String.Char */ +pre.pygments .tok-dl { color: #BA2121 } /* Literal.String.Delimiter */ +pre.pygments .tok-sd { color: #BA2121; font-style: italic } /* Literal.String.Doc */ +pre.pygments .tok-s2 { color: #BA2121 } /* Literal.String.Double */ +pre.pygments .tok-se { color: #BB6622; font-weight: bold } /* Literal.String.Escape */ +pre.pygments .tok-sh { color: #BA2121 } /* Literal.String.Heredoc */ +pre.pygments .tok-si { color: #BB6688; font-weight: bold } /* Literal.String.Interpol */ +pre.pygments .tok-sx { color: #008000 } /* Literal.String.Other */ +pre.pygments .tok-sr { color: #BB6688 } /* Literal.String.Regex */ +pre.pygments .tok-s1 { color: #BA2121 } /* Literal.String.Single */ +pre.pygments .tok-ss { color: #19177C } /* Literal.String.Symbol */ +pre.pygments .tok-bp { color: #008000 } /* Name.Builtin.Pseudo */ +pre.pygments .tok-fm { color: #0000FF } /* Name.Function.Magic */ +pre.pygments .tok-vc { color: #19177C } /* Name.Variable.Class */ +pre.pygments .tok-vg { color: #19177C } /* Name.Variable.Global */ +pre.pygments .tok-vi { color: #19177C } /* Name.Variable.Instance */ +pre.pygments .tok-vm { color: #19177C } /* Name.Variable.Magic */ +pre.pygments .tok-il { color: #666666 } /* Literal.Number.Integer.Long */ \ No newline at end of file From c5516cdc6cce489d325d64225ff6599ea6e3aecc Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Tue, 21 Mar 2023 09:58:00 +0000 Subject: [PATCH 31/54] added highlighttest to see if pygments is actually working in the github version of asciidoctor --- docs/highlighttest.adoc | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 docs/highlighttest.adoc diff --git a/docs/highlighttest.adoc b/docs/highlighttest.adoc new file mode 100644 index 0000000..55615e4 --- /dev/null +++ b/docs/highlighttest.adoc @@ -0,0 +1,4 @@ += Testing syntax highlighting for text in tables +include::./includes/attributes.asciidoc[] + +include::./partials/abstract.asciidoc[] From 269c46bbe7af4ea52499585aa346eb4847904dba Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Tue, 21 Mar 2023 10:07:04 +0000 Subject: [PATCH 32/54] Update dev-build.yml --- .github/workflows/dev-build.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/dev-build.yml b/.github/workflows/dev-build.yml index 66d7dd2..aa15a38 100644 --- a/.github/workflows/dev-build.yml +++ b/.github/workflows/dev-build.yml @@ -27,7 +27,7 @@ jobs: uses: peaceiris/actions-gh-pages@v3 with: personal_token: ${{ secrets.API_TOKEN_GITHUB }} - external_repository: agiorguk/gemini-dev + external_repository: archaeogeek/gemini-dev publish_branch: gh-pages publish_dir: ./docs/ enable_jekyll: true From 1758627628734bacdfa3c5c403b3c096888a3215 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Tue, 21 Mar 2023 10:14:23 +0000 Subject: [PATCH 33/54] Update dev-build.yml --- .github/workflows/dev-build.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/dev-build.yml b/.github/workflows/dev-build.yml index aa15a38..2217923 100644 --- a/.github/workflows/dev-build.yml +++ b/.github/workflows/dev-build.yml @@ -17,12 +17,12 @@ jobs: id: adocbuild-datasets uses: avattathil/asciidoctor-action@master with: - program: "asciidoctor -a variant-dataset -a stylesheet=assets/gemini.css -a docinfo1 'docs/*.asciidoc' 'docs/*.adoc'" + program: "asciidoctor -a variant-dataset -a stylesheet=./assets/gemini.css -a docinfo1 'docs/*.asciidoc' 'docs/*.adoc'" - name: Build services variant id: adocbuild-services uses: avattathil/asciidoctor-action@master with: - program: "asciidoctor -a variant-service -a stylesheet=assets/gemini.css -a docinfo1 'docs/*.asciidoc' 'docs/*.adoc'" + program: "asciidoctor -a variant-service -a stylesheet=./assets/gemini.css -a docinfo1 'docs/*.asciidoc' 'docs/*.adoc'" - name: Deploy docs to ghpages uses: peaceiris/actions-gh-pages@v3 with: From 4a2c5b012ec3b10b736e5d50c306515f9f2f1934 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Tue, 21 Mar 2023 10:22:50 +0000 Subject: [PATCH 34/54] WIP test relative URLs in readme page --- docs/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/README.md b/docs/README.md index 3411357..9c8adaf 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,8 +1,8 @@ # Gemini documentation DEV branch -* [Services](https://agiorguk.github.io/gemini-dev/services.html) -* [Datasets](https://agiorguk.github.io/gemini-dev/datasets.html) +* [Services](services.html) +* [Datasets](datasets.html) The files below have been converted but have not been altered to work using the new workflow. Consequently internal links will go to the agi website and there may be other errors. * [1037-uk-gemini-standard-and-inspire-implementing-rules](https://agiorguk.github.io/gemini-dev/1037-uk-gemini-standard-and-inspire-implementing-rules.html) From c292a28b40c5d1e1299196ecaf4224d9662d712e Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Tue, 21 Mar 2023 11:19:39 +0000 Subject: [PATCH 35/54] WIP- made changes to encoding guidelines for conformity, coupledresource, dataformat, dataquality, datasetlanguage, equivalentscale and extent --- docs/Gemini.css | 89 ------------------- docs/README.md | 4 +- docs/includes/attributes.asciidoc | 4 +- docs/partials/conformity.asciidoc | 41 +++++---- docs/partials/coupledresource.asciidoc | 47 +++++----- docs/partials/dataformat.asciidoc | 25 +++--- docs/partials/dataquality.asciidoc | 38 ++++---- docs/partials/datasetlanguage.asciidoc | 19 ++-- docs/partials/datasetreferencedate.asciidoc | 46 +++++----- docs/partials/equivalentscale.asciidoc | 20 +++-- docs/partials/extent.asciidoc | 47 +++++----- .../includes/partials-attributes.adoc | 8 +- 12 files changed, 150 insertions(+), 238 deletions(-) delete mode 100644 docs/Gemini.css diff --git a/docs/Gemini.css b/docs/Gemini.css deleted file mode 100644 index 838f6fd..0000000 --- a/docs/Gemini.css +++ /dev/null @@ -1,89 +0,0 @@ - .gem .box { - display:block; - padding:9.5px; - margin:20px 0 10px; - font-size:16px; - line-height:1.5; - color:#333; - word-break:break-all; - word-wrap:break-word; - background-color:#f5f5f5; - border:1px solid #ccc; - border-radius:4px - } - .gem .spacer { padding-bottom: 80px } - .gem .box a { - text-decoration:none; - color:inherit; - } - .gem .readmore { - padding-left:10px; - } - .gem .readmore a { - cursor:pointer; - } - .gem .gemini-list { - /* background:#e5e1e0; */ - padding:10px 0; - border-top:1px solid #7f7f7f; - border-bottom:1px solid #7f7f7f; - margin-bottom:20px; - } - .gem .gemini-item { - border-bottom:1px solid #7f7f7f; - padding-bottom:15px; - margin-bottom:15px; - } - .gem .gemini-expander { - display: none; - } - .gem .gemini-mono { - font-size:12px; - font-weight:bold; - } - .gem .gemini-xml { - font-family: monospace; - font-size:12px; - color:red; - } - # moved - .gem pre { - font-family: monospace; - font-size:12px; - color:red; - overflow: auto; - word-wrap: normal; - white-space: pre; - } - # moved - .gem table { - border: 1px solid #ddd; - border-collapse: collapse; - margin:15px 0; - } - .gem table table { - margin:0; - } - .gem th, - .gem td { - border: 1px solid #ddd; - padding: 3px; - text-align: left; - vertical-align: top; - font-size:12px; - } - .gem .thOther { - background-color: #7f7f7f; - color: white; - } - .gem .tbold { - font-size:12px; - font-weight:bold; - background-color: #7f7f7f; - color: white; - } - .gem .tgrey { - font-size:12px; - background-color: #cdcdcd; - color: grey; - } diff --git a/docs/README.md b/docs/README.md index 9c8adaf..3411357 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,8 +1,8 @@ # Gemini documentation DEV branch -* [Services](services.html) -* [Datasets](datasets.html) +* [Services](https://agiorguk.github.io/gemini-dev/services.html) +* [Datasets](https://agiorguk.github.io/gemini-dev/datasets.html) The files below have been converted but have not been altered to work using the new workflow. Consequently internal links will go to the agi website and there may be other errors. * [1037-uk-gemini-standard-and-inspire-implementing-rules](https://agiorguk.github.io/gemini-dev/1037-uk-gemini-standard-and-inspire-implementing-rules.html) diff --git a/docs/includes/attributes.asciidoc b/docs/includes/attributes.asciidoc index 436b0f7..4d4e458 100644 --- a/docs/includes/attributes.asciidoc +++ b/docs/includes/attributes.asciidoc @@ -1,10 +1,8 @@ -:assetdir: ./assets -:stylesdir: {assetdir} +:stylesdir: assets :figure-caption: Figure :docinfo: shared :iconfont-remote!: :stylesheet: gemini.css -:scriptsdir: {assetdir} :data-uri: :iconfont-name: font-awesome.min :imagesdir: media diff --git a/docs/partials/conformity.asciidoc b/docs/partials/conformity.asciidoc index 814e8c8..926c133 100644 --- a/docs/partials/conformity.asciidoc +++ b/docs/partials/conformity.asciidoc @@ -1,4 +1,4 @@ -= Conformity +== Conformity include::includes/partials-attributes.adoc[] [#41] @@ -124,9 +124,10 @@ been tested against the relevant INSPIRE specification .Encoding guidelines... [%collapsible] ==== -[width="100%",cols="50%,50%",] +[cols="a,a"] |=== -|Guidelines a| +| Guidelines +| . The encoding for Conformity is shown in the example. . Note that the encoding of conformity requires a specification (encoded using gmd:CI_Citation), an explanation and a pass. @@ -134,7 +135,6 @@ using gmd:CI_Citation), an explanation and a pass. possible conformance results: conformant, not conformant and not evaluated. Not evaluated is expressed by a conformity statement with a nilReason (unknown) specified in the pass element. - ifdef::variant-dataset[] . All gmd:dataQualityInfo XML element shall have a gmd:scope XML element, set to 'dataset' or 'series' as appropriate. @@ -146,35 +146,38 @@ element, set to 'service'. information is 'service' then the gmd:levelDescription XML element is required, as shown below. endif::[] -|Example a| - -.... +|Example +| +[source,xml] +---- ifdef::variant-dataset[] include::../snippets/dataset-conformity-inspire-ortho.xml[] +---- endif::[] ifdef::variant-service[] include::../snippets/service-conformity-abstracttestsuite.xml[] +---- +|=== endif::[] -.... ifdef::variant-dataset[] - -Example of a conformity report for Implementing Rule 1089/2010, where +| Example of a conformity report for Implementing Rule 1089/2010, where conformance is not evaluated. + Example follows updated guidance to use gmx:Anchor over gco:CharacterString for Citation titles - -.... +| +[source,xml] +---- include::../snippets/dataset-conformity-inspire-notevaluated.xml[] -.... - -Example three ~ Topological consistency, showing mandatory elements for +---- +| Example three ~ Topological consistency, showing mandatory elements for a descriptive topological consistency report - -.... +| +[source,xml] +---- include::../snippets/dataset-conformity-inspire-topo.xml[] -.... -endif::[] +---- |=== +endif::[] ==== .Metadata errors observed... diff --git a/docs/partials/coupledresource.asciidoc b/docs/partials/coupledresource.asciidoc index eb04801..49db919 100644 --- a/docs/partials/coupledresource.asciidoc +++ b/docs/partials/coupledresource.asciidoc @@ -1,4 +1,4 @@ -= Coupled resource +== Coupled resource include::includes/partials-attributes.adoc[] [#38] @@ -56,11 +56,13 @@ This may be: GEMINI 1 to 2.0: New element, required for INSPIRE ==== -.Encoding guidelines... +Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +| Guidelines +| . https://inspire.ec.europa.eu/documents/inspire-metadata-implementing-rules-technical-guidelines-based-en-iso-19115-and-en-iso-1[INSPIRE guidance] link:component/content/article?id=1047[[9]] states that Coupled resource shall be implemented by reference, i.e. through a URL @@ -109,35 +111,32 @@ obtain from the metadata instance. In the case of GEMINI and INSPIRE metadata it will be the first MD_DataIdentification element in the instance (XPath //gmd:identificationInfo[1]) unless a fragment identifier is used, in which case it may be in any location. - -|Example a| -`Example One using the by reference mechanism and an OGC CSW request ` - -.... +| Example One using the by reference mechanism and an OGC CSW request +| +[source,xml] +---- include::../snippets/coupledresource-cswrequest.xml[] -.... - -Example Two using WAF - -.... +---- +| Example Two using WAF +| +[source,xml] +---- include::../snippets/coupledresource-waf.xml[] -.... - -Example Three using the by reference mechanism and an OGC CSW request +---- +| Example Three using the by reference mechanism and an OGC CSW request with a fragment identifier. - -.... +| +[source,xml] +---- include::../snippets/coupledresource-cswrequest-fragment.xml[] -.... - +---- In this example the fragment identifier #BGS-13480426 would correspond to the value of the id attribute of the gmd:MD_DataIdentification element of the dataset metadata record, like below - -.... +[source,xml] +---- -.... - +---- |=== ==== diff --git a/docs/partials/dataformat.asciidoc b/docs/partials/dataformat.asciidoc index 2d91377..90426df 100644 --- a/docs/partials/dataformat.asciidoc +++ b/docs/partials/dataformat.asciidoc @@ -1,4 +1,4 @@ -= Data format +== Data format include::includes/partials-attributes.adoc[] [#21] @@ -67,23 +67,22 @@ versioned, a nil reason attribute shall be specified with either .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== |Guidelines |Both a gmd:name and gmd:version shall be provided for the format - -|Example a| -Example One - -.... +|Example One +| +[source,xml] +---- include::../snippets/dataformat-name-version.xml[] -.... - -Example Two - unknown version - -.... +---- +|Example Two - unknown version +| +[source,xml] +---- include::../snippets/dataformat-name-unknownversion.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/dataquality.asciidoc b/docs/partials/dataquality.asciidoc index e14a93e..3badb17 100644 --- a/docs/partials/dataquality.asciidoc +++ b/docs/partials/dataquality.asciidoc @@ -1,4 +1,4 @@ -= Data quality +== Data quality include::includes/partials-attributes.adoc[] [#52] @@ -257,9 +257,10 @@ New element in GEMINI 2.3 .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| -There shall be exactly one gmd:dataQualityInfo/gmd:DQ_DataQuality +|Guidelines +| There shall be exactly one gmd:dataQualityInfo/gmd:DQ_DataQuality element scoped to the entire described data set or data set series. So if the scope of the quality measure is the entire dataset or series, then the result shall be in the same DQ_DataQuality element as the @@ -285,26 +286,25 @@ declared as xs:double. As well as the mandatory elements, it is also recommended to supply a name of the measure, a short description of the evaluation method, and a date for the evaluation of the consistency check - -|Example a| - -.... +|Example +| +[source,xml] +---- include::../snippets/dataquality-mixed.xml[] -.... - -Example two - Topological consistency - -.... +---- +| Example two - Topological consistency +| +[source,xml] +---- include::../snippets/dataquality-topo-qualitative.xml[] -.... - -Example three ~ Topological consistency, showing a quantitative +---- +| Example three ~ Topological consistency, showing a quantitative topological consistency report with recommended elements included - -.... +| +[source,xml] +---- include::../snippets/dataquality-topo-quantitative.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/datasetlanguage.asciidoc b/docs/partials/datasetlanguage.asciidoc index 47aa9c3..8d995a0 100644 --- a/docs/partials/datasetlanguage.asciidoc +++ b/docs/partials/datasetlanguage.asciidoc @@ -1,4 +1,4 @@ -= Dataset language +== Dataset language include::includes/partials-attributes.adoc[] [#3] @@ -80,9 +80,10 @@ content; not applicable" shall be used. .Encoding guidelines... [%collapsible] ==== -[width="100%",cols="50%,50%",] +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| . Note that according to the ISO 19115 logical model the language property is typed as a CharacterString. The use of the gco:CharacterString type is permitted by the ISO 19139 schemas but this @@ -95,14 +96,12 @@ value in GEMINI2 metadata instances: http://www.loc.gov/standards/iso639-2/php/code_list.php . Note however, that this URL resolves to an HTML web page rather than a service endpoint providing ISO 639-2 language codes. - -|Example a| -Example following the INSPIRE recommendation of using the name of the language as the content of the gmd:LanguageCode - -.... +|Example following the INSPIRE recommendation of using the name of the language as the content of the gmd:LanguageCode +| +[source,xml] +---- include::../snippets/datasetlanguage.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/datasetreferencedate.asciidoc b/docs/partials/datasetreferencedate.asciidoc index 1834048..abd5911 100644 --- a/docs/partials/datasetreferencedate.asciidoc +++ b/docs/partials/datasetreferencedate.asciidoc @@ -1,4 +1,4 @@ -= Dataset reference date +== Dataset reference date include::includes/partials-attributes.adoc[] [#8] @@ -109,8 +109,10 @@ GEMINI 1 to 2.0: Addition of date type .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| * The encoding for dataset reference date is shown in Example One. * Dates may be expressed with low precision, as shown in the example. GEMINI2 also allows the date and time to be published in metadata. In @@ -120,34 +122,34 @@ link:component/content/article?id=1048#2.2.3[Dates and Times] * Dataset reference date shall include a date type. The content of this XML element is drawn from a link:component/content/article?id=1048#2.2.9[code list]. - -|Example a| ifdef::variant-dataset[] -Example One (datasets/series): dataset reference date encoding example - -.... +| Example One: date +| +[source,xml] +---- include::../snippets/dataset-datasetreferencedate-date.xml[] -.... - -Example Two - date and time - -.... -... +---- +| Example Two - date and time +| +[source,xml] +---- include::../snippets/datasetreferencedate-datetime.xml[] -... -.... +---- endif::[] ifdef::variant-service[] -Example One: date - -.... +| Example One: date +| +[source,xml] +---- include::../snippets/service-datasetreferencedate-date.xml[] -... +---- +| Example Two - date and time +| +[source,xml] +---- include::../snippets/datasetreferencedate-datetime.xml[] -... -.... +---- endif::[] - |=== ==== diff --git a/docs/partials/equivalentscale.asciidoc b/docs/partials/equivalentscale.asciidoc index ce9d8b9..0f6d3fc 100644 --- a/docs/partials/equivalentscale.asciidoc +++ b/docs/partials/equivalentscale.asciidoc @@ -1,4 +1,4 @@ -= Equivalent scale +== Equivalent scale include::includes/partials-attributes.adoc[] [#43] @@ -64,17 +64,21 @@ GEMINI 1 to 2.0: New element .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== ifdef::variant-dataset[] -|Guidelines | -|Example a| - -.... +|Guidelines +| +|Example +| +[source,xml] +---- include::../snippets/equivalentscale.xml[] -.... +---- endif::[] ifdef::variant-service[] -|Guidelines a| +|Guidelines +| * For services, it is not possible to express the restriction of a service concerning the spatial resolution when using the ISO 19139 XML Schema. @@ -83,7 +87,7 @@ Schema. equivalent scale as integer valued scale denominator or a resolution distance using a numerical length value and with a unit of length. endif::[] - +| |=== ==== diff --git a/docs/partials/extent.asciidoc b/docs/partials/extent.asciidoc index cb9a900..d98ef87 100644 --- a/docs/partials/extent.asciidoc +++ b/docs/partials/extent.asciidoc @@ -1,4 +1,4 @@ -= Extent +== Extent include::includes/partials-attributes.adoc[] [#15] @@ -92,8 +92,10 @@ GEMINI 1 to 2.0: Made optional .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| . The examples shown below use codes (URIs in URL form) from the http://data.os.uk[Ordnance Survey Linked Data] link:component/content/article?id=1047[[22]] @@ -120,35 +122,34 @@ Note that the extent XML element is in the srv namespace. This differs from dataset metadata instances where the extent XML element will be in the gmd namespace. endif::[] - -|Example a| ifdef::variant-dataset[] -Example One (datasets/series) - -.... +|Example One +| +[source,xml] +---- include::../snippets/dataset-extent-code.xml[] -.... - -Example Two (datasets/series) - Extent encoding example with authority - -.... +---- +| Example Two- Extent encoding example with authority +| +[source,xml] +---- include::../snippets/dataset-extent-codeauthority.xml[] -.... +---- endif::[] ifdef::variant-service[] -Example One (services) ` - -.... +| Example One +| +[source,xml] +---- include::../snippets/service-extent-code.xml[] -.... - -Example Two (services) - Extent encoding example with authority - -.... +---- +|Example Two - Extent encoding example with authority +| +[source,xml] +---- include::../snippets/service-extent-codeauthority.xml[] -.... +---- endif::[] - |=== ==== diff --git a/docs/partials/includes/partials-attributes.adoc b/docs/partials/includes/partials-attributes.adoc index f0e9c13..1ed5726 100644 --- a/docs/partials/includes/partials-attributes.adoc +++ b/docs/partials/includes/partials-attributes.adoc @@ -1,13 +1,8 @@ -:assetdir: ../assets -:stylesdir: {assetdir} +:stylesdir: assets :figure-caption: Figure -:toc: left :docinfo: shared -:docinfodir: {assetdir} -:docinfosubs: attributes :iconfont-remote!: :stylesheet: gemini.css -:scriptsdir: {assetdir} :data-uri: :iconfont-name: font-awesome.min :imagesdir: media @@ -15,5 +10,6 @@ :sectnumlevels: 3 :sectlinks: :sectanchors: +:toclevels: 4 :source-highlighter: pygments :pygments-style: default \ No newline at end of file From 805c3da8ad3923be50fa0dfbf997553a88aaef07 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Mon, 27 Mar 2023 14:53:57 +0100 Subject: [PATCH 36/54] 1056 Glossary Page checked- plus tweak to stylesheet to add some padding to the left and right of the content and header divs --- docs/1056-glossary.asciidoc | 54 ++++++++++++++++++++++--------------- docs/assets/gemini.css | 12 +++++++++ 2 files changed, 45 insertions(+), 21 deletions(-) diff --git a/docs/1056-glossary.asciidoc b/docs/1056-glossary.asciidoc index 3556e38..8735f51 100644 --- a/docs/1056-glossary.asciidoc +++ b/docs/1056-glossary.asciidoc @@ -1,13 +1,13 @@ -= Glossary += [[top]]Glossary include::./includes/attributes.asciidoc[] -https://www.agi.org.uk/40-gemini/1056-glossary#A[A]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#B[B]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#C[C]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#D[D]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#E[E]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#F[F]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#G[G]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#H[H]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#I[I]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#J[J]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#K[K]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#L[L]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#M[M]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#N[N]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#O[O]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#P[P]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#Q[Q]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#R[R]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#S[S]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#T[T]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#U[U]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#V[V]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#W[W]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#X[X]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#Y[Y]{nbsp}https://www.agi.org.uk/40-gemini/1056-glossary#Z[Z] +<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<>{nbsp}<> -Return -to{nbsp}https://www.agi.org.uk/gemini/40-gemini/1037-uk-gemini-standard-and-inspire-implementing-rules[GEMINI +Return to link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI 2.3 home page] -[#A]##*acceptable quality level (AQL)* +*acceptable quality level (AQL)* +[#A] threshold value applied to the results of testing data quality to determine whether the data meets criteria determined from a standard, @@ -18,7 +18,8 @@ specification or user requirements acceptable quality level for aggregated results from a number of tests, e.g. 100% correct -[#C]##*Coordinate Reference System* +*Coordinate Reference System* +[#C] a coordinate system that is related to an object by a datum [ISO 19111] @@ -33,7 +34,8 @@ for OGC Catalogue Service. Note: see{nbsp}http://www.opengeospatial.org/standards/specifications/catalog -[#D]##*Data Provider* +*Data Provider* +[#D] the organisation that creates the data and supplies the data for web publication, along with its metadata. @@ -85,7 +87,8 @@ blocks of an XML document. It is not relevant in the context of GEMINI2 metadata instances where{nbsp}_XSD_{nbsp}schemas are used to define the structure of XML documents. -*[#E]####EDEN* +*EDEN* +[#E] l’Equipe D’Experts en Normalisation @@ -106,7 +109,8 @@ Note: examples are given of the use of EPSG{nbsp}__URI__s in{nbsp}_metadata instances_. This does not imply that the EPSG registry is the{nbsp}_de jure_{nbsp}registry of geodetic parameters for UK Location. -*[#G]####GEMET* +*GEMET* +[#G] General Multilingual Environmental Thesaurus. @@ -138,7 +142,8 @@ Geography Markup Language [ISO 19136] resolution in terms of density or frequency -*[#I]####INSPIRE* +*INSPIRE* +[#I] infrastructure for Spatial Information in Europe @@ -155,11 +160,13 @@ Notes: ISO Technical Committee 211 is responsible for standardisation in the field of digital geographic information. The home page of ISO / TC 211 is{nbsp}http://www.isotc211.org/ -*[#L]####location* +*location* +[#L] identifiable geographic place -*[#M]####metadata* +*metadata* +[#M] data about data [ISO 19115] @@ -195,7 +202,8 @@ service that supplies information about data resources identifiable set of metadata relating to a single data resource -*[#O]####OGC* +*OGC* +[#O] Open Geospatial Consortium. @@ -208,12 +216,14 @@ IT. See{nbsp}http://www.opengeospatial.org/ International Association of Oil and Gas Producers -*[#P]####profile* +*profile* +[#P] set of one or more base standards or subsets of base standards for a particular application -*[#Q]####quality assessment* +*quality assessment* +[#Q] review of quality of a data resource @@ -234,7 +244,8 @@ overall process for assessing and controlling quality value of a quality measure -*[#S]####Schematron* +*Schematron* +[#S] a{nbsp}language for making assertions about patterns in XML documents; ISO 19757 Document Schema Definition Language @@ -251,7 +262,8 @@ Spatial Reference System. Note: a system for specifying position in the real world [ISO 19112] -*[#U]####UK Information Infrastructure* +*UK Information Infrastructure* +[#U] Infrastructure for the publication of location information as part of the implementation of the UK Location Strategy.{nbsp} Incorporates the UK @@ -301,7 +313,8 @@ generated twice by any computer in existence. * Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx * Example: 3ce4f380-b394-4e5d-b222-6914ea311156 -*[#W]####WAF* +*WAF* +[#W] a Web Accessible Folder (WAF) is an HTTP accessible directory of files @@ -318,7 +331,8 @@ Web Mapping Service Web Feature Service -*[#X]####XLink* +*XLink* +[#X] XML Linking Language @@ -354,8 +368,6 @@ XML Schema Definition language. Note: an XSD is a document written in XML that defines the structure of an XML document. -_Last updated: March 2017_ - http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative Commons Licence]] + This work is licensed under diff --git a/docs/assets/gemini.css b/docs/assets/gemini.css index 653126e..d9a2240 100644 --- a/docs/assets/gemini.css +++ b/docs/assets/gemini.css @@ -42,3 +42,15 @@ code[data-lang="xml"] { background-color: transparent !important; } +#content { + max-width: 1500px; + margin-right: auto; + margin-left: auto; +} + +#header { + max-width: 1500px; + margin-right: auto; + margin-left: auto; +} + From ce9c8f7f237cadebb69d5e7e5f2d8cbaa44eb562 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Mon, 27 Mar 2023 17:57:46 +0100 Subject: [PATCH 37/54] finished the encoding changes for the remaining partials. Renamed datasets and services to the correct name. Added ulist.html.slim to improve line-spacing for ordered lists. Edited gemini.css to change list-style inside disclosure blocks to remove linebreak between number and list item --- ...uk-gemini-major-changes-since-1-0.asciidoc | 101 +++++++++--------- ...1062-gemini-datasets-and-data-series.adoc} | 0 ...ervices.adoc => 1063-gemini-services.adoc} | 0 docs/README.md | 4 +- docs/assets/gemini.css | 2 +- docs/partials/fileidentifier.asciidoc | 18 ++-- docs/partials/hierarchylevelname.asciidoc | 46 ++++---- docs/partials/keyword.asciidoc | 71 ++++++------ .../limitationsonpublicaccess.asciidoc | 40 ++++--- docs/partials/lineage.asciidoc | 18 ++-- docs/partials/maintenanceinformation.asciidoc | 14 +-- docs/partials/metadatalanguage.asciidoc | 15 ++- docs/partials/metadatapointofcontact.asciidoc | 18 ++-- docs/partials/metadatastandardname.asciidoc | 25 +++-- .../partials/metadatastandardversion.asciidoc | 15 ++- docs/partials/parentidentifier.asciidoc | 14 +-- docs/partials/qualityscope.asciidoc | 18 ++-- docs/partials/resourceidentifier.asciidoc | 28 ++--- docs/partials/resourcelocator.asciidoc | 73 +++++++------ docs/partials/resourcetype.asciidoc | 14 +-- .../partials/responsibleorganisation.asciidoc | 27 ++--- docs/partials/spatialdataservicetype.asciidoc | 17 +-- docs/partials/spatialreferencesystem.asciidoc | 48 ++++----- .../spatialrepresentationtype.asciidoc | 14 +-- docs/partials/spatialresolution.asciidoc | 17 +-- docs/partials/temporalextent.asciidoc | 91 ++++++++-------- docs/partials/title.asciidoc | 36 ++++--- docs/partials/topiccategory.asciidoc | 18 ++-- docs/partials/useconstraints.asciidoc | 39 ++++--- docs/partials/verticalextent.asciidoc | 57 +++++----- docs/templates/slim/ulist.html.slim | 16 +++ 31 files changed, 465 insertions(+), 449 deletions(-) rename docs/{datasets.adoc => 1062-gemini-datasets-and-data-series.adoc} (100%) rename docs/{services.adoc => 1063-gemini-services.adoc} (100%) create mode 100644 docs/templates/slim/ulist.html.slim diff --git a/docs/1055-uk-gemini-major-changes-since-1-0.asciidoc b/docs/1055-uk-gemini-major-changes-since-1-0.asciidoc index 77c3eb3..1af7b3b 100644 --- a/docs/1055-uk-gemini-major-changes-since-1-0.asciidoc +++ b/docs/1055-uk-gemini-major-changes-since-1-0.asciidoc @@ -1,8 +1,7 @@ -== UK GEMINI Changes Log += [[top]]UK GEMINI Changes Log include::./includes/attributes.asciidoc[] -Return -to{nbsp}https://www.agi.org.uk/gemini/40-gemini/1037-uk-gemini-standard-and-inspire-implementing-rules[GEMINI +Return to link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI 2.3 home page] == UK GEMINI 2.3 @@ -61,34 +60,34 @@ longer just be the century. ==== April 2020 Changed -the{nbsp}https://www.agi.org.uk/40-gemini/1048-uk-gemini-encoding-guidance[XML +the{nbsp}link:1048-uk-gemini-encoding-guidance.html[XML guidance]{nbsp}and examples to cope with the disappearance of the XML resources from{nbsp}http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/. The authoritative location is now on{nbsp}https://schemas.isotc211.org/. -Note: I didn't mark this as a revision to each element. +Note: this hasn't been marked as a revision to each element. Fixed example file on{nbsp}https://github.com/AGIGemini/Schematron[GitHub], and changed links to point there. -https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#53[Maintenance +link:1062-gemini-datasets-and-data-series.html#53[Maintenance information]: * corrected maximum multiplicity; * expanded the description of the domain -https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#25[Limitations +link:1062-gemini-datasets-and-data-series.html#25[Limitations on public access]: * clarified guidance on how to express more than one limitation, and added an example -https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#54[Metadata +link:1062-gemini-datasets-and-data-series.html#54[Metadata standard name]: * minor change to guidance and example -https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#41[Conformity]: +link:1062-gemini-datasets-and-data-series.html#41[Conformity]: * correct the description of what has changed in cases where the resource has not been tested against an INSPIRE specification @@ -98,68 +97,68 @@ relate to an INSPIRE document ==== January 2020 Added guidance for two additional -elements:{nbsp}https://www.agi.org.uk/1062-gemini-datasets-and-data-series#54[Metadata +elements:{nbsp}link:1062-gemini-datasets-and-data-series.html#54[Metadata standard name], -and{nbsp}https://www.agi.org.uk/1062-gemini-datasets-and-data-series#54[Metadata +and{nbsp}link:1062-gemini-datasets-and-data-series.html#54[Metadata standard version] -https://www.agi.org.uk/1062-gemini-datasets-and-data-series#6[Keyword]{nbsp}for +link:1062-gemini-datasets-and-data-series.html#6[Keyword]{nbsp}for INSPIRE theme: fixed the URL in the encoding example -https://www.agi.org.uk/1062-gemini-datasets-and-data-series#47[Hierarchy +link:1062-gemini-datasets-and-data-series.html#47[Hierarchy level name]: changed guidance and example to match INSPIRE. Note: this means the value is fixed depending on the value chosen for Resource type (Hierarchy level). + -https://www.agi.org.uk/1062-gemini-datasets-and-data-series#41[Conformity]{nbsp}to +link:1062-gemini-datasets-and-data-series.html#41[Conformity]{nbsp}to an INSPIRE specification: minor fix to guidance, and added a new 'known error' -https://www.agi.org.uk/1062-gemini-datasets-and-data-series#25[Limitations +link:1062-gemini-datasets-and-data-series.html#25[Limitations on public access]: improve guidance by listing the allowable INSPIRE reasons, with a hyperlink to the register ==== March 2019 Change -to{nbsp}https://www.agi.org.uk/40-gemini/1048-uk-gemini-encoding-guidance#2.1,[https://www.agi.org.uk/1048-uk-gemini-encoding-guidance#2.1,]{nbsp}to +to{nbsp}link:1048-uk-gemini-encoding-guidance#2.1,[1048-uk-gemini-encoding-guidance#2.1],{nbsp}to describe a wider choice of relevant XML Schema Definition Files (XSDs) that can be used to validate GEMINI instances. -https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#8[_Dataset_{nbsp}reference +link:1062-gemini-datasets-and-data-series.html#8[_Dataset_{nbsp}reference date]: removed mention of the maximum occurrence for service records, when viewing this element for dataset records. Corrected the INSPIRE "corresponding element" entry -for{nbsp}https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#41[Conformity],{nbsp}https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#4[Abstract],{nbsp}https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#5[Topic -category],{nbsp}https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#6[Keyword],{nbsp}https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#17[Spatial +for{nbsp}link:1062-gemini-datasets-and-data-series.html#41[Conformity],{nbsp}link:1062-gemini-datasets-and-data-series.html#4[Abstract],{nbsp}link:1062-gemini-datasets-and-data-series.html#5[Topic +category],{nbsp}link:1062-gemini-datasets-and-data-series.html#6[Keyword],{nbsp}link:1062-gemini-datasets-and-data-series.html#17[Spatial reference -system],{nbsp}https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#21[Data -format],{nbsp}https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#45[File -Identifier],{nbsp}https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#47[Hierarchy +system],{nbsp}link:1062-gemini-datasets-and-data-series.html#21[Data +format],{nbsp}link:1062-gemini-datasets-and-data-series.html#45[File +Identifier],{nbsp}link:1062-gemini-datasets-and-data-series.html#47[Hierarchy level name], -and{nbsp}https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series#48[Quality +and{nbsp}link:1062-gemini-datasets-and-data-series.html#48[Quality scope]. Corrected the "corresponding element" entries for service elements to reference ISO 19119 -for{nbsp}https://www.agi.org.uk/gemini/40-gemini/1063-gemini-services#15[Extent],{nbsp}https://www.agi.org.uk/gemini/40-gemini/1063-gemini-services#16[Vertical +for{nbsp}link:1063-gemini-services.html#15[Extent],{nbsp}link:1063-gemini-services.html#16[Vertical extent -information],{nbsp}https://www.agi.org.uk/gemini/40-gemini/1063-gemini-services#37[Spatial +information],{nbsp}link:1063-gemini-services.html#37[Spatial data service type], -and{nbsp}https://www.agi.org.uk/gemini/40-gemini/1063-gemini-services#38[Coupled +and{nbsp}link:1063-gemini-services.html#38[Coupled resource]. Corrected the ISO 19139 "corresponding element" entries for service -elements{nbsp}https://www.agi.org.uk/gemini/40-gemini/1063-gemini-services#15[Extent],{nbsp}https://www.agi.org.uk/gemini/40-gemini/1063-gemini-services#16[Vertical +elements{nbsp}link:1063-gemini-services.html#15[Extent],{nbsp}link:1063-gemini-services.html#16[Vertical extent information], -and{nbsp}https://www.agi.org.uk/gemini/40-gemini/1063-gemini-services#18[Spatial +and{nbsp}link:1063-gemini-services.html#18[Spatial resolution] Corrected the ISO 19139 "corresponding element" entries -for{nbsp}https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#1[Title],{nbsp}https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#2[Alternative +for{nbsp}link:1062-gemini-datasets-and-data-series.html#1[Title],{nbsp}link:1062-gemini-datasets-and-data-series.html#2[Alternative title], -and{nbsp}https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#4[Abstract]. +and{nbsp}link:1062-gemini-datasets-and-data-series.html#4[Abstract]. _Note: these are all minor corrections of the way the element is referenced, rather than substantive changes to which element we consider @@ -176,10 +175,10 @@ should use it didn't. ==== October 2018 -*https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#27[Additional -information]{nbsp}(source) -and{nbsp}https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#19[Resource -locator]* +*link:1062-gemini-datasets-and-data-series.html#27[Additional +information]*{nbsp}(source) +and{nbsp}**link:1062-gemini-datasets-and-data-series.html#19[Resource +locator]** Clarified that, in line with the underlying ISO standards, Resource locator is for links to access the resource, or obtain more information @@ -199,7 +198,7 @@ than by citation or link. Note: additional information is not available for services. -*https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#36[Resource +*link:1062-gemini-datasets-and-data-series.html#36[Resource identifier]* Fixed two typos. @@ -209,26 +208,25 @@ another, into hyperlinks. ==== September 2018 -*https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#3[Dataset -language]{nbsp}and{nbsp}https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#33[metadata]https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#33[{nbsp}language]* +*link:1062-gemini-datasets-and-data-series.html#3[Dataset +language]*{nbsp}and{nbsp}**link:1062-gemini-datasets-and-data-series.html#33[metadata]link:1062-gemini-datasets-and-data-series.html#33[{nbsp}language]** Corrected the name of the Irish language. -*https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#17[Spatial +*link:1062-gemini-datasets-and-data-series.html#17[Spatial reference -system]{nbsp}and{nbsp}https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#48[Quality -scope] + -* +system]*{nbsp}and{nbsp}**link:1062-gemini-datasets-and-data-series.html#48[Quality +scope]** Corrected that there is an equivalent INSPIRE requirement, although not a 'named' metadata element. -*https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#25[Limitations +*link:1062-gemini-datasets-and-data-series.html#25[Limitations on public access]* Corrected the equivalent ISO 19115 & 19139 elements -*https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#26[Use +*link:1062-gemini-datasets-and-data-series.html#26[Use constraints]* Corrected encoding rules & examples, from "gmd:LegalConstraints" (which @@ -243,7 +241,7 @@ Corrected the equivalent ISO 19115 & 19139 elements. *Description of validation* Fixed the description in section 1.5 of -the{nbsp}https://www.agi.org.uk/gemini/40-gemini/1053-common-metadata-errors-uk-location-discovery-metadata-service[Common +the{nbsp}link:1053-common-metadata-errors-uk-location-discovery-metadata-service.html[Common Metadata Errors article], which only described the GEMINI 2.2 / UK Location / data.gov.uk validation. @@ -268,11 +266,10 @@ Metadata TG, not the Regulations ==== July 2018 -*https://www.agi.org.uk/40-gemini/1048-uk-gemini-encoding-guidance[UK +*link:1048-uk-gemini-encoding-guidance.html[UK GEMINI Encoding Guidance]* -*first line*: remove misleading phrase "using XSD schemas"* + -* +*first line*: remove misleading phrase "using XSD schemas" *section 2.2.14*: minor clarifications, and improved the placement of figure captions. @@ -280,19 +277,19 @@ figure captions. *Change log{nbsp}*(this article): reordered to bring newest to top; added this section (editorial changes) -https://www.agi.org.uk/gemini/40-gemini/1037-uk-gemini-standard-and-inspire-implementing-rules["*Home +link:1037-uk-gemini-standard-and-inspire-implementing-rules.html["*Home page*"]: fixed link to encoding guidance -*https://www.agi.org.uk/gemini/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1[Guidelines +*link:1052-metadata-guidelines-for-geospatial-data-resources-part-1.html[Guidelines - part 1 Introduction to Metadata]*: clarifications & general update *All pages*: introduce a link back to the GEMINI 2.3 "home page". -*https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#3[Guidance +*link:1062-gemini-datasets-and-data-series.html#3[Guidance for element 3 Dataset language]*: fix typo in anchor text for ISO 639 link -*https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series#44[Guidance +*link:1062-gemini-datasets-and-data-series.html#44[Guidance for element 44 Bounding box]*: fix typos in two domain sub element names == UK GEMINI 2.2 @@ -310,7 +307,7 @@ Box for which multiple occurrences are allowed. == UK GEMINI 2.1 -{nbsp}Resource language, Metadata language: +Resource language, Metadata language: * The code for the Ulster Scots language was changed to "sco". diff --git a/docs/datasets.adoc b/docs/1062-gemini-datasets-and-data-series.adoc similarity index 100% rename from docs/datasets.adoc rename to docs/1062-gemini-datasets-and-data-series.adoc diff --git a/docs/services.adoc b/docs/1063-gemini-services.adoc similarity index 100% rename from docs/services.adoc rename to docs/1063-gemini-services.adoc diff --git a/docs/README.md b/docs/README.md index 3411357..97efd87 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,8 +1,8 @@ # Gemini documentation DEV branch -* [Services](https://agiorguk.github.io/gemini-dev/services.html) -* [Datasets](https://agiorguk.github.io/gemini-dev/datasets.html) +* [Services](https://agiorguk.github.io/gemini-dev/1063-gemini-services.html) +* [Datasets](https://agiorguk.github.io/gemini-dev/1062-gemini-datasets-and-series.html) The files below have been converted but have not been altered to work using the new workflow. Consequently internal links will go to the agi website and there may be other errors. * [1037-uk-gemini-standard-and-inspire-implementing-rules](https://agiorguk.github.io/gemini-dev/1037-uk-gemini-standard-and-inspire-implementing-rules.html) diff --git a/docs/assets/gemini.css b/docs/assets/gemini.css index d9a2240..6c6f079 100644 --- a/docs/assets/gemini.css +++ b/docs/assets/gemini.css @@ -23,7 +23,7 @@ table { details { color: rgb(40,158,197); cursor: pointer; - list-style: disclosure-closed inside; + /*list-style: disclosure-closed inside;*/ } details .content { diff --git a/docs/partials/fileidentifier.asciidoc b/docs/partials/fileidentifier.asciidoc index 9f40bff..7413752 100644 --- a/docs/partials/fileidentifier.asciidoc +++ b/docs/partials/fileidentifier.asciidoc @@ -1,4 +1,4 @@ -= File Identifier +== File Identifier include::includes/partials-attributes.adoc[] [#45] @@ -67,9 +67,10 @@ resource being described. + .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| -. The first XML child element of any GEMINI2 metadata instance shall be +|Guidelines +|. The first XML child element of any GEMINI2 metadata instance shall be gmd:fileIdentifier. The content of this XML element is the identifier of the metadata instance. File identifier is not a metadata item of GEMINI2. It is not to be confused with the metadata item @@ -77,14 +78,13 @@ link:#36[Resource identifier]. . The content of the XML element shall be a unique managed identifier, such as a system generated UUID. Once the identifier has been set for a metadata instance it shall not change. - -|Example a| -.... +|Example +| +[source,xml] +---- include::../snippets/fileidentifier.xml[] -.... - +---- |=== -[%collapsible] ==== .Metadata errors observed... diff --git a/docs/partials/hierarchylevelname.asciidoc b/docs/partials/hierarchylevelname.asciidoc index cd7214e..e80c2d7 100644 --- a/docs/partials/hierarchylevelname.asciidoc +++ b/docs/partials/hierarchylevelname.asciidoc @@ -1,4 +1,4 @@ -= Hierarchy level name +== Hierarchy level name include::includes/partials-attributes.adoc[] [#47] @@ -57,38 +57,36 @@ New element in GEMINI 2.3 .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== |Guidelines |No specific rules for this metadata element -|Example a| ifdef::variant-dataset[] - -Example 1 - dataset, where hierarchyLevelName could just be omitted - -.... +|Example 1 - dataset, where hierarchyLevelName could just be omitted +| +[source,xml] +---- include::../snippets/dataset-hierarchylevelname.xml[] - -.... - -Example 2 - series, where hierarchyLevelName is required - -.... +---- +|Example 2 - series, where hierarchyLevelName is required +| +[source,xml] +---- include::../snippets/series-hierarchylevelname.xml[] -.... +---- endif::[] ifdef::variant-service[] -|Example a| -.... +|Example +| +[source,xml] +---- include::../snippets/service-hierarchylevelname.xml[] - -.... +---- endif::[] - - - |=== ==== -Metadata errors observed... - -[[errors47]] -No error information available \ No newline at end of file +.Metadata errors observed... +[%collapsible] +==== +No error information available +==== \ No newline at end of file diff --git a/docs/partials/keyword.asciidoc b/docs/partials/keyword.asciidoc index c06a992..a7927f1 100644 --- a/docs/partials/keyword.asciidoc +++ b/docs/partials/keyword.asciidoc @@ -1,4 +1,4 @@ -= Keyword +== Keyword include::includes/partials-attributes.adoc[] [#6] @@ -117,9 +117,11 @@ controlled vocabulary .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== |Guidelines a| ifdef::variant-dataset[] +[arabic] . The GEMINI2 keyword item comprises keyword value(s) and, conditionally, the specification of an originating controlled vocabulary. If keywords are not selected from a controlled vocabulary @@ -150,6 +152,7 @@ controlled vocabulary. An example from the Marine Geospatial community is http://seadatanet.maris2.nl/v_bodc_vocab_v2/search.asp?lib=P02 endif::[] ifdef::variant-service[] +| . The GEMINI2 keyword item comprises keyword value(s) and, conditionally, the specification of an originating controlled vocabulary. If keywords are not selected from a controlled vocabulary the encoding shown in Example One shall be used. . In the context of INSPIRE the presence of at least one keyword is mandated. For service metadata there shall be at least one keyword defining the category or subcategory of the service using its language neutral name as defined in Part D 4 of the Metadata Implementing Rules (the language neutral names are the words in brackets using lower camel case notation). The keyword shown in Example Two is an example of this . Where keywords do originate from a controlled vocabulary the encoding shown in Example Two shall be used. Note the inclusion of the gmd:thesaurusName XML element which contains the XML element gmd:CI_Citation. This element must contain at least a title, reference date and date type. In the example keywords have been selected from the GEMET Concepts controlled vocabulary. @@ -159,50 +162,54 @@ ifdef::variant-service[] . This case arises because the XML element gmd:descriptiveKeywords is a an instance of the property (or role in fact) on the ISO 19115 abstract class MD_Identification, from which both SV_ServiceIdentification and MD_DataIdentification inherit. Therefore, SV_ServiceIdentification inherits the descriptiveKeywords property and adds a similar property called keywords. . Recommended best practice is to select a human readable value from a controlled vocabulary. An example from the Marine Geospatial community is http://seadatanet.maris2.nl/v_bodc_vocab_v2/search.asp?lib=P02 endif::[] - - -|Example a| ifdef::variant-dataset[] -` Example One (datasets/series) - without originating controlled vocabulary ` - -.... +| Example One (datasets/series) - without originating controlled vocabulary +| +[source,xml] +---- include::../snippets/dataset-keyword-freetext.xml[] -.... - -Example Two (datasets/series) - INSPIRE theme - -.... +---- +| Example Two (datasets/series) - INSPIRE theme +| +[source,xml] +---- include::../snippets/dataset-keyword-freetext.xml[] -.... - -Example Three (datasets/series) - keywords from 2 controlled +---- +| Example Three (datasets/series) - keywords from 2 controlled vocabularies - -.... +| +[source,xml] +---- include::../snippets/dataset-keyword-controlled.xml[] -.... +---- endif::[] ifdef::variant-service[] -`Example One (services) - without controlled vocabulary -.... +|Example One (services) - without controlled vocabulary +| +[source,xml] +---- include::../snippets/service-keyword-freetext.xml[] -.... -Example Two (services) - service keyword from part D4 on the INSPIRE +---- +| Example Two (services) - service keyword from part D4 on the INSPIRE Metadata Implementing Rules -.... +| +[source,xml] +---- include::../snippets/service-keyword-inspire.xml[] -.... -Example Three (services) - GEMET concepts -.... +---- +| Example Three (services) - GEMET concepts +| +[source,xml] +---- include::../snippets/service-keyword-gemet.xml[] -.... - -Example Four (services) - keywords from two controlled vocabularies -.... +---- +| Example Four (services) - keywords from two controlled vocabularies +| +[source,xml] +---- include::../snippets/service-keyword-controlled.xml[] -.... +---- endif::[] - |=== ==== diff --git a/docs/partials/limitationsonpublicaccess.asciidoc b/docs/partials/limitationsonpublicaccess.asciidoc index 23ae226..cd0b03a 100644 --- a/docs/partials/limitationsonpublicaccess.asciidoc +++ b/docs/partials/limitationsonpublicaccess.asciidoc @@ -1,4 +1,4 @@ -= Limitations on public access +== Limitations on public access include::includes/partials-attributes.adoc[] [#25] @@ -90,9 +90,10 @@ accessConstraint making domain free text. .Encoding guidelines... [%collapsible] ==== -[width="100%",cols="50%,50%",] +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| . This element shall be encoded in a different resourceConstraints/MD_LegalConstraints XML element to GEMINI element 26 Use constraints @@ -110,32 +111,29 @@ http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess . Free text content cannot be empty . To encode multiple limitations, include more than one gmd:otherConstraints element - -|Example a| -Example One - -.... +|Example One +| +[source,xml] +---- ifdef::variant-dataset[] include::../snippets/dataset-limitationsonpublicaccess.xml[] endif::[] ifdef::variant-service[] include::../snippets/service-limitationsonpublicaccess.xml[] endif::[] - -.... - -Example Two - no limitations - -.... +---- +| Example Two - no limitations +| +[source,xml] +---- include::../snippets/limitationsonpublicaccess-nolimitations.xml[] -.... - -Example Three - two limitations - -.... +---- +| Example Three - two limitations +| +[source,xml] +---- include::../snippets/limitationsonpublicaccess-twolimitations.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/lineage.asciidoc b/docs/partials/lineage.asciidoc index 6951e72..244f779 100644 --- a/docs/partials/lineage.asciidoc +++ b/docs/partials/lineage.asciidoc @@ -1,4 +1,4 @@ -= Lineage +== Lineage include::includes/partials-attributes.adoc[] [#10] @@ -74,9 +74,10 @@ conform to INSPIRE .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| -. The encoding for lineage is shown in the example below. +|Guidelines +|. The encoding for lineage is shown in the example below. . Note that, in addition to the lineage statement, the data quality scope shall be encoded. For dataset metadata instances the MD_ScopeCode code list value shall be 'dataset'. For series metadata instances the @@ -84,13 +85,12 @@ code list value shall be 'series'. . For INSPIRE, the lineage statement must appear in the gmd:dataQualityInfo/gmd:DQ_DataQuality element scoped to the entire described dataset or series - -|Example a| - -.... +|Example +| +[source,xml] +---- include::../snippets/lineage.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/maintenanceinformation.asciidoc b/docs/partials/maintenanceinformation.asciidoc index 82ca392..a4e5e6b 100644 --- a/docs/partials/maintenanceinformation.asciidoc +++ b/docs/partials/maintenanceinformation.asciidoc @@ -1,4 +1,4 @@ -= Maintenance information +== Maintenance information include::includes/partials-attributes.adoc[] [#53] @@ -84,15 +84,15 @@ New element in GEMINI 2.3 .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== |Guidelines |No specific rules for this metadata element - -|Example a| - -.... +|Example +| +[source,xml] +---- include::../snippets/maintenanceinformation.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/metadatalanguage.asciidoc b/docs/partials/metadatalanguage.asciidoc index 2df2bba..9cee1f5 100644 --- a/docs/partials/metadatalanguage.asciidoc +++ b/docs/partials/metadatalanguage.asciidoc @@ -1,4 +1,4 @@ -= Metadata language +== Metadata language include::includes/partials-attributes.adoc[] [#33] @@ -80,17 +80,16 @@ GEMINI 1 to 2.0: New element .Encoding guidelines... [%collapsible] ==== -[width="100%",cols="50%,50%",] +[cols="a,a"] |=== |Guidelines |INSPIRE recommends providing the name of the language as content of the gmd:LanguageCode element - -|Example a| - -.... +|Example +| +[source,xml] +---- include::../snippets/metadatadate.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/metadatapointofcontact.asciidoc b/docs/partials/metadatapointofcontact.asciidoc index 7a2fead..dcf7135 100644 --- a/docs/partials/metadatapointofcontact.asciidoc +++ b/docs/partials/metadatapointofcontact.asciidoc @@ -1,4 +1,4 @@ -= Metadata point of contact +== Metadata point of contact include::includes/partials-attributes.adoc[] [#35] @@ -54,8 +54,10 @@ GEMINI 1 to 2.0: New element .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| * The encoding example for metadata point of contact is shown below. Note that the example shows the minimum required information. * The format of address and contact information is described at @@ -64,14 +66,12 @@ more fully populated example. * More than one metadata point of contact may be expressed in metadata. The role of at least one metadata point of contact shall be 'pointOfContact'. - -|Example a| -Example showing minimum required information - -.... +|Example showing minimum required information +| +[source,xml] +---- include::../snippets/metadatapointofcontact.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/metadatastandardname.asciidoc b/docs/partials/metadatastandardname.asciidoc index 475890d..cfa42cf 100644 --- a/docs/partials/metadatastandardname.asciidoc +++ b/docs/partials/metadatastandardname.asciidoc @@ -1,4 +1,4 @@ -= Metadata standard name +== Metadata standard name include::includes/partials-attributes.adoc[] [#54] @@ -61,6 +61,7 @@ guidance .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== |Guidelines |GEMINI is supported by a https://www.bodc.ac.uk/resources/vocabularies/vocabulary_search/M25/[register @@ -68,20 +69,18 @@ of metadata standard and profile names], hosted on the NERC vocab server. + The relevant standard shall be cited with a reference to the appropriate register entry, using an Anchor. - -|Example a| -` Example One – UK GEMINI 2.3 - -.... +|Example One – UK GEMINI 2.3 +| +[source,xml] +---- include::../snippets/metadatastandardname-gemini.xml[] - -Example Two – MEDIN profile of GEMINI 2.3 -... +---- +| Example Two – MEDIN profile of GEMINI 2.3 +| +[source,xml] +---- include::../snippets/metadatastandardname-medin.xml[] -... - -.... - +---- |=== ==== diff --git a/docs/partials/metadatastandardversion.asciidoc b/docs/partials/metadatastandardversion.asciidoc index e4674ea..e940d62 100644 --- a/docs/partials/metadatastandardversion.asciidoc +++ b/docs/partials/metadatastandardversion.asciidoc @@ -1,4 +1,4 @@ -= Metadata standard version +== Metadata standard version include::includes/partials-attributes.adoc[] [#55] @@ -60,16 +60,15 @@ link:#54[Metadata standard name] .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== |Guidelines |No specific rules for this metadata element - -|Example a| -` Example One – GEMINI 2.3 ` - -.... +| Example One – GEMINI 2.3 +| +[source,xml] +---- include::../snippets/metadatastandardversion.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/parentidentifier.asciidoc b/docs/partials/parentidentifier.asciidoc index 8f25fb3..0e753a3 100644 --- a/docs/partials/parentidentifier.asciidoc +++ b/docs/partials/parentidentifier.asciidoc @@ -1,4 +1,4 @@ -= Parent identifier +== Parent identifier include::includes/partials-attributes.adoc[] [#49] @@ -55,15 +55,15 @@ New element in GEMINI 2.3 .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== |Guidelines |No specific rules for this metadata element - -|Example a| - -.... +|Example +| +[source,xml] +---- include::../snippets/parentidentifier.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/qualityscope.asciidoc b/docs/partials/qualityscope.asciidoc index 39ffd95..f169e11 100644 --- a/docs/partials/qualityscope.asciidoc +++ b/docs/partials/qualityscope.asciidoc @@ -1,4 +1,4 @@ -= Quality scope +== Quality scope include::includes/partials-attributes.adoc[] [#48] @@ -81,8 +81,10 @@ New element in GEMINI 2.3 .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| ifdef::variant-dataset[] All gmd:dataQualityInfo XML element shall have a gmd:scope XML element, set to as appropriate. @@ -103,19 +105,17 @@ required * The value of gmd:other must be *service* (in the language of the metadata), as shown below. endif::[] - - -|Example a| - -.... +|Example +| +[source,xml] +---- ifdef::variant-dataset[] include::../snippets/dataset-qualityscope.xml[] endif::[] ifdef::variant-service[] include::../snippets/service-qualityscope.xml[] endif::[] -.... - +---- |=== ==== diff --git a/docs/partials/resourceidentifier.asciidoc b/docs/partials/resourceidentifier.asciidoc index 19e9409..729182d 100644 --- a/docs/partials/resourceidentifier.asciidoc +++ b/docs/partials/resourceidentifier.asciidoc @@ -1,4 +1,4 @@ -= Resource identifier +== Resource identifier include::includes/partials-attributes.adoc[] [#36] @@ -110,8 +110,10 @@ reduce confusion with W3C URI .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| . The resource identifier can be a globally unique identifier such as a UUID, in which case it is encoded as shown in Example One. . The form used in Example One can also be used if the identifier is @@ -133,20 +135,18 @@ cannot be an UUID or an URI. The id must also be unique across all id attributes in the metadata document . See notes on link:component/content/article?id=1048#2.2.12[XML Identifiers]. - -|Example a| -Example One - -.... +|Example One +| +[source,xml] +---- include::../snippets/resourceidentifier-characterstring.xml[] -.... - -Example Two - resolveable identifier using gmx:Anchor - -.... +---- +| Example Two - resolveable identifier using gmx:Anchor +| +[source,xml] +---- include::../snippets/resourceidentifier-anchor.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/resourcelocator.asciidoc b/docs/partials/resourcelocator.asciidoc index 65f9603..143373b 100644 --- a/docs/partials/resourcelocator.asciidoc +++ b/docs/partials/resourcelocator.asciidoc @@ -1,4 +1,4 @@ -= Resource locator +== Resource locator include::includes/partials-attributes.adoc[] [#19] @@ -128,8 +128,10 @@ GEMINI 1 to 2.0: Modification of Online resource .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| ifdef::variant-dataset[] . The two examples illustrate different uses of Resource locator. Example one gives direct access to the dataset. Example two gives the @@ -155,25 +157,24 @@ https://inspire.ec.europa.eu/documents/inspire-metadata-implementing-rules-techn guidance] link:component/content/article?id=1047[[9]]. If the format and version values are known, then they should be given (see link:#21[Data format]). - -|Example a| -Example one, showing only required linkage content (for a dataset) - -.... +|Example one, showing only required linkage content (for a dataset) +| +[source,xml] +---- include::../snippets/dataset-resourcelocator-required.xml[] -.... - -Example two - including name, description, and indication of function +---- +| Example two - including name, description, and indication of function (for a dataset ordering page) - -.... +| +[source,xml] +---- include::../snippets/dataset-resourcelocator-information.xml[] -.... - +---- |=== endif::[] ifdef::variant-service[] -|Guidelines a| +|Guidelines +| . In the examples, the URLs provided are for OGC GetCapabilities requests. . The gmd:transferOptions XML element of gmd:MD_Distribution is used to @@ -216,35 +217,33 @@ five entity references: * > - The character > * " - The character " * ' - The character ' - -|Example a| -`Example one, showing only required linkage content (for a WMS) ` - -.... +|Example one, showing only required linkage content (for a WMS) +| +[source,xml] +---- include::../snippets/service-resourcelocator-required.xml[] -.... - -Example Two - including name, description, and indication of function +---- +| Example Two - including name, description, and indication of function (for a WMS) - -.... +| +[source,xml] +---- include::../snippets/service-resourcelocator-function-wms.xml[] -.... - -Example Three - including name, description, and indication of function +---- +|Example Three - including name, description, and indication of function (for a WCS) - -.... +| +[source,xml] +---- include::../snippets/service-resourcelocator-function-wcs.xml[] -.... - -Example Four - including name, description, and indication of function +---- +|Example Four - including name, description, and indication of function (for an invocable spatial data service) - -.... +| +[source,xml] +---- include::../snippets/service-resourcelocator-function-invocable.xml[] -.... - +---- |=== endif::[] ==== diff --git a/docs/partials/resourcetype.asciidoc b/docs/partials/resourcetype.asciidoc index fcc7156..dfd336d 100644 --- a/docs/partials/resourcetype.asciidoc +++ b/docs/partials/resourcetype.asciidoc @@ -1,4 +1,4 @@ -= Resource type +== Resource type include::includes/partials-attributes.adoc[] [#39] @@ -54,15 +54,15 @@ GEMINI 1 to 2.0: New element, required for INSPIRE .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== |Guidelines |No specific rules for this metadata element - -|Example a| - -.... +|Example +| +[source,xml] +---- include::../snippets/resourcetype.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/responsibleorganisation.asciidoc b/docs/partials/responsibleorganisation.asciidoc index 448dd86..f24a22e 100644 --- a/docs/partials/responsibleorganisation.asciidoc +++ b/docs/partials/responsibleorganisation.asciidoc @@ -1,4 +1,4 @@ -= Responsible organisation +== Responsible organisation include::includes/partials-attributes.adoc[] [#23] @@ -148,8 +148,10 @@ corrected. .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| . The encoding example for responsible organisation is shown below. The example shows the minimum required information. . The format of address and contact information is described at @@ -158,23 +160,22 @@ more fully populated example. . Note on role code: the UK Location portal (data.gov.uk site) interprets ISO 'owner' as Data Provider, and ISO 'publisher' as Data Publisher. - -|Example a| ifdef::variant-dataset[] -Example One (datasets/series) - -.... +| Example One (datasets/series) +| +[source,xml] +---- include::../snippets/dataset-responsibleorganisation.xml[] -.... +---- endif::[] ifdef::variant-service[] -Example One (service) - -.... +| Example One (service) +| +[source,xml] +---- include::../snippets/service-responsibleorganisation.xml[] -.... +---- endif::[] - |=== ==== diff --git a/docs/partials/spatialdataservicetype.asciidoc b/docs/partials/spatialdataservicetype.asciidoc index 7d66732..ed5e13d 100644 --- a/docs/partials/spatialdataservicetype.asciidoc +++ b/docs/partials/spatialdataservicetype.asciidoc @@ -1,4 +1,4 @@ -= Spatial data service type +== Spatial data service type include::includes/partials-attributes.adoc[] [#37] @@ -64,8 +64,10 @@ GEMINI 1 to 2.0: New element .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| The encoding example for spatial data service type is shown in the example below. The value domain of the service type (i.e. the list of acceptable values to encode in view) is @@ -78,13 +80,12 @@ repeated below (the words are to be encoded in lower case): * transformation * invoke * other - -|Example a| - -.... +|Example +| +[source,xml] +---- include::../snippets/spatialdataservicetype.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/spatialreferencesystem.asciidoc b/docs/partials/spatialreferencesystem.asciidoc index 4873b44..7a2f016 100644 --- a/docs/partials/spatialreferencesystem.asciidoc +++ b/docs/partials/spatialreferencesystem.asciidoc @@ -1,4 +1,4 @@ -= Spatial reference system +== Spatial reference system include::includes/partials-attributes.adoc[] [#17] @@ -94,39 +94,39 @@ GEMINI 1 to 2.0: Changed from enumerated list .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| * When the provided text is a term or code from an externally defined explanation or registry value, gmx:Anchor should be used instead of gco:CharacterString * The content of gmx:Anchor or gco:CharacterString must not be empty - -|Example a| -Example One - using gmx:Anchor for a default Coordinate Reference System (as defined in Annex D.4 of the INSPIRE metadata technical guidance v.2) - -.... +|Example One - using gmx:Anchor for a default Coordinate Reference System (as defined in Annex D.4 of the INSPIRE metadata technical guidance v.2) +| +[source,xml] +---- include::../snippets/spatialreferencesystem-default-anchor.xml[] -.... - -Example Two - using gmx:Anchor for a non default CRS. - -.... +---- +| Example Two - using gmx:Anchor for a non default CRS. +| +[source,xml] +---- include::../snippets/spatialreferencesystem-nondefault-anchor.xml[] -.... - -Example Three - encoding example with authority - -.... +---- +|Example Three - encoding example with authority +| +[source,xml] +---- include::../snippets/spatialreferencesystem-authority.xml[] -.... - -Example Four - encoding example for spatial reference systems using +---- +|Example Four - encoding example for spatial reference systems using geographic identifiers - -.... +| +[source,xml] +---- include::../snippets/spatialreferencesystem-identifiers.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/spatialrepresentationtype.asciidoc b/docs/partials/spatialrepresentationtype.asciidoc index 517e174..5cc27e1 100644 --- a/docs/partials/spatialrepresentationtype.asciidoc +++ b/docs/partials/spatialrepresentationtype.asciidoc @@ -1,4 +1,4 @@ -= Spatial representation type +== Spatial representation type include::includes/partials-attributes.adoc[] [#50] @@ -73,16 +73,16 @@ is a superset of values used by INSPIRE .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== |Guidelines |Only the codeListValue is required, the codeList and the free text content are optional and informative only - -|Example a| - -.... +|Example +| +[source,xml] +---- include::../snippets/spatialrepresentationtype.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/spatialresolution.asciidoc b/docs/partials/spatialresolution.asciidoc index 76f557e..105db3c 100644 --- a/docs/partials/spatialresolution.asciidoc +++ b/docs/partials/spatialresolution.asciidoc @@ -1,4 +1,4 @@ -= Spatial resolution +== Spatial resolution include::includes/partials-attributes.adoc[] [#18] @@ -78,8 +78,10 @@ GEMINI 1 to 2.0: made conditional .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| ifdef::variant-dataset[] . The encoding example for spatial resolution is shown in the example below. @@ -101,14 +103,13 @@ Schema. equivalent scale as integer valued scale denominator or a resolution distance using a numerical length value and with a unit of length. endif::[] - ifdef::variant-dataset[] -|Example a| - -.... +|Example +| +[source,xml] +---- include::../snippets/spatialresolution.xml[] -.... - +---- |=== endif::[] ==== diff --git a/docs/partials/temporalextent.asciidoc b/docs/partials/temporalextent.asciidoc index 5d1465e..89f601a 100644 --- a/docs/partials/temporalextent.asciidoc +++ b/docs/partials/temporalextent.asciidoc @@ -1,4 +1,4 @@ -= Temporal extent +== Temporal extent include::includes/partials-attributes.adoc[] [#7] @@ -94,8 +94,10 @@ endif::[] .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| . The basic encoding for temporal extent is shown in Example One (datasets/series). The temporal extent data shall be encoded using the gml:TimePeriod type from the gml namespace. The underlying schemas and @@ -159,63 +161,58 @@ before the specified date * 'after': in which case the actual date is unknown but known to be after the specified date . Example Four shows encoding examples using these values. - - -|Example a| ifdef::variant-dataset[] -Example One (datasets/series) : (gml:TimePeriod) - -.... +| Example One (datasets/series) : (gml:TimePeriod) +| +[source,xml] +---- include::../snippets/dataset-temporalextent-timeperiod.xml[] - - -.... - -Example Two (datasets/series): (gml:TimeInstant) - -.... +---- +| Example Two (datasets/series): (gml:TimeInstant) +| +[source,xml] +---- include::../snippets/dataset-temporalextent-timeinstant.xml[] - - -.... - -Example Three (datasets/series): unknown dates - -.... +---- +| Example Three (datasets/series): unknown dates +| +[source,xml] +---- include::../snippets/temporalextent-unknowndates.xml[] -.... - -Example Four: other unknown or unspecified dates - -.... +---- +| Example Four: other unknown or unspecified dates +| +[source,xml] +---- include::../snippets/temporalextent-other.xml[] -.... +---- endif::[] ifdef::variant-service[] -Example One (services) : (gml:TimePeriod) -.... +| Example One (services) : (gml:TimePeriod) +| +[source,xml] +---- include::../snippets/service-temporalextent-timeperiod.xml[] -.... - -Example Two (services) : (gml:TimeInstant) - -.... +---- +|Example Two (services) : (gml:TimeInstant) +| +[source,xml] +---- include::../snippets/service-temporalextent-timeinstant.xml[] -.... - -Example Three (services) : unknown dates - -.... +---- +| Example Three (services) : unknown dates +| +[source,xml] +---- include::../snippets/temporalextent-unknowndates.xml[] -.... - -Example Four: other unkown or unspecified dates - -.... +---- +| Example Four: other unkown or unspecified dates +| +[source,xml] +---- include::../snippets/temporalextent-other.xml[] -.... +---- endif::[] - |=== ==== diff --git a/docs/partials/title.asciidoc b/docs/partials/title.asciidoc index 1405b69..f445e9c 100644 --- a/docs/partials/title.asciidoc +++ b/docs/partials/title.asciidoc @@ -1,4 +1,4 @@ -= Title +== Title include::includes/partials-attributes.adoc[] [#1] @@ -58,33 +58,37 @@ in the abstract or Alternative Title. .Change history... [%collapsible] ==== +No error information available ==== + .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== |Guidelines |Cannot be empty - -|Example a| -[#dataset] -.... +|Example ifdef::variant-dataset[] - +[#dataset] +| +[source,xml] +---- include::../snippets/dataset-title.xml[] - -endif::[] -.... +---- +endif::[] +ifdef::variant-service[] [#service] -.... - -ifdef::variant-service[] - +| +[source,xml] +---- include::../snippets/service-title.xml[] - +---- endif::[] -.... |=== - ==== +.Metadata errors observed... +[%collapsible] +==== No error information available +==== diff --git a/docs/partials/topiccategory.asciidoc b/docs/partials/topiccategory.asciidoc index 8347847..7d58950 100644 --- a/docs/partials/topiccategory.asciidoc +++ b/docs/partials/topiccategory.asciidoc @@ -1,4 +1,4 @@ -= Topic Category +== Topic Category include::includes/partials-attributes.adoc[] [#5] @@ -140,8 +140,10 @@ Change history... .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| . The encoding example for topic category is shown in Example One. Note that it is possible to include more than one topic category. . The value of the XML element gmd:MD_TopicCategoryCode must not contain @@ -151,14 +153,12 @@ in an XSD schema validation error because the element content will be parsed as shown in Example 3 (excluding the square brackets denoting the start and end) resulting in a value that does not exist in the enumerated list. - -|Example a| - -.... +|Example +| +[source,xml] +---- include::../snippets/topiccategory.xml[] - -.... - +---- |=== ==== diff --git a/docs/partials/useconstraints.asciidoc b/docs/partials/useconstraints.asciidoc index 6926346..01ef8a3 100644 --- a/docs/partials/useconstraints.asciidoc +++ b/docs/partials/useconstraints.asciidoc @@ -1,4 +1,4 @@ -= Use constraints +== Use constraints include::includes/partials-attributes.adoc[] [#26] @@ -76,8 +76,10 @@ making mandatory to conform with INSPIRE. .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| . This element shall be encoded in a different resourceConstraints/MD_LegalConstraints XML element to GEMINI element 25 Limitations on public access @@ -100,32 +102,29 @@ list. . If there are no limitations the value of gmd:otherConstraints shall be 'no limitations' (see Example Three). . There may be more than one gmd:otherConstraints element - -|Example a| -Example One - -.... +|Example One +| +[source,xml] +---- ifdef::variant-dataset[] include::../snippets/dataset-useconstraints.xml[] endif::[] ifdef::variant-service[] include::../snippets/service-useconstraints.xml[] endif::[] -.... - -Example Two - with external file - -.... +---- +| Example Two - with external file +| +[source,xml] +---- include::../snippets/useconstraints-externalfile.xml[] -... -.... - -Example Three - no conditions apply - -.... +---- +| Example Three - no conditions apply +| +[source,xml] +---- include::../snippets/useconstraints-noconditions.xml[] -.... - +---- |=== ==== diff --git a/docs/partials/verticalextent.asciidoc b/docs/partials/verticalextent.asciidoc index 33df265..305842b 100644 --- a/docs/partials/verticalextent.asciidoc +++ b/docs/partials/verticalextent.asciidoc @@ -1,4 +1,4 @@ -= Vertical extent information +== Vertical extent information include::includes/partials-attributes.adoc[] [#16] @@ -103,8 +103,10 @@ description of class EX_VerticalExtent changed to match change to ISO .Encoding guidelines... [%collapsible] ==== +[cols="a,a"] |=== -|Guidelines a| +|Guidelines +| . The encoding of the vertical extent information is explained. The vertical extent information is expressed by a minimum and maximum coordinate value and a vertical CRS. The vertical CRS expresses the CRS @@ -135,41 +137,40 @@ CRS is unknown (Example Three) but this renders the vertical extent information ambiguous at best. Consequently it would be better to refrain from including vertical extent information in the metadata instance altogether. - -|Example a| -Example One (datasets/series) - Vertical CRS by reference ifdef::variant-dataset[] -.... +| Example One (datasets/series) - Vertical CRS by reference +| +[source,xml] +---- include::../snippets/dataset-extent-verticalcrs-reference.xml[] -.... - -Example Two (datasets/series) - Vertical CRS by value - -.... +---- +|Example Two (datasets/series) - Vertical CRS by value +| +[source,xml] +---- include::../snippets/dataset-extent-verticalcrs-value.xml[] -.... +---- endif::[] ifdef::variant-service[] -Example One (services) - Vertical CRS by reference - -.... +| Example One (services) - Vertical CRS by reference +| +[source,xml] +---- include::../snippets/service-extent-verticalcrs-reference.xml[] -.... - -Example Two (services) - Vertical CRS by value - -.... +---- +|Example Two (services) - Vertical CRS by value +| +[source,xml] +---- include::../snippets/service-extent-verticalcrs-value.xml[] -.... - +---- endif::[] - -Example Three - Vertical CRS unknown - -.... +|Example Three - Vertical CRS unknown +| +[source,xml] +---- include::../snippets/extent-verticalcrs-unknown.xml[] -.... - +---- |=== ==== diff --git a/docs/templates/slim/ulist.html.slim b/docs/templates/slim/ulist.html.slim new file mode 100644 index 0000000..9eb7a1d --- /dev/null +++ b/docs/templates/slim/ulist.html.slim @@ -0,0 +1,16 @@ +- if title? + figure.list.unordered id=id + figcaption=title + ul class=[style, role] + - items.each do |_item| + li + span.primary=_item.text + - if _item.blocks? + =_item.content +- else + ul id=id class=[style, role] + - items.each do |_item| + li + span.primary=_item.text + - if _item.blocks? + =_item.content \ No newline at end of file From 7c47b509d343c2a49f1620b35b4c536fc918e174 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Mon, 27 Mar 2023 18:08:03 +0100 Subject: [PATCH 38/54] corrected urls in readme and added additional parameters for using slim template in command examples --- docs/README.md | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/README.md b/docs/README.md index 97efd87..0f85b29 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,25 +1,25 @@ # Gemini documentation DEV branch -* [Services](https://agiorguk.github.io/gemini-dev/1063-gemini-services.html) -* [Datasets](https://agiorguk.github.io/gemini-dev/1062-gemini-datasets-and-series.html) +* [Services](https://archaeogeek.github.io/gemini-dev/1063-gemini-services.html) +* [Datasets](https://archaeogeek.github.io/gemini-dev/1062-gemini-datasets-and-series.html) The files below have been converted but have not been altered to work using the new workflow. Consequently internal links will go to the agi website and there may be other errors. -* [1037-uk-gemini-standard-and-inspire-implementing-rules](https://agiorguk.github.io/gemini-dev/1037-uk-gemini-standard-and-inspire-implementing-rules.html) -* [1048-uk-gemini-encoding-guidance](https://agiorguk.github.io/gemini-dev/1048-uk-gemini-encoding-guidance.html) -* [1049-metadata-guidelines-for-geospatial-data-resources-part-2](https://agiorguk.github.io/gemini-dev/1049-metadata-guidelines-for-geospatial-data-resources-part-2.html) -* [1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources](https://agiorguk.github.io/gemini-dev/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html) -* [1052-metadata-guidelines-for-geospatial-data-resources-part-1](https://agiorguk.github.io/gemini-dev/1052-metadata-guidelines-for-geospatial-data-resources-part-1.html) -* [1053-common-metadata-errors-uk-location-discovery-metadata-service](https://agiorguk.github.io/gemini-dev/1053-common-metadata-errors-uk-location-discovery-metadata-service.html) -* [1054-operational-guide](https://agiorguk.github.io/gemini-dev/1054-operational-guide.html) -* [1055-uk-gemini-major-changes-since-1-0](https://agiorguk.github.io/gemini-dev/1055-uk-gemini-major-changes-since-1-0.html) -* [1056-glossary](https://agiorguk.github.io/gemini-dev/1056-glossary.html) - -Links above this are to the GitHub pages published in https://agiorguk.github.io/gemini-dev/ +* [1037-uk-gemini-standard-and-inspire-implementing-rules](https://archaeogeek.github.io/gemini-dev/1037-uk-gemini-standard-and-inspire-implementing-rules.html) +* [1048-uk-gemini-encoding-guidance](https://archaeogeek.github.io/gemini-dev/1048-uk-gemini-encoding-guidance.html) +* [1049-metadata-guidelines-for-geospatial-data-resources-part-2](https://archaeogeek.github.io/gemini-dev/1049-metadata-guidelines-for-geospatial-data-resources-part-2.html) +* [1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources](https://archaeogeek.github.io/gemini-dev/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html) +* [1052-metadata-guidelines-for-geospatial-data-resources-part-1](https://archaeogeek.github.io/gemini-dev/1052-metadata-guidelines-for-geospatial-data-resources-part-1.html) +* [1053-common-metadata-errors-uk-location-discovery-metadata-service](https://archaeogeek.github.io/gemini-dev/1053-common-metadata-errors-uk-location-discovery-metadata-service.html) +* [1054-operational-guide](https://archaeogeek.github.io/gemini-dev/1054-operational-guide.html) +* [1055-uk-gemini-major-changes-since-1-0](https://archaeogeek.github.io/gemini-dev/1055-uk-gemini-major-changes-since-1-0.html) +* [1056-glossary](https://archaeogeek.github.io/gemini-dev/1056-glossary.html) + +Links above this are to the GitHub pages published in https://archaeogeek.github.io/gemini-dev/ ## Services and Datasets workflow -* These files are generated from [include files](https://docs.asciidoctor.org/asciidoc/latest/directives/include/), one per element, in the [docs/partials](https://github.com/agiorguk/gemini/tree/main/docs/partials) folder. +* These files are generated from [include files](https://docs.asciidoctor.org/asciidoc/latest/directives/include/), one per element, in the [docs/partials](https://github.com/archaeogeek/gemini/tree/main/docs/partials) folder. * The xml snippets are in the docs/snippets folder. * The naming convention for the element files is {element name in lower case without spaces}.asciidoc * The naming convention for the xml snippets is {optional dataset or service prefix}-{element name in lower case without spaces}-{optional specific example}.xml @@ -29,13 +29,13 @@ Where content differs between datasets and services, an [asciidoctor conditional To generate using the asciidoctor docker container, use the `-a` parameter, from the docs folder: ``` -docker run --rm -v $(pwd):/documents/ asciidoctor/docker-asciidoctor asciidoctor -a docinfo1 -a stylesheet=./assets/gemini.css -a variant-dataset *.adoc +docker run --rm -v $(pwd):/documents/ asciidoctor/docker-asciidoctor asciidoctor -a docinfo1 -a stylesheet=./assets/gemini.css -T templates -E slim -a variant-dataset *.adoc ``` Then repeat for services: ``` -docker run --rm -v $(pwd):/documents/ asciidoctor/docker-asciidoctor asciidoctor -a docinfo1 -a stylesheet=./assets/gemini.css -a variant-service *.adoc +docker run --rm -v $(pwd):/documents/ asciidoctor/docker-asciidoctor asciidoctor -a docinfo1 -a stylesheet=./assets/gemini.css -T templates -E slim -a variant-service *.adoc ``` ## Styling From b282dc286b4d9d197a22e5826c94b4f02ca6f8c4 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Mon, 27 Mar 2023 18:09:51 +0100 Subject: [PATCH 39/54] Update dev-build.yml --- .github/workflows/dev-build.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/dev-build.yml b/.github/workflows/dev-build.yml index 2217923..cce394e 100644 --- a/.github/workflows/dev-build.yml +++ b/.github/workflows/dev-build.yml @@ -17,12 +17,12 @@ jobs: id: adocbuild-datasets uses: avattathil/asciidoctor-action@master with: - program: "asciidoctor -a variant-dataset -a stylesheet=./assets/gemini.css -a docinfo1 'docs/*.asciidoc' 'docs/*.adoc'" + program: "asciidoctor -a variant-dataset -a stylesheet=./assets/gemini.css -a docinfo1 -T templates -E slim 'docs/*.asciidoc' 'docs/*.adoc'" - name: Build services variant id: adocbuild-services uses: avattathil/asciidoctor-action@master with: - program: "asciidoctor -a variant-service -a stylesheet=./assets/gemini.css -a docinfo1 'docs/*.asciidoc' 'docs/*.adoc'" + program: "asciidoctor -a variant-service -a stylesheet=./assets/gemini.css -a docinfo1 -T templates -E slim 'docs/*.asciidoc' 'docs/*.adoc'" - name: Deploy docs to ghpages uses: peaceiris/actions-gh-pages@v3 with: From 391b1a36462f6c6a6b7568f4f55a2bbef4ac2ea5 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Mon, 27 Mar 2023 18:18:12 +0100 Subject: [PATCH 40/54] Update dev-build.yml --- .github/workflows/dev-build.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/dev-build.yml b/.github/workflows/dev-build.yml index cce394e..15727f6 100644 --- a/.github/workflows/dev-build.yml +++ b/.github/workflows/dev-build.yml @@ -17,12 +17,12 @@ jobs: id: adocbuild-datasets uses: avattathil/asciidoctor-action@master with: - program: "asciidoctor -a variant-dataset -a stylesheet=./assets/gemini.css -a docinfo1 -T templates -E slim 'docs/*.asciidoc' 'docs/*.adoc'" + program: "asciidoctor -a variant-dataset-a docinfo1 -T templates -E slim 'docs/*.asciidoc' 'docs/*.adoc'" - name: Build services variant id: adocbuild-services uses: avattathil/asciidoctor-action@master with: - program: "asciidoctor -a variant-service -a stylesheet=./assets/gemini.css -a docinfo1 -T templates -E slim 'docs/*.asciidoc' 'docs/*.adoc'" + program: "asciidoctor -a variant-service -a docinfo1 -T templates -E slim 'docs/*.asciidoc' 'docs/*.adoc'" - name: Deploy docs to ghpages uses: peaceiris/actions-gh-pages@v3 with: From ca303cbe1dd4a30ef9a1970f60d905c71d685024 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Mon, 27 Mar 2023 18:20:00 +0100 Subject: [PATCH 41/54] Update dev-build.yml --- .github/workflows/dev-build.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/dev-build.yml b/.github/workflows/dev-build.yml index 15727f6..14e4341 100644 --- a/.github/workflows/dev-build.yml +++ b/.github/workflows/dev-build.yml @@ -17,7 +17,7 @@ jobs: id: adocbuild-datasets uses: avattathil/asciidoctor-action@master with: - program: "asciidoctor -a variant-dataset-a docinfo1 -T templates -E slim 'docs/*.asciidoc' 'docs/*.adoc'" + program: "asciidoctor -a variant-dataset -a docinfo1 -T templates -E slim 'docs/*.asciidoc' 'docs/*.adoc'" - name: Build services variant id: adocbuild-services uses: avattathil/asciidoctor-action@master From 807514224c12e0891e29140784bc3a952cc9c407 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Tue, 28 Mar 2023 12:08:11 +0100 Subject: [PATCH 42/54] corrected URL for datasets page --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index 0f85b29..7071369 100644 --- a/docs/README.md +++ b/docs/README.md @@ -2,7 +2,7 @@ # Gemini documentation DEV branch * [Services](https://archaeogeek.github.io/gemini-dev/1063-gemini-services.html) -* [Datasets](https://archaeogeek.github.io/gemini-dev/1062-gemini-datasets-and-series.html) +* [Datasets](https://archaeogeek.github.io/gemini-dev/1062-gemini-datasets-and-data-series.html) The files below have been converted but have not been altered to work using the new workflow. Consequently internal links will go to the agi website and there may be other errors. * [1037-uk-gemini-standard-and-inspire-implementing-rules](https://archaeogeek.github.io/gemini-dev/1037-uk-gemini-standard-and-inspire-implementing-rules.html) From b5541b45713530f6f76526a95c98f0b6a4bc97a9 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Tue, 28 Mar 2023 12:38:56 +0100 Subject: [PATCH 43/54] Update dev-build.yml --- .github/workflows/dev-build.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/dev-build.yml b/.github/workflows/dev-build.yml index 14e4341..7154a87 100644 --- a/.github/workflows/dev-build.yml +++ b/.github/workflows/dev-build.yml @@ -17,12 +17,12 @@ jobs: id: adocbuild-datasets uses: avattathil/asciidoctor-action@master with: - program: "asciidoctor -a variant-dataset -a docinfo1 -T templates -E slim 'docs/*.asciidoc' 'docs/*.adoc'" + program: "asciidoctor -a variant-dataset -a docinfo1 -T docs/templates -E slim 'docs/*.asciidoc' 'docs/*.adoc'" - name: Build services variant id: adocbuild-services uses: avattathil/asciidoctor-action@master with: - program: "asciidoctor -a variant-service -a docinfo1 -T templates -E slim 'docs/*.asciidoc' 'docs/*.adoc'" + program: "asciidoctor -a variant-service -a docinfo1 -T docs/templates -E slim 'docs/*.asciidoc' 'docs/*.adoc'" - name: Deploy docs to ghpages uses: peaceiris/actions-gh-pages@v3 with: From d44a1d3975c018777441c2a4fc5309eae94bf50c Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Tue, 28 Mar 2023 13:56:14 +0100 Subject: [PATCH 44/54] Made some corrections to services doc and partials --- docs/1063-gemini-services.adoc | 90 ++++++++---------------- docs/partials/abstract.asciidoc | 1 + docs/partials/spatialresolution.asciidoc | 3 +- 3 files changed, 33 insertions(+), 61 deletions(-) diff --git a/docs/1063-gemini-services.adoc b/docs/1063-gemini-services.adoc index c94ef14..45dddfd 100644 --- a/docs/1063-gemini-services.adoc +++ b/docs/1063-gemini-services.adoc @@ -1,4 +1,4 @@ -== [[top]]UK GEMINI 2.3 2020-04-07 service += [[top]]UK GEMINI 2.3 2020-04-07 service include::./includes/attributes.asciidoc[] == Contents @@ -6,65 +6,35 @@ include::./includes/attributes.asciidoc[] [width="100%",cols="50%,50%",options="header",] |=== |Metadata about the metadata record |Metadata about the resource -|<<45, File Identifier>> -|<<4, Abstract>> - -|<<47, Hierarchy level name>> -|<<2, Alternative title>> - -|<<30, Metadata date>> -|<<44, Bounding box>> - -|<<33, Metadata language>> -|<<41, Conformity>> - -|<<35, Metadata point of contact>> -|<<38, Coupled resource>> - -|<<54, Metadata standard name>> -|<<8, Dataset reference date>> - -|<<55, Metadata standard version>> -|<<43, Equivalent scale>> - -|<<49, Parent identifier>> -|<<15, Extent>> - -|<<39, Resource type>> -|<<6, Keyword>> - -| -|<<25, Limitations on public access>> - -| -|<<48, Quality scope>> - -| -|<<19, Resource locator>> - -| -|<<23, Responsible organisation>> - -| -|<<37, Spatial data service type>> - -| -|<<17, Spatial reference system>> - -| -|<<18, Spatial resolution>> - -| -|<<7, Temporal extent>> - -| -|<<1, Title>> - -| -|<<26, Use constraints>> - -| -|<<16, Vertical extent information>> +|<<45, File Identifier>> + +<<47, Hierarchy level name>> + +<<30, Metadata date>> + +<<33, Metadata language>> + +<<35, Metadata point of contact>> + +<<54, Metadata standard name>> + +<<55, Metadata standard version>> + +<<39, Resource type>> + +|<<4, Abstract>> + +<<2, Alternative title>> + +<<44, Bounding box>> + +<<41, Conformity>> + +<<38, Coupled resource>> + +<<8, Dataset reference date>> + +<<43, Equivalent scale>> + +<<49, Parent identifier>> + +<<15, Extent>> + +<<6, Keyword>> + +<<25, Limitations on public access>> + +<<48, Quality scope>> + +<<19, Resource locator>> + +<<23, Responsible organisation>> + +<<37, Spatial data service type>> + +<<17, Spatial reference system>> + +<<18, Spatial resolution>> + +<<7, Temporal extent>> + +<<1, Title>> + +<<26, Use constraints>> + +<<16, Vertical extent information>> + |=== Return to link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI diff --git a/docs/partials/abstract.asciidoc b/docs/partials/abstract.asciidoc index 0439674..b1b5e25 100644 --- a/docs/partials/abstract.asciidoc +++ b/docs/partials/abstract.asciidoc @@ -91,6 +91,7 @@ Change history... ---- ifdef::variant-dataset[] include::../snippets/dataset-abstract.xml[] +endif::[] ifdef::variant-service[] include::../snippets/service-abstract.xml[] endif::[] diff --git a/docs/partials/spatialresolution.asciidoc b/docs/partials/spatialresolution.asciidoc index 105db3c..3a04de8 100644 --- a/docs/partials/spatialresolution.asciidoc +++ b/docs/partials/spatialresolution.asciidoc @@ -110,8 +110,9 @@ ifdef::variant-dataset[] ---- include::../snippets/spatialresolution.xml[] ---- -|=== endif::[] +|=== + ==== .Metadata errors observed... From 6b736ab7dc1da39dde962226d12db6942516f135 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Tue, 28 Mar 2023 14:07:22 +0100 Subject: [PATCH 45/54] Checked and tweaked 1037 --- ...rd-and-inspire-implementing-rules.asciidoc | 21 ++++++++----------- 1 file changed, 9 insertions(+), 12 deletions(-) diff --git a/docs/1037-uk-gemini-standard-and-inspire-implementing-rules.asciidoc b/docs/1037-uk-gemini-standard-and-inspire-implementing-rules.asciidoc index adc41eb..58ecb1a 100644 --- a/docs/1037-uk-gemini-standard-and-inspire-implementing-rules.asciidoc +++ b/docs/1037-uk-gemini-standard-and-inspire-implementing-rules.asciidoc @@ -1,5 +1,4 @@ = UK-GEMINI Standard and Inspire Implementing Rules - include::./includes/attributes.asciidoc[] == Introduction{nbsp} _(GEMINI 2.3, June 2018)_ @@ -50,7 +49,7 @@ a{nbsp}link:1055-uk-gemini-major-changes-since-1-0.html[summary of changes]{nbsp}from earlier versions. Here is -a{nbsp}https://www.agi.org.uk/gemini/40-gemini/1250-element-summary/[summary]{nbsp}of +a{nbsp}link:1250-element-summary.html[summary]{nbsp}of the GEMINI elements (similar to Table 1 and Table 2 in GEMINI 2.2). Note: in GEMINI 2.3, the GEMINI Element number is called "GEMINI id"; @@ -66,32 +65,32 @@ follow{nbsp}link:1052-metadata-guidelines-for-geospatial-data-resources-part-1.h link]{nbsp}to gain a general introduction to metadata for geographic information before going any further. The{nbsp}link:1056-glossary.html[glossary of -terms]{nbsp}and{nbsp}https://www.agi.org.uk/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[list +terms]{nbsp}and{nbsp}link:1047-metadata-guidelines-for-geospatial-data-resources-part-3.html[list of references]{nbsp}may also be useful; * *starting to compile metadata conforming to UK GEMINI2*{nbsp}and are unfamiliar with the standard, then follow{nbsp}link:1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html[this link]{nbsp}to understand the scope, terms used and the requirements and also{nbsp}link:1049-metadata-guidelines-for-geospatial-data-resources-part-2.html[this -one]{nbsp}which provides general guidance;https://www.agi.org.uk/40-gemini/ +one]{nbsp}which provides general guidance; * *familiar with UK GEMINI*{nbsp}and require specific information about the requirements and guidance for the metadata elements, then follow one of these links: to -describe{nbsp}https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series[datasets +describe{nbsp}link:1062-gemini-datasets-and-data-series.html[datasets or series]{nbsp}or -for{nbsp}https://www.agi.org.uk/40-gemini/1063-gemini-services[services]; +for{nbsp}link:1063-gemini-services.html[services]; * *encoding UK GEMINI metadata in XML*, then{nbsp}link:1048-uk-gemini-encoding-guidance.html[general guidance]{nbsp}is supplemented with detailed guidance for each metadata element -at{nbsp}https://www.agi.org.uk/40-gemini/1062-gemini-datasets-and-data-series[datasets +at{nbsp}link:1062-gemini-datasets-and-data-series.html[datasets or series]{nbsp}or -for{nbsp}https://www.agi.org.uk/40-gemini/1063-gemini-services[services] +for{nbsp}link:1063-gemini-services.html[services] * *quality assuring metadata*, then information on common metadata errors can found{nbsp}link:1053-common-metadata-errors-uk-location-discovery-metadata-service.html[here]. * *Schematron rules*{nbsp}which check many of the constraints in GEMINI is -available as a{nbsp}https://github.com/AGIGemini/Schematron[on GitHub (free +available{nbsp}https://github.com/AGIGemini/Schematron[on GitHub (free link)], under a Creative Commons license. === Feedback @@ -108,8 +107,6 @@ therefore we would like to hear from you if you spot any of these or you would like to see improvements in terms of presentation and usability. Please send any comments -to{nbsp}mailto:gemini@agi.org.uk?subject=GEMINI2.3%20Release%20candidate[gemini@agi.org.uk], -copied to Peter Parslow at Ordnance Survey (chair of AGI Standards -Committee) +to{nbsp}mailto:gemini@agi.org.uk?subject=GEMINI2.3[gemini@agi.org.uk] _Last updated: May 2018_ \ No newline at end of file From d6346ebc2220148b3bfdeeae912b374eaa135026 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Tue, 28 Mar 2023 14:22:25 +0100 Subject: [PATCH 46/54] added a page for 1046-xml-element-order, made a few editorial changes to make it look neater --- docs/1046-xml-element-order.asciidoc | 126 +++++++++++++++++++++++++++ 1 file changed, 126 insertions(+) create mode 100644 docs/1046-xml-element-order.asciidoc diff --git a/docs/1046-xml-element-order.asciidoc b/docs/1046-xml-element-order.asciidoc new file mode 100644 index 0000000..6be7ed6 --- /dev/null +++ b/docs/1046-xml-element-order.asciidoc @@ -0,0 +1,126 @@ += XML element order +include::./includes/attributes.asciidoc[] + +== Dataset and Dataset Series Metadata + +Return +to{nbsp}link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI +2.3 home page] + +[cols=",,",] +|=== +|*ISO 19139 XML Element* |*GEMINI2 Item Number* |*GEMINI2 Item Name* +|*_gmd:MD_Metadata_* | | +|gmd:fileIdentifier |45 |File Identifier +|gmd:language |33 |Metadata language +|gmd:parentIdentifier |49 |Parent identifier +|gmd:hierarchyLevel |39 |Resource type +|gmd:hierarchyLevelName |47 |Hierarchy level name +|gmd:contact |35 |Metadata point of contact +|gmd:dateStamp |30 |Metadata date +|gmd:referenceSystemInfo |17 |Spatial reference system +|gmd:identificationInfo | | +|*_gmd:MD_DataIdentification_* | | +|_  gmd:citation_ | | +|_    gmd:CI_Citation_ | | +|      gmd:title |1 |Title +|      gmd:alternateTitle |2 |Alternative title +|      gmd:date |8 |Dataset reference date +|      gmd:identifier |36 |Unique resource identifier +|  gmd:abstract |4 |Abstract +|  gmd:pointOfContact |23 |Responsible organisation +|  gmd:resourceMaintenance |24 |Frequency of update +|  gmd:descriptiveKeywords |6 |Keyword +|  _gmd:resourceConstraints_ | | +|   _gmd:MD_LegalConstraints_ | | +|     _gmd:accessConstraints_ | | +|      gmd:otherConstraints |25 |Limitations on public access +|  _gmd:resourceConstraints_ | | +|   _gmd:MD_Constraints_ | | +|      gmd:useLimitation |26 |Use constraints +| gmd:spatialRepresentationType |50 |Spatial representation type +| _ gmd:spatialResolution_ | | +|   _ gmd:MD_Resolution_ | | +|      gmd:distance |18 |Spatial resolution +|  _gmd:spatialResolution_ | | +|_    gmd:MD_Resolution_ | | +|      gmd:equivalentScale |43 |Equivalent scale +|  gmd:language |3 |Dataset language +|  gmd:characterSet |51 |Character encoding +|  gmd:topicCategory |5 |Topic category +|_  gmd:extent_ | | +|   _gmd:EX_Extent_ | | +|     _gmd:geographicElement_ | | +|        gmd:EX_GeographicDescription |15 |Extent +|_      _  gmd:EX_GeographicBoundingBox |44 |Bounding box +|      gmd:temporalElement |7 |Temporal extent +|      gmd:verticalElement |16 |Vertical extent information +|  gmd:supplementalInformation |27 |Additional information source +|_gmd:distributionInfo_ | | +|  gmd:distributionFormat |21 |Data format +|  gmd:transferOptions |19 |Resource locator +|_gmd:dataQualityInfo_ | | +|  gmd:scope |48 |Quality scope +|  _gmd:report_ | | +|   gmd:DQ_DomainConsistency |41 |Conformity +|  gmd:lineage |10 |Lineage +|_gmd:dataQualityInfo_ | | +|_  gmd:report_ | | +|   gmd:DQ__XXXXXX_ |52 |Data quality +|=== + +== Service Metadata + +[cols=",,",] +|=== +|*ISO 19139 XML Element* |*GEMINI2 Item Number* |*GEMINI2 Item Name* +|*_gmd:MD_Metadata_* | | +|gmd:fileIdentifier |45 |File Identifier +|gmd:language |33 |Metadata language +|gmd:parentIdentifier |49 |Parent identifier +|gmd:hierarchyLevel |39 |Resource type +|gmd:hierarchyLevelName |47 |Hierarchy level name +|gmd:contact |35 |Metadata point of contact +|gmd:dateStamp |30 |Metadata date +|gmd:referenceSystemInfo |17 |Spatial reference system +|gmd:identificationInfo | | +|*_srv:SV_Identification_* | | +|_  gmd:citation_ | | +|_    gmd:CI_Citation_ | | +|      gmd:title |1 |Title +|      gmd:alternateTitle |2 |Alternative title +|      gmd:date |8 |Dataset reference date +|      gmd:identifier |- |- +|  gmd:abstract |4 |Abstract +|  gmd:pointOfContact |23 |Responsible organisation +|  gmd:resourceMaintenance |- |- +|  gmd:descriptiveKeywords |6 |Keyword +|  _gmd:resourceConstraints_ | | +|   _gmd:MD_LegalConstraints_ | | +|     _gmd:accessConstraints_ | | +|      gmd:otherConstraints |25 |Limitations on public access +|  _gmd:resourceConstraints_ | | +|   _gmd:MD_Constraints_ | | +|      gmd:useLimitation |26 |Use constraints +|  srv:serviceType |37 |Spatial data service type +|_ srv:extent_ | | +|   _gmd:EX_Extent_ | | +|     _gmd:geographicElement_ | | +|        gmd:EX_GeographicDescription |15 |Extent +|_      _  gmd:EX_GeographicBoundingBox |44 |(the bounding coordinates) +|      gmd:temporalElement |7 |Temporal extent +|      gmd:verticalElement |16 |Vertical extent information +|    srv:couplingType |- |- +|    srv:containsOperations |- |- +|    srv:operatesOn |38 |Coupled resource +|_gmd:distributionInfo_ | | +|  gmd:distributionFormat |- |- +|  gmd:transferOptions |19 |Resource locator +|_gmd:dataQualityInfo_ | | +|  gmd:scope |48 |Quality scope (including levelDescription) +|  _gmd:report_ | | +|   gmd:DQ_DomainConsistency |41 |Conformity +|=== + +_Last updated: April 2018_ + From 67b51e7faf3e1a4dfa9bc5d3256e84b893455e9c Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Tue, 28 Mar 2023 14:28:51 +0100 Subject: [PATCH 47/54] added 1250-element-summary --- docs/1250-element-summary.asciidoc | 115 +++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 docs/1250-element-summary.asciidoc diff --git a/docs/1250-element-summary.asciidoc b/docs/1250-element-summary.asciidoc new file mode 100644 index 0000000..a982fff --- /dev/null +++ b/docs/1250-element-summary.asciidoc @@ -0,0 +1,115 @@ += Element Summary +include::./includes/attributes.asciidoc[] + +Return +to{nbsp}link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI +2.3 home page] + +[cols=",,,,,,",] +|=== +|UK GEMINI id |Element name |Obligation |Number of occurrences |Dataset +and series |Service |Revision date + +|1 |Title |Mandatory |Single |✓ |✓ |March 2019 + +|2 |Alternative title |Optional |Multiple |✓ |✓ |April 2020 + +|3 |Dataset language |Mandatory |Multiple |✓ |n/a |September 2018 + +|4 |Abstract |Mandatory |Single |✓ |✓ |March 2019 + +|5 |Topic Category |Mandatory when the data resource is a dataset or +dataset series. Not applicable to services. |Multiple |✓ |n/a |March +2019 + +|6 |Keyword |Mandatory |Multiple |✓ |✓ |May 2019 + +|7 |Temporal extent |Mandatory for datasets and dataset series |Multiple +|✓ |✓ |May 2018 + +|8 |Dataset reference date |Mandatory |Multiple |✓ |✓ |March 2019 + +|10 |Lineage |Mandatory |Single |✓ |n/a |March 2019 + +|15 |Extent |Optional |Multiple |✓ |✓ |August 2010 + +|16 |Vertical extent information |Optional |Multiple |✓ |✓ |March 2019 + +|17 |Spatial reference system |At least one coordinate reference system +shall be given |Multiple |✓ |✓ |March 2019 + +|18 |Spatial resolution |Conditional - where a resolution distance can +be specified |Multiple |✓ |✓ |March 2019 + +|19 |Resource locator |Conditional - Must be supplied when online access +is available |Multiple |✓ |✓ |July 2009 + +|21 |Data format |Mandatory |Multiple |✓ |n/a |March 2019 + +|23 |Responsible organisation |Mandatory |Multiple |✓ |✓ |July 2009 + +|25 |Limitations on public access |Mandatory |Multiple |✓ |✓ |January +2020 + +|26 |Use constraints |Mandatory |Multiple |✓ |✓ |September 2018 + +|27 |Additional information |Optional |Single |✓ |n/a |October 2018 + +|30 |Metadata date* |Mandatory |Single |✓ |✓ |May 2018 + +|33 |Metadata language* |Mandatory |Single |✓ |✓ |September 2018 + +|35 |Metadata point of contact* |Mandatory |Multiple |✓ |✓ |July 2009 + +|36 |Resource identifier |Mandatory for datasets and dataset series +|Multiple |✓ |n/a |May 2018 + +|37 |Spatial data service type |Mandatory |Single |n/a |✓ |July 2009 + +|38 |Coupled resource |Conditional - mandatory for View and Download +services, optional for other service types. |Multiple |n/a |✓ |March +2019 + +|39 |Resource type* |Mandatory |Single |✓ |✓ |July 2009 + +|41 |Conformity |Mandatory |Multiple |✓ |✓ |April 2020 + +|43 |Equivalent scale |Optional |Multiple |✓ |✓ |July 2009 + +|44 |Bounding box |Mandatory |Multiple |✓ |✓ |December 2012 + +|45 |File Identifier* |Mandatory |Single |✓ |✓ |March 2019 + +|47 |Hierarchy level name* |Conditional, required when Resource type +(ISO hierarchyLevel) is not "dataset". |Single |✓ |✓ |April 2020 + +|48 |Quality scope |Mandatory |Multiple |✓ |✓ |March 2019 + +|49 |Parent identifier* |Optional |Single |✓ |✓ |May 2018 + +|50 |Spatial representation type |Mandatory |Multiple |✓ |n/a |May 2018 + +|51 |Character encoding |Conditional (mandatory if an encoding is used +that is not based on UTF-8, otherwise optional) |Multiple |✓ |n/a |May +2018 + +|52 |Data quality |Conditional: Topological consistency report is +mandatory if the dataset includes types from the INSPIRE Generic Network +Model and does not assure centerline topology (connectivity of +centrelines) for the network, otherwise optional |Multiple |✓ |n/a |May +2018 + +|53 |Maintenance information |Optional |Single |✓ |n/a |April 2020 + +|54 |Metadata standard name* |Optional |Single |✓ |✓ |January 2020 + +|55 |Metadata standard version* |Optional |Single |✓ |✓ |January 2020 +|=== + +* indicates metadata on metadata + +Note. Element numbers 9, 11, 12, 13, 14, 20, 22, 28, 29, 31, 32, 40 and +42 have been omitted because they were used to identify elements that +have now been deleted from the Standard, and have not been reallocated +to avoid confusion. + From 3bf6d11c82e0822487b491dbfbac33713df767c1 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Tue, 28 Mar 2023 15:04:02 +0100 Subject: [PATCH 48/54] added 1053 common metadata errors --- ...cation-discovery-metadata-service.asciidoc | 224 +++++++++--------- 1 file changed, 116 insertions(+), 108 deletions(-) diff --git a/docs/1053-common-metadata-errors-uk-location-discovery-metadata-service.asciidoc b/docs/1053-common-metadata-errors-uk-location-discovery-metadata-service.asciidoc index f7f1f26..ec1f52a 100644 --- a/docs/1053-common-metadata-errors-uk-location-discovery-metadata-service.asciidoc +++ b/docs/1053-common-metadata-errors-uk-location-discovery-metadata-service.asciidoc @@ -1,32 +1,33 @@ -== Common Metadata Errors UK Location Discovery Metadata Service += Common Metadata Errors UK Location Discovery Metadata Service include::./includes/attributes.asciidoc[] Return -to{nbsp}https://www.agi.org.uk/gemini/40-gemini/1037-uk-gemini-standard-and-inspire-implementing-rules[GEMINI +to{nbsp}link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI 2.3 home page] -https://www.agi.org.uk/gemini/40-gemini/1053-common-metadata-errors-uk-location-discovery-metadata-service#Intro[1. +link:1053-common-metadata-errors-uk-location-discovery-metadata-service.html#Intro[1. Introduction] -https://www.agi.org.uk/gemini/40-gemini/1053-common-metadata-errors-uk-location-discovery-metadata-service#schema_errors[2. +link:1053-common-metadata-errors-uk-location-discovery-metadata-service.html#schema_errors[2. Schema errors] -https://www.agi.org.uk/gemini/40-gemini/1053-common-metadata-errors-uk-location-discovery-metadata-service#ISO_errors[3. +link:1053-common-metadata-errors-uk-location-discovery-metadata-service.html#ISO_errors[3. ISO 19139 Schematron errors] -https://www.agi.org.uk/gemini/40-gemini/1053-common-metadata-errors-uk-location-discovery-metadata-service#proc_errors[4. +link:1053-common-metadata-errors-uk-location-discovery-metadata-service.html#proc_errors[4. Processing Errors] -https://www.agi.org.uk/gemini/40-gemini/1053-common-metadata-errors-uk-location-discovery-metadata-service#inspire_warnings[5. +link:1053-common-metadata-errors-uk-location-discovery-metadata-service.html#inspire_warnings[5. European INSPIRE Geoportal errors and warnings] -https://www.agi.org.uk/gemini/40-gemini/1053-common-metadata-errors-uk-location-discovery-metadata-service#soft_errors[6. +link:1053-common-metadata-errors-uk-location-discovery-metadata-service.html#soft_errors[6. "Soft" errors] -https://www.agi.org.uk/gemini/40-gemini/1053-common-metadata-errors-uk-location-discovery-metadata-service#winner[7. +link:1053-common-metadata-errors-uk-location-discovery-metadata-service.html#winner[7. And the winner?] -=== [#Intro]####1. Introduction +== 1. Introduction +[#Intro] The UK Location Discovery Metadata Service (DMS) lies at the heart of UK Location and the delivery of the UK Location Strategy and INSPIRE - 'to @@ -36,31 +37,31 @@ The DMS operates by collecting valid metadata records from data publishers and making them available on data.gov.uk, and for further collection to the European INSPIRE Geoportal. -==== 1.1 Target Audience +=== 1.1 Target Audience The primary audience for this document are those responsible for creating and maintaining metadata records, located within data provider organisations, and their technical partners. -==== 1.2 Background +=== 1.2 Background This document is largely based on an analysis of validation failures when metadata validation was first run on the records that had already been collected into{nbsp}https://data.gov.uk/[data.gov.uk]. Approximately half the records present in data.gov.uk at that time initially failed. -==== 1.3 Assumed Knowledge +=== 1.3 Assumed Knowledge This guide assumes that the reader is familiar with the creation and management of metadata and has read the{nbsp}UK Location “Getting Started' series of -guides{nbsp}[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[27]], +guides{nbsp}link:1047-metadata-guidelines-for-geospatial-data-resources-part-3.html[27]], and the DMS Operational Guide. Readers requiring an introduction to discovery metadata for geospatial data resources are referred to the UK GEMINI guide “Metadata Guidelines for Geospatial Data Resources, Introduction – Part 1” -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[1]]. +[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3.html[1]]. Other useful reading includes AGI’s Guidelines for UK GEMINI Part 3 Metadata Quality @@ -68,9 +69,8 @@ Metadata Quality *GEMINI 2.3 note: the DMS Operational Guide, UK GEMINI Encoding Guidance and AGI's Guidelines - Part 2 have all been consolidated into this content. + -* -==== 1.4 Where to Obtain More Information +=== 1.4 Where to Obtain More Information The latest information, and additional resources, can be obtained by visiting the{nbsp}UK Location{nbsp}web site. @@ -78,7 +78,7 @@ visiting the{nbsp}UK Location{nbsp}web site. If you would like to contact the UK Location Coordination Unit, contact details are at{nbsp}http://data.gov.uk/location/contact_points -==== 1.5 Validation +=== 1.5 Validation ==== GEMINI 2.3 @@ -134,9 +134,10 @@ metadata may be misleading. With GEMINI 2.3,{nbsp}a second (supplemental) schematron is provided to test for recommendations. -=== [#schema_errors]####2. Schema errors +== 2. Schema errors +[#schema_errors] -==== 2.1 Confusion of Date and DateTime +=== 2.1 Confusion of Date and DateTime In ISO 19115, Date and DateTime are distinct types. Although in many elements, either is allowed, the XML encoding needs to be explicit about @@ -145,31 +146,33 @@ DateTime element. Example of invalid structure: -`` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} 2012-11-15` - -`` +[source,xml] +---- + + 2012-11-15 + +---- Examples of valid structure: This should either include the time, e.g. -`` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} 2012-11-15T13:50:38` - -`` +[source,xml] +---- + + 2012-11-15T13:50:38 + +---- Or be explicit that it doesn’t: +[source,xml] +---- + + 2012-11-15 + +---- -`` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} 2012-11-15` - -`` - -==== 2.2 Elements in the wrong order +=== 2.2 Elements in the wrong order Although there is no “logical” ordering of the elements in ISO 19115, INSPIRE, or GEMINI, the XML pattern adopted by ISO 19139 means that the @@ -181,13 +184,14 @@ used by GEMINI. The example found contained the ISO 19115 metadata characterSet element before the metadata language element. -=== [#ISO_errors]####3. ISO 19139 Schematron errors +== 3. ISO 19139 Schematron errors +[#ISO_errors] See -also{nbsp}https://www.agi.org.uk/gemini/40-gemini/1053-common-metadata-errors-uk-location-discovery-metadata-service#soft_errors[“Empty +also{nbsp}link:1053-common-metadata-errors-uk-location-discovery-metadata-service.html#soft_errors[“Empty strings”]. -==== 3.1 No level description +=== 3.1 No level description ISO 19115 requires that a “level description” is given for any quality statement that is not describing the “dataset” or “series” level. @@ -195,34 +199,26 @@ INSPIRE and GEMINI use the quality statement for both lineage and conformity. This means that any “service” record must provide a gmd:DQ_Scope/gmd:levelDescription element, such as: -`` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} ` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} service` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} ` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} ` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} ` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} ` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} Geographic web service` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} ` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} ` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} ` - -`` +[source,xml] +---- + + + service + + + + + Geographic web service + + + + +---- A similar rule applies to “hierarchyLevelName”, which must be provided for any record that is not describing a dataset. -==== 3.4 No Format provided +=== 3.2 No Format provided ISO 19139 requires that a format is given, either within the “distribution” section or the “distributor” section. INSPIRE & UK GEMINI @@ -230,12 +226,13 @@ encoding guidance only expects the distribution section, as the place to encode the Resource locator, which effectively renders distribution format mandatory. -=== [#proc_errors]####4. Processing errors +== 4. Processing errors +[#proc_errors] These errors do not result in invalid records on an individual basis, but may well result in the wrong records being available to the public. -==== 4.1 Non-compliant Web Accessible Folder (WAF) +=== 4.1 Non-compliant Web Accessible Folder (WAF) The collection definition is very precise. Just because you can browse to a page that appears to contain the records, it does not mean that the @@ -245,7 +242,7 @@ links to records that are elsewhere. Similarly, collection differentiates between a single XML record at the end of a URL, and a WAF. -==== 4.2 FileIdentifier +=== 4.2 FileIdentifier This is the identifier for a metadata record through time, so do ensure that it remains the same when you update a record, and is different in @@ -257,7 +254,7 @@ the old one. If you accidently provide two records with the same identifier, one will replace the other. -==== 4.3 Metadata date +=== 4.3 Metadata date This is used to distinguish which of two records with the same fileIdentifier the system will keep. @@ -266,9 +263,10 @@ Even if the records are moved to a different server, if the fileIdentifier and metadata date are the same, the harvester will not collect the new files. -=== [#inspire_warnings]####5. European INSPIRE Geoportal errors & warnings +== 5. European INSPIRE Geoportal errors & warnings +[#inspire_warnings] -==== 5.1 Conformity statement missing +=== 5.1 Conformity statement missing INSPIRE requires a ‘conformity’ statement, which can say that the resource conforms, does not conform, or has not been evaluated against, @@ -284,7 +282,7 @@ incomplete but it is required”. This can be ignored. *GEMINI Consolidation Note: The INSPIRE Encoding Guidelines were updated in 2013; GEMINI 2.3 will be updated on this point.* -==== 5.2 Missing “coupled resource” +=== 5.2 Missing “coupled resource” INSPIRE requires “Coupled resource” to be populated “where relevant”. This effectively makes it mandatory for View & Download services, and @@ -292,9 +290,10 @@ the INSPIRE Geoportal reports this as a validation issue. However, the Geoportal also reports this issue for a Discovery service metadata record, where coupled resource is not mandatory. -=== [#soft_errors]####6. “Soft” errors +== 6. “Soft” errors +[#soft_errors] -==== 6.1 Empty strings +=== 6.1 Empty strings When first run, approximately half the rejections were down to this error. UK Location decided to remove this check, so the records can be @@ -312,36 +311,40 @@ empty”. The most common examples were structures like: -`` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} ` - -`` - -(in this case, as gmd:phone is optional, it should be entirely missing) - -and - -`` +[source,xml] +---- + + + +---- -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} ` +(in this case, as gmd:phone is optional, it should be entirely missing), and: -`` +[source,xml] +---- + + + +---- Examples of valid structures are: -`` +[source,xml] +---- + +---- (although again, it would be equally valid to leave the element out entirely) -`` +[source,xml] +---- + + Explorer House, Adanac Drive + +---- -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} Explorer House, Adanac Drive` - -`` - -==== 6.2 Short relative URLs +=== 6.2 Short relative URLs The issues discussed here have just been noted whilst browsing the records in data.gov.uk @@ -352,37 +355,42 @@ mostly these are populated with a local path, which is then impossible to use once the dataset is harvested to any other location – even if it did work in the data publisher’s original location. For example: -`` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} ` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} Council_Housing_s.png` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} ` - -`{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp}{nbsp} …` - -`` +[source,xml] +---- + + + Council_Housing_s.png + + ... + +---- -==== 6.3 Incorrect code list URL +=== 6.3 Incorrect code list URL The INSPIRE encoding guidance, and therefore earlier versions of the GEMINI Encoding Guidance had a minor spelling (capitalisation) mistake in the path for the code list dictionary. This is used a number of times in most records. -`information` +[source,xml] +---- +information +---- Should be -`information` +[source,xml] +---- +information +---- (a lower case ‘c’ in the first occurrence of ‘codelist’ within the URL) *GEMINI Consolidation Note: The INSPIRE Encoding Guidelines have been updated to correct this, in 2016.* -=== [#winner]####7. And the winner? +== 7. And the winner? +[#winner] This table, for interest, gives the approximate error rate for each of the above errors, in the sample tested in late 2012. This does not From 5b6a0e3ae8b37646cc0bd00ba4b734b3f9a0994c Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Tue, 28 Mar 2023 15:23:47 +0100 Subject: [PATCH 49/54] added first pass at 1054 operational guide --- docs/1054-operational-guide.asciidoc | 262 +++++++++++++-------------- 1 file changed, 131 insertions(+), 131 deletions(-) diff --git a/docs/1054-operational-guide.asciidoc b/docs/1054-operational-guide.asciidoc index 46dce00..baab29f 100644 --- a/docs/1054-operational-guide.asciidoc +++ b/docs/1054-operational-guide.asciidoc @@ -1,99 +1,71 @@ -== Operational Guide += Operational Guide include::./includes/attributes.asciidoc[] == UK Location Discovery Metadata Service -Return -to{nbsp}https://www.agi.org.uk/gemini/40-gemini/1037-uk-gemini-standard-and-inspire-implementing-rules[GEMINI +Return to link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI 2.3 home page] Contents -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#Intro[1. -Introduction] +link:1054-operational-guide.html#Intro[1.Introduction] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#1.1[1.1 -Target audience] +link:1054-operational-guide.html#1.1[1.1 Target audience] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#1.2[1.2 -Assumed knowledge] +link:1054-operational-guide.html#1.2[1.2 Assumed knowledge] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#1.3[1.3 -DMS resources] +link:1054-operational-guide.html#1.3[1.3 DMS resources] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#1.4[1.4 -Where to obtain more information] +link:1054-operational-guide.html#1.4[1.4 Where to obtain more information] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#Pub_Dis_Met[2. -Publishing Discovery Metadata] +link:1054-operational-guide.html#Pub_Dis_Met[2. Publishing Discovery Metadata] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#2.1[2.1 -Requirements on data providers and publishers] +link:1054-operational-guide.html#2.1[2.1 Requirements on data providers and publishers] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#2.2[2.2 -Accountability] +link:1054-operational-guide.html#2.2[2.2 Accountability] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#2.3[2.3 -Publishing discovery metadata for data] +link:1054-operational-guide.html#2.3[2.3 Publishing discovery metadata for data] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#2.4[2.4 -Publishing discovery metadata for on-line services] +link:1054-operational-guide.html#2.4[2.4 Publishing discovery metadata for on-line services] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#2.5[2.5 -Maintaining discovery metadata] +link:1054-operational-guide.html#2.5[2.5 Maintaining discovery metadata] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#2.6[2.6 -Data sharing and charging and licensing] +link:1054-operational-guide.html#2.6[2.6 Data sharing and charging and licensing] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#Dis_Met_Req[3. -Discovery Metadata Requirements] +link:1054-operational-guide.html#Dis_Met_Req[3. Discovery Metadata Requirements] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#3.1[3.1 -Elements of importance to the DMS] +link:1054-operational-guide.html#3.1[3.1 Elements of importance to the DMS] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#3.2[3.2 -Data provider licence information] +link:1054-operational-guide.html#3.2[3.2 Data provider licence information] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#3.3[3.3 -Metadata encoding] +link:1054-operational-guide.html#3.3[3.3 Metadata encoding] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#3.4[3.4 -Metadata validation] +link:1054-operational-guide.html#3.4[3.4 Metadata validation] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#3.5[3.5 -Community extensions to UK GEMINI2] +link:1054-operational-guide.html#3.5[3.5 Community extensions to UK GEMINI2] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#3.6[3.6 -Extensions to code lists] +link:1054-operational-guide.html#3.6[3.6 Extensions to code lists] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#3.7[3.7 -Local guidance] +link:1054-operational-guide.html#3.7[3.7 Local guidance] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#Pub_Dis_Met_rec[4. -Publishing Discovery Metadata records] +link:1054-operational-guide.html#Pub_Dis_Met_rec[4. Publishing Discovery Metadata records] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#4.1[4.1 -Publishing discovery metadata records] +link:1054-operational-guide.html#4.1[4.1 Publishing discovery metadata records] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#4.2[4.2 -Registering the harvest location] +link:1054-operational-guide.html#4.2[4.2 Registering the harvest location] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#4.3[4.3 -Collection] +link:1054-operational-guide.html#4.3[4.3 Collection] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#Met_Pub_Tec[5. -Metadata Publishing and Technology Choices] +link:1054-operational-guide.html#Met_Pub_Tec[5. Metadata Publishing and Technology Choices] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#5.1[5.1 -UK Location metadata editor] +link:1054-operational-guide.html#5.1[5.1 UK Location metadata editor] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#5.2[5.2 -Geonetwork publishing solution] +link:1054-operational-guide.html#5.2[5.2 Geonetwork publishing solution] -https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#5.3[5.3 -Third party solutions] +link:1054-operational-guide.html#5.3[5.3 Third party solutions] -=== [#Intro]####1. Introduction +== 1. Introduction +[#Intro] The UK Location Discovery Metadata Service (DMS) lies at the heart of UK Location and the delivery of the UK Location Strategy and INSPIRE - 'to @@ -123,7 +95,8 @@ publishing mechanisms to those described here. Therefore in the first instance, please use the appropriate contact information listed under “Where to obtain more information” below. -==== *[#1.1]####1.1 Target Audience* +=== 1.1 Target Audience +[#1.1] The primary audience for the Guide are business managers and information officers, located within data provider organisations, and their @@ -137,33 +110,34 @@ The guide will also be of interest to anyone who requires a general understanding of the UK Location Discovery Metadata Service and how it is intended to operate. -==== *[#1.2]####1.2 Assumed Knowledge* +=== 1.2 Assumed Knowledge +[#1.2] This guide assumes that the reader is familiar with the creation and management of metadata and has read the UK Location “Getting Started' series of -guides[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[27]]. +guides[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3[27]]. Readers requiring an introduction to discovery metadata for geospatial data resources are referred to the UK GEMINI guide -“https://www.agi.org.uk/gemini/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1[Metadata +“link:1052-metadata-guidelines-for-geospatial-data-resources-part-1[Metadata Guidelines for Geospatial Data Resources, Introduction – Part -1]”[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[1]] +1]”[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3[1]] . -===== *1.2.1 Do you know your “Data Provider” from your “Data Publisher”* +=== 1.2.1 Do you know your “Data Provider” from your “Data Publisher” Throughout this guide we refer to “Data Providers” and “Data Publishers”. Within UK Location, the definition and distinction being made between these two roles is very important.{nbsp} So what is the difference?: -====== The Data Provider +==== The Data Provider The organisation that creates the data and supplies the data for web publication, along with its metadata -====== The Data Publisher +==== The Data Publisher The organisation that publishes the data on the web and supplies data services to data users @@ -171,14 +145,16 @@ services to data users If you as a Data Provider publish directly, then you will perform both the roles of Data Provider and Data Publisher. -==== *[#1.3]####1.3 DMS Resources* +=== 1.3 DMS Resources +[#1.3] The latest versions of all the UK Location resources referred to in this guide can be found via the UK Location Resource Centre: https://data.gov.uk/[http://data.gov.uk/location] -==== *[#1.4]####1.4 Where to Obtain More Information* +=== 1.4 Where to Obtain More Information +[#1.4] The latest information, and additional resources, can be obtained by visiting the{nbsp}UK Location{nbsp}web site. @@ -206,7 +182,8 @@ E-mail:{nbsp}[#cloak0de48b02b62ff6b0733df4ab33e5b829]#mailto:Bill.Oates@wales.gs Email:{nbsp}[#cloak4e2ac9d8ddb12cb122f38a77142a18f4]#ProgrammeOffice@dfpni.gov.uk#{nbsp}or visit the{nbsp}Spatial NI{nbsp}website at{nbsp}https://www.spatialni.gov.uk/ -=== [#Pub_Dis_Met]####2. Publishing Discovery Metadata +== 2. Publishing Discovery Metadata +[#Pub_Dis_Met] Data Providers publish their data and on-line services into UK Location by creating and publishing discovery metadata. These resources are @@ -214,7 +191,8 @@ registered with UK Location and made discoverable through its central metadata catalogue, which forms part of the public data access portal, data.gov.uk. -==== *[#2.1]####2.1 Requirements on Data Providers and Publishers* +=== 2.1 Requirements on Data Providers and Publishers +[#2.1] Deciding to publish data into UK Location is a major commitment. INSPIRE and UK Location is not a simple cataloguing service of what data exists @@ -233,7 +211,7 @@ data.gov.uk the resources you publish, based on the feedback you receive, as this will be beneficial to both data provider and user * You -will{nbsp}https://www.agi.org.uk/gemini/40-gemini/1054-operational-guide#2.5[maintain +will{nbsp}link:1054-operational-guide.html#2.5[maintain your discovery metadata]: ** assuring its quality against appropriate standards ** reviewing it and updating it regularly and ensuring it is updated @@ -257,19 +235,20 @@ Coordination Unit * For all data: ** compliance with the INSPIRE Metadata Regulation -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[6]] +[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3[6]] and the UK Location operational requirements as set out in this guide ** if publishing INSPIRE Network (on-line) Services, compliance with the INSPIRE Network Services Regulation -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[9]] +[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3[9]] ** the publishing of INSPIRE View Services for a given dataset or data series * For data that comes under an INSPIRE Theme and contains features listed in the INSPIRE Data Specifications: ** legal compliance with the INSPIRE Directive -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[8]] +[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3[8]] -==== *[#2.2]####2.2 Accountability* +=== 2.2 Accountability +[#2.2] Accountability for publishing data and associated resources rests with you the Data Provider. If you are a Data Provider and are publishing @@ -279,7 +258,8 @@ services published.{nbsp} Accountability at all times remains with you as Data Provider, e.g. in relation to INSPIRE compliance and conformance to INSPIRE and UK Location technical guidance. -==== *[#2.3]####2.3 Publishing Discovery Metadata for Data* +=== 2.3 Publishing Discovery Metadata for Data +[#2.3] The process for publishing metadata records for data is shown as a process model below. @@ -329,7 +309,8 @@ becomes discoverable through the UK Location discovery service.{nbsp} If errors are found, then the Data Publisher will need to correct these and re-submit the resource. -==== *[#2.4]####2.4 Publishing Discovery Metadata for On-line Services* +=== 2.4 Publishing Discovery Metadata for On-line Services +[#2.4] The process for publishing metadata records for on-line services is shown as a process model below. @@ -356,7 +337,8 @@ Collection of the service metadata record is as for data, unless it is an existing service, in which case it will be an update of the existing registration. -==== *[#2.5]####2.5 Maintaining Discovery Metadata* +==== 2.5 Maintaining Discovery Metadata +[#2.5] UK Location requires that Data Providers and their Data Publishers maintain their published metadata records in line with the INSPIRE @@ -366,7 +348,8 @@ change your published dataset, or move the location of a resource e.g. view service, then you are responsible for ensuring that these changes are updated in your metadata. -==== *[#2.6]####2.6 Data Sharing and Charging and Licensing* +==== 2.6 Data Sharing and Charging and Licensing +[#2.6] Data sharing, including charging and licensing, 3rd party intellectual property, and e-commerce issues are covered under separate UK Location @@ -374,7 +357,8 @@ data sharing operational guidance. This is in the process of being published.{nbsp} Please visit the UK Location Resource Centre for more details. -=== [#Dis_Met_Req]####3. Discovery Metadata Requirements +== 3. Discovery Metadata Requirements +[#Dis_Met_Req] UK Location discovery metadata will be used by potential data users to discover and evaluate published location information for use in a range @@ -389,45 +373,47 @@ needs an application profile. *Considerable care needs to be taken over the creation of discovery metadata. It is strongly recommended that you use a metadata editor tool, that fully supports the encoding requirements defined in -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[28]] +[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3[28]] and uses the UK Location XSD and Schematron schemas -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[28,30]], +[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3[28,30]], to ensure that your metadata is fully compliant with UKL and INSPIRE requirements.* GEMINI 2.3 metadata is encoded in XML, as described in -the{nbsp}https://www.agi.org.uk/gemini/40-gemini/1048-uk-gemini-encoding-guidance[encoding +the{nbsp}link:1048-uk-gemini-encoding-guidance[encoding guidance{nbsp}]{nbsp}and a Schematron ruled-based validation Schema -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[30]] +[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3[30]] can be used to check these XML instances. For a detailed explanation of each element, please refer to -the{nbsp}https://www.agi.org.uk/gemini/40-gemini/1037-uk-gemini-standard-and-inspire-implementing-rules[UK +the{nbsp}link:1037-uk-gemini-standard-and-inspire-implementing-rules[UK GEMINI2 standard{nbsp}]and associated guidance. For metadata describing data (datasets and services), -click{nbsp}https://www.agi.org.uk/gemini/40-gemini/1062-gemini-datasets-and-data-series[here]. +click{nbsp}link:1062-gemini-datasets-and-data-series[here]. For metadata describing services, -click{nbsp}https://www.agi.org.uk/gemini/40-gemini/1063-gemini-services[here]. +click{nbsp}link:1063-gemini-services[here]. -==== [#3.1]####3.1 Elements of importance to the DMS +=== 3.1 Elements of importance to the DMS +[#3.1] Some metadata elements are particularly important to the operation of the DMS, rather than to the users of the DMS. -===== 3.1.1 Metadata record File Identifier +==== 3.1.1 Metadata record File Identifier To support the operation of UK Location and INSPIRE, discovery metadata records must include a File Identifier for the resource. The file identifier is the unique persistant identifier of the metadata record; it must not change when the record is updated. -===== 3.1.2 Metadata date +==== 3.1.2 Metadata date This must be updated when ever the metadata record is edited. Data.gov.uk harvesting will only collect the new record if the Metadata date is more recent than the old one. -===== [#data_servce_linking]####3.1.3 Data and Service Linking +==== 3.1.3 Data and Service Linking +[#data_servce_linking] UK Location and INSPIRE is a network of distributed on-line services that provide access to published location information. To provide this @@ -460,7 +446,8 @@ e.g.service=WMS&request=GetCapabilities&, or the location of further information about a service. |=== -==== *[#3.2]####3.2 Data Provider Licence information* +=== 3.2 Data Provider Licence information +[#3.2] The following Data Provider licensing information must be provided: @@ -479,15 +466,17 @@ categorise your data as open, ensure these licence titles are stated in the Use Constraints text field exactly as quoted here, for example “Open Government Licence”. -==== *[#3.3]####3.3 Metadata Encoding* +=== 3.3 Metadata Encoding +[#3.3] UK Location discovery metadata records must be published as an Extensible Markup Language (XML) document. This must follow -the{nbsp}https://www.agi.org.uk/gemini/40-gemini/1048-uk-gemini-encoding-guidance[UK +the{nbsp}link:1048-uk-gemini-encoding-guidance[UK Location UK GEMINI Encoding -Guidance]{nbsp}[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[28]]. +Guidance]{nbsp}[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3.html[28]]. -==== *[#3.4]####3.4 Metadata Validation* +=== 3.4 Metadata Validation +[#3.4] Published discovery metadata XML document resources will be validated in a three stage process, using: @@ -495,14 +484,15 @@ a three stage process, using: * The ISO XML schemas * The UK Location variant of the ISO Schematron rules * A{nbsp}UK Location GEMINI Schematron schema -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[30]] +[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3[30]] Data Publishers are required to validate their metadata records using these before resource registration. UK Location has published guidance on using its Schematron rules -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[29]]. +[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3[29]]. -==== *[#3.5]####3.5 Community Extensions to UK GEMINI2* +=== 3.5 Community Extensions to UK GEMINI2 +[#3.5] Within a given organisation or thematic community, there may be the need to record additional items of metadata to meet local requirements. @@ -514,7 +504,8 @@ UK Location will accept additional metadata elements within a metadata record XML document. These elements must be taken from ISO 19115 and be encoded in conformance with ISO 19139. -==== *[#3.7]####3.6 Extension to Code Lists* +=== 3.6 Extension to Code Lists +[#3.7] UK GEMINI2 includes a number of code lists taken from ISO 19115. Within a given organisation or thematic community, you may wish to extend these @@ -523,14 +514,16 @@ and/or UK Location specified code lists before they can be used.{nbsp} If you wish to extend a code list for an INSPIRE metadata element, please contact the UK Location Coordination Unit. -==== *[#3.7]####3.7 Local Guidance* +=== 3.7 Local Guidance +[#3.7] The type of data being published will have a strong bearing on the content of the metadata created. It is strongly recommended that data providers create local guidance, based on UK GEMINI2 and this operational guide. -=== [#Pub_Dis_Met_rec]####4. Publishing Discovery Metadata records +== 4. Publishing Discovery Metadata records +[#Pub_Dis_Met_rec] Publishing discovery metadata for UK Location for data and services is a three stage process: @@ -543,7 +536,8 @@ data.gov.uk collects the metadata records from the registered location, makes them available within data.gov.uk, and for further collection on to Europe. -==== *[#4.1]####4.1 Publishing Discovery Metadata records* +=== 4.1 Publishing Discovery Metadata records +[#4.1] This involves transferring your completed discovery metadata records to an on-line location, which can be machine accessed through the Internet. @@ -556,9 +550,9 @@ These mechanisms will be used by the Discovery Metadata Service, to collect registered discovery metadata records. For more information about this interface, please refer to the DMS Collection Interface Specification -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[26]]. +[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3[26]]. -===== 4.1.1 Discovery Metadata Harvest location +==== 4.1.1 Discovery Metadata Harvest location This can take a number of forms. It may be local to your business unit, or organisation, or a community resource, shared across a number of @@ -573,7 +567,7 @@ If publishing elsewhere, e.g. to thematic or regional catalogues and information portals, you should consider using this same control point – applying the ‘publish only once principle’. -====== *_Record Organisation_* +===== *_Record Organisation_* How you organise your records will be subject to your own local needs and practices. Possible catalogue/file directory structures include: @@ -605,7 +599,8 @@ If you have an immediate requirement for UK Location to support CSW Filtering, by category or element, please contact the UK Location Coordination Unit, using the contact form at:{nbsp}https://defra.gov.uk/. -==== *[#4.2]####4.2 Registering the harvest location* +=== 4.2 Registering the harvest location +[#4.2] UK Location discovery metadata records are registered using the UK Government data publishing and discovery @@ -624,7 +619,7 @@ records for data and services, using data.gov.uk, is shown below. image:https://www.agi.org.uk/images/xslt/RegisterDiscoveryMetadata.jpg[Register Discovery Metadata Records,width=960,height=720] -===== 4.2.1 Data.gov.uk Publisher Accounts +==== 4.2.1 Data.gov.uk Publisher Accounts Data and services are published against a registered organisation, e.g. government department or agency. This is the organisation{nbsp}*legally @@ -651,7 +646,7 @@ lets you edit publisher’s details (including name, description, and contact information), and authorize access for other users to be editor or administrator for the organisation. -====== *_Special Guidance for Third Party Publishers_* +==== *_Special Guidance for Third Party Publishers_* If you are a third party Data Publisher, i.e. publishing on behalf of a Data Provider, you will need to adopt a different approach for data and @@ -663,22 +658,22 @@ You will need to ensure that you have formal approval to publish from your Data Provider. This will be checked by The National Archives before approval is given. -====== *_Signing up for{nbsp}__data.gov.uk accounts_* +==== *_Signing up for{nbsp}__data.gov.uk accounts_* Before you can publish data and services on data.gov.uk, you will need to sign up and associate yourself with one or more Publishers. For further information, see the data.gov.uk User Guide -[https://www.agi.org.uk/gemini/40-gemini/1047-metadata-guidelines-for-geospatial-data-resources-part-3[31]] +[link:1047-metadata-guidelines-for-geospatial-data-resources-part-3[31]] -====== *_Creating a Publisher_* +==== *_Creating a Publisher_* If there is not an existing data.gov.uk Publisher for the UK Location Data Provider, you will need to contact the Cabinet Office data.gov.uk team to request the addition of your publisher: http://data.gov.uk/publisher/apply/cabinet-office -====== *_Publisher Administrators and Editors_* +==== *_Publisher Administrators and Editors_* Publishers are associated with two tiers of user: @@ -702,7 +697,7 @@ The addition of Administrators and Editors can only be done by the account Administrators; you can request this via the data.gov.uk site, or by contacting the account administrator directly. -===== 4.2.2 Registering Metadata Harvesting Resources +==== 4.2.2 Registering Metadata Harvesting Resources Having created an account on data.gov.uk and gained editor rights to the relevant Publisher, you are now in a position to register metadata @@ -739,14 +734,15 @@ at an interval specified by the Data Publisher * Response handling – automatic forwarding of error messages to an address specified by the Data Publisher, e.g. to a central error log -==== *[#4.3]####4.3 Collection* +=== 4.3 Collection +[#4.3] The collection task created as described above is only run when requested, that is, when you click the ‘Refresh’ button for that harvest source, which is on the list of harvesting sources visible to the administrators of the publisher. -===== 4.3.1 Validation +==== 4.3.1 Validation Once collected, the individual data and service discovery metadata records will be subject to the following validation checks: @@ -769,7 +765,7 @@ be added to the data.gov.uk metadata catalogue and the XML documents stored for subsequent use. Resources will take approximately 30 minutes to appear on data.gov.uk once successfully collected. -===== 4.3.2 Error Handling +==== 4.3.2 Error Handling If, having harvested from a metadata resource, the collection task fails, errors will be returned to the Discovery Metadata status panel. @@ -786,7 +782,7 @@ at{nbsp}http://inspire-geoportal.ec.europa.eu/proxybrowser/ProxyBrowser/; this includes validation reports on metadata records, services, and layers within services. -===== 4.3.3 Maintaining Registered Discovery Metadata records +==== 4.3.3 Maintaining Registered Discovery Metadata records To maintain previous discovery metadata registrations, first select [Data] then [Dataset Harvesting] from the Publisher tools sub-menu. @@ -805,7 +801,7 @@ at:{nbsp}http://location.defra.gov.uk/resources/contact-us/. the source. An updated record is one with the same file identifier, but a more recent metadata date. -====== *_Withdrawing Discovery Metadata records_* +==== *_Withdrawing Discovery Metadata records_* Once a discovery metadata record has been registered, the record should not be removed from the source location. If, in exceptional cases, you @@ -845,7 +841,7 @@ weblink and the unique Harvest GUID for the metadata record that you would like to withdraw, and email to the UK Location Helpdesk:{nbsp}[#cloak8b865acef497806498058eabbfa4f7da]#UKLocation.Helpdesk@defra.gsi.gov.uk# -====== *_Reinstating a withdrawn record_* +==== *_Reinstating a withdrawn record_* This should be an even rarer exception. If your harvest source contains a metadata record with the same file identifier as has been used before, @@ -853,7 +849,8 @@ but with a more recent metadata date, then when that record is harvested, it will be re-instated at data.gov.uk, and from there will appear in the Catalogue Publishing Service and the INSPIRE GeoPortal. -=== [#Met_Pub_Tec]####5. Metadata Publishing and Technology Choices +== 5. Metadata Publishing and Technology Choices +[#Met_Pub_Tec] There are a number of technical solution options that will help you create UK Location discovery metadata records and publish them to UK @@ -869,7 +866,8 @@ These options are outlined below. Using the information provided here, it is recommended that you then discuss your specific requirements with your IT department and/or system supplier. -==== *[#5.1]####5.1 UK Location Metadata Editor* +=== 5.1 UK Location Metadata Editor +[#5.1] UK Location includes its own Metadata Editor that can be used by Data Providers and Publishers to create compliant discovery metadata records. @@ -882,23 +880,25 @@ server-based installation of Geonetwork. For more information, to register for the on-line service or to download the configuration package, please visit the UK Location Resource Centre. -==== *[#5.2]####5.2 Geonetwork Publishing Solution* +=== 5.2 GeoNetwork Publishing Solution +[#5.2] -The use of Geonetwork as the basis for the UK Location Metadata Editor +The use of GeoNetwork as the basis for the UK Location Metadata Editor provides the option for Data Providers and Publishers to extend a local instance of the editor to provide cataloguing, change and release management and publishing (using CSW) services. This is all -out-of-the-box Geonetwork functionality.{nbsp} In addition, there are other -open source products that enable you to integrate Geonetwork with your +out-of-the-box GeoNetwork functionality.{nbsp} In addition, there are other +open source products that enable you to integrate GeoNetwork with your existing GIS and build a full data publishing environment, supporting the delivery of on-line services, e.g. View (WMS) and Download (WFS) services. -For more information on Geonetwork and links to other open source Geoweb +For more information on GeoNetwork and links to other open source Geoweb products, please visit:{nbsp}http://geonetwork-opensource.org/[http://geonetwork-opensource.org] -==== *[#5.3]####5.3 Third Party Solutions* +=== 5.3 Third Party Solutions +[#5.3] Most of the providers of Geospatial Information Systems provide metadata creation and publishing tools as part of their solution packages. @@ -907,7 +907,7 @@ UK Location have created a number of resources to help solution providers integrate the support for UK Location discovery metadata creation and publishing into these existing packages: -* https://www.agi.org.uk/gemini/40-gemini/1048-uk-gemini-encoding-guidance[UK +* link:1048-uk-gemini-encoding-guidance.html[UK GEMINI Encoding Guidance] * http://data.gov.uk/library/uk-gemini-schematron-schema-technical-guidance[UK GEMINI Schematron Schema and Guidance] From 2199d91e12b6cee2940716b8e38030882159faa2 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Tue, 28 Mar 2023 15:28:50 +0100 Subject: [PATCH 50/54] added additional pages to README --- docs/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/README.md b/docs/README.md index 7071369..d537715 100644 --- a/docs/README.md +++ b/docs/README.md @@ -14,6 +14,8 @@ The files below have been converted but have not been altered to work using the * [1054-operational-guide](https://archaeogeek.github.io/gemini-dev/1054-operational-guide.html) * [1055-uk-gemini-major-changes-since-1-0](https://archaeogeek.github.io/gemini-dev/1055-uk-gemini-major-changes-since-1-0.html) * [1056-glossary](https://archaeogeek.github.io/gemini-dev/1056-glossary.html) +* [1046-xml-element-order](https://archaeogeek.github.io/gemini-dev/1046-xml-element-order.html) +* [1250-element-summary](https://archaeogeek.github.io/gemini-dev/1250-element-summary.html) Links above this are to the GitHub pages published in https://archaeogeek.github.io/gemini-dev/ @@ -29,13 +31,13 @@ Where content differs between datasets and services, an [asciidoctor conditional To generate using the asciidoctor docker container, use the `-a` parameter, from the docs folder: ``` -docker run --rm -v $(pwd):/documents/ asciidoctor/docker-asciidoctor asciidoctor -a docinfo1 -a stylesheet=./assets/gemini.css -T templates -E slim -a variant-dataset *.adoc +docker run --rm -v $(pwd):/documents/ asciidoctor/docker-asciidoctor asciidoctor -a docinfo1 -a stylesheet=./assets/gemini.css -T templates -E slim -a variant-dataset *.adoc *.asciidoc ``` Then repeat for services: ``` -docker run --rm -v $(pwd):/documents/ asciidoctor/docker-asciidoctor asciidoctor -a docinfo1 -a stylesheet=./assets/gemini.css -T templates -E slim -a variant-service *.adoc +docker run --rm -v $(pwd):/documents/ asciidoctor/docker-asciidoctor asciidoctor -a docinfo1 -a stylesheet=./assets/gemini.css -T templates -E slim -a variant-service *.adoc *.asciidoc ``` ## Styling From 96e29d728f73176797bce7fb33cda381ae0552bc Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Fri, 14 Apr 2023 11:21:40 +0100 Subject: [PATCH 51/54] created a separate branch to hold version of docs that have agi URLs rather than archaeogeek --- docs/README.md | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/README.md b/docs/README.md index d537715..5de8b16 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,27 +1,27 @@ # Gemini documentation DEV branch -* [Services](https://archaeogeek.github.io/gemini-dev/1063-gemini-services.html) -* [Datasets](https://archaeogeek.github.io/gemini-dev/1062-gemini-datasets-and-data-series.html) +* [Services](https://agiorguk.github.io/gemini-dev/1063-gemini-services.html) +* [Datasets](https://agiorguk.github.io/gemini-dev/1062-gemini-datasets-and-data-series.html) The files below have been converted but have not been altered to work using the new workflow. Consequently internal links will go to the agi website and there may be other errors. -* [1037-uk-gemini-standard-and-inspire-implementing-rules](https://archaeogeek.github.io/gemini-dev/1037-uk-gemini-standard-and-inspire-implementing-rules.html) -* [1048-uk-gemini-encoding-guidance](https://archaeogeek.github.io/gemini-dev/1048-uk-gemini-encoding-guidance.html) -* [1049-metadata-guidelines-for-geospatial-data-resources-part-2](https://archaeogeek.github.io/gemini-dev/1049-metadata-guidelines-for-geospatial-data-resources-part-2.html) -* [1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources](https://archaeogeek.github.io/gemini-dev/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html) -* [1052-metadata-guidelines-for-geospatial-data-resources-part-1](https://archaeogeek.github.io/gemini-dev/1052-metadata-guidelines-for-geospatial-data-resources-part-1.html) -* [1053-common-metadata-errors-uk-location-discovery-metadata-service](https://archaeogeek.github.io/gemini-dev/1053-common-metadata-errors-uk-location-discovery-metadata-service.html) -* [1054-operational-guide](https://archaeogeek.github.io/gemini-dev/1054-operational-guide.html) -* [1055-uk-gemini-major-changes-since-1-0](https://archaeogeek.github.io/gemini-dev/1055-uk-gemini-major-changes-since-1-0.html) -* [1056-glossary](https://archaeogeek.github.io/gemini-dev/1056-glossary.html) -* [1046-xml-element-order](https://archaeogeek.github.io/gemini-dev/1046-xml-element-order.html) -* [1250-element-summary](https://archaeogeek.github.io/gemini-dev/1250-element-summary.html) - -Links above this are to the GitHub pages published in https://archaeogeek.github.io/gemini-dev/ +* [1037-uk-gemini-standard-and-inspire-implementing-rules](https://agiorguk.github.io/gemini-dev/1037-uk-gemini-standard-and-inspire-implementing-rules.html) +* [1048-uk-gemini-encoding-guidance](https://agiorguk.github.io/gemini-dev/1048-uk-gemini-encoding-guidance.html) +* [1049-metadata-guidelines-for-geospatial-data-resources-part-2](https://agiorguk.github.io/gemini-dev/1049-metadata-guidelines-for-geospatial-data-resources-part-2.html) +* [1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources](https://agiorguk.github.io/gemini-dev/1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html) +* [1052-metadata-guidelines-for-geospatial-data-resources-part-1](https://agiorguk.github.io/gemini-dev/1052-metadata-guidelines-for-geospatial-data-resources-part-1.html) +* [1053-common-metadata-errors-uk-location-discovery-metadata-service](https://agiorguk.github.io/gemini-dev/1053-common-metadata-errors-uk-location-discovery-metadata-service.html) +* [1054-operational-guide](https://agiorguk.github.io/gemini-dev/1054-operational-guide.html) +* [1055-uk-gemini-major-changes-since-1-0](https://agiorguk.github.io/gemini-dev/1055-uk-gemini-major-changes-since-1-0.html) +* [1056-glossary](https://agiorguk.github.io/gemini-dev/1056-glossary.html) +* [1046-xml-element-order](https://agiorguk.github.io/gemini-dev/1046-xml-element-order.html) +* [1250-element-summary](https://agiorguk.github.io/gemini-dev/1250-element-summary.html) + +Links above this are to the GitHub pages published in https://agiorguk.github.io/gemini-dev/ ## Services and Datasets workflow -* These files are generated from [include files](https://docs.asciidoctor.org/asciidoc/latest/directives/include/), one per element, in the [docs/partials](https://github.com/archaeogeek/gemini/tree/main/docs/partials) folder. +* These files are generated from [include files](https://docs.asciidoctor.org/asciidoc/latest/directives/include/), one per element, in the [docs/partials](https://github.com/agiorguk/gemini/tree/main/docs/partials) folder. * The xml snippets are in the docs/snippets folder. * The naming convention for the element files is {element name in lower case without spaces}.asciidoc * The naming convention for the xml snippets is {optional dataset or service prefix}-{element name in lower case without spaces}-{optional specific example}.xml From 3478431209dcc7b9b12e5e17ecc5b6100da7ca1c Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Fri, 14 Apr 2023 11:25:33 +0100 Subject: [PATCH 52/54] added corrected dev-build.yml --- .github/workflows/dev-build.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/dev-build.yml b/.github/workflows/dev-build.yml index 7154a87..276d46b 100644 --- a/.github/workflows/dev-build.yml +++ b/.github/workflows/dev-build.yml @@ -27,7 +27,7 @@ jobs: uses: peaceiris/actions-gh-pages@v3 with: personal_token: ${{ secrets.API_TOKEN_GITHUB }} - external_repository: archaeogeek/gemini-dev + external_repository: agiorguk/gemini-dev publish_branch: gh-pages publish_dir: ./docs/ enable_jekyll: true From 71fa9fef8ebe3b707c068c9f10708ee853867de5 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Thu, 6 Jul 2023 11:30:33 +0100 Subject: [PATCH 53/54] Added pages that were previously missing --- docs/1037-uk-gemini-introduction.asciidoc | 97 +++++++++++++ docs/1040-checklist-for-conformity.asciidoc | 33 +++++ ...-geospatial-data-resources-part-3.asciidoc | 131 ++++++++++++++++++ ...050-inspire-metadata-requirements.asciidoc | 111 +++++++++++++++ 4 files changed, 372 insertions(+) create mode 100644 docs/1037-uk-gemini-introduction.asciidoc create mode 100644 docs/1040-checklist-for-conformity.asciidoc create mode 100644 docs/1047-metadata-guidelines-for-geospatial-data-resources-part-3.asciidoc create mode 100644 docs/1050-inspire-metadata-requirements.asciidoc diff --git a/docs/1037-uk-gemini-introduction.asciidoc b/docs/1037-uk-gemini-introduction.asciidoc new file mode 100644 index 0000000..40f8df9 --- /dev/null +++ b/docs/1037-uk-gemini-introduction.asciidoc @@ -0,0 +1,97 @@ += UK-GEMINI Introduction +include::./includes/attributes.asciidoc[] + +This page describes the requirements and guidance for metadata +conforming to the UK standard known as UK GEMINI. There are several +entry points to the guidance: + +* link:1062-gemini-datasets-and-data-series[GEMINI +for datasets and series] +* link:1063-gemini-services[GEMINI for +services] +* Other material +** link:1052-metadata-guidelines-for-geospatial-data-resources-part-1.html[General +introduction to metadata for geographic information] +** link:1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html[General +introduction to GEMINI] +** link:1049-metadata-guidelines-for-geospatial-data-resources-part-2.html[General +guidance for GEMINI] +** link:048-uk-gemini-encoding-guidance.html[General +guidance on the XML encoding of GEMINI] +** https://github.com/AGIGemini/Schematron[Schematron rules for +validating GEMINI records (GitHub link)] +** link:40-gemini/1056-glossary.html[Glossary of terms] +** link:1047-metadata-guidelines-for-geospatial-data-resources-part-3.html[List +of references] +** link:053-common-metadata-errors-uk-location-discovery-metadata-service.html[Common +errors] + +Conformance to GEMINI should ensure conformance to the INSPIRE +Implementing Rules. UK specific guidance is provided. If you're +thinking, why GEMINI? Why not just use the INSPIRE Metadata guidance or +the ISO standards?{nbsp}https://www.agi.org.uk/why-uk-gemini/[Click here for +some +reasons.]{nbsp}The{nbsp}https://www.gov.uk/government/publications/recommended-open-standards-for-government/using-metadata-to-describe-data-shared-within-government[UK +Government Digital Service recommends using GEMINI when describing +geographic data]{nbsp}and it is the preferred way to catalogue geographic +data and services at Data.gov.uk. + +Both UK GEMINI and the INSPIRE Technical Guidance have been developed +from the International +Standard{nbsp}http://www.iso.org/iso/catalogue_detail?csnumber=26020[ISO +19115:2003]{nbsp}Geographic information - Metadata, with supplementary +material from ISO 19119:2005 Geographic information - Services. The XML +encoding follows ISO 19139:2007 Geographic information - Metadata - XML +encoding. This means that a GEMINI record is widely understood by +geospatial software and users internationally. + +Note that GEMINI (and the INSPIRE Guidance) are about metadata for +datasets, series, and services (collectively, 'resources'); not +everything in a GEMINI record can be assumed to be true individually for +each feature instance in the resource. The underlying ISO standards +(19115, 19139) do allow for metadata at the instance level, so the +elements could be used to describe metadata for that, but the guidance +here may not be appropriate and the resulting record could not be +validated as a GEMINI (or INSPIRE) record. + +Here is +a{nbsp}link:055-uk-gemini-major-changes-since-1-0.html[summary +of changes]{nbsp}from earlier versions. + +Here is +a{nbsp}link:1250-element-summary.html/[summary]{nbsp}of +the GEMINI elements (similar to Table 1 and Table 2 in GEMINI 2.2). + +Note: in GEMINI 2.3, the GEMINI Element number is called "GEMINI id"; +the actual numbers have not changed, where the same element was in +GEMINI 2.2. + +== Software that implements GEMINI 2.3 + +Several software implementations exist and are in use across the UK: + +* https://locationmde.data.gov.uk/[UK Location Metadata Editor]: online +editor owned by the Defra INSPIRE team +* https://geonetwork-opensource.org/[GeoNetwork Open +Source]{nbsp}-{nbsp}https://github.com/AstunTechnology/iso19139.gemini23[GEMINI +plugin]: server software in use in several government departments +* https://www.medin.org.uk/data/submit-metadata[MEDIN metadata editors]: +online and downloadable client editors for the MEDIN community profile + +== Feedback + +We realise that various aspects of the website could be improved and +that there may be some errors and inconsistencies in the content, +therefore we would like to hear from you if you spot any of these or you +would like to see improvements in terms of presentation and usability. + +Please send any comments +to{nbsp}mailto:gemini@agi.org.uk?subject=GEMINI2.3%20feedback[gemini@agi.org.uk] + +_Last updated: June 2021_ + +http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative +Commons Licence]] + +This work is licensed under +a{nbsp}http://creativecommons.org/licenses/by/4.0/[Creative Commons +Attribution 4.0 International License] \ No newline at end of file diff --git a/docs/1040-checklist-for-conformity.asciidoc b/docs/1040-checklist-for-conformity.asciidoc new file mode 100644 index 0000000..bb5f96a --- /dev/null +++ b/docs/1040-checklist-for-conformity.asciidoc @@ -0,0 +1,33 @@ += Checklist for Confirmity +include::./includes/attributes.asciidoc[] + +Return +to link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI +2.3 home page] + +Metadata for a data resource shall be conformant with UK GEMINI if: + +{empty}1. It contains entries for all the mandatory metadata elements as +defined in this Standard; + +{empty}2. It contains entries for all those conditional elements where +the condition for inclusion holds; + +{empty}3. Each element included in the metadata contains a valid value +from the prescribed domain; + +{empty}4. The number of occurrences of each element does not exceed the +maximum number specified; + +{empty}5. Each entry is in the prescribed format; + +{empty}6. The metadata represents the state of the data resource on the +specified date. + +_Last updated: December 2012_ + +http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative +Commons Licence]] + +This work is licensed under +a{nbsp}http://creativecommons.org/licenses/by/4.0/[Creative Commons +Attribution 4.0 International License] \ No newline at end of file diff --git a/docs/1047-metadata-guidelines-for-geospatial-data-resources-part-3.asciidoc b/docs/1047-metadata-guidelines-for-geospatial-data-resources-part-3.asciidoc new file mode 100644 index 0000000..1923086 --- /dev/null +++ b/docs/1047-metadata-guidelines-for-geospatial-data-resources-part-3.asciidoc @@ -0,0 +1,131 @@ += Metadata Guidelines for Geospatial Data Resources Part 3 +include::./includes/attributes.asciidoc[] + +Return +to link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI +2.3 home page] + +[cols=",",] +|=== +|Reference Number |Author, Title, Version, Date of publication + +| 1 |AGI, +“https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1[Metadata +Guidelines for Geospatial Data Resources – Part 1, Introduction]”, +September 2010 + +| 2 |AGI, +“https://www.agi.org.uk/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2[Metadata +Guidelines for Geospatial Data Resources - Part 2, Creating metadata +using UK GEMINI2 (v2.1)]”, April 2015 + +| 3 |AGI, +"https://www.agi.org.uk/wp-content/uploads/2020/12/METADATAGUIDELINESPART32015-04.pdf[Metadata +Guidelines for Geospatial Data Resources in the UK Part 3 – Metadata +quality]" , April 2015 + +| 4 |AGI, +“https://www.agi.org.uk/wp-content/uploads/2020/12/GEMINI2.2.pdf[UK +GEMINI, Specification for discovery metadata for geospatial data +resources, v2.2]”, December 2012, https://www.agi.org.uk/uk-gemini/ + +| 5 |Canonical XML, Version 1.1, 2008-05-02, +W3C http://www.w3.org/TR/xml-c14n + +| 6 |EC “Commission Regulation (EC) No 976/2009 of 19 October 2009 +implementing Directive 2007/2/EC of the European Parliament and of the +Council as regards the +Network Services” https://inspire.ec.europa.eu/network-services/ + +| 7 |EC, “Commission Regulation (EC) No. 1205/2008 of 3 December 2008 +Implementing Directive 2007/2/EC of the European Parliament and of the +Council as regards metadata”, December 2008. Accessed +through http://inspire.ec.europa.eu/metadata + +| 8 |EC, “Directive 2007/2/EC of the European Parliament and of the +Council of 14 March 2007 establishing an Infrastructure for Spatial +Information in the European Community (INSPIRE)” 14.03.2007. Accessed +through http://inspire.ec.europa.eu/inspire-legislation/ + +| 9 |EC, “Technical Guidance for implementing dataset and service +metadata based on ISO/TS 19139:2007”, (Version 2.0.1)  2017-03-02, +INSPIRE Maintenance and Implementation Group +(MIG) http://inspire.ec.europa.eu/id/document/tg/metadata-iso19139/2.0 + +|10 |e-Government Metadata Standard (e-GMS). Cabinet Office e-Government +Unit. (see http://www.gov.uk/government/organisations/cabinet-office) + +|11 |Elliotte Rusty Harold and W. Scott Means, "XML in a Nutshell, +Second Edition", June 2002 + +|12 |EPSG Geodetic Parameter Registry, Version +7.5.6, http://www.epsg-registry.org/ + +|13 |Federal Geographic Data Committee "Content Standard for Digital +Geospatial Metadata" Version 2 - 1998. +(see http://www.fgdc.gov/standards/standards_publications[www.fgdc.gov/standards/standards_publications]) + +|14 |INSPIRE  Metadata Regulation 03.12.2008 +(see http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32008R1205:EN:NOT) + +|15 |Integrated Public Sector Vocabulary (IPSV) from the esd-toolkit, +at http://id.esd.org.uk/list/subjects + +|16 |EC, "Technical Guidance for the implementation of INSPIRE View +Services", Version 3.11, +2013-04-04 https://inspire.ec.europa.eu/documents/technical-guidance-implementation-inspire-view-services-1 + +|17 |ISO 15836: 2003 Dublin Core metadata element set + +|18 |ISO 19115:2003 Geographic information – Metadata, published by ISO +(and national standards bodies) + +|19 |ISO 19139:2007 Geographic information – Metadata – XML schema +implementation – published by ISO (and national standards bodies) + +|20 |ISO 8402:1994 Quality management and quality assurance - Vocabulary + +|21 |https://www.iso.org/iso-8601-date-and-time-format.html[ISO +8601]:2004 Data elements and interchange formats – Information +interchange – Representation of dates and times. + +|22 |Ordnance Survey Linked Data, https://data.os.uk/ + +|23 |UK GEMINI2 Standard Version 2.1.AGI August 2010. + +|24 |UK Location, +"https://www.agi.org.uk/40-gemini/1054-operational-guide[Discovery +Metadata Service, Operational Guide]", Edition 2-2, February 2013 + +|25 |UK Location, +“https://www.google.co.uk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0ahUKEwj6usbW17TZAhXKKewKHQYDD_gQFghIMAI&url=https%3A%2F%2Fdata.gov.uk%2Fsites%2Fdefault%2Ffiles%2FCoordinate%2520Reference%2520Systems%2520for%2520UK%2520Location%2520-%2520INSPIRE%2520View%2520Service%2520v1.1_10.pdf&usg=AOvVaw1j3l9XLXLzK6RcuOLDNVPa[Coordinate +Reference Systems for UK Location]”, v1.1, December 2012 + +|26 |UK Location, “Discovery Metadata Service Collection Interface +Specification”, Versions 2.2, Feb +2013 https://data.gov.uk/sites/default/files/DMS%20Operational%20Guide%202-2_10.pdf + +|27 |UK Location, Getting started - series of +guides, https://data.gov.uk/location/guidance_and_tools + +|28 |UK Location, +“https://data.gov.uk/sites/default/files/UK%20GEMINI%20Encoding%20Guidance%201.4_10.pdf[UK +GEMINI Encoding Guidance, Version 1.4]”, February 2013 + +|29 |UK Location, “UK GEMINI Schematron Schema Guidance”, Version 1.3, +January +2013 http://data.gov.uk/library/uk-gemini-schematron-schema-technical-guidance + +|30 |UK Location, “UK GEMINI Schematron Schema”, Version 1.3, January +2013 + +|31 |User Guide: Administrators and Editors, version 1.5, data.gov.uk +|=== + +_Last updated: February 2018_ + +http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative +Commons Licence]] + +This work is licensed under +a{nbsp}http://creativecommons.org/licenses/by/4.0/[Creative Commons +Attribution 4.0 International License] \ No newline at end of file diff --git a/docs/1050-inspire-metadata-requirements.asciidoc b/docs/1050-inspire-metadata-requirements.asciidoc new file mode 100644 index 0000000..7c44e6e --- /dev/null +++ b/docs/1050-inspire-metadata-requirements.asciidoc @@ -0,0 +1,111 @@ += INSPIRE Metadata Requirements +include::./includes/attributes.asciidoc[] + +The INSPIRE Implementing Rules for Metadata requires that a set of +metadata elements shall be provided. These are grouped in the following +categories: + +. Identification +. Classification of spatial and data services +. Keyword +. Geographic location +. Temporal reference +. Quality and validity +. Conformity +. Constraint related to access and use +. Organisations responsible for the establishment, management, +maintenance and distribution of the resource +. Metadata on metadata + +These are realized as a set of elements shown below. These may be +implemented in various ways including ISO 19115 and Dublin Core. UK +GEMINI is an ISO 19115 implementation. + +[width="100%",cols="20%,20%,20%,20%,20%",] +|=== +|*  Metadata category* |*INSPIRE Reference* |*  Metadata element* +|*Multiplicity^†^* |*  Condition (where applicable)* + +|Identification |1.1 |Resource title |1 | + +| |1.2 |Resource abstract |1 | + +| |1.3 |Resource type |1 | + +| |1.4 |Resource locator |0..* |Mandatory if a URL is available to +obtain more information on the resource, and/or access related services, +or if linkage to the service is available + +| |1.5 |Unique resource identifier |1..* |Not required for services + +| |1.6 |Coupled resource |0..* |Only for services, where it is mandatory +if linkage to data sets on which the service operates are available + +| |1.7 |Resource language |0..* |Mandatory if the resource includes +textual information. Not required for services + +|Classification of spatial and data services |2.1 |Topic category |1..* +|Not required for services + +| |2.2 |Spatial data service type |1 |Only for services + +|Keyword |3.1 |Keyword value |1..* | + +| |3.2 |Originating controlled vocabulary |0..* |Where a vocabulary is +used as the source of the keywords + +|Geographic location |4.1 |Geographic bounding box |1..* |Mandatory for +datasets and dataset series, and for services with an explicit +geographic extent + +|Temporal reference |5.1 |Temporal extent |1..* |At least one of these +must be given. + +| | 5.2 |Date of publication | | + +| | 5.3 |Date of last revision | | + +| | 5.4 |Date of creation | | + +|Quality and validity |6.1 |Lineage |1 |Not required for services + +| |6.2 |Spatial resolution |0..* |Mandatory for datasets and dataset +series if an equivalent scale or a resolution distance can be specified, +and for services where there is a restriction on the spatial resolution +for the service. + +|Conformity |7.1 |Specification |1..* | + +| | 7.2 |Degree |1..* | + +|Constraint related to access and use |8.1 |Conditions applying to +access and use |1..* | + +| |8.2 |Limitations on public access |1..* | + +|Organisations responsible for the establishment, management, +maintenance and distribution of the resource |9.1 |Responsible party +|1..* | + +| | 9.2 |Responsible party role |1..* | + +|Metadata on metadata |10.1 |Metadata point of contact |1..* | + +| |10.2 |Metadata date |1 | + +| |10.3 |Metadata language |1 | + +a| +Notes + +**^† ^**1 indicates mandatory, single valued, 1 ..* indicates mandatory, +multi-valued, 0..* indicates optional multi-valued + +| | | | +|=== + +http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative +Commons Licence]] + +This work is licensed under +a{nbsp}http://creativecommons.org/licenses/by/4.0/[Creative Commons +Attribution 4.0 International License] \ No newline at end of file From 4ca608236965719aad7a9456a59159ddf8f13922 Mon Sep 17 00:00:00 2001 From: archaeogeek Date: Thu, 6 Jul 2023 13:42:08 +0100 Subject: [PATCH 54/54] Finished formatting guidelines part 3 and corrected typo in conformity --- docs/1040-checklist-for-conformity.asciidoc | 2 +- ...-geospatial-data-resources-part-3.asciidoc | 157 ++++++------------ 2 files changed, 54 insertions(+), 105 deletions(-) diff --git a/docs/1040-checklist-for-conformity.asciidoc b/docs/1040-checklist-for-conformity.asciidoc index bb5f96a..83ef6ed 100644 --- a/docs/1040-checklist-for-conformity.asciidoc +++ b/docs/1040-checklist-for-conformity.asciidoc @@ -1,4 +1,4 @@ -= Checklist for Confirmity += Checklist for Conformity include::./includes/attributes.asciidoc[] Return diff --git a/docs/1047-metadata-guidelines-for-geospatial-data-resources-part-3.asciidoc b/docs/1047-metadata-guidelines-for-geospatial-data-resources-part-3.asciidoc index 1923086..7e74a0e 100644 --- a/docs/1047-metadata-guidelines-for-geospatial-data-resources-part-3.asciidoc +++ b/docs/1047-metadata-guidelines-for-geospatial-data-resources-part-3.asciidoc @@ -5,121 +5,70 @@ Return to link:1037-uk-gemini-standard-and-inspire-implementing-rules.html[GEMINI 2.3 home page] -[cols=",",] +[%header,cols="1,.^9"] |=== |Reference Number |Author, Title, Version, Date of publication -| 1 |AGI, -“https://www.agi.org.uk/40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1[Metadata -Guidelines for Geospatial Data Resources – Part 1, Introduction]”, +| 1|AGI, +link:40-gemini/1052-metadata-guidelines-for-geospatial-data-resources-part-1.html[Metadata +Guidelines for Geospatial Data Resources – Part 1, Introduction], September 2010 - -| 2 |AGI, -“https://www.agi.org.uk/40-gemini/1049-metadata-guidelines-for-geospatial-data-resources-part-2[Metadata +| 2|AGI, +link:1049-metadata-guidelines-for-geospatial-data-resources-part-2.html[Metadata Guidelines for Geospatial Data Resources - Part 2, Creating metadata -using UK GEMINI2 (v2.1)]”, April 2015 - -| 3 |AGI, -"https://www.agi.org.uk/wp-content/uploads/2020/12/METADATAGUIDELINESPART32015-04.pdf[Metadata +using UK GEMINI2 (v2.1)], April 2015 +| 3|AGI, +https://www.agi.org.uk/wp-content/uploads/2020/12/METADATAGUIDELINESPART32015-04.pdf[Metadata Guidelines for Geospatial Data Resources in the UK Part 3 – Metadata -quality]" , April 2015 - -| 4 |AGI, -“https://www.agi.org.uk/wp-content/uploads/2020/12/GEMINI2.2.pdf[UK +quality] , April 2015 +| 4|AGI, +https://www.agi.org.uk/wp-content/uploads/2020/12/GEMINI2.2.pdf[UK GEMINI, Specification for discovery metadata for geospatial data -resources, v2.2]”, December 2012, https://www.agi.org.uk/uk-gemini/ - -| 5 |Canonical XML, Version 1.1, 2008-05-02, -W3C http://www.w3.org/TR/xml-c14n - -| 6 |EC “Commission Regulation (EC) No 976/2009 of 19 October 2009 +resources, v2.2], December 2012 +| 5|W3C, http://www.w3.org/TR/xml-c14n[Canonical XML, Version 1.1], May 2008 +| 6|EC, https://inspire.ec.europa.eu/network-services/[Commission Regulation (EC) No 976/2009 of 19 October 2009 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards the -Network Services” https://inspire.ec.europa.eu/network-services/ - -| 7 |EC, “Commission Regulation (EC) No. 1205/2008 of 3 December 2008 +Network Services], October 2009 +| 7|EC, http://inspire.ec.europa.eu/metadata[Commission Regulation (EC) No. 1205/2008 of 3 December 2008 Implementing Directive 2007/2/EC of the European Parliament and of the -Council as regards metadata”, December 2008. Accessed -through http://inspire.ec.europa.eu/metadata - -| 8 |EC, “Directive 2007/2/EC of the European Parliament and of the +Council as regards metadata], December 2008 +| 8|EC, http://inspire.ec.europa.eu/inspire-legislation/[Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial -Information in the European Community (INSPIRE)” 14.03.2007. Accessed -through http://inspire.ec.europa.eu/inspire-legislation/ - -| 9 |EC, “Technical Guidance for implementing dataset and service -metadata based on ISO/TS 19139:2007”, (Version 2.0.1)  2017-03-02, -INSPIRE Maintenance and Implementation Group -(MIG) http://inspire.ec.europa.eu/id/document/tg/metadata-iso19139/2.0 - -|10 |e-Government Metadata Standard (e-GMS). Cabinet Office e-Government -Unit. (see http://www.gov.uk/government/organisations/cabinet-office) - -|11 |Elliotte Rusty Harold and W. Scott Means, "XML in a Nutshell, -Second Edition", June 2002 - -|12 |EPSG Geodetic Parameter Registry, Version -7.5.6, http://www.epsg-registry.org/ - -|13 |Federal Geographic Data Committee "Content Standard for Digital -Geospatial Metadata" Version 2 - 1998. -(see http://www.fgdc.gov/standards/standards_publications[www.fgdc.gov/standards/standards_publications]) - -|14 |INSPIRE  Metadata Regulation 03.12.2008 -(see http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32008R1205:EN:NOT) - -|15 |Integrated Public Sector Vocabulary (IPSV) from the esd-toolkit, -at http://id.esd.org.uk/list/subjects - -|16 |EC, "Technical Guidance for the implementation of INSPIRE View -Services", Version 3.11, -2013-04-04 https://inspire.ec.europa.eu/documents/technical-guidance-implementation-inspire-view-services-1 - -|17 |ISO 15836: 2003 Dublin Core metadata element set - -|18 |ISO 19115:2003 Geographic information – Metadata, published by ISO -(and national standards bodies) - -|19 |ISO 19139:2007 Geographic information – Metadata – XML schema -implementation – published by ISO (and national standards bodies) - -|20 |ISO 8402:1994 Quality management and quality assurance - Vocabulary - -|21 |https://www.iso.org/iso-8601-date-and-time-format.html[ISO -8601]:2004 Data elements and interchange formats – Information -interchange – Representation of dates and times. - -|22 |Ordnance Survey Linked Data, https://data.os.uk/ - -|23 |UK GEMINI2 Standard Version 2.1.AGI August 2010. - -|24 |UK Location, -"https://www.agi.org.uk/40-gemini/1054-operational-guide[Discovery -Metadata Service, Operational Guide]", Edition 2-2, February 2013 - -|25 |UK Location, -“https://www.google.co.uk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0ahUKEwj6usbW17TZAhXKKewKHQYDD_gQFghIMAI&url=https%3A%2F%2Fdata.gov.uk%2Fsites%2Fdefault%2Ffiles%2FCoordinate%2520Reference%2520Systems%2520for%2520UK%2520Location%2520-%2520INSPIRE%2520View%2520Service%2520v1.1_10.pdf&usg=AOvVaw1j3l9XLXLzK6RcuOLDNVPa[Coordinate -Reference Systems for UK Location]”, v1.1, December 2012 - -|26 |UK Location, “Discovery Metadata Service Collection Interface -Specification”, Versions 2.2, Feb -2013 https://data.gov.uk/sites/default/files/DMS%20Operational%20Guide%202-2_10.pdf - -|27 |UK Location, Getting started - series of -guides, https://data.gov.uk/location/guidance_and_tools - -|28 |UK Location, -“https://data.gov.uk/sites/default/files/UK%20GEMINI%20Encoding%20Guidance%201.4_10.pdf[UK -GEMINI Encoding Guidance, Version 1.4]”, February 2013 - -|29 |UK Location, “UK GEMINI Schematron Schema Guidance”, Version 1.3, -January -2013 http://data.gov.uk/library/uk-gemini-schematron-schema-technical-guidance - -|30 |UK Location, “UK GEMINI Schematron Schema”, Version 1.3, January -2013 - -|31 |User Guide: Administrators and Editors, version 1.5, data.gov.uk +Information in the European Community (INSPIRE)], March 2007 +| 9|EC, http://inspire.ec.europa.eu/id/document/tg/metadata-iso19139/2.0[Technical Guidance for implementing dataset and service +metadata based on ISO/TS 19139:2007 (Version 2.0.1), INSPIRE Maintenance and Implementation Group +(MIG)], March 2017 +|10|e-Government Metadata Standard (e-GMS). Cabinet Office e-Government +Unit. (see http://www.gov.uk/government/organisations/cabinet-office, suggest https://cdn.nationalarchives.gov.uk/documents/information-management/egms-metadata-standard.pdf) +|11|Elliotte Rusty Harold and W. Scott Means, XML in a Nutshell, +Second Edition, June 2002 +|12|EPSG, http://www.epsg-registry.org/[Geodetic Parameter Registry, Version +7.5.6] +|13|Federal Geographic Data Committee, http://www.fgdc.gov/standards/standards_publications[Content Standard for Digital +Geospatial Metadata, Version 2], 1998 +|14|EU, http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32008R1205:EN:NOT[Commission Regulation (EC) No 1205/2008 of 3 December 2008 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata], December 2008 +|15|ESD, http://id.esd.org.uk/list/subjects[Integrated Public Sector Vocabulary (IPSV)] +|16|EC, https://inspire.ec.europa.eu/documents/technical-guidance-implementation-inspire-view-services-1[Technical Guidance for the implementation of INSPIRE View +Services, Version 3.11], April 2013 +|17|ISO (and national standards bodies), https://www.iso.org/standard/37629.html[ISO 15836: 2003 Dublin Core metadata element set], November 2003 +|18|ISO (and national standards bodies), https://www.iso.org/standard/26020.html[ISO 19115:2003 Geographic information – Metadata], May 2003 +|19|ISO (and national standards bodies), https://www.iso.org/standard/32557.html[ISO 19139:2007 Geographic information – Metadata – XML schema +implementation], April 2007 +|20|ISO (and national standards bodies), https://www.iso.org/standard/20115.html[ISO 8402:1994 Quality management and quality assurance - Vocabulary], March 1994 +|21|ISO (and national standards bodies), https://www.iso.org/standard/40874.html[ISO 8601:2004 Data elements and interchange formats – Information interchange – Representation of dates and times], December 2012 +|22|Ordnance Survey, https://data.ordnancesurvey.co.uk/[Ordnance Survey Linked Data Platform] +|23|AGI, https://www.agi.org.uk/wp-content/uploads/2020/11/GEMINI2.2.pdf[UK GEMINI2 Standard Version 2.2], August 2010 +|24|UK Location, link:1054-operational-guide.html[Discovery Metadata Service, Operational Guide], Edition 2-2, February 2013 +|25|UK Location, https://data.gov.uk/sites/default/files/Coordinate Reference Systems for UK Location - INSPIRE View Servicev1.1_10.pdf[Coordinate Reference Systems for UK Location], December 2012 +|26|UK Location, https://data.gov.uk/sites/default/files/DMS%20Operational%20Guide%202-2_10.pdf[Discovery Metadata Service Collection Interface +Specification], February 2013 +|27|UK Location, https://data.gov.uk/location/guidance_and_tools[Getting started - series of guides] +|28|UK Location, https://data.gov.uk/sites/default/files/UK%20GEMINI%20Encoding%20Guidance%201.4_10.pdf[UK +GEMINI Encoding Guidance, Version 1.4], February 2013 +|29|UK Location, http://data.gov.uk/library/uk-gemini-schematron-schema-technical-guidance[UK GEMINI Schematron Schema Guidance], January 2013 +|30|UK Location, UK GEMINI Schematron Schema Version 1.3, January 2013 +|31|UK Location, User Guide: Administrators and Editors |=== _Last updated: February 2018_