DOCSLIB.ORG

Creative Commons Licenses Legal Pitfalls: Incompatibilities and Solutions

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Creative Commons Licenses Legal Pitfalls: Incompatibilities and Solutions INSTITUTE FOR INFORMATION LAW Creative Commons Licenses Legal Pitfalls: Incompatibilities and Solutions Melanie Dulong de Rosnay Institute for Information Law University of Amsterdam Version 1.1 20 December 2010 This work is licensed under a Creative Commons Attribution 3.0 Nederland license available at http://creativecommons.org/licenses/by/3.0/nl/ TABLE OF CONTENTS Foreword .................................................................................................................................... 1 Executive summary .................................................................................................................... 2 1. Introduction ............................................................................................................................ 7 1.1 Sources of legal incompatibilities .................................................................................... 9 1.2 Scope, methodology and outline .................................................................................... 10 2. Creative Commons licenses diversity .................................................................................. 13 2.1 Creative Commons: an organization and a set of licenses ............................................. 15 2.1.1 The licensing infrastructure: a technical standard .................................................. 15 2.1.2 Creative Commons policy strategy: not quite a legal standard ............................... 18 2.2 The different licenses available ..................................................................................... 20 2.2.1 The licenses formats ............................................................................................... 20 2.2.2 The license elements ............................................................................................... 25 i. Attribution (BY) ...................................................................................................... 27 ii. Share Alike (SA) .................................................................................................... 30 iii. Non Commercial (NC) .......................................................................................... 31 iv. No Derivative (ND) ............................................................................................... 34 v. Instruments Outside The Core Suite .................................................................... 35 2.2.3 The main clauses ..................................................................................................... 39 i. Definitions ................................................................................................................ 41 a. Work ..................................................................................................................... 41 b. Adaptation ............................................................................................................ 43 c. Collection ............................................................................................................. 44 d. Rights: Reproduce, Distribute and Publicly Perform .......................................... 45 e. The parties: the Licensor, the Original Author and You ...................................... 47 ii. Fair Dealing Rights .................................................................................................. 48 iii. License Grant .......................................................................................................... 48 iv. Restrictions ............................................................................................................. 49 v. Representations, Warranties and Disclaimer & vi. Limitation on Liability ............ 51 vii. Termination ............................................................................................................ 51 viii. Miscellaneous ....................................................................................................... 52 2.3 The legal nature of the licenses ...................................................................................... 53 2.3.1 Unilateral permissions or contractual agreements? ................................................ 54 2.3.2 Consent to online non-negotiated texts ................................................................... 57 2.3.3 Transmission of obligations to third parties ............................................................ 63 3. Sources of potential incompatibility .................................................................................... 67 3.1 Incompatibility between different formats ..................................................................... 69 3.2 Incompatibility among different versions ...................................................................... 72 3.2.1 From 1.0 to 2.0, in May 2004 ................................................................................. 72 a) Attribution becomes standard .................................................................................. 72 b) Share Alike compatibility with future and international versions ........................... 73 c) Link-back attribution requirement ........................................................................... 74 d) Synchronization and music rights ............................................................................ 74 e) Limited warranties: the hidden risk of infringement ............................................... 74 3.2.2 From 2.0 to 2.5, in June 2005 ................................................................................. 75 a) Attribution to authors or other parties ...................................................................... 75 3.2.3 From 2.5 to 3.0, in February 2007 .......................................................................... 76 a) Attribution and the no-endorsement clause ............................................................. 76 b) Compatibility structure between BY-SA and other licenses: to be determined ...... 76 c) Internationalization of the generic/unported licenses .............................................. 77 d) Moral rights clause, for international harmonization .............................................. 77 e) Collecting society clause, for international harmonization ..................................... 78 f) TPM language clarification ...................................................................................... 78 g) Database sui generis rights in CCi versions ............................................................ 78 3.3 Incompatibility between different options ..................................................................... 80 3.4 Incompatibility among different jurisdictions ............................................................... 83 3.4.1 Legal porting ........................................................................................................... 84 3.4.2 Internal validity vs. unexpected inconsistencies ..................................................... 85 3.4.3 Representation of non-infringement ....................................................................... 86 3.4.4 Scope of rights ........................................................................................................ 86 3.5 Incompatibility with other open content licenses .......................................................... 88 3.5.1 Cross-licensing: the example of the Free Art License ............................................ 89 3.5.2 Combination of works licensed under non-compatible terms: the Digital Peer Publishing Licenses ......................................................................................................... 92 3.5.3 Dual licensing and relicensing: Wikipedia and the GNU-GFDL ........................... 94 3.5.4 Free Culture core freedoms: defining open license ................................................ 95 4. Impact of the differences between licenses ......................................................................... 98 4.1 Identification of the parties and enforcement ................................................................ 99 4.2 Scope of rights granted ................................................................................................ 100 4.2.1 A difference among formats: Collections and Adaptations ...................................... 101 4.2.2 Differences among jurisdictions ............................................................................... 102 a. Database rights ....................................................................................................... 102 b. Moral rights ............................................................................................................ 104 c. Representation of non-infringement ...................................................................... 106 d. Collecting societies ................................................................................................ 109 5. Conclusion: options to mitigate risks and improve compatibility ..................................... 111 5.1 Improve the interface ................................................................................................... 111 5.1.1 Develop more technologies to support the licenses’ requirements ....................... 111 5.1.2 Remodel the acceptation infrastructure ................................................................ 113 5.1.3 Reverse the system’s logic ...................................................................................
Load more

