DOCSLIB.ORG

Licensing-In Keep Track of Third-Party Components; Manage Their Compatibility

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Licensing-In Keep Track of Third-Party Components; Manage Their Compatibility Challenges in Software Licensing You can do IT. Entrepreneurship in IT and Maths Saarbrücken, 06 June 2018 Sigmar Lampe Counsel IP and Licensing European Patent and Trademark Attorney Technology Transfer Office University of Luxembourg 1 Outline 1. Defining software – what is it? 2. Intellectual property rights (IPR) in software 3. Free and open source software (FOSS) vs. proprietary software 4. Software licence compliance 5. Licensing models 6. Examples 7. Take home messages 2 1. Defining software 3 Computer System HARDWARE SOFTWARE (physical) (logial) 4 ASTP-Proton Annual Conference 2016 25 – 27 May, Copenhagen, Denmark Software:Software: broad broaD meaningmeaning Software: narrow meaning Databases Data Databases Data Graphic Graphic Document Document user user libraries libraries interface interface Computer Software Computer Software … … programs (electronic) programs (electronic) 5 Elements of computer program Functionality Data files Preparatory Computer Design work programs Programming statements Algorithms IPR IN SOFTWARE Programming language 2 ASTP-Proton Annual Conference 2016 25 – 27 May, Copenhagen, Denmark Software: broaD meaning Software:Software: narrow narrow meaningmeaning Databases Data Databases Data Graphic Graphic Document Document user user libraries libraries interface interface Computer Software Computer Software … … programs (electronic) programs (electronic) 6 Elements of computer program Functionality Data files Preparatory Computer Design work programs Programming statements Algorithms IPR IN SOFTWARE Programming language 2 ASTP-Proton Annual Conference 2016 25 – 27 May, Copenhagen, Denmark Software: broaD meaning Software: narrow meaning Databases Data Databases Data Graphic Graphic Document Document user user libraries libraries interface interface Computer Software Computer Software … … programs (electronic) programs (electronic) ElementsElements of of a computerComputer program Program Functionality Data files Preparatory Computer Design work programs Programming statements Algorithms IPR IN SOFTWARE Programming language 7 2 2. Intellectual property rights in software 8 ASTP-Proton Annual Conference 2016 25 – 27 May, Copenhagen, Denmark IPRIPR inin elementselements ofof computer computer programprogram Legal definition of computer program • Usually not defined in legal acts, except: – US copyright law: A “computer program” is a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result. (17 U.S. Code § 101 – Definitions) Source: European IPR Helpdesk. Fact Sheet. IPR management in software development. June Source: European IPR Helpdesk. FactSheet. IPR management in software development. June 2013 https://www.iprhelpdesk.eu/Fact-Sheet-IPR-Management-in-Software-Development2013 - http s:/ /www.i prh el pd es k.eu / Fact-Sheet-IPR-Management -in-Software-Development 9 Protected elements of a computer Protected vs non-protected elements program according to legal acts of software in court practice • TRIPS: Copyright Patent Computer programs, whether in source or object code, shall be protected as literary works under the Berne Convention (1971) (TRIPS art 10 (1)) USA/Europe: USA: • Berne Convention: X Preparatory design material X Computer program „as such“ The expression “literary and artistic works” shall include every production X Expression of programming statements USA/Europe: and/or instructions in the literary, scientific and artistic domain, whatever may be the mode or X Computer program as part of form of its expression, such as books, pamphlets and other writings […] USA/Europe: (medical) devices (computer- (Berne Convention art 2 (1)) £ Ideas and principles which underlie any implemented inventions) element of a program, including those • Directive 2009/24/EC of the European Parliament and of the which underlie its interfaces Council £ Functionality USA/Europe: For the purpose of this Directive, the term ‘computer program’ shall £ Logic, algorithms £ Abstract ideas include programs in any form, including those which are incorporated £ Programming language £ Mathematical formulae into hardware. This term also includes preparatory design work leading £ Format of data files £ Natural phenomena to the development of a computer program provided that the nature of £ Database* £ Business methods the preparatory work is such that a computer program can result from it £ Graphic user interfaces, application Europe: at a later stage (Directive 2009/24/EC recital (7); see also art 1) programming interfaces* £ User manuals, guidelines, other £ Computer program „as such“ documentation* 3 Legal definition: “computer program” Usually not defined in legal acts, except: US copyright law: • A “computer program” is a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result. (17 U.S. Code § 101 – Definitions) 10 Protected elements (legal acts) TRIPS, art. 10(1) (1971) Computer programs, whether in source or object code, shall be protected as literary works under the Berne Convention Berne Convention, art. 2(1): The expression “literary and artistic works” shall include every production in the literary, scientific and artistic domain, whatever may be the mode or form of its expression, such as books, pamphlets and other writings [...] European “Software” Directive 2009/24/EC, recital (7), art. 1) For the purpose of this Directive, the term ‘computer program’ shall include programs in any form, including those which are incorporated into hardware. This term also includes preparatory design work leading to the development of a computer program 11 Protected vs. non-protected elements COPYRIGHT ≠ PATENT USA and Europe USA + Preparatory design material + Machine-transformation test + Expression of programming statements and/or instructions Europe – Ideas and principles which underlie + Further technical effect any element of a program, including – Computer program „as such“ those which underlie its interfaces – Functionality USA and Europe – Logic, algorithms + Computer program as part of devices – Programming language (computer-implemented inventions) – Format of data files – Abstract ideas – Graphic user interfaces, application – Mathematical formulae programming interfaces* – Natural phenomena – Database* – Business methods – User manuals, guidelines, other documentation* (* own law) 12 Forms of computer program SOURCE CODE OBJECT CODE 13 Modular architecture NEW CODE PRE-EXISTING (UNMODIFIED) CODE MODIFIED PRE-EXISTING CODE 14 Multiple ownership UNIVERSITY OPEN-SOURCE SPIN-OFF COMMUNITY COMPANY 3RD PARTY COMMERCIAL PROVIDER 15 Multiple licences F/OSS LICENCEF/OSS LICENCEF/OSS LICENCE CUSTOMISED PROPRIETARYCUSTOMISED PROPRIETARYLICENCE LICENCE 3RD PARTY RD COMMERCIAL3 PARTY COMMERCIALLICENCE LICENCE 16 Software Function (impact) Data Code Structure Name Graphics Software !17 Software Protection A brief review of IPRs relevant for software: 1. Patents 2. Copyright 3. Trademarks 4. Designs 5. Databases 18 A review of Industrial Property Rights (IPR) Legal right What for? How? Application and Patents New technical inventions examination Original creative or artistic Copyright Exists automatically forms Distinctive identification of Use and/or Trade marks products or services registration Registered External appearance Registration designs Valuable information not Reasonable efforts to Trade secrets known to the public keep secret 19 Patent • negative right = exclusivity • prevent others from • making • using • selling or offering for sale • importing • in countries for which the patent was granted • for a limited time (up to 20 years) 20 Requirements for a patent to be granted The invention must • be absolutely new on a worldwide basis • involve an inventive step (not obvious to skilled person) and • be susceptible to industrial application Sufficiency of disclosure: • the invention must be described in sufficient detail • description must be comprehensible to a “person skilled in the 21 What can’t be protected? PROGRAMS FOR COMPUTERS ! • However, could be patentable, unless it is a computer program “as such” If the program is purely of abstract or intellectual character: • only non-technical aspects à no invention ✘ à no patent ✘ If the program implements a technical solution to a (technical) problem: • “computer-implemented invention” • see: novelty, inventive step à identify technical aspects à examine technical aspects of invention à patentable, if novelty and inventive step confirmed ✔ (❓ ) 22 Computer implemented inventions: Examples • control of machines or industrial processes • control of the internal processes in a computer • helps to use resources in a computer more efficiently, or increases its performance • increases the safety of the computer • makes a computer system easier to use • improves the transmission or storage of data • technical considerations were necessary • provides a device with new functionality computer program: patentable under certain conditions Attention - always required: novelty + inventive step! 23 Copyright Negative right = exclusivity Economic rights for author: • reproducing • modifying (software) • distributing These rights are freely transferable or licensable, per country Moral rights for author (moral interest) • modifying (literary/artistic works) • authorship 24 Copyright and Software Traditional view (1960-1970): source code can be fixed in writing, but object code is virtual (in computer memory) WIPO Copyright Treaty (WCT) 1996, Articles 4 and
Load more

