This includes deciding what is the canonical (master) version of the metadata, and how the metadata publisher considers copies and other representations that are likely to be made, for example on aggregating services and portals, or by restyling to HTML.
See “canonical” discussion in Provide encoding guidance on embedding Schema.org in HTML using JSON-LD above.
The GEMINI guidance should state that it is valid to describe a deprecated dataset and describe how to do this. In ISO 19115, this is best supported by MD_Identification.status – see recommendation to add this element.
It’s not clear whether this general discussion should go in UK GEMINI standard and INSPIRE implementing rules, Metadata Guidelines for Geospatial Data Resources - Part 1, Part 2, or even in Part 3 of the guidance. The subject is touched on at 2.3 in Part 1 Metadata as a business process and expanded in Part 3.
This includes deciding what is the canonical (master) version of the metadata, and how the metadata publisher considers copies and other representations that are likely to be made, for example on aggregating services and portals, or by restyling to HTML. See “canonical” discussion in Provide encoding guidance on embedding Schema.org in HTML using JSON-LD above. The GEMINI guidance should state that it is valid to describe a deprecated dataset and describe how to do this. In ISO 19115, this is best supported by MD_Identification.status – see recommendation to add this element. It’s not clear whether this general discussion should go in UK GEMINI standard and INSPIRE implementing rules, Metadata Guidelines for Geospatial Data Resources - Part 1, Part 2, or even in Part 3 of the guidance. The subject is touched on at 2.3 in Part 1 Metadata as a business process and expanded in Part 3.