DD3 R9. Add a GEMINI element identical to ISO 19115 MD_Identification.purpose

[PeterParslow]

This makes it clearer to users what the original purpose in collecting and publishing the data was. Note: ISO 19115 only allows a single purpose which is a free text “summary of the intentions with which the resource(s) was developed”. If DD3 (or anyone else!) does establish a register of “purposes” then this would be best encoded with a gmx:Anchor to the purpose in that register.

Name: Purpose
Definition	Summary of the intentions for which the resource was developed
Purpose and meaning	To make it clearer to users what the original purpose in collecting and publishing the data was.
Obligation	Optional
Occurrence	Single
Data type	Character string
Domain	Free text
Guidance
Comment	If this element is used, the information should not be repeated in the Abstract.
Examples	Natura 2000 report Marine navigation Town planning

Corresponding element in other standards	Standard	Name	Comparison
ISO 19115:2003	MD_Identification.purpose	Identical
ISO 19139:2007	/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:purpose	Identical
Schema.org	If the resource was developed for education: educationalPurpose	The GEMINI element is more general

Encoding guidelines

Guidelines	If there is a register of purposes (use cases), then include a reference to that, using gmx:Anchor
Example

<gmd:MD_Metadata> 

  ... 
  <gmd:identificationInfo> 
    <gmd:MD_DataIdentification> 
      ... 
      <gmd:purpose>
        <gco:CharacterString>Town planning</gco:CharacterString> 
      </gmd:purpose> 
      ... 
    </gmd:MD_DataIdentification> 
  </gmd:identificationInfo> 
  ... 
</gmd:MD_Metadata>
``` |

[nmtoken]

Other example of use of Purpose from PURE portal description of models:

• Distributed Recharge Model
• Numerical ground water flow model
• Landscape model
• Particle Tracking
• Saturated groundwater flow model
• Simulating 3D variably saturated flow with overland flow
• Volcanic Hazard Model