Merge pull request #188 from agiorguk/dev

Updates to dev branch

Author: archaeogeek

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

@@ -360,8 +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, gco:Date and gco:DateTime XML elements do not accept negative
-values.
+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
@@ -1111,7 +1110,7 @@ with null values with the nil reason being missing (Figure 25).
 
 link:1063-gemini-services.html[Services]
 
-_Last technical update: March 2019_
+_Last technical update: {docdate}_
 
 http://creativecommons.org/licenses/by/4.0/[image:https://i.creativecommons.org/l/by/4.0/88x31.png[Creative
 Commons Licence]] 

docs/partials/boundingbox.asciidoc

@@ -59,7 +59,10 @@ resource, and determine the coordinates of the boundaries. It may be
 necessary to convert from another coordinate system (e.g. National Grid)
 into lat/long.
 . Only approximate values are required, sufficient to identify the
-extent on a global basis. The bounding box is implicitly in WGS84.
+extent on a global basis. Following the lead of the INSPIRE technical guidance, 
+use WGS84 to define the bounding box.
+. More precise spatial extents can also be provided, such as polygon extents, using the
+encoding options within the ISO 19115 EX_Extent.EX_GeographicExtent element. 
 
 |Comment |The bounding box will often cover areas that are not directly
 related to the area covered by the resource.

docs/partials/extent.asciidoc

@@ -39,6 +39,7 @@ provided.
 Britain if it only covers England and Wales).
 
 |Comment |
+. This element should be used in preference to a keyword of type "place".
 
 |Examples a|
 * England
@@ -50,6 +51,8 @@ linked data as a gazetteer
 Authority, using GDS "Local authorities in England" as a controlled list
 * http://vocab.nerc.ac.uk/collection/C64/current/5/, Irish Sea, in the
 NERC Vocabulary "C64, United Kingdom Charting Progress 2 sea regions"
+* http://statistics.data.gov.uk/id/statistical-geography/E09000011, Royal 
+Borough of Greenwich ONS Output Area
 
 |Revision date |August 2010
 |===

docs/partials/resourceidentifier.asciidoc

@@ -65,13 +65,15 @@ as the manager of the spatial data infrastructure.
 . Where present, a DOI should be recorded as a resource identifier, with
 the codespace being doi. If a DOI landing page is also available, then
 include this using an Anchor.
-
-|Comment |Since INSPIRE metadata technical guidance version 2, it is no
-longer required to use RS_Identifier if a value for code space value is
-provided. +
-In such cases (where there is a code space provided) it is now strongly
-recommended to use MD_Identifier and encode the complete URI in the code
-element.
+. For best practice, ensure assignments are fixed. Do not modify or reuse identifiers.
+. Avoid incorporating changeable details in identifiers such as version numbers, names or organisations.
+. Implement a preferred presentation method, eg all capitals, and using underscores instead of spaces.
+. Ensure the identifier is web-friendly by using only characters that are un-reserved in URIs or html
+(see https://www.w3.org/Addressing/URL/4_URI_Recommentations.html for more information).
+. Maximise traceability over time by sharing rules for changes and retirement.
+
+|Comment |Since INSPIRE metadata technical guidance version 2, it is no longer required to use RS_Identifier if a value for code space value is provided. +
+In such cases (where there is a code space provided) it is now strongly recommended to use MD_Identifier and encode the complete URI as a gmx:Anchor in the code element.
 
 |Examples a|
 * image2000_1_nl2_multi