{"id":1219,"date":"2011-06-22T12:11:55","date_gmt":"2011-06-22T11:11:55","guid":{"rendered":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/?p=1219"},"modified":"2011-06-22T12:16:03","modified_gmt":"2011-06-22T11:16:03","slug":"an-internal-monologue-on-metadata-licensing","status":"publish","type":"post","link":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/2011\/06\/an-internal-monologue-on-metadata-licensing\/","title":{"rendered":"An internal monologue on Metadata Licensing"},"content":{"rendered":"

I’ve been involved in discussions around the licensing of library\/museum\/archive metadata over the last couple of years, specifically through my work on UK Discovery<\/a> (http:\/\/discovery.ac.uk<\/a>) – an initiative to enable resource discovery through the publication and aggregation of metadata according to simple, open, principles.<\/p>\n

In the course of this work I’ve co-authored the JISC Guide to Open Bibliographic Data<\/a> and become a signatory of the Discovery Open Metadata Principles<\/a>. Recently I’ve been\u00a0discussing some of the issues around licensing with Ed Chamberlain and others (see Ed’s thoughts on licensing on the CUL-COMET blog<\/a>), and over coffee this morning I was trying to untangle \u00a0the issues and reasons for specific approaches to licensing – for some reason they formed in my head as a set of Q&A so I’ve jotted them down in this form… at the moment this is really to help me with my thinking but I thought I’d share in case.<\/p>\n

N.B. These are just some thoughts – not comprehensive and not official views from the Discovery intiative<\/strong><\/p>\n

Q1: Why apply an explicit license to your metadata?
\nA1.1: To enable appropriate re-use<\/p>\n

Q2: What prevents appropriate re-use
\nA2.1: Uncertainty\/lack of clarity about what can be done with the data
\nA2.2: Any barriers that add an overhead – could be technical or legal<\/p>\n

Q3: What sort of barriers add overhead?
\nA3.1: Attribution licensing –\u00a0where data from many sources are being mixed together this overhead can be considerable.
\nA3.2: Machine readable licensing data to be provided with data – adds complexity to data processing, potentially increases network traffic and slows applications
\nA3.3: Licensing requiring human intervention to determine rights for reuse at a data level – this type of activity effectively stops applications being built on the data as it isn’t possible for software to decide if a piece of data can be included or not (NB human intervention for whole datasets is less of an issue – building an app on a dataset where all data is covered by the same license which has been interpreted by a human in advance of writing software is not an issue)
\nA3.4: Licensing which is not clear about what type of reuse is allowed. The NC (Non-commercial) licenses exemplify this as the definition of what amounts to ‘commerical use’ is often unclear.
\nA3.5: Licensing not generally familiar to the potential consumers of the data (for re-use purposes) – e.g. writing a new license specific to your requirements rather than adopting a Creative Commons or other more widely used licence.<\/p>\n

Q4: What does this suggest in terms of data licensing decisions?
\nA4.1: Putting data in public domain removes all doubt – it can be reused freely – a consumer doesn’t have to check anything etc.
\nA4.2: Putting data in public domain removes the overhead of attribution – where data from many sources are being mixed together this overhead can be considerable
\nA4.3: Where there is licensing beyond public domain, reuse will be encouraged if it is easy to establish (preferably in an automated way) what licensing is associated with any particular data
\nA4.4: Where data within a single set is available under different licensing, reuse will be encouraged by making it easy to address only data with a specified license attached. E.g. ‘only give me data that is CC0 or ODC-PDDL’<\/p>\n

Comments\/questions welcome…<\/p>\n","protected":false},"excerpt":{"rendered":"

I’ve been involved in discussions around the licensing of library\/museum\/archive metadata over the last couple of years, specifically through my work on UK Discovery (http:\/\/discovery.ac.uk) – an initiative to enable resource discovery through the publication and aggregation of metadata according to simple, open, principles. In the course of this work I’ve co-authored the JISC Guide […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[66],"class_list":["post-1219","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-ukdiscovery"],"_links":{"self":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/1219","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/comments?post=1219"}],"version-history":[{"count":3,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/1219\/revisions"}],"predecessor-version":[{"id":1221,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/1219\/revisions\/1221"}],"wp:attachment":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/media?parent=1219"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/categories?post=1219"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/tags?post=1219"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}