DOCSLIB.ORG

An Overview of Open-Source Software Licenses and the Value of Open-Source Software to Public Health Initiatives

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
An Overview of Open-Source Software Licenses and the Value of Open-Source Software to Public Health Initiatives An Overview of Open-Source Software Licenses and the Value of Open-Source Software to Public Health Initiatives Erin N. Hahn he use of open-source software (OSS) has dramatically increased in the past several years, particularly in the public health domain. The Johns Hopkins Uni- versity Applied Physics Laboratory’s (APL) work on developing and licens- ing OSS identified a need within the public health community to better understand the definition and connotations of the words open source and the various open-source licenses. The use of OSS in the public health domain can dramatically improve the implementation of mobile and electronic health initiatives in resource-limited settings because OSS provides an affordable alternative to costly proprietary software. INTRODUCTION The term open source generally refers to software that In the past several years, the use of OSS in the public is made readily available by an individual or group for health field has grown dramatically. In particular, the others to use, modify, or redistribute under a licensing field of mobile health, or mHealth, has seen a substantial agreement with very few restrictions. Anyone can use increase in the use of OSS due to the ubiquitous nature the software without having to pay royalties or negoti- of cellular telephones.3 By definition, mHealth refers to ate a license agreement. Open-source software (OSS) is “the practice of medicine and public health, supported by not a new creation, but it has been used with increasing mobile devices.”4 In general, it involves the use of “mobile popularity in large-scale commercial software projects in communication devices, such as mobile phones and recent years. It has been called “the software that runs PDAs, for health services and information.”5 Many of the Internet,” referring to its significant use in the Inter- these platforms and associated tools, whose primary users net’s infrastructure, including the Apache Web server, are those in the field of public health or clinical care, the Mozilla browser, and Linux operating system.1 There are purportedly open source. However, in a community are currently at least 50 different open-source licenses, that is generally not as savvy in information technology, and they represent a unique approach to licensing when the term open source is confusing and leaves many unan- compared with licenses normally used in a commer- swered questions. The Johns Hopkins University Applied cial environment. (See Table 1 for a listing of licenses Physics Laboratory (APL), in conjunction with the Global by name.2) Emerging Infections Surveillance and Response System, 690 JOHNS HOPKINS APL TECHNICAL DIGEST, VOLUME 32, NUMBER 4 (2014) a division of the U.S. Armed Forces Health Surveillance has the right to change the source code. The term copyleft Center (AFHSC-GEIS), has been working to develop and was generated by the free software community and is the deploy open-source disease surveillance capabilities in term for a license condition that ensures that all modified resource-limited settings. In the course of this work, APL versions of the software can be copied, modified, and/or and AFHSC-GEIS identified a need to better understand distributed in the same way as the original. By ensuring the definition, nuances, and connotations of the term that downstream users receive source code and permis- open source within the public health community. sion to modify it, a copyleft license is said to keep code The purpose of this article is to provide an introduc- “forever free.”7 Not all open-source licenses have copyleft tion to open-source licensing and the main elements provisions, but many do. Despite what the name may to consider when determining whether to use OSS or imply, copyleft is still a license and is enforced by copy- when selecting an open-source license. In particular, it right law. Instead of withholding permission to copy or provides examples of the use of open-source licensing in modify a work (as in the traditional sense of a copyright), the development tools used in the public health domain. copyleft uses copyright law to actually require that those This article also provides background on copyright and permissions be granted. the distinction between a copyright and a license, a dis- It is important to note that using an open-source cussion of the history of open source and “free software” license is not the same as placing the software in the (terms that are often used interchangeably and also fre- public domain. The terms of the open source license quently consolidated and referred to as FOSS, or Free and must be met, and the copyright holder retains rights to Open-Source Software), and an overview of commonly the work. If the terms of the open-source license are not used licenses with strong user communities. It also dis- met (e.g., the same licensing provisions are not applied to cusses several myths related to the benefits and hazards of derivative works), the copyright has been infringed and using open-source licenses and OSS and provides exam- the copyright holder has certain legal remedies available ples of how government agencies are confronting these to him or her.5 No matter how permissive the open-source myths and successfully using OSS to their advantage. license, the copyright holder’s interests are protected. If the software is released into the public domain, the author surrenders the copyright. Put another way, as soon BACKGROUND ON COPYRIGHT as software code is created and saved, a copyright attaches Copyright is a form of intellectual property law and to the work. Placing the software in the public domain protects original works of authorship.5, 6 All software is relinquishes all rights associated with the work. It is not subject to copyright law, and as soon as source code is cre- equivalent to granting a license because the author is not ated, anyone (other the author) who wants to use it must limiting or placing restrictions on the use of the software obtain explicit permission from the author. (As soon as in any way. In fact, software placed in the public domain a work is created and “fixed in a tangible form that is can be used, modified, and removed from the public 5 perceptible either directly or with the aid of a machine domain by another user asserting copyright ownership. or device,” it is protected by copyright.1, 6, 7) Copyright is how an author retains control over his or her work. Software copyright is “the exclusive legal right to control FREE VERSUS OPEN SOFTWARE the rules for copying, modifying, and distributing a work The terms free software and open software are often of software.”7 The person or organization that has the used interchangeably, and they are also frequently con- right to control the work is called the copyright holder. solidated and referred to as FOSS. However, although a When copyright holders permit others to use, modify, or majority of software is both open and free, there are dis- distribute their software, they have granted a license.7 tinctions to be made between the two categories, both The license is the permission to use the software in some in philosophy and in the licenses that fall within each. way—it can be an unconditional grant of permission The free software movement is, at its roots, about the that mirrors the rights of the copyright holder or a con- users’ freedoms, whereas open source focuses on making ditional grant of permission that allows individuals to software better from a practical perspective by allowing copy or use the software according to certain provisions. access to the code so that others to improve it. These Open-source licenses fall into both categories. two views may lead to the same outcome in how the A general commercial copyright license usually pro- software is treated from a copyright perspective, but the tects the copyright holder’s interests by placing restric- goals for getting to that outcome are slightly different. tions on how the software can be used. For example, a (For a comprehensive overview of free software and commercial software license usually prohibits the copying OSS, see Ref. 8.) or modification of the software, mainly by distributing The concept of free software began in 1984 with only the machine-readable binary or object code. OSS Richard Stallman, a Massachusetts Institute of Tech- licenses give users more rights than a general commercial nology (MIT) researcher. Stallman was concerned that license because the user gets access to the source code and computing would be dominated by a few powerful people JOHNS HOPKINS APL TECHNICAL DIGEST, VOLUME 32, NUMBER 4 (2014) 691 E. N. HAHN if software were all proprietary. He considered software “1. Free Redistribution. The license shall not restrict scientific knowledge that should be shared and distrib- any party from selling or giving away the software as uted to further innovation in computer science. In 1984, a component of an aggregate software distribution he left MIT and began the GNU Project and the Free containing programs from several different sources. Software Foundation (GNU is a recursive acronym for The license shall not require a royalty or other fee “GNU’s Not Unix”). One goal of the GNU Project was for such sale. the development of a freely available operating system 8 2. Source Code. The program must include source that could run GNU software. code, and must allow distribution in source code as The most important characteristic of free software is well as compiled form. Where some form of a prod- the underlying philosophy for why software should be uct is not distributed with source code, there must be free and what free means.
Load more

