This enables the data publisher (metadata creator/editor) to add other uses which have successfully been made of the data.
ISO 19115 allows many of these, which “provides basic information about specific application(s) for which the resource(s) has/have been or is being used by different users”. It is an association to a class MD_Usage which officially requires a “brief description” and one or more contacts for the users. Where this second part is not appropriate, then perhaps GEMINI ”Resource specific usage” could be encoded as resourceSpecificUsage.MD_Usage.specificUsage with userContactInfo explicitly missing (xsi:nil)?
Name:
Definition
basic description of specific application(s) for which the resource(s) has/have been or is being used by different users
Purpose and meaning
An other purpose for which it has been used, beyond the original purposes for which resource was developed.
Obligation
Optional
Occurrence
Multiple
Data type
Character string
Domain
Free text
Guidance
To make it clearer to users what uses other than the original purpose the data has been used for. Give a simple description. If possible provide a link to the actual example of use.
Comment
Examples
Conservation planning Dive planning Assessing suitability for housing development
This enables the data publisher (metadata creator/editor) to add other uses which have successfully been made of the data. ISO 19115 allows many of these, which “provides basic information about specific application(s) for which the resource(s) has/have been or is being used by different users”. It is an association to a class MD_Usage which officially requires a “brief description” and one or more contacts for the users. Where this second part is not appropriate, then perhaps GEMINI ”Resource specific usage” could be encoded as resourceSpecificUsage.MD_Usage.specificUsage with userContactInfo explicitly missing (xsi:nil)?
resource(s) has/have been or is being used by different users
Dive planning
Assessing suitability for housing development
Corresponding element in other standards
Encoding guidelines
Guidelines: No need to provide user contact information If the use case occurs in an accessible register, use gmx:Anchor
Example: