Friday, November 26, 2010

Proprietary software

Proprietary software

From Wikipedia, the free encyclopedia
  (Redirected from Closed source software)
Jump to: navigation, search
Proprietary software or closed-source software is computer software licensed under exclusive legal right of its owner. The purchaser, or licensee, is given the right to use the software under certain conditions, but restricted from other uses, such as modification, further distribution, or reverse engineering.
Complementary terms include public domain software, which is not subject to copyright and can be used for any purpose, and free software, licensed by the owner under more permissive terms. Many proponents of free and open source software use proprietary or non-free to describe software that doesn't meet their criteria for free or open source, though specific definitions vary.

Contents

[hide]

[edit] Software becoming commercial

Until the late 1960s computers—huge and expensive mainframe machines in specially air-conditioned computer rooms—were usually supplied on a leasing rather than purchase basis[1][2]. Service and all software available were usually supplied by manufacturers without separate charge until 1969. Software source code was usually provided. Users who developed software often made it available, without charge; software was not seen as valuable in its own right, compared to the extremely expensive hardware. In 1969 IBM led an industry change by starting to charge separately for (mainframe) software and services, and ceasing to supply source code[3].

[edit] Legal basis

Further information: Software law, Software copyright, and Software patent
See also: Software patents and free software
Most software is covered by copyright, which provides legal basis for its owner to establish exclusive rights. Applicable Contract law, patent, and trade secrets may also apply.
A software vendor delineates the specific terms of use in an end-user license agreement (EULA). The user may agree to this contract interactively, called clickwrap licensing, by opening the box containing the software, called shrink wrap licensing, or in writing. License agreements are usually not negotiable.
Software patents grant exclusive rights to algorithms, software features, or other patentable subject matter. Laws on software patents vary by jurisdiction and are a matter of ongoing debate. Vendors sometimes grant patent rights to the user in the license agreement.[4] For example, the algorithm for creating, or encoding, MP3s is patented. LAME is an encoder which is open source but illegal to use without obtaining a license to use the algorithm it contains.
Proprietary software vendors usually regard source code as a trade secret.[5]
License agreements do not override applicable copyright law or contract law. Provisions that conflict may not be enforceable.
Some vendors say that software licensing is not a sale, and that limitations of copyright like the first-sale doctrine do not apply. The EULA for Microsoft Windows states that the software is licensed, not sold.[6]

[edit] Technical restrictions

In addition to legal means, restrictions on proprietary software are enforced by technical means. The most common form of technical restriction is by releasing "closed-source" programs that are only computer-readable (for example, in binary format), and withholding the human-readable source code.[7][8]

[edit] Legal meanings and licensing

Exclusive legal rights to software by a proprietor are not required for software to be proprietary. The free software movement's founder Richard Stallman sometimes uses the term "user-subjugating software"[9] to describe proprietary software, while Eben Moglen sometimes talks of "unfree software". The term "non-free" is often used by Debian developers to describe any software whose license does not comply with Debian Free Software Guidelines, and they use "proprietary software" specifically for non-free software that provides no source code. The Open Source Initiative uses the terms "proprietary software" and "closed source software" interchangeably.[10][11]
Semi-free software, as defined by the Free Software Foundation, is software that is not free software, but comes with permission for individuals to use, copy, distribute, and modify either for non-profit purposes only or with the prohibition to redistribute modified copies or derived works.[12] Such software is also rejected by the Open Source Initiative and Debian. PGP and Angband are examples of semi-free programs. The Free Software Foundation classifies semi-free software as non-free software, but draws a distinction between semi-free software and proprietary software.
Free software licences use the same laws used by proprietary software, but to preserve the rights to use, copy and modify the software. This technique is used with copyleft, but with other software as well.[13] Free software companies and projects are also joining into patent pools like the Patent Commons and the Open Invention Network. See software patents and free software.
"Proprietary software" is not synonymous with "commercial software",[14][15][15] though the industry commonly confuses the term,[16] [17] as does the free software community.[18][19]
Proprietary software can be distributed at no cost or for a fee, and free software can be distributed at no cost or for a fee.[20] The difference is that whether or not proprietary software can be distributed, and what the fee would be, is at the proprietor's discretion. With free software, anyone who has a copy can decide whether, and how much, to charge for a copy or related services.[21]
Proponents of commercial proprietary software argue that requiring users to pay for software as a product increases funding or time available for the research and development of software. For example, Microsoft says that per-copy fees maximise the profitability of software development.[22]
Proprietary software is said to create greater commercial activity over free software, especially in regard to market revenues.[23]
R&D however has a possibility of hurting the consumer if the company uses what the consumer funded primarily for the development of anti-features. According to Richard Stallman, "malicious features, such as spying on the users, restricting the users, back doors, and imposed upgrades are common in proprietary software".[24]
A dependency on the future versions and upgrades for a proprietary software package can create "vendor lock-in", entrenching a monopoly position.[25] If the proprietor of a software package should cease to exist, or decide to cease or limit production or support for a proprietary software package, recipients and users of the package may have no recourse if problems are found with the software. Proprietors can fail to improve and support software because of business problems.[26] When no other vendor can provide support for the software, the ending of support for older or existing versions of a software package may be done to force users to upgrade and pay for newer versions; or migrate to either competing systems with longer support life cycles or to FOSS-based systems.[27]

[edit] Proprietary APIs

A proprietary application programming interface (API) is a software library interface "specific to one device or, more likely to a number of devices within a particular manufacturer's product range."[28] The motivation for using a proprietary API can be vendor lock-in or because standard APIs do not support the device's functionality.[28]
The European Commission, in its March 24, 2004 decision on Microsoft's business practices,[29] quotes, in paragraph 463, Microsoft general manager for C++ development Aaron Contorer as stating in a February 21, 1997 internal Microsoft memo drafted for Bill Gates:
"The Windows API is so broad, so deep, and so functional that most ISVs would be crazy not to use it. And it is so deeply embedded in the source code of many Windows apps that there is a huge switching cost to using a different operating system instead...

[edit] Examples

Well known examples of proprietary software include Microsoft Windows, Adobe Flash Player, PS3 OS, iTunes, Adobe Photoshop, Google Earth, Mac OS X, Skype, WinZip, and some versions of Unix.
Software distributions considered as proprietary may in fact incorporate a "mixed source" model including both free and non-free software in the same distribution.[30] Most if not all so-called proprietary UNIX distributions are mixed source software, bundling open source components like BIND, Sendmail, X Window System, DHCP, and others along with a purely proprietary kernel and system utilities.[31][32]
Windows XP Professional's license restricts the software's installation to one computer,[33] and limits the number of permitted connections with computers or other electronic devices which utilize certain services to 10.[34]
Some proprietary software comes with source code or provides offers to the source code. Users are free to use and even study and modify the software in these cases, but are restricted by either licenses or non-disclosure agreements from redistributing modifications or sharing the software. Examples include Pine, the Microsoft Shared source license program, and certain proprietary implementations of Secure Shell. Microsoft's Reference Source License (Ms-RSL) and Limited Public License (Ms-LPL) are examples of a license where the source code is made available but it remains proprietary software.
Some free software packages are also simultaneously available under proprietary terms. Examples include MySQL, Sendmail and ssh. The original copyright holders for a work of free software, even copyleft free software, can use dual-licensing to allow themselves or others to redistribute proprietary versions. Non-copyleft free software (i.e. software distributed under a permissive free software license or released to the public domain) allows anyone to make proprietary redistributions.[35][36] Free software that depends on proprietary software is considered "trapped" by the Free Software Foundation. This includes software written only for Microsoft Windows,[37] or software that could only run on Java, before it became free software.[38]
Proprietary software that comes for no cost is called freeware. Shareware, like freeware, is proprietary software available at zero price, but differs in being free only for a trial period, after which some restriction is imposed or it is completely disabled. Proprietary software which is no longer marketed by its owner and is used without permission by users is called abandonware and may include source code. Some abandonware has the source code released to the public domain either by its author or copyright holder and is therefore free software, and no longer proprietary software.
For certain proprietary software where the user can access source code, such as online applications (for example, Internet forum software) or Java applications (where the source can be obtained by decompiling), some developers will obfuscate the source code in order to make it difficult for users to obtain the original code.[39] According to Jonathan Zittrain, the emergence of "closed devices" and online applications, like the iPhone, Facebook and Google apps, have made the Internet become far more proprietary than early versions of Microsoft Windows.[40]

[edit] See also

[edit] References

  1. ^ Paul E. Ceruzzi (2003) (in English), A history of modern computing, MIT Press, p. 128, ISBN 0-262-53203-4, "Although IBM agreed to sell its machines as part of a Consent Decree effective January 1956, leasing continued to be its preferred way of doing business" 
  2. ^ "History of Leasing". leasegenie.com. http://www.leasegenie.com/History_of_Leasing.html. Retrieved 2010-11-12. "In the 1960s, IBM and Xerox recognized that substantial sums could be made from the financing of their equipment. The leasing of computers and office equipment that occurred then was a significant contribution to leasings growth, since many companies were exposed to equipment leasing for the first time when they leased such equipment" 
  3. ^ "http://www-03.ibm.com/ibm/history/history/decade_1960.html". IBM. http://www-03.ibm.com/ibm/history/history/decade_1960.html. Retrieved 2010-11-12. "Rather than offer hardware, services and software exclusively in packages, marketers "unbundled" the components and offered them for sale individually. Unbundling gave birth to the multibillion-dollar software and services industries, of which IBM is today a world leader" 
  4. ^ Daniel A. Tysver (2008-11-23). "Why Protect Software Through Patents". Bitlaw.com. http://www.bitlaw.com/software-patent/why-patent.html. Retrieved 2009-06-03. "In connection with software, an issued patent may prevent others from utilizing a certain algorithm (such as the GIF image compression algorithm) without permission, or may prevent others from creating software programs that perform a function in a certain way. In connection with computer software, copyright law can be used to prevent the total duplication of a software program, as well as the copying of a portion of software code." 
  5. ^ Donovan, S. (1994), "Patent, copyright and trade secret protection for software", Potentials, IEEE 13 (3): 20, "Essentially there are only three ways to protect computer software under the law: patent it, register a copyright for it, or keep it as a trade secret." 
  6. ^ Microsoft Corporation (2005-04-01). "End-User License Agreement for Microsoft Software: Microsoft Windows XP Professional Edition Service Pack 2" (PDF). p. Page 3. http://www.microsoft.com/about/legal/useterms/. Retrieved 2009-04-29. 
  7. ^ Heffan, Ira V. (1997). "Copyleft: Licensing Collaborative Works in the Digital Age". Stanford Law Review 49: 1490. http://www.open-bar.org/docs/copyleft.pdf. "Under the proprietary software model, most software developers withhold their source code from users." 
  8. ^ Margolis, Philip E. (1999). Webster's Computer & Internet Dictionary. Random House. pp. 452. "[P]roprietary is the opposite of open. A proprietary design or technique is one that is owned by a company. It also implies that the company has not divulged specifications that would allow other companies to duplicate the product." 
  9. ^ Stallman, Richard (February 17, 2009). "Re: GCC and the Visual Basic programmer....". gcc@gcc.gnu.org mailing list. http://gcc.gnu.org/ml/gcc/2009-02/msg00275.html. Retrieved September 24, 2009. 
  10. ^ Russell Nelson (2008-03-14). "Who speaks for the Open Source Community?". http://www.opensource.org/node/272. Retrieved 2008-06-11. "When we, the open source community, want to make an agreement with the proprietary software vendors, who do we talk to?" 
  11. ^ Russell Nelson (2008-03-24). "Patent owners and Open Source". http://www.opensource.org/node/279. Retrieved 2009-06-11. "The purpose of closed-source software is to give you ownership over the code." 
  12. ^ Semi-free software, definition by the Free Software Foundation
  13. ^ Eben Moglen (2005-02-12). "Why the FSF gets copyright assignments from contributors". http://www.fsf.org/licensing/licenses/why-assign.html. Retrieved 2009-06-26. "Under US copyright law, which is the law under which most free software programs have historically been first published, [...] only the copyright holder or someone having assignment of the copyright can enforce the license." 
  14. ^ Rosen, Lawrence (2004). Open Source Licensing. Upper Saddle River: Prentice Hall. pp. 52, 255, 259. ISBN 978-0131487871. http://rosenlaw.com/oslbook.htm. 
  15. ^ a b Havoc Pennington (2008-03-02). "Debian Tutorial". http://www.debian.org/doc/manuals/debian-tutorial/. Retrieved 2009-06-04. "It is important to distinguish commercial software from proprietary software. Proprietary software is non-free software, while commercial software is software sold for money." 
  16. ^ Cynthia Keeshan (2009-04-30). "The Software Ecosystem". Microsoft Corporation, Canada. http://www.microsoft.com/canada/media/ecosystem.mspx. Retrieved 2009-04-30. "Commercial software companies develop and distribute proprietary software to generate revenue. (original emphasis)" 
  17. ^ Vinod Valloppillil, Microsoft Corporation (2006-10-12). "Halloween Document 1". Microsoft Halloween documents leak. Eric S. Raymond. http://www.catb.org/~esr/halloween/halloween1.html. Retrieved 2009-04-30. "Commercial software is classic Microsoft bread-and-butter. It must be purchased, may NOT be redistributed, and is typically only available as binaries to end users. (original emphasis)" 
  18. ^ Russell McOrmond (2000-01-04). "What is "Commercial Software"?". http://www.linuxtoday.com/news_story.php3?ltsn=2000-01-04-005-05-NW-SM/halloween1.html. Retrieved 2009-05-02. 
  19. ^ Michael K. Johnson (1996-09-01). "Licenses and Copyright". http://www.linuxjournal.com/article/1297. Retrieved 2009-06-16. "If you program for Linux, you do need to understand licensing, no matter if you are writing free software or commercial software." 
  20. ^ Eric S. Raymond (2003-12-29). "Proprietary, Jargon File". http://www.catb.org/~esr/jargon/html/P/proprietary.html. Retrieved 2009-06-12. "Proprietary software should be distinguished from commercial software. It is possible for software to be commercial [...] without being proprietary. The reverse is also possible, for example in binary-only freeware." 
  21. ^ Free Software Foundation (2008-12-31). "Selling Free Software". http://www.gnu.org/philosophy/selling.html. Retrieved 2009-06-03. 
  22. ^ "The Commercial Software Model". Microsoft. May 2001. http://www.microsoft.com/presspass/exec/craig/05-03sharedsource.mspx. Retrieved 2007-03-05. 
  23. ^ "Open Source Versus Commercial Software: Why Proprietary Software is Here to Stay". Sams Publishing. October 2005. http://www.informit.com/articles/article.aspx?p=420290&seqNum=3. Retrieved 2007-03-05. 
  24. ^ Stallman, Richard (June 2009). "Viewpoint: Why "open source" misses the point of free software". Communications of the ACM (ACM) 52 (6): 31–33. doi:10.1145/1516046.1516058. http://portal.acm.org/citation.cfm?doid=1516046.1516058. Retrieved 2010-03-08. 
  25. ^ The Linux Information Project (2006-04-29). "Vendor Lock-in Definition". http://www.linfo.org/vendor_lockin.html. Retrieved 2009-06-11. "Vendor lock-in, or just lock-in, is the situation in which customers are dependent on a single manufacturer or supplier for some product [...] This dependency is typically a result of standards that are controlled by the vendor [...] It can grant the vendor some extent of monopoly power [...] The best way for an organization to avoid becoming a victim of vendor lock-in is to use products that conform to free, industry-wide standards. Free standards are those that can be used by anyone and are not controlled by a single company. In the case of computers, this can usually be accomplished by using free software rather than proprietary software (i.e., commercial software)." 
  26. ^ "What happens when a proprietary software company dies?". NewsForge. October 2003. http://www.linux.com/archive/feature/32277. Retrieved 2007-03-05. 
  27. ^ "Microsoft Turns Up The Heat On Windows 2000 Users". InformationWeek. December 2006. http://informationweek.com/news/showArticle.jhtml;jsessionid=GL4O5EZFOXYJGQSNDLPSKH0CJUNN2JVN?articleID=196700071. Retrieved 2008-09-16. 
  28. ^ a b http://features.techworld.com/applications/471/apis-what-they-are-and-what-theyre-for/
  29. ^ "Commission Decision of 24.03.2004 relating to a proceeding under Article 82 of the EC Treaty (Case COMP/C-3/37.792 Microsoft)" (PDF). European Commission. March 24, 2004. http://ec.europa.eu/comm/competition/antitrust/cases/decisions/37792/en.pdf. Retrieved June 17, 2009. 
  30. ^ Engelfriet, Arnoud (August/September 2006). "The best of both worlds". Intellectual Asset Management (IAM) (New Hibernia House, Winchester Walk, London Bridge, London SE1 9AG, United Kingdom: Gavin Stewart) (19). http://www.iam-magazine.com/issues/article.ashx?g=64d0a423-1249-4de3-929c-91b57c15f702. Retrieved 2008-05-19. 
  31. ^ Loftus, Jack (2007-02-19). "LinuxWorld: Managing mixed source software stacks". SearchEnterpriseLinux.com. http://searchenterpriselinux.techtarget.com/news/article/0,289142,sid39_gci1244277,00.html. 
  32. ^ Tan, Aaron (2006-12-28). "Novell: We're a 'mixed-source' company". CNET Networks, Inc. http://www.zdnetasia.com/news/software/0,39044164,61977995,00.htm. 
  33. ^ Microsoft Corporation (2005-04-01). "End-User License Agreement for Microsoft Software: Microsoft Windows XP Professional Edition Service Pack 2" (PDF). p. Page 1. http://www.microsoft.com/about/legal/useterms/. Retrieved 2009-04-29. "You may install, use, access, display and run one copy of the Software on a single computer, such as a workstation, terminal or other device (“Workstation Computer”). The Software may not be used by more than two (2) processors at any one time on any single Workstation Computer." 
  34. ^ Microsoft Corporation (2005-04-01). "End-User License Agreement for Microsoft Software: Microsoft Windows XP Professional Edition Service Pack 2" (PDF). p. Page 1. http://www.microsoft.com/about/legal/useterms/. Retrieved 2009-04-29. "You may permit a maximum of ten (10) computers or other electronic devices (each a 'Device') to connect to the Workstation Computer to utilize one or more of the following services of the Software: File Services, Print Services, Internet Information Services, Internet Connection Sharing and telephony services." 
  35. ^ Rosenberg, Donald (2000). Open Source: The Unauthorized White Papers. Foster City: IDG. pp. 109. ISBN 0-7645-4660-0. http://www.stromian.com/Book/FrontMatter.html. 
  36. ^ "Categories of Free and Non-Free Software - Free Software Foundation". http://www.fsf.org/licensing/essays/categories.html#PublicDomainSoftware. 
  37. ^ Free Software Foundation (2009-05-05). "Frequently Asked Questions about the GNU Licenses". http://www.gnu.org/licenses/gpl-faq.html#WindowsRuntimeAndGPL. Retrieved 2009-06-25. 
  38. ^ Richard Stallman (2004-04-12). "Free But Shackled - The Java Trap". http://www.gnu.org/philosophy/java-trap.html. Retrieved 2009-06-25. 
  39. ^ Tony Patton (2008-11-21). "Protect your JavaScript with obfuscation". http://blogs.techrepublic.com.com/programming-and-development/?p=762. Retrieved 2009-06-12. "While the Web promotes the sharing of such code, there are times when you or a client may not want to share their JavaScript code. This may be due to the sensitive nature of data within the code, proprietary calculations, or any other scenario." 
  40. ^ Brian Braiker (2008-05-02). "A Killer Product: Will closed devices like Apple's iPhone murder the Web?". http://www.newsweek.com/id/135150. Retrieved 2009-06-16. "Through historical accident, we've ended up with a global network that pretty much allows anybody to communicate with anyone else at any time. Devices could be reprogrammed by them at any time, including code written by other people, so you don't have to be a nerd to get the benefits of reprogramming it. [But] this is an historical accident. Now, I see a movement away from that framework--even though it doesn't feel like a movement away. [For example,] an iPhone can only be changed by Steve Jobs or soon, with the software development kit, by programmers that he personally approves that go through his iPhone apps store. Or whimsical applications that run on the Facebook platform or the new Google apps. These are controllable by their vendors in ways that Bill Gates never dreamed of controlling Windows applications. [...] That's the ironic thing. Bill Gates is Mr. Proprietary. But for my purposes, even under the standard Windows operating system from 1990, 1991, you write the code, you can hand it to somebody else and they can run it. Bill Gates has nothing to say about it. So it's funny to think that by moving in Steve Jobs's direction it actually ends up far more proprietary." 
Retrieved from "http://en.wikipedia.org/wiki/Proprietary_software"
Personal tools
Namespaces
Variants
Actions
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)