-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mmd:location #11
Comments
I'll add this as a task suggestion for the sprint. It seems to be ok but it would be nice to integrate this in the sprint workflow. |
I am not sure how much this is used, but I would not mind keeping it from a semantic prospective, as a text description of location. |
I have no objection keeping it but preferably then extending slightly to get a proper semantic context framework around it. This links directly to similar discussions in the context of SeaDataNet and CODATA. |
What is the status here? |
I am not sure we reached an conclusion here. I think if we keep, we need to link with resources that have good descriptions/definitions of names used. E.g. when referring to the North Sea, what does that actually mean... |
Considering we have added in the Keywords controlled vocabulary the support for GCMDLOC, which uses also the resource https://gcmd.earthdata.nasa.gov/kms/concepts/concept_scheme/locations we could think about removing this element in mmd. Parsing the keyword vocabulary attribute in xslt will allow to expose proper GCMD/dif location in hierarchical way and also use the appropriate thesauri in iso, as done for the GCMD Science Keywords. |
Decide if continued or to be removed. If continued check information for sub element location_reference and how that should be reformulated.
The text was updated successfully, but these errors were encountered: