Die Rechtliche Relevanz Von Open Source Lizenzen Unter Besonderer Berücksichtigung Praktischer Problemstellungen

Total Page:16

File Type:pdf, Size:1020Kb

Die Rechtliche Relevanz Von Open Source Lizenzen Unter Besonderer Berücksichtigung Praktischer Problemstellungen Die rechtliche Relevanz von Open Source Lizenzen unter besonderer Berücksichtigung praktischer Problemstellungen von Mag. Dr. Kai Erenli [email protected] (Dissertation, eingereicht im WS 2007/2008 bei Univ. Prof. Dr. Alfred Schramm Institut für Rechtsphilosophie, Rechtssoziologie und Rechtsinformatik und: Univ. Prof. Dr. Gunter Nitsche Institut für Österreichisches und Internationales Unternehmens- und Wirtschaftsrecht) Die rechtliche Relevanz von Open Source-Lizenzen und deren praktische Bedeutung INHALTSVERZEICHNIS 1.EINLEITUNG .............................................................................................1 2.ENTSTEHUNG UND ENTWICKLUNG VON OPEN SOURCE UND DIE DEFINITION UND ABGRENZUNG VERSCHIEDENER SOFTWAREVARIANTEN ...........................................................................6 2.1. Die Entstehung von Softwarelizenzen ............................................... 7 2.1.1. Die Geschichte der Softwareindustrie....................................... 8 2.1.2. Die ersten Open Source Lizenzen .......................................... 10 2.2. Die Geburtsstunde der „Free Software Foundation“ ..................... 11 2.3. „Freie Software und “Open Source Software“................................ 14 2.3.1. Die Abspaltung von Richard Stallman..................................... 15 2.3.2. “The Cathedral and the Bazaar”.............................................. 16 2.3.3. Bill Gates und die Halloweendokumente................................. 17 2.3.4. Linux ....................................................................................... 17 2.3.5. Aus Netscape wird Mozilla ...................................................... 19 2.3.6. Der Begriff Open Source wird geprägt .................................... 20 2.3.7. Die „Open Source Definition“ .................................................. 21 2.4. Abgrenzung verschiedener Softwarevarianten............................... 25 2.4.1. Freie Software......................................................................... 26 2.4.2. Public Domain......................................................................... 27 2.4.3. „Copyleft“ und „Non-Copyleft“-Software.................................. 28 2.4.4. Microsoft Shared Source......................................................... 30 2.4.5. Freeware, Donationware und Cardware ................................. 31 2.4.6. Shareware und Crippleware.................................................... 32 2.4.7. Kommerzielle und Proprietäre Software.................................. 32 2.5. Ergebnis ............................................................................................. 34 3.URHEBERRECHTLICHE ASPEKTE .............................................................36 3.1. Allgemeines zum Schutz nach dem österreichischen Urheberrechtsgesetz ......................................................................... 37 3.2. Der Schutz von Computerprogrammen im österreichischen UrhG.................................................................................................... 39 3.2.1. Schutzgegenstand .................................................................. 40 3.2.1.1. Einordnung und Werkhöhe....................................... 40 ii Die rechtliche Relevanz von Open Source-Lizenzen und deren praktische Bedeutung 3.2.1.2. Begriff....................................................................... 42 3.2.2. Der Urheber als Rechteinhaber und die verschiedenen Arten der Urheberschaft an Open Source Software................ 44 3.2.2.1. Der oder die Alleinurheber ....................................... 45 3.2.2.2. Miturheber ................................................................ 48 3.2.2.3. Gehilfe...................................................................... 50 3.2.2.4. Teilurheberschaft...................................................... 51 3.2.2.4.1. Gruppenarbeitsverträge im Open Source Bereich................................................................... 53 3.2.2.4.2. Gelegenheitsgesellschaften im Open Source Bereich................................................................... 54 3.2.2.4.3. Kooperationsverträge im Open Source Bereich..... 54 3.2.2.4.4. Die Genossenschaft im Open Source Bereich....... 55 3.2.2.5. Arbeitnehmerurheberrecht ....................................... 57 3.2.2.5.1. Neuentwicklung durch einen einzelnen Dienstnehmer......................................................... 58 3.2.2.5.2. Neuentwicklung durch mehrere Dienstnehmer ...... 59 3.2.2.5.3. Weiterentwicklung durch einen einzelnen oder mehrere Arbeitnehmer ........................................... 60 3.2.2.5.4. Neu- oder Weiterentwicklung auf Grund eines freien Dienstvertrags oder durch arbeitnehmerähnliche Personen ............................ 61 3.2.2.5.5. Abgrenzung zwischen in „Erfüllung der Arbeitspflicht“ entwickelte Open Source Software, bei „Gelegenheit des Arbeitsverhältnis“ entwickelte Open Source Software und „außerhalb des Arbeitsverhältnis“ entwickelte Open Source Software. ....................... 62 3.2.3. Der zivilrechtliche Schutz und die Auswirkung der verschiedenen Arten der Urheberschaft auf die Aktivlegitimation ...................................................................... 65 3.2.3.1. Unterlassungsanspruch............................................ 66 3.2.3.2. Beseitigungsanspruch.............................................. 69 3.2.3.3. Anspruch auf angemessenes Entgelt und der Anspruch auf Schadenersatz und die Herausgabe des Gewinns ........................................ 70 3.3. Das Urhebervertragsrecht und die Open Source Lizenzen ........... 74 3.3.1. Die Open Source Lizenzen – Werknutzungsbewilligung oder Werknutzungsrecht? ....................................................... 76 3.3.2. Schutzrechtsumfang und -wirkungen...................................... 77 3.3.2.1. Die Problematik des Erschöpfungsgrundsatzes....... 78 iii Die rechtliche Relevanz von Open Source-Lizenzen und deren praktische Bedeutung 3.3.2.1.1. Download........................................................... 79 3.3.2.1.2. Eigentumsübertragung ohne Download............. 81 3.3.2.2. Zugänglichmachung im Internet ............................... 82 3.3.2.3. Die Problematik der Vermietung............................... 84 3.3.2.4. Die Problematik des Application Service Providing und Software as a Service........................ 86 3.3.2.5. Der Einfluss des GebG auf Open Source Lizenzverträge.................................... 88 3.4. Ergebnis ............................................................................................. 91 4.DIE ANNAHME DES LIZENZVERTRAGS ......................................................95 4.1. Die Anwendbarkeit von österreichischem Recht auf Open Source Lizenzverträge ...................................................................... 95 4.2. Die Annahme des Lizenzvertrags..................................................... 97 4.2.1. Abschlussvarianten................................................................. 98 4.2.2. Überblick über die Notwendigkeit zum Abschluss eines Open Source Lizenzvertrags........................ 99 4.2.3. Download und Kaufvertrag.................................................... 100 4.2.4. OEM und Embedded-Systems.............................................. 102 4.3. AGB................................................................................................... 103 4.4. Lizenzsprache.................................................................................. 104 4.5. Erwerb der Lizenzrechte von einem unberechtigten Dritten ....... 106 4.6. Ergebnis ........................................................................................... 107 5.DIE OPEN SOURCE LIZENZEN – RECHTE UND PFLICHTEN ........................109 5.1. Die Lizenzarten ................................................................................ 111 5.2. Lizenzen ohne Copyleft-Effekt – BSDartige Lizenzen .................. 112 5.2.1. Die BSD-Lizenz..................................................................... 113 5.2.1.1. Hintergrund ............................................................ 114 5.2.1.2. Lizenzmerkmale ..................................................... 115 5.2.1.3. Kompatibilität.......................................................... 116 5.2.2. Die Apache Software License ............................................... 116 5.2.2.1. Hintergrund ............................................................ 117 5.2.2.2. Lizenzmerkmale der Version 1.0 und 1.1 ............... 117 5.2.2.3. Lizenzmerkmale der Version 2.0............................ 118 5.2.2.4. Kompatibilität.......................................................... 120 5.2.2.4.1. Sichtweise der FSF.......................................... 120 5.2.2.4.2. Sichtweise der ASF.......................................... 121 iv Die rechtliche Relevanz von Open Source-Lizenzen und deren praktische Bedeutung 5.2.2.4.3. Kommentar zu den Sichtweisen....................... 122 5.2.3. Die OpenLDAP Public License ............................................. 123 5.2.3.1. Hintergrund ............................................................ 123 5.2.3.2. Lizenzmerkmale ..................................................... 123 5.2.3.3. Kompatibilität.......................................................... 124 5.2.4. W3C Software Notice und License ....................................... 124 5.2.4.1. Hintergrund ............................................................ 125
Recommended publications
  • Diplomarbeit Limux
    Diplomarbeit LiMux Ist Open-Source-Software eine Alternative für die öffentliche Verwaltung? Überprüfung des Migrationsprozesses der Stadt München von Windows auf Linux anhand eines Kriterienkatalogs Erstellt am: Arbeitsbereich Softwaretechnik Departement Informatik MIN Fakultät Universität Hamburg Erstbetreuer: Dr. Wolf-Gideon Bleek Zweitbetreuer: Prof. Dr.-Ing. Bernd Page Abgabedatum: 02.05.2007 Erstellt von: Benjamin Stukenberg Matrikelnummer: 5498671 Studiengang: Wirtschaftsinformatik Adresse: Rantzaustr. 85, 22926 Ahrensburg Diplomarbeit: LiMux Seite 3 von 65 Danksagung Ich danke meinem Erstbetreuer Dr. Bleek für die Betreuung und für Anregungen für meine Diplomarbeit und meinem Zweitbetreuer Prof. Dr.-Ing. Page für die Zweitbetreu- ung. Ich danke der Stadt München dafür, dass sie auf Open-Source-Software umsteigt und mir somit das Thema meiner Diplomarbeit ermöglicht hat. Insbesondere danke ich dem stellvertretenden Projektleiter des LiMux-Projekts Herrn Lubig-Konzett für das In- terview. Des weiteren danke ich allen Entwicklern von Open-Source-Software, ohne sie wäre diese Diplomarbeit nicht möglich gewesen, d. h. ohne sie hätte ich nicht über dieses Thema schreiben können. Insbesondere danke ich den Entwicklern von OpenOffice.org und Linux, denn ich habe diese Diplomarbeit mit OpenOffice.org unter Linux ohne einen einzigen Absturz verfassen können. Diplomarbeit: LiMux Seite 4 von 65 Inhaltsverzeichnis Tabellenverzeichnis...........................................................................................................6
    [Show full text]
  • Licensing 101 December 3, 2020 Meet the Speakers
    Licensing 101 December 3, 2020 Meet The Speakers Sushil Iyer Adam Kessel Principal Principal fr.com | 2 Roadmap • High level, introductory discussion on IP licensing • Topics – Types of IP – Monetization strategies – Key parts of a license agreement – Certain considerations • Licensing software, especially open source software • Licensing pharmaceutical patents • Trademarks • Trade secrets • Know-how fr.com | 3 Types of IP Patents Trademarks Copyrights Know-how (including trade secrets) fr.com | 4 Monetization Strategies • IP licensing – focus of this presentation – IP owner (licensor) retains ownership and grants certain rights to licensee – IP licensee obtains the legal rights to practice the IP – Bundle of rights can range from all the rights that the IP owner possesses to a subset of the same • Sale – IP owner (assignor) transfers ownership to the purchaser (assignee) • Litigation – Enforcement, by IP owner, of IP rights against an infringer who impermissibly practices the IP owner’s rights – Damages determined by a Court fr.com | 5 What is an IP License? • Contract between IP owner (Licensor) and Licensee – Licensor’s offer – grant of Licensor’s rights in IP • Patents – right to sell products that embody claimed inventions of Licensor’s US patents • Trademarks – right to use Licensor’s US marks on products or when selling products • Copyright – right to use and/or make derivative works of Licensor’s copyrighted work • Trade Secret – right to use and obligation to maintain Licensor’s trade secret – Licensee’s consideration – compensation
    [Show full text]
  • One of the Biggest Aims of Limux Was to Make the City More Independent.”
    FEATURE MUNICH Munich city council has migrated 15,000 workers from Windows to Linux. Mike Saunders and Graham Morrison visited the city and learned just how upset Steve Ballmer was… “One of the biggest aims of LiMux was to make the city more independent.” irschgarten, in the west of the last decade. Migrating workers of Munich, is one of Europe’s biggest Germany’s third-largest city was no easy Hbeer gardens, with over 8,000 task and there were plenty of hurdles along places to sit. It’s a spectacular sight in the way, but by and large the project has summer: hundreds of benches as far as been a storming success. the eye can see, trees providing some We’ve been following the progress of shelter from the heat, and a vast number LiMux (Linux in Munich) for years, and now of people relaxing and enjoying the city’s that the project is effectively complete, we famous beers. decided to visit the city and talk to the man But while 8,000 is an impressive number, in charge of it. Read on to discover how it it’s not as impressive as 15,000. That’s all started, how Microsoft tried to torpedo how many people the Munich city council it, and whether other cities in the world can has switched from Windows to Linux over follow Munich’s lead… 52 www.linuxvoice.com MUNICH FEATURE Humble beginnings Cast your mind back to 2001, and the state of Linux at the time. It was well established as a server OS and fairly well known among computing hobbyists, but still a small fish in the desktop pond.
    [Show full text]
  • Optional Package 1WIRE Paket OPT OW V. 1.0.0 Für Fli4l - 3.4.0
    Optional Package 1WIRE Paket OPT_OW V. 1.0.0 für Fli4L - 3.4.0 Karl M. Weckler [email protected] Rockenberg, Mai 2009 OPT_OW Inhaltsverzeichnis Paket OPT_OW.......................................................................................................... 1 Inhaltsverzeichnis ....................................................................................................... 2 Dokumentation des Paketes OPT_OW ...................................................................... 3 1. Einleitung................................................................................................................ 3 1.1. OPT_OW ......................................................................................................... 3 1.2. OW = OneWire = 1-Wire .................................................................................. 3 1.2.1. Der 1-Wire Standard.................................................................................. 3 1.2.2. 1-Wire-Bauteile.......................................................................................... 3 1.2.3. 1-Wire Bus................................................................................................. 3 1.3. OWFS .............................................................................................................. 4 1.4. Fuse................................................................................................................. 4 2. Lizenz ....................................................................................................................
    [Show full text]
  • Rootkit- Rootkits.For.Dummies 2007.Pdf
    01_917106 ffirs.qxp 12/21/06 12:04 AM Page i Rootkits FOR DUMmIES‰ 01_917106 ffirs.qxp 12/21/06 12:04 AM Page ii 01_917106 ffirs.qxp 12/21/06 12:04 AM Page iii Rootkits FOR DUMmIES‰ by Larry Stevenson and Nancy Altholz 01_917106 ffirs.qxp 12/21/06 12:04 AM Page iv Rootkits For Dummies® Published by Wiley Publishing, Inc. 111 River Street Hoboken, NJ 07030-5774 www.wiley.com Copyright © 2007 by Wiley Publishing, Inc., Indianapolis, Indiana Published by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permit- ted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4355, or online at http://www.wiley.com/go/permissions. Trademarks: Wiley, the Wiley Publishing logo, For Dummies, the Dummies Man logo, A Reference for the Rest of Us!, The Dummies Way, Dummies Daily, The Fun and Easy Way, Dummies.com, and related trade dress are trademarks or registered trademarks of John Wiley & Sons, Inc. and/or its affiliates in the United States and other countries, and may not be used without written permission.
    [Show full text]
  • Mcafee Potentially Unwanted Programs (PUP) Policy March, 2018
    POLICY McAfee Potentially Unwanted Programs (PUP) Policy March, 2018 McAfee recognizes that legitimate technologies such as commercial, shareware, freeware, or open source products may provide a value or benefit to a user. However, if these technologies also pose a risk to the user or their system, then users should consent to the behaviors exhibited by the software, understand the risks, and have adequate control over the technology. McAfee refers to technologies with these characteristics as “potentially unwanted program(s),” or “PUP(s).” The McAfee® PUP detection policy is based on the process includes assessing the risks to privacy, security, premise that users should understand what is being performance, and stability associated with the following: installed on their systems and be notified when a ■ Distribution: how users obtain the software including technology poses a risk to their system or privacy. advertisements, interstitials, landing-pages, linking, PUP detection and removal is intended to provide and bundling notification to our users when a software program or technology lacks sufficient notification or control over ■ Installation: whether the user can make an informed the software or fails to adequately gain user consent to decision about the software installation or add- the risks posed by the technology. McAfee Labs is the ons and can adequately back out of any undesired McAfee team responsible for researching and analyzing installations technologies for PUP characteristics. ■ Run-Time Behaviors: the behaviors exhibited by the technology including advertisements, deception, and McAfee Labs evaluates technologies to assess any impacts to privacy and security risks exhibited by the technology against the degree of user notification and control over the technology.
    [Show full text]
  • Linux. Sécuriser Un Réseau
    11960_Securiser_Linux_XP 31/10/06 9:40 Page 1 Cahiers Cahiers de de l’Admin Collection dirigée par Nat Makarévitch Delaunay Boutherin l’Admin B. B. Ingénieur de formation, Bernard Boutherin a éd. éd. e été administrateur système et e 3 édition réseau successivement dans e trois laboratoires du CNRS. Il 3 est actuellement responsable in- 3 Quelles règles d’or appliquer pour préserver la sûreté d’un réseau Linux ? formatique du LPSC à Grenoble Comment protéger les systèmes et les données ? et est chargé de mission pour la sécurité informatique auprès de la direction de l’IN2P3 (18 labo- Grâce à des principes simples et à la mise en œuvre d’outils libres réputés pour ratoires de recherche, près de leur efficacité, on apprendra dans ce cahier à améliorer l’architecture d’un réseau trois mille utilisateurs). d’entreprise et à le protéger contre les intrusions, dénis de service et autres Bernard Boutherin attaques. On verra notamment comment filtrer des flux (netfilter/IPtables…), De formation universitaire, sécuriser la messagerie (milter-greylist, ClamAV…), chiffrer avec SSL (stunnel…) Benoit Delaunay travaille Benoit Delaunay et (Open)SSH. On étudiera les techniques et outils de surveillance (métrologie avec actuellement au Centre de Cal- MRTG, empreintes Tripwire, détection d’intrusion avec des outils tel Snort, créa- cul de l’IN2P3 (Institut National tion de tableaux de bord) et l’authentification unique (SSO) avec LDAP, Kerberos, de Physique Nucléaire et de PAM, les certificats X509 et les PKI… Physique des Particules). Il y est Linux administrateur système et ré- Linux seau en charge de la sécurité informatique.
    [Show full text]
  • Licencování Softwaru Software Licensing
    Licencování softwaru Software licensing Bakalá řská práce Michal Kudrna Vedoucí bakalá řské práce: Ing. Václav Novák, CSc. Jiho česká univerzita v Českých Bud ějovicích Pedagogická fakulta Katedra informatiky Rok 2009 Prohlášení Prohlášení Prohlašuji, že svoji bakalá řskou práci jsem vypracoval samostatn ě pouze s použitím pramen ů a literatury uvedených v seznamu citované literatury. Prohlašuji, že v souladu s § 47b zákona č. 111/1998 Sb. v platném zn ění souhlasím se zve řejn ěním své bakalá řské práce, a to v nezkrácené podob ě elektronickou cestou ve ve řejn ě p řístupné části databáze STAG provozované Jiho českou univerzitou v Českých Bud ějovicích na jejích internetových stránkách. V Českých Bud ějovicích dne - 2 - Anotace Anotace Tato bakalá řská práce pojednává o možnostech licencování program ů, uvádí příklady licencování vybraných spole čností typu Microsoft Corporation, Sun Microsystems a za řazuje metody kontroly dodržování diskutovaných licencí. Abstract This work deals with ways and means of program licensing, shows examples of licensing in companies like Microsoft Corporation, Sun Microsystems and includes verification methods to observance these license rules. - 3 - Pod ěkování Pod ěkování Rád bych pod ěkoval všem, kte ří mi pomáhali po celou dobu mého bakalá řského studia, zvlášt ě však pedagogickým pracovník ům Katedry informatiky Pedagogické fakulty Jiho české univerzity v Českých Bud ějovicích, zejména pak vedoucímu této práce, panu Ing. Václavu Novákovi, CSc. - 4 - Obsah Obsah 1 ÚVOD.......................................................................................6
    [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]
  • Max Spyware Detector-Windows-EULA
    END-USER LICENSE AGREEMENT END-USER LICENSE AGREEMENT FOR MAX SPYWARE DETECTOR FOR WINDOWS PLATFORM PLEASE READ THIS MAX SPYWARE DETECTOR FOR WINDOWS PLATFORM END-USER LICENSE AGREEMENT (HEREINAFTER REFERRED TO AS THE “AGREEMENT”) CAREFULLY BEFORE USING OR TRYING TO ATTEMPT TO USE THIS MAX SPYWARE DETECTOR FOR WINDOWS PLATFORM (HEREINAFTER REFERRED TO AS THE “SOFTWARE”). BY USING THIS SOFTWARE OR BY ACCEPTING OUR SOFTWARE USAGE AGREEMENT POLICY OR ATTEMPTING TO LOAD THE SOFTWARE IN ANY WAY, (SUCH ACTION WILL CONSTITUTE A SYMBOL OF YOUR CONSENT AND SIGNATURE), YOU ACKNOWLEDGE AND ADMIT THAT YOU HAVE READ, UNDERSTOOD AND AGREED TO ALL THE TERMS AND CONDITIONS OF THIS AGREEMENT. THIS AGREEMENT ONCE ACCEPTED BY “YOU” [AS AN INDIVIDUAL (ASSUMING YOU ARE HAVING LEGAL CAPACITY TO ENTER INTO AN AGREEMENT), OR THE COMPANY OR ANY LEGAL ENTITY THAT WILL BE USING THE SOFTWARE (HEREINAFTER REFERRED TO AS 'YOU' OR 'YOUR' FOR THE SAKE OF BREVITY)] SHALL BE A LEGALLY ENFORCEABLE AGREEMENT BETWEEN YOU AND MAX SECURE SOFTWARE INDIA PVT. LTD., PUNE, MH, INDIA (HEREINAFTER REFERRED TO AS “MSS”). YOU SHALL HAVE THE RIGHTS TO USE THE SOFTWARE FOR YOUR OWN USE SUBJECT TO THE TERMS AND CONDITIONS MENTIONED IN THIS AGREEMENT OR AS AMENDED BY MSS FROM TIME TO TIME. IF YOU DO NOT AGREE TO ALL THE TERMS AND CONDITIONS BELOW, DO NOT USE THIS SOFTWARE IN ANY WAY AND PROMPTLY RETURN IT OR DELETE ALL THE COPIES OF THIS SOFTWARE IN YOUR POSSESSION. In consideration of payment of the License Fee, evidenced by the Payment Receipt, MSS grants you, a non-exclusive and non-transferable right for your own use only.
    [Show full text]
  • Versatility (C) Reliability (D) All of the Above
    1. Which of the following is/are characteristics of Computer? (A) Diligence (B) Versatility (C) Reliability (D) All of the Above Answer (D) All of the Above 2. Faulty inputs lead to faulty results. It is known as _______ (A) Diligence (B) Versatility (C) GIGO (D) None of the Above Answer (C) GIGO 3. GIGO stands for______ (A) Garbage In Garbage Out (B) Gateway In Gateway Out (C) Gopher In Gopher Out (D) Geographic In Geographic Out Answer (A) Garbage In Garbage Out 4. The capacity to perform multiple tasks simultaneously is termed as ______ (A) Diligence (B) Versatility (C) Reliability (D) All of the Above Answer (B) Versatility 5. A computer does not suffer from tiredness and lack of concentration. It is known as _______ (A) Diligence (B) Versatility (C) GIGO (D) None of the Above Answer (A) Diligence 6. First Generation computers used ______ for Circuitry and ________ for memory (A) Transistor and Magnetic Core (B) IC and Magnetic Memory (C) Vacuum tubes and Magnetic drum (D) IC and Magnetic Core Answer (C) Vacuum tubes and Magnetic drum 7. Second Generation computers were based on _______ (A) IC (B) Vacuum tube (C) transistor (D) None of the Above Answer (C) transistor 8. FLOPS stands for______ (A) Floating Point Operation Per Second (B) File Processing Operation Per Second (C) Floating Processing Operation Per Second (D) File Loading Operation Per Second Answer (A) Floating Point Operation Per Second 9. Which language was used to program Second Generation computers? (A) Binary Coded language (B) Assembly language (C) Machine language (D) None of the Above Answer (B) Assembly language 10.
    [Show full text]
  • Openchrom: a Cross-Platform Open Source Software for the Mass Spectrometric Analysis of Chromatographic Data Philip Wenig*, Juergen Odermatt
    Wenig and Odermatt BMC Bioinformatics 2010, 11:405 http://www.biomedcentral.com/1471-2105/11/405 SOFTWARE Open Access OpenChrom: a cross-platform open source software for the mass spectrometric analysis of chromatographic data Philip Wenig*, Juergen Odermatt Abstract Background: Today, data evaluation has become a bottleneck in chromatographic science. Analytical instruments equipped with automated samplers yield large amounts of measurement data, which needs to be verified and analyzed. Since nearly every GC/MS instrument vendor offers its own data format and software tools, the consequences are problems with data exchange and a lack of comparability between the analytical results. To challenge this situation a number of either commercial or non-profit software applications have been developed. These applications provide functionalities to import and analyze several data formats but have shortcomings in terms of the transparency of the implemented analytical algorithms and/or are restricted to a specific computer platform. Results: This work describes a native approach to handle chromatographic data files. The approach can be extended in its functionality such as facilities to detect baselines, to detect, integrate and identify peaks and to compare mass spectra, as well as the ability to internationalize the application. Additionally, filters can be applied on the chromatographic data to enhance its quality, for example to remove background and noise. Extended operations like do, undo and redo are supported. Conclusions: OpenChrom is a software application to edit and analyze mass spectrometric chromatographic data. It is extensible in many different ways, depending on the demands of the users or the analytical procedures and algorithms. It offers a customizable graphical user interface.
    [Show full text]