In the AP, we are recommending the type of a License Document (dct:type) to take values from the ADMS licence type vocabulary (available at http://purl.org/adms/licencetype/1.1).
What happens in practice is that data publishers are licensing their datasets under a particular license, which is of a type, but the type is not explicitly defined.
The ENGAGE project has a nice collection of existing open data licenses (http://www.engagedata.eu/opendatasites).
A mapping between license types and licenses would be very helpful.
Component
DocumentationCategory
improvement
Login or
create an account to comment.
Comments
+1 from me to supporting the creation of these mappings, and to use licence type in metadata.
Consideration
This issue is not technically related to the Application Profile. It could be a separate guidance document.
Proposed resolution
Consider a separate guidance document.
Proposed action
No change to the specification, unless such a mapping document exists in which case the Application Profile could refer to it (possibly in section 8.3)
Resolved at meeting 18 July 2013, see report at https://joinup.ec.europa.eu/document/dcat-application-profile-wg-virtual-meeting-2013-07-18.
No change.