Merge pull request #191 from agiorguk/dev

Update 1055-uk-gemini-major-changes-since-1-0.asciidoc

Author: archaeogeek

docs/1048-uk-gemini-encoding-guidance.asciidoc

@@ -360,7 +360,7 @@ increasing precision:
 * yyyy-MM-ddThh:mm:ss (e.g. 1995-01-25T12:01:55)
 
 The ISO 8601 encoding also allows negative dates to represent BC.
-However, due to the limitations of negative dates in the Gregorian calendar, these should only be used with care. Given the uses that these data types are put to in GEMINI, this is not expected to be an issue
+However, due to the limitations of negative dates in the Gregorian calendar, these should only be used with care. Given the uses that these data types are put to in GEMINI, this is not expected to be an issue.
 
 The GEMINI2 standard states that temporal extents may be given with as
 coarse a granularity as century (e.g. yy or 19). However, unfortunately

docs/1052-metadata-guidelines-for-geospatial-data-resources-part-1.asciidoc

@@ -3,18 +3,18 @@ include::./includes/attributes.asciidoc[]
 
 *July 2018*
 
-Return to link:1037-uk-gemini-introduction[GEMINI 2.3 home page]
+Return to link:1037-uk-gemini-introduction.html[GEMINI 2.3 home page]
 
 :sectnums:
 :sectnumlevels: 3
 
 == Preface
 
-These guidelines cover the basics of metadata for geospatial data
-resources and services. They are intended for general use in the UK
+These guidelines cover the basics of metadata for geospatial 
+resources. They are intended for general use in the UK
 geographic information environment and serve as a preamble to the more
 detailed and specific guidelines 
-link:1049-metadata-guidelines-for-geospatial-data-resources-part-2[Metadata Guidelines for Geospatial Data Resources - Part 2].
+link:1049-metadata-guidelines-for-geospatial-data-resources-part-2.html[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
@@ -43,16 +43,16 @@ to{nbsp}gemini@agi.org.uk.
 == Introduction
 
 These guidelines for the creation, maintenance and quality management of
-metadata for geospatial data resources, including the services which
-provide access to the resources, provide a general introduction to the
+metadata for geospatial resources, including the data and the services which
+provide access to that data, provide a general introduction to the
 principles and concepts of metadata. They are aimed at data managers and
 creators of metadata, providers of metadata services and general data
 users.
 
-The data resources may be datasets, dataset series, services delivering
+The 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. The data resources may be graphical or textual (tabular or free
+area. The resources may be graphical or textual (tabular or free
 text), hardcopy or digital. Geospatial data is data containing a
 positional or locational element relative to the Earth. Many data
 resources that at first sight do not appear to be geospatial
@@ -63,7 +63,7 @@ form of coordinates, for example in latitude and longitude, or
 references to geographic place names, for example street data.
 
 Metadata is data about data. It provides additional information about
-the data resource, to enable it to be better understood and used to good
+the resource, to enable it to be better understood and used to good
 effect.
 
 In an organisation, metadata is required for both internal and external
@@ -80,8 +80,8 @@ of the data and may find that they cannot trust results generated using
 this data.
 
 Externally, metadata is required to provide information about an
-organisation’s data holdings and data access services. Data resources
-are a major national asset, and information of what data resources exist
+organisation’s data holdings and data access services. These resources
+are a major national asset, and information of what resources exist
 within different organisations, particularly in the public sector, is
 required to improve efficiencies and reduce data duplication. Data
 catalogues and data discovery services enable potential users to find,
@@ -91,7 +91,7 @@ supplied by metadata, to process and interpret it.
 
 The requirements for metadata for internal and external purposes are
 different. Metadata for external purposes will be at a general level,
-providing basic information about the data resources. Having this in a
+providing basic information about the resources. Having this in a
 standardised form enables metadata services to be set up for widespread
 use. Standardisation of this aspect is thus important, and most metadata
 standards are designed for this purpose. Metadata for internal purposes
@@ -132,7 +132,7 @@ Infrastructure (SDI). They are used within organisations as part of the
 information management facilities, and on a national basis for discovery
 purposes. Essentially, they work on the basis of a user defining
 parameters such as Topic Category and Extent, to carry out a search to
-discover data resources that might be suitable and return information
+discover resources that might be suitable and return information
 about their source, content and availability.
 
 === Metadata as a business process
@@ -157,15 +157,15 @@ Process model for metadata creation, maintenance, service provision and
 use,width=1114,height=483]
 
 If the main purpose of creating metadata is to document and enable
-discovery of an organisation’s own data resources and the exposure of
+discovery of an organisation’s own resources and the exposure of
 all or part of that metadata to some external service is secondary, then
 there will be far greater chance of support and resources for metadata
 in the business.
 
 However, if metadata is seen as an additional activity to support some
 external service, it is likely to be ignored or forgotten. When it is
 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
+knowledge of the resource and no interest in the quality of the
 metadata.
 
 === Metadata roles
@@ -188,14 +188,14 @@ metadata creators.
 
 * *Service user{nbsp}*- the consumer of the service who selects the search
 criteria matching their requirements, performs the searches and finds
-data resources meeting their requirements or, at least, meriting further
+resources meeting their requirements or, at least, meriting further
 investigation.
 
 === Metadata standards
 
 There are many metadata standards in existence. These have been produced
 at different times by different bodies for different purposes. The main
-ones that are relevant to geospatial data resources are:
+ones that are relevant to geospatial resources are:
 
 * **ISO 19115**
 
@@ -258,7 +258,7 @@ also relevant to other metadata specifications.
 
 The aim of a discovery metadata such as specified in UK GEMINI2 is to
 define metadata in a form that provides easily understood information
-for potential users of the data resource, and is searchable in a
+for potential users of the resource, and is searchable in a
 computerised discovery metadata service such as
 the{nbsp}http://inspire-geoportal.ec.europa.eu/[INSPIRE Geoportal]. It is
 difficult to carry out searches on free text, since the same thing can
@@ -306,8 +306,8 @@ not just as Grid References. They can take the form of the name or
 identifier of a geographic location which can be described in a
 gazetteer. Examples are property addresses, postcodes and census areas.
 These spatial references are a key means of searching the data by
-location, not only within the data resource, but also positioning the
-data resource in the world (e.g. data for Scotland). A consistent set of
+location, not only within the resource, but also positioning the
+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.
 
@@ -322,7 +322,7 @@ different places. Here it is recommended that the extended format
 defined in https://www.iso.org/iso-8601-date-and-time-format.html[ISO
 8601] (YYYY-MM-DD) is used.
 