Recommended publications
  • Open Licensing Toolkit for Staff
    Open Licensing Toolkit for Staff The Hewlett Foundation Open Licensing Toolkit for Staff is licensed May 2015 under a Creative Commons Attribution 4.0 International License. Legal Disclaimer: This material is for general informational purposes only and does not represent legal advice as to any particular set of facts; nor does it represent any undertaking to keep recipients advised of any relevant legal developments. Please consult appropriate professional advisors as you deem necessary. The Hewlett Foundation shall not be held responsible for any claims or losses that may arise from any errors or omissions in this document. Hewlett Foundation Open Licensing Toolkit for Staff Table of Contents 1. Hewlett Foundation Commitment to Open Licensing 2. Hewlett Foundation Procedures a. Frequently Asked Questions b. Decision Tree c. Creative Commons License Types d. Guidelines for Marking Openly Licensed Documents 3. Sample Language a. Grantee Communications b. Grant Proposal Template c. Grant Reporting Requirements d. Grant Agreement Letter e. Direct Charitable Activities (DCA) Contract May 2015 Hewlett Foundation Open Licensing Toolkit for Staff Hewlett Foundation Commitment to Open Licensing As part of our commitment to openness and transparency, the Hewlett Foundation has long supported open licensing—an alternative for traditional copyright that allows and encourages sharing of intellectual property. Open licenses, such as those developed by our longtime grantee Creative Commons, protect authors’ rights while giving explicit permission to others to freely use, distribute, and build upon their work. The benefits of open licensing are clear: open licensing increases the chances that good ideas will get a hearing, that others will be able to do something with them, and ultimately that they will have their greatest impact.
    [Show full text]
  • “The Future Is Open” for Composition Studies: a New
    THE FLORIDA STATE UNIVERSITY COLLEGE OF ARTS AND SCIENCES “THE FUTURE IS OPEN” FOR COMPOSITION STUDIES: A NEW INTELLECTUAL PROPERTY MODEL IN THE DIGITAL AGE By CHARLES LOWE A Dissertation submitted to the Department of English in partial fulfillment of the requirements for the degree of Doctor of Philosophy Degree Awarded Summer Semester, 2006 Copyright © 2006 Charles Lowe All Rights Reserved The members of the committee approve the dissertation of Charles Lowe defended on May 25, 2006. ______________________________ John Fenstermaker Professor Directing Dissertation ______________________________ Ernest Rehder Outside Committee Member ______________________________ Eric Walker Committee Member ______________________________ Deborah Coxwell-Teague Committee Member Approved: ______________________________ Hunt Hawkins, Chair, Department of English The Office of Graduate Studies has verified and approved the above named committee members. ii This text is dedicated to Wendy Bishop, John Lovas, Candace Spigelman, and Richard Straub, four teachers and researchers in the field of composition studies with whom it was my pleasure to work. I only wish I could have the opportunity again. iii TABLE OF CONTENTS ABSTRACT...............................................................................................................................vi INTRODUCTION.......................................................................................................................1 The Future Is Open.............................................................................................................
    [Show full text]
  • Creative Commons Open Licenses - What Is It All About?
    CREATIVE COMMONS OPEN LICENSES - WHAT IS IT ALL ABOUT? Introductory presentation by Paul G. West Creative Commons South African Chapter Lead STATING THE UNNECESSARY This workshop is dedicated to providing a harassment-free experience for everyone regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age or religion. We do not tolerate harassment of participants or facilitators in any form. Sexual language and imagery is not appropriate, including in any online platform that may be used. AND IT IS IMPORTANT TO ADD THAT . • Nothing in this workshop should be construed as legal advice! • We will be talking about an interesting range of topics that touch on copyright, fair use and open licensing. • We will together learn more about copyright, open licensing and open practices in various communities. • Upon completion, you should feel a little more comfortable sharing facts about copyright and open licensing and good open practices. • I am NOT a lawyer – I am a supporter of Open Educational Resources (OER) and Creative Commons (CC) open licenses. THE STORY DOES NOT START IN 2002 UNESCO Forum on the Impact of Open Courseware for Higher Education in Developing Countries https://unesdoc.unesco.org/ark:/48223/pf0000181682 ORIGINS OF OER CREATION OF A MOVEMENT Larry Lessig and others founded the Creative Commons 2001 Charles M. Vest speaks of a meta-university 2007 a transcendent, accessible, empowering, dynamic, communally constructed framework of open materials and platforms
    [Show full text]
  • Knowledge Management by Wikis
    Knowledge management by wikis Sander Spek [email protected] Institute for Knowledge and Agent Technology Universiteit Maastricht Abstract Wikis provide a new way of collaboration and knowledge sharing. Wikis are software that allows users to work collectively on a web-based knowledge base. Wikis are characterised by a sense of anarchism, collaboration, connectivity, organic development and self-healing, and they rely on trust. We list several concerns about applying wikis in professional organisation. After these concerns are met, wikis can provide a progessive, new knowledge sharing and collabora- tion tool. 1 Grassroots knowledge sharing During the last decades, the sharing of information and knowledge has gone through an unheard rapidisation. Both the amount of information shared, as well as the speed in which this happens, has taken a huge flight. In many fields of progress, professional organisations were more ad- vanced then ‘amateur knowledge sharers’. Remarkably, in some fields this has changed over the years. On the Internet, many succesful grassroots initiatives have popped up, that still didn’t make it to the somewhat static and controlled environment of professional business organisa- tions. Think of free-software projects, but also of free-information projects, as wikis, weblogs, and open news sites like Indymedia. (Möller, 2005) In this paper, we will examine on of the most popular and upcoming knowledge sharing enablers on the Internet: wikis. Consequently, we will discuss why wikis are not (yet) adequate for a professional environment, and what could be changed to have companies adapt the power of wiki-based knowledge sharing too. 2 Wikis Möller (2005, page vii, translated) defines wikis as “open websites that can be edited by every visitor.”1 We will extend this definition in two ways: (1) we explicitly state that modifying can also include deleting information, and (2) we mention the fact that a wiki is in fact a knowledge base.
    [Show full text]
  • Introductory Lecture & FLOSS
    Introductory Lecture & FLOSS Lecture 1 TU Wien, 193.067 Free and Open Technologies (WS 2019/2020) Christoph Derndorfer and Lukas F. Lang This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. Introduction Organization ● Lectures: ○ Weekly lecture to cover course materials (until Christmas) ○ Lectures take place on Tuesdays, 17:00–19:00, Argentinierstraße 8, Seminarraum/Bibliothek 194-05 ○ Attendance is mandatory ● Group project: ○ In groups of 4 students ○ 3 meetings with lecturers during the semester (week 44/2019, week 48/2019, week 2/2020) ○ Final presentations at the end of January (week 4/2020) ● Final paper: ○ In groups of 2 students ○ Final presentations at the end of January (week 5/2020) ○ Deadline: Sunday, February 9, 2020, 23:59 CET (no exceptions!) Organization ● Grading: ○ 50% group project ○ 35% seminar paper ○ 15% participation during lectures ○ All course components need to be passed in order to pass the overall course! ● Course materials: ○ Will be provided at https://free-and-open-technologies.github.io ● For further questions: ○ Email [email protected] and [email protected] Lecture outline 1. FLOSS (Free/Libre and Open Source Software) 2. Open Hardware 3. Open Data 4. Open Content/Open Educational Resources 5. Open Science/Research 6. Open Access 7. Open Spaces/Open Practices: Metalab Vienna 8. Guest Lecture: Stefanie Wuschitz (Mz* Baltazar’s Lab) Group project ● Goal: ○ Extend, contribute to, or create a new open project within scope of lecture topics ● Choose topic from a list (see course website) or (even better) suggest your own: ○ Groups of 4 students ○ Send a 1-page proposal until Friday, October 25, via email to both lecturers ■ Define the idea, goal, (potential) impact, requirements, and estimated effort ■ State deliverables (should be broken down into three milestones to discuss in meetings) ● Requirements: ○ Open and accessible (Git repository, openly licensed) → others can access/use/study/extend ○ Use time sheet to track and compare estimated vs.
    [Show full text]
  • FOSS Philosophy 6 the FOSS Development Method 7
    1 Published by the United Nations Development Programme’s Asia-Pacific Development Information Programme (UNDP-APDIP) Kuala Lumpur, Malaysia www.apdip.net Email: [email protected] © UNDP-APDIP 2004 The material in this book may be reproduced, republished and incorporated into further works provided acknowledgement is given to UNDP-APDIP. For full details on the license governing this publication, please see the relevant Annex. ISBN: 983-3094-00-7 Design, layout and cover illustrations by: Rezonanze www.rezonanze.com PREFACE 6 INTRODUCTION 6 What is Free/Open Source Software? 6 The FOSS philosophy 6 The FOSS development method 7 What is the history of FOSS? 8 A Brief History of Free/Open Source Software Movement 8 WHY FOSS? 10 Is FOSS free? 10 How large are the savings from FOSS? 10 Direct Cost Savings - An Example 11 What are the benefits of using FOSS? 12 Security 13 Reliability/Stability 14 Open standards and vendor independence 14 Reduced reliance on imports 15 Developing local software capacity 15 Piracy, IPR, and the WTO 16 Localization 16 What are the shortcomings of FOSS? 17 Lack of business applications 17 Interoperability with proprietary systems 17 Documentation and “polish” 18 FOSS SUCCESS STORIES 19 What are governments doing with FOSS? 19 Europe 19 Americas 20 Brazil 21 Asia Pacific 22 Other Regions 24 What are some successful FOSS projects? 25 BIND (DNS Server) 25 Apache (Web Server) 25 Sendmail (Email Server) 25 OpenSSH (Secure Network Administration Tool) 26 Open Office (Office Productivity Suite) 26 LINUX 27 What is Linux?
    [Show full text]
  • Translate's Localization Guide
    Translate’s Localization Guide Release 0.9.0 Translate Jun 26, 2020 Contents 1 Localisation Guide 1 2 Glossary 191 3 Language Information 195 i ii CHAPTER 1 Localisation Guide The general aim of this document is not to replace other well written works but to draw them together. So for instance the section on projects contains information that should help you get started and point you to the documents that are often hard to find. The section of translation should provide a general enough overview of common mistakes and pitfalls. We have found the localisation community very fragmented and hope that through this document we can bring people together and unify information that is out there but in many many different places. The one section that we feel is unique is the guide to developers – they make assumptions about localisation without fully understanding the implications, we complain but honestly there is not one place that can help give a developer and overview of what is needed from them, we hope that the developer section goes a long way to solving that issue. 1.1 Purpose The purpose of this document is to provide one reference for localisers. You will find lots of information on localising and packaging on the web but not a single resource that can guide you. Most of the information is also domain specific ie it addresses KDE, Mozilla, etc. We hope that this is more general. This document also goes beyond the technical aspects of localisation which seems to be the domain of other lo- calisation documents.
    [Show full text]
  • Åtta Licenser För Öppet Innehåll En Bilaga Till Internetguiden ”Copyright – Copyleft”
    Åtta licenser för öppet innehåll En bilaga till Internetguiden ”Copyright – Copyleft” Innehåll Innehåll Licenserna i sin helhet 5 Free Art License 1.3 .............................................................. 5 GNU Free Documentation License ...................................... 8 SPARC Author Addendum ................................................. 14 Open Database Licence Agreement (ODbL) ...................... 15 Kopimi ................................................................................. 23 The FreeBSD Documentation License ............................... 24 Open Game License ............................................................ 25 Creative Commons-licensen Erkännande- IckeKommersiell-DelaLika v2.5 Licens ............................. 27 bilaga till copyright – copyleft 3 Licenserna i sin helhet Free Art License 1.3 Preamble The Free Art licence authorises you to freely copy, spread, and transform creative works while re- specting the author’s rights. Far from ignoring such rights, the Free Art License recognizes them and protects them. It reformu- lates their application byallowing each and every creative use of the mind’s creation, regardless of their genres and the forms in which they are expressed. While the application of copyright law commonly results in restricting the public’s access to the mind’s creation, the Free Art License facilitates. Its intent is to allow the use of the resources constitu- tive of a work; to enable new conditions for creation in order to amplify the possibilities of creation.
    [Show full text]
  • The Copyleft Movement: Creative Commons Licensing
    Centre for the Study of Communication and Culture Volume 26 (2007) No. 3 IN THIS ISSUE The Copyleft Movement: Creative Commons Licensing Sharee L. Broussard, MS APR Spring Hill College AQUARTERLY REVIEW OF COMMUNICATION RESEARCH ISSN: 0144-4646 Communication Research Trends Table of Contents Volume 26 (2007) Number 3 http://cscc.scu.edu The Copyleft Movement:Creative Commons Licensing Published four times a year by the Centre for the Study of Communication and Culture (CSCC), sponsored by the 1. Introduction . 3 California Province of the Society of Jesus. 2. Copyright . 3 Copyright 2007. ISSN 0144-4646 3. Protection Activity . 6 4. DRM . 7 Editor: William E. Biernatzki, S.J. 5. Copyleft . 7 Managing Editor: Paul A. Soukup, S.J. 6. Creative Commons . 8 Editorial assistant: Yocupitzia Oseguera 7. Internet Practices Encouraging Creative Commons . 11 Subscription: 8. Pros and Cons . 12 Annual subscription (Vol. 26) US$50 9. Discussion and Conclusion . 13 Payment by check, MasterCard, Visa or US$ preferred. Editor’s Afterword . 14 For payments by MasterCard or Visa, send full account number, expiration date, name on account, and signature. References . 15 Checks and/or International Money Orders (drawn on Book Reviews . 17 USA banks; for non-USA banks, add $10 for handling) should be made payable to Communication Research Journal Report . 37 Trends and sent to the managing editor Paul A. Soukup, S.J. Communication Department In Memoriam Santa Clara University Michael Traber . 41 500 El Camino Real James Halloran . 43 Santa Clara, CA 95053 USA Transfer by wire: Contact the managing editor. Add $10 for handling. Address all correspondence to the managing editor at the address shown above.
    [Show full text]
  • Elements of Free and Open Source Licenses: Features That Define Strategy
    Elements Of Free And Open Source Licenses: Features That Define Strategy CAN: Use/reproduce: Ability to use, copy / reproduce the work freely in unlimited quantities Distribute: Ability to distribute the work to third parties freely, in unlimited quantities Modify/merge: Ability to modify / combine the work with others and create derivatives Sublicense: Ability to license the work, including possible modifications (without changing the license if it is copyleft or share alike) Commercial use: Ability to make use of the work for commercial purpose or to license it for a fee Use patents: Rights to practice patent claims of the software owner and of the contributors to the code, in so far these rights are necessary to make full use of the software Place warranty: Ability to place additional warranty, services or rights on the software licensed (without holding the software owner and other contributors liable for it) MUST: Incl. Copyright: Describes whether the original copyright and attribution marks must be retained Royalty free: In case a fee (i.e. contribution, lump sum) is requested from recipients, it cannot be royalties (depending on the use) State changes: Source code modifications (author, why, beginning, end) must be documented Disclose source: The source code must be publicly available Copyleft/Share alike: In case of (re-) distribution of the work or its derivatives, the same license must be used/granted: no re-licensing. Lesser copyleft: While the work itself is copyleft, derivatives produced by the normal use of the work are not and could be covered by any other license SaaS/network: Distribution includes providing access to the work (to its functionalities) through a network, online, from the cloud, as a service Include license: Include the full text of the license in the modified software.
    [Show full text]
  • Public Wikis: Sharing Knowledge Over the Internet
    Technical Communication Wiki : Chapter 2 This page last changed on Apr 15, 2009 by kjp15. Public Wikis: Sharing Knowledge over the Internet What is a public wiki? A public wiki refers to a wiki that everyone can edit, that is, it is open to the general public on the Internet with or without a free login. Anyone is welcome to add information to the wiki, but contributors are asked to stay within the subject area, policies, and standards of the particular wiki. Content that does not relate to the subject or is not of good quality can and will be deleted by other users. Also, if a contributor makes a mistake or a typo, other users will eventually correct the error. Open collaboration by anyone means that multiple articles can be written very fast simultaneously. And, while there may be some vandalism or edit wars, quality of the articles will generally improve over time after many editors have contributed. The biggest public wiki in the world, with over 75,000 contributors, is Wikipedia, "the free encyclopedia that anyone can edit" [1]. Wikipedia has over 2.8 million articles in the English version, which includes over 16 million wiki pages, and is one of the top ten most popular websites in the United States [2]. There are versions of Wikipedia in ten different languages, and articles in more than 260 languages. Wikipedia is operated by the non-profit Wikimedia Foundation [3] which pays a small group of employees and depends mainly on donations. There are also over 1,500 volunteer administrators with special powers to keep an eye on editors and make sure they conform to Wikipedia's guidelines and policies.
    [Show full text]
  • Collective Authoring the Free Wikipedia Encyclopedia Uses the Mediawiki Engine to Collect an Enormous Knowledge Database
    SYSADMIN Mediawiki Installing and Maintaining Mediawiki Collective Authoring The free Wikipedia encyclopedia uses the Mediawiki engine to collect an enormous knowledge database. If you want to launch your own wiki, this PHP-based software is a good choice that provides rich functional- ity and plenty of power. BY ERIK MÖLLER iki means quick in Hawaiian each wiki page in the browser. Square an asterisk at the start of a line creates a – and the Web-based wiki brackets are all you need to make a text list; text surrounded by equals signs Wtechnology has established string into a link. If the page already turns into a heading. itself extremely quickly. Ward Cunning- exists, the link is created; if not, the user There are more than 100 wiki engines ham had the idea back in 1995, when he is provided access to an edit box where [1] at present. Mediawiki [2] is a popular was looking for a method to collect he can create a new page with the pro- example. It provides the underlying tech- examples of common programming tasks vided heading (see Figure 1). nology for the Copyleft encyclopedia, amongst a group of developers. The sim- An easily understandable syntax Wikipedia, the role model for most other ple idea was to allow modifications of makes light work of formatting. Typing wikis (see A Journey to the World of Wikis). In its first year, Wikipedia used A Journey to the World of Wikis the usemod wiki [3], which is written in Although it was specially developed for released under a free license.The Wikibooks Perl.
    [Show full text]