Tilburg University Free and Open Source Software Schellekens, M.H.M

Total Page:16

File Type:pdf, Size:1020Kb

Tilburg University Free and Open Source Software Schellekens, M.H.M Tilburg University Free and Open Source Software Schellekens, M.H.M. Published in: The Future of the Public Domain Publication date: 2006 Link to publication in Tilburg University Research Portal Citation for published version (APA): Schellekens, M. H. M. (2006). Free and Open Source Software: An Answer to Commodification? In L. Guibault, & B. Hugenholtz (Eds.), The Future of the Public Domain: Identifying the Commons in Information Law (pp. 303- 323). (Information Law Series; No. 16). Kluwer Law International. General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal Take down policy If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim. Download date: 27. sep. 2021 Free and open source software: an answer to commodification? Maurice Schellekens 1. Introduction Linux is a PC operating system which is distributed under the General Public License (hereinafter: GPL). The GPL allows for the (royalty-)free use, modification and redistribution of the software. Given these license conditions, Linux users believed they could use the operating system without too many license worries. That was until SCO claimed to own the rights in certain parts of the Linux code, and started sending bills to Linux user for their use of the code ‘owned’ by SCO. IBM was targeted as well because it allegedly ‘leaked’ the code-segments to open source communities. This case perfectly illustrates the effects of an ever increasing trend towards commodification. In the early days of computers software was given away for free to those who bought the hardware, but these days are over. Users of software must pay for its use as for any tradable commodity. Only the free and open source movements adhere to the old idea of sharing software instead of locking it in. But these movements are increasingly confronted with opposition from the proponents of what I shall call the proprietary software model. The SCO v. IBM case is a case in point. If free and open source software is an exponent of the public domain for software, then this part of the public domain is ‘under pressure’. Given the importance of a wealthy public domain for economic and social innovation, this development is a reason for concern. In this chapter I will focus on the following question: ‘Does the open source model for development and distribution of software (and increasingly also of other types of information) provide an adequate counterweight to commodification?’ In the open source model software is developed in a free and open way. Software is 1 MAURICE SCHELLEKENS made available freely (i.e. without requiring payment of royalties) for anyone to use or modify, inclusive of its source code. In answering this question I will investigate whether open source lends itself conceptually to such task. I will also try to shed some light on the viability of the open source model, as it needs to compete with the traditional proprietary model and is under pressure from that model’s proponents. The outline of this chapter is as follows. Since free software and open source software are still relatively new phenomena, the following paragraph will explain what free and open source software are. The so-called Open Source Definition will take centre stage in this discussion. In the next paragraph (par. 3) I will then focus on the central question of this chapter: is the open source model an answer to the real (or perceived?) drawbacks of commodification? In order to answer this question the interrelationship between a number of key concepts, such as commodification, public domain and open source software, is explained. This section provides an answer to the question whether the open source model lends itself conceptually to form a counterweight against commodification or the proprietary model which is the exponent of commodification. Having answered this question in the affirmative, I will then address a few doctrinal issues with respect to the free or open source license, more specifically the General Public License (hereinafter: GPL). These issues may become important, since there is a rather fierce ‘competition’ between the proprietary and open source models. The doctrinal weaknesses of the open source model run a certain risk of being exploited by the protagonists of the proprietary model. In the next section the converse question will be addressed: how does open source model affect the proprietary model? Following that the relation between technical protection of works and open source software will be dealt with. Section &.4 deals with the suitability of he model to function in conjunction with other types of information than software. In the penultimate section (&.5) the role of government with respect to the open source model is investigated. The last section contains a conclusion reflecting the preceding sections. 2. What is Open Source? The term ‘open source’ refers primarily to the fact that the source code of computer software is made available to the public. But this is only part of the concept, as will be clarified below. The Open Source Definition (hereinafter: OSD) by the Open Source Initiative (hereinafter: OSI) is generally taken to be most authoritative definition of what open source is. 1 It must however be said that this is the definition of the OSI and diverts from what e.g. the Free Software Foundation 1 M.H. Webbink, ‘Open source licensing: today’s big legal challenge (Part 1)’, Georgetown CLE 1 – 22 (2003). The Open Source Definition will be discussed below. 2 FREE AND OPEN SOURCE SOFTWARE : AN ANSWER TO COMMODIFICATION ? (hereinafter: FSF) takes to be free software. According to the FSF, ‘free software is a matter of the users' freedom to run, copy, distribute, study, change and improve the software.’2 Free software is for most practical purposes entirely comparable to open source software. The main difference is in the ideological background. Stallman, the man behind free software, holds the opinion that all software should be freely available. You should think of ``free'' as in ``free speech,'' not as in ``free beer.'' 3 Stallman’s main focus is on freedom. Raymond, the man behind open source software, takes a more practical stance. 4 Open source is simply a good way to develop and distribute software, no more, no less. In this chapter I will assume that software is open source if there is a material conformance to the OSD. This is in keeping with practice; the term open source often used in a broader meaning, so that it also encompasses free software and software distributed under the BSD license. 5 So there is some room for a finding that licenses qualify as open source even if they divert in some respect from the OSD. From the OSD it appears that the terms for distribution determine what open source software is and what not. The definition consists of ten criteria that will be dealt with hereinafter. The terms of the definition are rendered in italics. 1. Free Redistribution The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale. The licensee is free to redistribute the software. It can be assumed that copying necessary for redistribution is also allowed. Distribution is not limited to distribution of physical copies, but also includes distribution by other means such as transmission through the Internet. 2. Source Code The program must include source code, and must allow distribution in source code as well as compiled form. Where some form of a product is not distributed with source code, there must be a well-publicized means of obtaining the source code for no more than a reasonable reproduction cost preferably, downloading via the Internet without charge. The source code must be the preferred form in which a programmer would modify the 2 See http://www.gnu.org/philosophy/free-sw.html . 3 See http://www.gnu.org/philosophy/free-sw.html . 4 E.S. Raymond, Homesteading the Noosphere , First Monday 1998, available at: http://www.firstmonday.dk/issues/issue3_10/raymond/. 5 BSD stands for Berkeley Software Distribution., a derivative of the UNIX operating system. 3 MAURICE SCHELLEKENS program. Deliberately obfuscated source code is not allowed. Intermediate forms such as the output of a pre-processor or translator are not allowed. Computer programs are written in higher programming languages, such as Pascal, C++, etc. These higher programming languages do not include precise machine-readable instructions and thus make programming easier. Computer programmers can concentrate on the essentials, not bothered by machine-specific details. Programs written in higher programming languages do however have a significant drawback: they cannot be directly executed (i.e. run) by a computer. Such programs must be first converted (‘translated’) into machine-executable form by special programs called compilers. The program in the higher programming language is called source code and the resulting machine code is called the object code. The machine code can be run on a computer independently of the source code from which it stems.
Recommended publications
  • Open Source Software Vs Proprietary Software Sakshi Singh, Madhvik Verma, Naveen Kumar N
    International Journal of Scientific & Engineering Research Volume 8, Issue 12, December-2017 735 ISSN 2229-5518 Open Source Software Vs Proprietary Software Sakshi Singh, Madhvik Verma, Naveen Kumar N Abstract— Open Source software are the most revolutionizing concept that has been put forth in the Information Technology spectrum. This new release has raised quite a lot of brows, similar to when the Internet was launched. For a very long time, there has been a tiff going on between the Proprietary software and the open source software and how the open source software are taking over their ancestors. The technical experts often indulge in conversations as to which of the two software is better and why. People also get confused as to which type of software can be listed as Open source. In this paper we aim to emphasize that the open source development cycle has been there in the market for quite some time and has a huge user base now, thus giving it a strong hold in the software market. It has encouraged the use of new strategically placed actions which has in turn made a huge base for open source software systems. On the other hand, many experts also suggest that this is just momentary and it will pass over a period of time whereas the proprietary software are there to stay. This paper gives the understanding and recommendations for both the kind of software thus giving the user a proper understanding of which software is suitable for their use and thus they can make a better choice for their purpose.
    [Show full text]
  • Arxiv:1812.09167V1 [Quant-Ph] 21 Dec 2018 It with the Tex Typesetting System Being a Prime Example
    Open source software in quantum computing Mark Fingerhutha,1, 2 Tomáš Babej,1 and Peter Wittek3, 4, 5, 6 1ProteinQure Inc., Toronto, Canada 2University of KwaZulu-Natal, Durban, South Africa 3Rotman School of Management, University of Toronto, Toronto, Canada 4Creative Destruction Lab, Toronto, Canada 5Vector Institute for Artificial Intelligence, Toronto, Canada 6Perimeter Institute for Theoretical Physics, Waterloo, Canada Open source software is becoming crucial in the design and testing of quantum algorithms. Many of the tools are backed by major commercial vendors with the goal to make it easier to develop quantum software: this mirrors how well-funded open machine learning frameworks enabled the development of complex models and their execution on equally complex hardware. We review a wide range of open source software for quantum computing, covering all stages of the quantum toolchain from quantum hardware interfaces through quantum compilers to implementations of quantum algorithms, as well as all quantum computing paradigms, including quantum annealing, and discrete and continuous-variable gate-model quantum computing. The evaluation of each project covers characteristics such as documentation, licence, the choice of programming language, compliance with norms of software engineering, and the culture of the project. We find that while the diversity of projects is mesmerizing, only a few attract external developers and even many commercially backed frameworks have shortcomings in software engineering. Based on these observations, we highlight the best practices that could foster a more active community around quantum computing software that welcomes newcomers to the field, but also ensures high-quality, well-documented code. INTRODUCTION Source code has been developed and shared among enthusiasts since the early 1950s.
    [Show full text]
  • Diverted Derived Design
    Diverted Derived Design Table of Contents Introduction 0 Motivations 1 Licenses 2 Design (as a) process 3 Distributions 4 Economies 5 Propositions 6 This book 7 Glossary 8 2 Diverted Derived Design Introduction The term open source is becoming popular among product designers. We see websites and initiatives appear with a lot of good intentions but sometimes missing the point and often creating confusion. Design magazines and blogs are always rushing into calling an openly published creation open source but rarely question the licenses or provide schematics or design files to download. We are furniture designers, hackers and artists who have been working with free/libre and open source software for quite some time. For us, applying these prirciples to product design was a natural extension, providing new areas to explore. But we also realized that designers coming to this with no prior open source experience had a lot of information to grasp before getting a clear picture of what could be open source product design. So we set ourselves to mobilize our knowledge in this book. We hope that this tool can be a base for teaching and learning about open source product design; a collective understanding of what one should know today to get started and join the movement; a reference students, amateurs and educators can have in their back pocket when they go out to explain what they are passionate about. How to read this book We have divided this book in sections that make sense for us. Each of these tries to address what we think is a general question you might have about open source product design.
    [Show full text]
  • Open Source Licensing Information for Cisco IOS Release 15.4(1)T
    Open Source Used In Cisco IOS Release 15.4(1)T Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-15140077 Open Source Used In Cisco IOS Release 15.4(1)T 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-15140077 Contents 1.1 bzip2 1.0.0 1.1.1 Available under license 1.2 C/C++ BEEP Core 0.2.00 1.2.1 Available under license 1.3 cd9660 8.18 1.3.1 Available under license 1.4 cthrift-without-GPL-code 0.3.14 1.4.1 Available under license 1.5 CUDD: CU Decision Diagram Package v2.4.1 1.5.1 Available under license 1.6 Cyrus SASL 2.1.0 1.6.1 Notifications 1.6.2 Available under license 1.7 DTOA unknown 1.7.1 Available under license 1.8 editline 1.11 1.8.1 Available under license 1.9 Expat XML Parser - Series 1 v1.2 1.9.1 Available under license 1.10 freebsd-tty-headers n/a 1.10.1 Available under license 1.11 ftp.h 4.4BSD? 1.11.1 Available under license 1.12 inflate.c c10p1 1.12.1 Available under license 1.13 iniparser 2.8 Open Source Used In Cisco IOS
    [Show full text]
  • Guide to Using Public Domain Tools
    Creative Commons makes sharing easy Public domain works are valuable because anyone What is the difference between can freely build upon, enhance, and reuse them for CC0 and the Public Domain Mark? any purposes without restriction under copyright or database law. CC0 (“CC Zero”) is intended for use only That’s why it’s important for creators to have a clear and by authors or holders of copyright and legally robust way to place their works in the public domain as related rights (including database rights), in connection Guide to completely as possible, and it’s also important for publishers with works that are still subject to those rights in one or and archives to have a standardized way to identify works that are already in the public domain. more countries. Creative Commons supports two distinct public domain tools, When CC0 is applied to a work, copyright and related using public rights are relinquished worldwide, making the work free the CC0 Public Domain Dedication and the Public Domain Mark. Creative Commons copyright licenses help authors from those restrictions to the greatest extent possible. manage their copyright on terms they choose. Conversely, CC0 domain tools enables authors and copyright owners who want to dedicate The Public Domain Mark (PDM) is used their works to the worldwide public domain to do so, and PDM to label works that are already free of facilitates the labeling and discovery of works that are already known copyright restrictions. Unlike CC0, PDM doesn’t free of known copyright restrictions. change the copyright status of a work.
    [Show full text]
  • Fifty Years of Open Source Movement: an Analysis Through the Prism of Copyright Law
    FIFTY YEARS OF OPEN SOURCE MOVEMENT: AN ANALYSIS THROUGH THE PRISM OF COPYRIGHT LAW V.K. Unni* I. INTRODUCTION The evolution of the software industry is a case study in itself. This evolution has multiple phases and one such important phase, termed open source, deals with the manner in which software technology is held, developed, and distributed.1 Over the years, open source software has played a leading role in promoting the Internet infrastructure and thus programs utilizing open source software, such as Linux, Apache, and BIND, are very often used as tools to run various Internet and business applications.2 The origins of open source software can be traced back to 1964–65 when Bell Labs joined hands with the Massachusetts Institute of Technology (MIT) and General Electric (GE) to work on the development of MULTICS for creating a dynamic, modular computer system capable of supporting hundreds of users.3 During the early stages of development, open source software had a very slow beginning primarily because of some preconceived notions surrounding it. Firstly, open source software was perceived as a product of academics and hobbyist programmers.4 Secondly, it was thought to be technically inferior to proprietary software.5 However, with the passage of time, the technical issues got relegated to the backside and issues pertaining to copyright, licensing, warranty, etc., began to be debated across the globe.6 * Professor—Public Policy and Management, Indian Institute of Management Calcutta; Thomas Edison Innovation Fellow (2016–17), Center for the Protection of Intellectual Property, George Mason University School of Law. 1.
    [Show full text]
  • Long-Term Sustainability of Open Source Software Communities Beyond a Fork: a Case Study of Libreoffice Jonas Gamalielsson, Björn Lundell
    Long-Term Sustainability of Open Source Software Communities beyond a Fork: A Case Study of LibreOffice Jonas Gamalielsson, Björn Lundell To cite this version: Jonas Gamalielsson, Björn Lundell. Long-Term Sustainability of Open Source Software Communities beyond a Fork: A Case Study of LibreOffice. 8th International Conference on Open Source Systems (OSS), Sep 2012, Hammamet, Tunisia. pp.29-47, 10.1007/978-3-642-33442-9_3. hal-01519071 HAL Id: hal-01519071 https://hal.inria.fr/hal-01519071 Submitted on 5 May 2017 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Distributed under a Creative Commons Attribution| 4.0 International License Long-term Sustainability of Open Source Software Communities beyond a Fork: a Case Study of LibreOffice Jonas Gamalielsson and Björn Lundell University of Skövde, Skövde, Sweden, {jonas.gamalielsson,bjorn.lundell}@his.se Abstract. Many organisations have requirements for long-term sustainable software systems and associated communities. In this paper we consider long- term sustainability of Open Source software communities in Open Source projects involving a fork. There is currently a lack of studies in the literature that address how specific Open Source software communities are affected by a fork.
    [Show full text]
  • Unlicense Yourself: Set Your Code Free
    Unlicense Yourself: Set Your Code Free Like 232 Follow on Tumblr 138 What is the Unlicense? The Unlicense is a template for disclaiming copyright monopoly interest in software you've written; in other words, it is a template for dedicating your software to the public domain. It combines a copyright waiver patterned after the very successful public domain SQLite project with the no-warranty statement from the widely-used MIT/X11 license. Why Use the Unlicense? Because you have more important things to do than enriching lawyers or imposing petty restrictions on users of your code. How often have you passed up on utilizing and contributing to a great software library just because its open source license was not compatible with your own preferred flavor of open source? How many precious hours of your life have you spent deliberating how to license your software or worrying about licensing compatibility with other software? You will never get those hours back, but here's your chance to start cutting your losses. Life's too short, let's get back to coding. The Unlicense To opt out of the copyright industry's game altogether and set your code free, put your next software project into the public domain using the following (un)licensing statement: This is free and unencumbered software released into the public domain. Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means. In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain.
    [Show full text]
  • 1. with Examples of Different Programming Languages Show How Programming Languages Are Organized Along the Given Rubrics: I
    AGBOOLA ABIOLA CSC302 17/SCI01/007 COMPUTER SCIENCE ASSIGNMENT ​ 1. With examples of different programming languages show how programming languages are organized along the given rubrics: i. Unstructured, structured, modular, object oriented, aspect oriented, activity oriented and event oriented programming requirement. ii. Based on domain requirements. iii. Based on requirements i and ii above. 2. Give brief preview of the evolution of programming languages in a chronological order. 3. Vividly distinguish between modular programming paradigm and object oriented programming paradigm. Answer 1i). UNSTRUCTURED LANGUAGE DEVELOPER DATE Assembly Language 1949 FORTRAN John Backus 1957 COBOL CODASYL, ANSI, ISO 1959 JOSS Cliff Shaw, RAND 1963 BASIC John G. Kemeny, Thomas E. Kurtz 1964 TELCOMP BBN 1965 MUMPS Neil Pappalardo 1966 FOCAL Richard Merrill, DEC 1968 STRUCTURED LANGUAGE DEVELOPER DATE ALGOL 58 Friedrich L. Bauer, and co. 1958 ALGOL 60 Backus, Bauer and co. 1960 ABC CWI 1980 Ada United States Department of Defence 1980 Accent R NIS 1980 Action! Optimized Systems Software 1983 Alef Phil Winterbottom 1992 DASL Sun Micro-systems Laboratories 1999-2003 MODULAR LANGUAGE DEVELOPER DATE ALGOL W Niklaus Wirth, Tony Hoare 1966 APL Larry Breed, Dick Lathwell and co. 1966 ALGOL 68 A. Van Wijngaarden and co. 1968 AMOS BASIC FranÇois Lionet anConstantin Stiropoulos 1990 Alice ML Saarland University 2000 Agda Ulf Norell;Catarina coquand(1.0) 2007 Arc Paul Graham, Robert Morris and co. 2008 Bosque Mark Marron 2019 OBJECT-ORIENTED LANGUAGE DEVELOPER DATE C* Thinking Machine 1987 Actor Charles Duff 1988 Aldor Thomas J. Watson Research Center 1990 Amiga E Wouter van Oortmerssen 1993 Action Script Macromedia 1998 BeanShell JCP 1999 AngelScript Andreas Jönsson 2003 Boo Rodrigo B.
    [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]
  • Copyright, an Incentive Or a Burden?
    Copyright, an Incentive or a Burden? Wolfgang Bein University of Nevada Las Vegas, USA, [email protected] Abstract A copyright provides protection for original artistic or literary work and is valid for the life of the owner plus 70 years. There is a growing tension between creative practices that require access to content that is often copyrighted, and increasingly restrictive intellectual property laws and policies governing access to copyrighted content. Very recently this has played out in the law suit between the media corporation Viacom and the Internet portal YouTube, which is owned by Google. This is against the background of a steadily emerging open source and creative commons culture. Milestones in the open source movement are the OpenOffice office suite, Netscape’s publication of the source code for its product as open software, Google’s library project, various free archives for scientific dissemination, such as Cornell University’s ArXiv. I. INTRODUCTION The gap between the cost of digital media and storage, and a copyrighted digital item (a CD or DVD) continually increases, as Internet is readily available, and the price of digitally duplicating anything capable of being transmitted via digital media dropped to near zero [1]. The use of a copyrighted material is less restrictive than other intellectual properties (patents, trademarks, service marks), even though the copyrighted material cannot be photocopied, scanned or copied in any way. But portions of it can be used for non-commercial purposes. The First Sale Doctrine (Copyright Act, 1976) does allow you to resell or give away the copy of the copyrighted item you bought.
    [Show full text]