Recommended publications
  • Easy As Abc: Categorizing Open Source Licenses
    EASY AS ABC: CATEGORIZING OPEN SOURCE LICENSES Andrew T. Pham1, Matthew B. Weinstein2, Jamie L. Ryerson3 With more than 180,000 open source projects available and its more than 1400 unique licenses, the complexity of deciding how to manage open source usage within “closed-source” commercial enterprises have dramatically increased.4 Because of the complexity and risks associated with open source—where source code is made freely available for all to review, edit, and use—many closed-source commercial enterprises discourage or prohibit use of open source; a common and short-sighted practice. With a proper open source management framework, open source can be an invaluable resource, and its risks can be understood, managed and controlled. This article proposes a simple, consistent and effective open source categorization and management system to enable a peaceful coexistence between open source and closed-source codes. Free and open source software (“FOSS” or collectively “open source”) is a valuable tool, but one that must be understood to be used effectively. The litany of risks associated with use of open source include: having to release a derivative product incorporating open source under the same open source license; incorporating code that infringes a patent; violating an open source license’s attribution requirements; and a lack of warranties and indemnities. Given the extensive investment of time, money and resources that goes into product development, it comes as no This article is an edited version of the original, which dealt not only with categorizing open source licenses but also a wider array of issues associated with implementing an open source policy.
    [Show full text]
  • Webroot Brightcloud® SDK for C and C++ Sdks Apache License 2.0
    Webroot BrightCloud® SDK For C and C++ SDKs Apache License 2.0 • Apache Portable Runtime Utilities (APR-util) Copyright © 2008-2018, The Apache Software Foundation • Apache Portable Runtime Utilities 1.2.12 (APR-util) Copyright © 2008-2018, The Apache Software Foundation • X Delta 3.0.3 Copyright (C) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015 [email protected] Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. “License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. “Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. “Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. “You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License. “Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. “Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
    [Show full text]
  • 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]
  • Artistic License
    Perl version 5.10.0 documentation - perlartistic NAME perlartistic - the Perl Artistic License SYNOPSIS You can refer to this document in Pod via "L<perlartistic>" Or you can see this document by entering "perldoc perlartistic" DESCRIPTION This is "The Artistic License". It's here so that modules,programs, etc., that want to declare this as their distributionlicense, can link to it. It is also one of the two licenses Perl allows itself to beredistributed and/or modified; for the other one, the GNU GeneralPublic License, see the perlgpl. The "Artistic License" Preamble The intent of this document is to state the conditions under which aPackage may be copied, such that the Copyright Holder maintains somesemblance of artistic control over the development of the package,while giving the users of the package the right to use and distributethe Package in a more-or-less customary fashion, plus the right to makereasonable modifications. Definitions "Package" refers to the collection of files distributed by theCopyright Holder, and derivatives of that collection of files createdthrough textual modification. "Standard Version" refers to such a Package if it has not beenmodified, or has been modified in accordance with the wishes of theCopyright Holder as specified below. "Copyright Holder" is whoever is named in the copyright orcopyrights for the package. "You" is you, if you're thinking about copying or distributing this Package. "Reasonable copying fee" is whatever you can justify on the basisof media cost, duplication charges, time of people involved, and so on.(You will not be required to justify it to the Copyright Holder, butonly to the computing community at large as a market that must bear thefee.) "Freely Available" means that no fee is charged for the itemitself, though there may be fees involved in handling the item.
    [Show full text]
  • End User License Agreement
    MICROSOFT SOFTWARE LICENSE TERMS WINDOWS EMBEDDED STANDARD 7 These license terms are an agreement between you and YSI incorporated. Please read them. They apply to the software included on this device. The software also includes any separate media on which you received the software. The software on this device includes software licensed from Microsoft Corporation or its affiliate. The terms also apply to any Microsoft • updates, • supplements, • Internet-based services, and • support services for this software, unless other terms accompany those items. If so, those terms apply. If you obtain updates or supplements directly from Microsoft, then Microsoft, and not YSI incorporated, licenses those to you. As described below, using the software also operates as your consent to the transmission of certain computer information for Internet-based services. By using the software, you accept these terms. If you do not accept them, do not use the software. Instead, contact YSI incorporated to determine its return policy for a refund or credit. If you comply with these license terms, you have the rights below. 1. USE RIGHTS Use. The software license is permanently assigned to the device with which you acquired the software. You may use the software on the device. 2. ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS a. Specific Use. YSI incorporated designed the device for a specific use. You may only use the software for that use. b. Other Software. You may use other programs with the software as long as the other programs directly supports the manufacturer’s specific use for the device, or provide system utilities, resource management, or anti-virus or similar protection.
    [Show full text]
  • ¢¡¤ £¦ ¥ ¡ £ ¥ ¡ £ ¥ ¡ £ ¥ Red Hat §© ¨ / ! " #%$'& ( ) 0 1! 23 % 4'5 6!7 8 9 @%
    ¢¡¤£¦¥ ¢¡¤£¦¥ ¢¡¤£¦¥ Subscription Agreement ¢¡¤£¦¥ ! PLEASE READ THIS AGREEMENT CAREFULLY BEFORE Red Hat §©¨ / PURCHASING OR USING RED HAT PRODUCTS AND "# $% &' ()*+ §©¨ ,- . Red Hat / # # SERVICES. BY USING OR PURCHASING RED HAT # 2©3 456 7 80 9: /.10 PRODUCTS OR SERVICES, CLIENT SIGNIFIES ITS ASSENT ;< 2=©>0 ?@ 'A BC© DE F©G ?1 . TO THIS AGREEMENT. IF YOU ARE ACTING ON BEHALF HI BC© D©: J !K CLM NO1 (P4 Q1RK HI OF AN ENTITY, THEN YOU REPRESENT THAT YOU HAVE STU >0 VWK XY Z1K F©G THE AUTHORITY TO ENTER INTO THIS AGREEMENT ON . 456 , §©¨ ,- M X [!\>0 BEHALF OF THAT ENTITY. IF CLIENT DOES NOT ACCEPT 45©3 Red Hat / THE TERMS OF THIS AGREEMENT, THEN IT MUST NOT PURCHASE OR USE RED HAT PRODUCTS AND SERVICES. @ = ©] ^ _`a b c d e e f gf g 3 e f gf g This Subscription Agreement, including all schedules and e (“ ”) Red Hat Limited hi appendices hereto (the "Agreement"), is between Red Hat # Y j § VWK X k (“Red Hat”) ] Red Hat Limited, Korea Branch ("Red Hat") and the purchaser or user of # §©¨ ©9 9 l ml m n CLo0 l m / (“ l m ”) . Red Hat products and services that accepts the terms of this # pq/r stvustvu 3 456 w,- stvustvu (“ ”) h h Agreement (“Client”). The effective date of this Agreement # !K X k r!9x 456 §©¨ Red Hat / (“Effective Date”) is the earlier of the date that Client signs or h 0 y z{ + |} accepts this Agreement or the date that Client uses Red Hat's r!9 . products or services.
    [Show full text]
  • An Introduction to Software Licensing
    An Introduction to Software Licensing James Willenbring Software Engineering and Research Department Center for Computing Research Sandia National Laboratories David Bernholdt Oak Ridge National Laboratory Please open the Q&A Google Doc so that I can ask you Michael Heroux some questions! Sandia National Laboratories http://bit.ly/IDEAS-licensing ATPESC 2019 Q Center, St. Charles, IL (USA) (And you’re welcome to ask See slide 2 for 8 August 2019 license details me questions too) exascaleproject.org Disclaimers, license, citation, and acknowledgements Disclaimers • This is not legal advice (TINLA). Consult with true experts before making any consequential decisions • Copyright laws differ by country. Some info may be US-centric License and Citation • This work is licensed under a Creative Commons Attribution 4.0 International License (CC BY 4.0). • Requested citation: James Willenbring, David Bernholdt and Michael Heroux, An Introduction to Software Licensing, tutorial, in Argonne Training Program on Extreme-Scale Computing (ATPESC) 2019. • An earlier presentation is archived at https://ideas-productivity.org/events/hpc-best-practices-webinars/#webinar024 Acknowledgements • This work was supported by the U.S. Department of Energy Office of Science, Office of Advanced Scientific Computing Research (ASCR), and by the Exascale Computing Project (17-SC-20-SC), a collaborative effort of the U.S. Department of Energy Office of Science and the National Nuclear Security Administration. • This work was performed in part at the Oak Ridge National Laboratory, which is managed by UT-Battelle, LLC for the U.S. Department of Energy under Contract No. DE-AC05-00OR22725. • This work was performed in part at Sandia National Laboratories.
    [Show full text]
  • Crowdsourcing: Today and Tomorrow
    Crowdsourcing: Today and Tomorrow An Interactive Qualifying Project Submitted to the Faculty of the WORCESTER POLYTECHNIC INSTITUTE in partial fulfillment of the requirements for the Degree of Bachelor of Science by Fangwen Yuan Jun Liang Zhaokun Xue Approved Professor Sonia Chernova Advisor 1 Abstract This project focuses on crowdsourcing, the practice of outsourcing activities that are traditionally performed by a small group of professionals to an unknown, large community of individuals. Our study examines how crowdsourcing has become an important form of labor organization, what major forms of crowdsourcing exist currently, and which trends of crowdsourcing will have potential impacts on the society in the future. The study is conducted through literature study on the derivation and development of crowdsourcing, through examination on current major crowdsourcing platforms, and through surveys and interviews with crowdsourcing participants on their experiences and motivations. 2 Table of Contents Chapter 1 Introduction ................................................................................................................................. 8 1.1 Definition of Crowdsourcing ............................................................................................................... 8 1.2 Research Motivation ........................................................................................................................... 8 1.3 Research Objectives ...........................................................................................................................
    [Show full text]
  • Software Licensing in the Cloud Age Solving the Impact of Cloud Computing on Software Licensing Models
    The International Journal of Soft Computing and Software Engineering [JSCSE], Vol. 3, No. 3, Special Issue: The Proceeding of International Conference on Soft Computing and Software Engineering 2013 [SCSE’13], San Francisco State University, CA, U.S.A., March 2013 Doi: 10.7321/jscse.v3.n3.60 e-ISSN: 2251-7545 Software Licensing in the Cloud Age Solving the Impact of Cloud Computing on Software Licensing Models Malcolm McRoberts Enterprise Architecture Core Technology Center Harris Corporation GCSD Melbourne, Florida, USA [email protected] Abstract—Cloud computing represents a major shift in identify key issues that require the attention of the industry information systems architecture, combining both new as a whole. deployment models and new business models. Rapid provisioning, elastic scaling, and metered usage are essential A. Characteristics of Cloud Computing (Benefits) characteristics of cloud services, and they require cloud According to the National Institute of Standards and resources with these same characteristics. When cloud services Technology (NIST) [1], cloud computing is a model for depend on commercial software, the licenses for that software enabling ubiquitous, convenient, on-demand network access become another resource to be managed by the cloud. This to a shared pool of configurable computing resources (e.g., paper examines common licensing models, including open networks, servers, storage, applications, and services) that source, and how well they function in a cloud services model. It can be rapidly provisioned and released with minimal discusses creative, new, cloud-centric licensing models and how management effort or service provider interaction. they allow providers to preserve and expand their revenue This translates to a number of benefits for large and small streams as their partners and customers transition to the organizations alike, as well as for individuals.
    [Show full text]
  • Building Online Content and Community with Drupal
    Collaborative Librarianship Volume 1 Issue 4 Article 10 2009 Building Online Content and Community with Drupal Gabrielle Wiersma University of Colorado at Boulder, [email protected] Follow this and additional works at: https://digitalcommons.du.edu/collaborativelibrarianship Part of the Collection Development and Management Commons Recommended Citation Wiersma, Gabrielle (2009) "Building Online Content and Community with Drupal," Collaborative Librarianship: Vol. 1 : Iss. 4 , Article 10. DOI: https://doi.org/10.29087/2009.1.4.10 Available at: https://digitalcommons.du.edu/collaborativelibrarianship/vol1/iss4/10 This Review is brought to you for free and open access by Digital Commons @ DU. It has been accepted for inclusion in Collaborative Librarianship by an authorized editor of Digital Commons @ DU. For more information, please contact [email protected],[email protected]. Wiersma: Building Online Content and Community with Drupal Building Online Content and Community with Drupal Gabrielle Wiersma ([email protected]) Engineering Research and Instruction Librarian, University of Colorado at Boulder Libraries use content management systems Additionally, all users are allowed to post in order to create, manage, edit, and publish content without using code, which enables content on the Web more efficiently. Drupal less tech savvy users to contribute content (drupal.org), one such Web-based content just as easily as their more proficient coun- management system, is unique because it terparts. For example, a library could use employs a bottom-up strategy for Web de- Drupal to allow library staff to view and sign that separates the content of the site edit the library Web site, blog, and staff from the formatting which means that “you intranet.
    [Show full text]
  • Unravel Data Systems Version 4.5
    UNRAVEL DATA SYSTEMS VERSION 4.5 Component name Component version name License names jQuery 1.8.2 MIT License Apache Tomcat 5.5.23 Apache License 2.0 Tachyon Project POM 0.8.2 Apache License 2.0 Apache Directory LDAP API Model 1.0.0-M20 Apache License 2.0 apache/incubator-heron 0.16.5.1 Apache License 2.0 Maven Plugin API 3.0.4 Apache License 2.0 ApacheDS Authentication Interceptor 2.0.0-M15 Apache License 2.0 Apache Directory LDAP API Extras ACI 1.0.0-M20 Apache License 2.0 Apache HttpComponents Core 4.3.3 Apache License 2.0 Spark Project Tags 2.0.0-preview Apache License 2.0 Curator Testing 3.3.0 Apache License 2.0 Apache HttpComponents Core 4.4.5 Apache License 2.0 Apache Commons Daemon 1.0.15 Apache License 2.0 classworlds 2.4 Apache License 2.0 abego TreeLayout Core 1.0.1 BSD 3-clause "New" or "Revised" License jackson-core 2.8.6 Apache License 2.0 Lucene Join 6.6.1 Apache License 2.0 Apache Commons CLI 1.3-cloudera-pre-r1439998 Apache License 2.0 hive-apache 0.5 Apache License 2.0 scala-parser-combinators 1.0.4 BSD 3-clause "New" or "Revised" License com.springsource.javax.xml.bind 2.1.7 Common Development and Distribution License 1.0 SnakeYAML 1.15 Apache License 2.0 JUnit 4.12 Common Public License 1.0 ApacheDS Protocol Kerberos 2.0.0-M12 Apache License 2.0 Apache Groovy 2.4.6 Apache License 2.0 JGraphT - Core 1.2.0 (GNU Lesser General Public License v2.1 or later AND Eclipse Public License 1.0) chill-java 0.5.0 Apache License 2.0 Apache Commons Logging 1.2 Apache License 2.0 OpenCensus 0.12.3 Apache License 2.0 ApacheDS Protocol
    [Show full text]
  • Open Source Software Notice
    Open Source Software Notice This document describes open source software contained in LG Smart TV SDK. Introduction This chapter describes open source software contained in LG Smart TV SDK. Terms and Conditions of the Applicable Open Source Licenses Please be informed that the open source software is subject to the terms and conditions of the applicable open source licenses, which are described in this chapter. | 1 Contents Introduction............................................................................................................................................................................................. 4 Open Source Software Contained in LG Smart TV SDK ........................................................... 4 Revision History ........................................................................................................................ 5 Terms and Conditions of the Applicable Open Source Licenses..................................................................................... 6 GNU Lesser General Public License ......................................................................................... 6 GNU Lesser General Public License ....................................................................................... 11 Mozilla Public License 1.1 (MPL 1.1) ....................................................................................... 13 Common Public License Version v 1.0 .................................................................................... 18 Eclipse Public License Version
    [Show full text]