-== Data resources in scope
+== Resources in scope
 
 === What is stated in UK GEMINI2
 
@@ -334,10 +334,10 @@ GEMINI2,
 (ii) the applicability of UK GEMINI2 and
 
 (iii) how to find an appropriate level for the individual
-documentation of data resources.
+documentation of resources.
 
 UK GEMINI2 “specifies a set of metadata elements for describing
-geographic data resources” but provides no other information about what
+geographic resources” but provides no other information about what
 types of data or services are in or out of scope.
 
 In practice it can be difficult to decide what data or service resources
@@ -348,10 +348,10 @@ 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.
 
-=== Characteristics of data resources in scope
+=== Characteristics of 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
+in the Introduction. As is emphasised there, many resources that at
 first sight do not appear to be geospatial nevertheless have a
 geospatial component. They are geographically constrained in some way,
 in that the data only refers to certain areas or locations on the
@@ -371,14 +371,14 @@ All these types can be documented using 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
+documenting resources within the United Kingdom that conforms with
 the INSPIRE Metadata Implementing Rules.
 
-=== Levels of data resources for documentation
+=== Levels of resources for documentation
 
 There are no absolute rules for deciding on an appropriate level for the
-individual documentation of a data resource. The overriding
-consideration is that the data resource has been documented with
+individual documentation of a resource. The overriding
+consideration is that the resource has been documented with
 sufficient granularity to yield a useful result if discovered using a
 metadata service. Too coarse a granularity will result in too
 generalised a result, too fine a granularity is likely to overwhelm the
@@ -388,17 +388,17 @@ geographical extent, temporal extent or subject.
 There are some questions that can be posed which may help the metadata
 creator to find an answer.
 
-* How is the data resource used and how is it made available? Is it a
+* How is the resource used and how is it made available? Is it a
 product, dataset, document that may be used and combined with other
-datasets or is it an integral part of a larger data resource?
-* Has the data resource been captured using a single data specification?
-Are there other data resources captured using the same data
+datasets or is it an integral part of a larger resource?
+* Has the data been captured using a single data specification?
+Are there other resources captured using the same data
 specification?
-* Is the data resource part of a time series? Is the data resource
+* Is the data part of a time series? Is the data
 covering the same extent periodically updated to the same specification?
-* Does the data resource relate to, or reference, a continuous area or
+* Does the resource relate to, or reference, a continuous area or
 contiguous areas, or does it reference specific locations?
-* Does the data resource relate to one or many subjects, topics or
+* Does the resource relate to one or many subjects, topics or
 themes?
 
 An approach to resolving these questions is found in the{nbsp}table below.
@@ -417,7 +417,7 @@ lying behind the single entry.
 
 [width="100%",cols="34%,33%,33%",]
 |===
-|*Nature of data resource* |*How to document* |*Examples*
+|*Nature of resource* |*How to document* |*Examples*
 
 a|
 *Stand-alone product or identifiable dataset or document*
@@ -430,9 +430,9 @@ Individually with one metadata record.
 
 *Notes:*
 
-* If the data resource references a number of separate locations then at
+* If the resource references a number of separate locations then at
 least ensure that this is reflected in a multiple entry for Extent.
-* If the data resource covers a number of topics or subjects then ensure
+* If the resource covers a number of topics or subjects then ensure
 that each of these is reflected, using multiple entries for Topic
 category and Keyword.
 
@@ -457,7 +457,7 @@ Together with one metadata record.
 * If the time series is not regular with periodic updates, consider
 documenting by individual dates or durations referring to particular
 periods of update.
-* If the data resource covers a number of topics or subjects then ensure
+* If the resource covers a number of topics or subjects then ensure
 that each of these is reflected, using multiple entries for Topic
 category and Keyword.
 
@@ -482,7 +482,7 @@ Each location or area individually with a metadata record.
 * If the time series is not regular with periodic updates, consider
 documenting by individual dates or durations referring to a particular
 period of update.
-* If the data resource covers a number of topics or subjects then ensure
+* If the resource covers a number of topics or subjects then ensure
 that each of these is reflected, using multiple entries for Topic
 category and Keyword.
 * If it is not feasible to individually document each location or
@@ -502,7 +502,7 @@ if feasible.
 
 |===
 
-_Last updated: July 2018_
+_Last updated: December 2025 ('data resource' generally to 'resource')_
 
 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]