Recommended publications
  • Python 2.6.2 License 04.11.09 14:37
    Python 2.6.2 license 04.11.09 14:37 Download > Releases > License Python 2.6.2 license This is the official license for the Python 2.6.2 release: A. HISTORY OF THE SOFTWARE ========================== Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands as a successor of a language called ABC. Guido remains Python's principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see http://www.cnri.reston.va.us) in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations (now Zope Corporation, see http://www.zope.com). In 2001, the Python Software Foundation (PSF, see http://www.python.org/psf/) was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation is a sponsoring member of the PSF. All Python releases are Open Source (see http://www.opensource.org for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the table below summarizes the various releases. Release Derived Year Owner GPL- from compatible? (1) 0.9.0 thru 1.2 1991-1995 CWI yes 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes 1.6 1.5.2 2000 CNRI no 2.0 1.6 2000 BeOpen.com no 1.6.1
    [Show full text]
  • Ironpython in Action
    IronPytho IN ACTION Michael J. Foord Christian Muirhead FOREWORD BY JIM HUGUNIN MANNING IronPython in Action Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> IronPython in Action MICHAEL J. FOORD CHRISTIAN MUIRHEAD MANNING Greenwich (74° w. long.) Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact Special Sales Department Manning Publications Co. Sound View Court 3B fax: (609) 877-8256 Greenwich, CT 06830 email: [email protected] ©2009 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15% recycled and processed without the use of elemental chlorine.
    [Show full text]
  • Diapositiva 1
    Chini Gianalberto 17.04.2008 ` Python Software Foundation License was created in early 1990s and the main author is Guido van Rossum. The last version is 2.4.2 released 2005 by PSF (Python Software Foundation). ` The major purpose of PSFL is to protect the Python project software. ` PSFL is a permissive free software license that allows “a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 2.4 alone or in any derivative version” (PSFL) ` This means... ` Python is free and you can distribute for free or sell every product written in python. ` You can insert the interpreter in all applications you want without to pay. ` You can modify and redistribute software derived from Python. ` PSFL copyright notice must be retained in every distribution of python or in every derivative version of python. This clause is in guarantee of python creator’s copyright. ` The main difference between GPLv3 and PSFL is that the first one is copyleft in contrast with PSFL. ` Since PSFL is a copyleft license, it isn’t required that the source code must be necesserely released. ` Only binary code of python or derivative works can be distribuited. ` Only binary code of python modules can be distribuited. ` But… PSFL is fully compatible with GPLv3 ` The 1.6.1PSFL version is not GPL-compatible because “the primary incompatibility is that this Python license is governed by the laws of the State of Virginia, in the USA, and the GPL does not permit this.” (Free Software Foundation).
    [Show full text]
  • Mysql NDB Cluster 7.5.16 (And Later)
    Licensing Information User Manual MySQL NDB Cluster 7.5.16 (and later) Table of Contents Licensing Information .......................................................................................................................... 2 Licenses for Third-Party Components .................................................................................................. 3 ANTLR 3 .................................................................................................................................... 3 argparse .................................................................................................................................... 4 AWS SDK for C++ ..................................................................................................................... 5 Boost Library ............................................................................................................................ 10 Corosync .................................................................................................................................. 11 Cyrus SASL ............................................................................................................................. 11 dtoa.c ....................................................................................................................................... 12 Editline Library (libedit) ............................................................................................................. 12 Facebook Fast Checksum Patch ..............................................................................................
    [Show full text]
  • 1. Scope 1.1 This Agreement Applies to the Celllibrarian Software Products You May Install Or Use (The “Software Product”)
    Yokogawa Software License Agreement for CQ1TM, CellVoyager®, CellPathfinderTM, CellLibrarianTM IMPORTANT - PLEASE READ CAREFULLY BEFORE INSTALLING OR USING: THIS AGREEMENT IS A LEGAL AGREEMENT BETWEEN YOU AND YOKOGAWA ELECTRIC CORPORATION AND/OR ITS SUBSIDIARIES (COLLECTIVELY, “YOKOGAWA”) FOR YOU TO INSTALL OR USE YOKOGAWA SOFTWARE PRODUCT. BY INSTALLING OR OTHERWISE USING THE SOFTWARE PRODUCT, YOU AGREE TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE, DO NOT INSTALL NOR USE THE SOFTWARE PRODUCT AND PROMPTLY RETURN IT TO THE PLACE OF PURCHASE FOR A REFUND, IF APPLICABLE. SHOULD THERE BE ANY DISCREPANCY BETWEEN THIS AGREEMENT AND ANY OTHER WRITTEN AGREEMENT MADE BETWEEN YOU AND YOKOGAWA, THE LATTER SHALL PREVAIL. 1. Scope 1.1 This Agreement applies to the CellLibrarian software products you may install or use (the “Software Product”). The Software Product consists of: a) Standard Software Product: The software products listed in "General Specifications" of Yokogawa. b) Customized Software Product: The software products made by Yokogawa based on individually agreed specifications, which will be used with or in addition to the function of the Standard Software Product. 1.2 The Software Product includes, without limitation, computer programs, key codes, manuals and other associated documents, databases, fonts, input data, and any images, photographs, animations, video, voice, music, text, and applets (software linked to text and icons) embedded in the software. 1.3 Unless otherwise provided by Yokogawa, this Agreement applies to the updates and upgrades of the Software Product. 2. Grant of License 2.1 Subject to the terms and conditions of this Agreement, Yokogawa hereby grants you a non-exclusive and non-transferable right to use the Software Product on the hardware specified by Yokogawa or if not specified, on a single hardware and solely for your internal operation use, in consideration of full payment by you of the license fee separately agreed upon.
    [Show full text]
  • License Terms
    License Terms Open Source Software Version: 1.00 ©2009-2018 r2p GmbH – All rights reserved License Terms Open Source Software Table of Contents Open Source License Terms .................................................................................................... 4 1 GNU GENERAL PUBLIC LICENSE VERSION 2 ........................................................................ 4 2 GNU GENERAL PUBLIC LICENSE VERSION 3 ........................................................................ 7 3 GNU LESSER GENERAL PUBLIC LICENSE VERSION 3 .......................................................... 13 4 MIT License ........................................................................................................................ 15 5 BSD License ........................................................................................................................ 16 6 Python Software Foundation License ................................................................................ 17 7 OpenSSL License ................................................................................................................ 19 8 BOOST License ................................................................................................................... 21 9 Apache License Version 2 .................................................................................................. 22 10 Zlib License .................................................................................................................... 24 ©2009-2018 r2p GmbH
    [Show full text]
  • Open Source Software Attributions for ETAS ASCMO
    OSS Attributions for ETAS ASCMO Open Source Software Attributions for ETAS ASCMO Public Page 1 of 40 OSS Attributions for ETAS ASCMO Table of Contents List of used Open Source Software Components ........................................................................... 3 1.1 Apache License 2.0 ............................................................................................................. 6 1.2 FMI for Co-Simulation 1.0 ................................................................................................ 10 1.3 GPL 3.0 .............................................................................................................................. 11 1.4 GUI Layout Toolbox License ............................................................................................. 24 1.5 W32api license .................................................................................................................. 24 1.6 MinGWruntime license ...................................................................................................... 24 1.7 FMI for Model Exchange and Co-Simulation 2.0 .............................................................. 25 1.8 GCC RUNTIME LIBRARY EXCEPTION ................................................................................ 26 1.9 PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 ................................................ 27 1.10 MIT License .............................................................................................................. 39 1.11 2-Clause BSD
    [Show full text]
  • Open Source Acknowledgements
    This document acknowledges certain third‐parties whose software is used in Esri products. GENERAL ACKNOWLEDGEMENTS Portions of this work are: Copyright ©2007‐2011 Geodata International Ltd. All rights reserved. Copyright ©1998‐2008 Leica Geospatial Imaging, LLC. All rights reserved. Copyright ©1995‐2003 LizardTech Inc. All rights reserved. MrSID is protected by the U.S. Patent No. 5,710,835. Foreign Patents Pending. Copyright ©1996‐2011 Microsoft Corporation. All rights reserved. Based in part on the work of the Independent JPEG Group. OPEN SOURCE ACKNOWLEDGEMENTS 7‐Zip 7‐Zip © 1999‐2010 Igor Pavlov. Licenses for files are: 1) 7z.dll: GNU LGPL + unRAR restriction 2) All other files: GNU LGPL The GNU LGPL + unRAR restriction means that you must follow both GNU LGPL rules and unRAR restriction rules. Note: You can use 7‐Zip on any computer, including a computer in a commercial organization. You don't need to register or pay for 7‐Zip. GNU LGPL information ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You can receive a copy of the GNU Lesser General Public License from http://www.gnu.org/ See Common Open Source Licenses below for copy of LGPL 2.1 License.
    [Show full text]
  • Extremewireless Open Source Declaration
    ExtremeWireless Open Source Declaration Release v10.41.01 9035210 Published September 2017 Copyright © 2017 Extreme Networks, Inc. All rights reserved. Legal Notice Extreme Networks, Inc. reserves the right to make changes in specifications and other information contained in this document and its website without prior notice. The reader should in all cases consult representatives of Extreme Networks to determine whether any such changes have been made. The hardware, firmware, software or any specifications described or referred to in this document are subject to change without notice. Trademarks Extreme Networks and the Extreme Networks logo are trademarks or registered trademarks of Extreme Networks, Inc. in the United States and/or other countries. All other names (including any product names) mentioned in this document are the property of their respective owners and may be trademarks or registered trademarks of their respective companies/owners. For additional information on Extreme Networks trademarks, please see: www.extremenetworks.com/company/legal/trademarks Software Licensing Some software files have been licensed under certain open source or third-party licenses. End- user license agreements and open source declarations can be found at: www.extremenetworks.com/support/policies/software-licensing Support For product support, phone the Global Technical Assistance Center (GTAC) at 1-800-998-2408 (toll-free in U.S. and Canada) or +1-408-579-2826. For the support phone number in other countries, visit: http://www.extremenetworks.com/support/contact/
    [Show full text]
  • Software Package Data Exchange (SPDX​®​) Specification
    Software Package Data Exchange (SPDX​®)​ S​ pecification – Draft 2.0­rc3­20150303 ®​ Software Package Data Exchange (SPDX​) Specification Draft: 2.0rc3­20150303 ` Copyright © 2010­2015 Linux Foundation and its Contributors. Licensed under the Creative Commons Attribution License 3.0 Unported. All other rights are expressly reserved. Page 1 ​of 91 Software Package Data Exchange (SPDX​®)​ S​ pecification – Draft 2.0­rc3­20150303 Copyright © 2010­2015 Linux Foundation and its Contributors. This work is licensed under the Creative Commons Attribution License 3.0 Unported (CC­BY­3.0) reproduced in its entirety in Appendix V herein. All other rights are expressly reserved. With thanks to Adam Cohn, Andrew Back, Ann Thornton, Bill Schineller, Bruno Cornec, Ciaran Farrell, Daniel German, Debra McGlade, Dennis Clark, Ed Warnicke, Eran Strod, Eric Thomas, Esteban Rockett, Gary O'Neall, Guillaume Rousseau, Hassib Khanafer, Jack Manbeck, Jaime Garcia, Jeff Luszcz, Jilayne Lovejoy, John Ellis, Karen Copenhaver, Kate Stewart, Kim Weins, Kirsten Newcomer, Liang Cao, Marc­Etienne Vargenau, Mark Gisi, Marshall Clow, Martin Michlmayr, Martin von Willebrand, Matt Germonprez, Michael J. Herzog, Michel Ruffin, Nuno Brito, Paul Madick, Peter Williams, Phil Robb, Philip Odence, Philip Koltun, Pierre Lapointe, Rana Rahal, Sameer Ahmed, Scott K Peterson, Scott Lamons, Scott Sterling, Shane Coughlan, Steve Cropper, Stuart Hughes, Tom Callaway, Tom Vidal, Thomas F. Incorvia, Venkata Krishna and Zachary McFarland for their contributions and assistance. Copyright
    [Show full text]
  • Software Package Licenses
    DAVIX 1.0.0 Licenses Package Version Platform License Type Package Origin Operating System SLAX 6.0.4 Linux GPLv2 SLAX component DAVIX 0.x.x Linux GPLv2 - DAVIX Manual 0.x.x PDF GNU FDLv1.2 - Standard Packages Font Adobe 100 dpi 1.0.0 X Adobe license: redistribution possible. Slackware Font Misc Misc 1.0.0 X Public domain Slackware Firefox 2.0.0.16 C Mozilla Public License (MPL), chapter 3.6 and Slackware 3.7 Apache httpd 2.2.8 C Apache License 2.0 Slackware apr 1.2.8 C Apache License 2.0 Slackware apr-util 1.2.8 C Apache License 2.0 Slackware MySQL Client & Server 5.0.37 C GPLv2 Slackware Wireshark 1.0.2 C GPLv2, pidl util GPLv3 Built from source KRB5 N/A C Several licenses: redistribution permitted dropline GNOME: Copied single libraries libgcrypt 1.2.4 C GPLv2 or LGPLv2.1 Slackware: Copied single libraries gnutls 1.6.2 C GPLv2 or LGPLv2.1 Slackware: Copied single libraries libgpg-error 1.5 C GPLv2 or LGPLv2.1 Slackware: Copied single libraries Perl 5.8.8 C, Perl GPL or Artistic License SLAX component Python 2.5.1 C, PythonPython License (GPL compatible) Slackware Ruby 1.8.6 C, Ruby GPL or Ruby License Slackware tcpdump 3.9.7 C BSD License SLAX component libpcap 0.9.7 C BSD License SLAX component telnet 0.17 C BSD License Slackware socat 1.6.0.0 C GPLv2 Built from source netcat 1.10 C Free giveaway with no restrictions Slackware GNU Awk 3.1.5 C GPLv2 SLAX component GNU grep / egrep 2.5 C GPLv2 SLAX component geoip 1.4.4 C LGPL 2.1 Built from source Geo::IPfree 0.2 Perl This program is free software; you can Built from source redistribute it and/or modify it under the same terms as Perl itself.
    [Show full text]
  • 1 Agreement Between Rothschild Patent Imaging
    DocuSign Envelope ID: 830AE77C-41F6-46CC-9DAA-945BD199B6E3 AGREEMENT BETWEEN ROTHSCHILD PATENT IMAGING, LLC, LEIGH ROTHSCHILD, AND THE GNOME FOUNDATION. This Agreement (“Agreement”), dated as of the date of signature of the last signatory below (the “Effective Date”), is entered into by and between, on the one hand, Leigh Rothschild, an individual (“Rothschild”), and Rothschild Patent Imaging LLC, a Texas limited liability company with a principal place of business at 1400 Preston Road, Suite 400, Plano, Texas 75093 (“Grantor”) and, on the other hand, the Gnome Foundation, with a principal place of business at #117 21 Orinda Way C, Orinda, CA 94563 (“Grantee”) (Grantor and Grantee may be individually referred to as “Party” and collectively as “Parties”); WHEREAS, Grantor owns all right, title, and interest in and to United States Patent No. 9,936,086 (“the ’086 patent”); WHEREAS, Rothschild is the named inventor on more than 100 patents and applications, and has the right and authority to grant, or cause other entities to grant, binding covenants not to sue, releases and licenses with respect to the patents and patent applications on which he is a named inventor; WHEREAS Rothschild desires to support the open source community generally and the Parties view this support to be a material part of this Agreement NOW THEREFORE, for valuable consideration, the receipt and sufficiency of which is acknowledged, and other consideration as set forth below, Grantor, Rothschild, and Grantee agree as follows: DEFINITIONS “Affiliate(s)” of an Entity shall mean any and all Entities, past, present, or future, that are or were Controlled, directly, by the Entity, but only for so long as such Control existed or exists.
    [Show full text]