Clarify how the metadata creator should decide whether to describe the licence in Limitations on public access or Use constraints.
INSPIRE Metadata TG mentions licences under TG Recommendation C.10: metadata/2.0/rec/common/licences: “For detailed information about the licensing of the resource it is recommended to provide a link to a licence type (e.g. http://creativecommons.org/licenses/by/3.0), a website or to a document containing the necessary information.” This means that INSPIRE suggests that GEMINI Use constraints is the appropriate place. However, GEMINI Limitations on public access states that its purpose is “to identify any external restrictions on access to the data such as licence arrangements.” Furthermore, in Use constraints, licensing is only mentioned in the guidance and the encoding guidance – but one of the examples does give licence information. Finally, “Metadata errors observed” section of each element suggests that it is an error to miss licence information out of either of them.
This could be implemented by revising both Limitations on public access and Use constraints, if the GEMINI Working Group decide that the question is clear cut.
Our preference is that Limitations on public access contains either “none” or the reason(s) why the data is not open data. The licence, open or not, should then be in Use constraints.
This has driven our specific recommendations for those two elements.
Clarify how the metadata creator should decide whether to describe the licence in Limitations on public access or Use constraints. INSPIRE Metadata TG mentions licences under TG Recommendation C.10: metadata/2.0/rec/common/licences: “For detailed information about the licensing of the resource it is recommended to provide a link to a licence type (e.g. http://creativecommons.org/licenses/by/3.0), a website or to a document containing the necessary information.” This means that INSPIRE suggests that GEMINI Use constraints is the appropriate place. However, GEMINI Limitations on public access states that its purpose is “to identify any external restrictions on access to the data such as licence arrangements.” Furthermore, in Use constraints, licensing is only mentioned in the guidance and the encoding guidance – but one of the examples does give licence information. Finally, “Metadata errors observed” section of each element suggests that it is an error to miss licence information out of either of them. This could be implemented by revising both Limitations on public access and Use constraints, if the GEMINI Working Group decide that the question is clear cut. Our preference is that Limitations on public access contains either “none” or the reason(s) why the data is not open data. The licence, open or not, should then be in Use constraints. This has driven our specific recommendations for those two elements.