Open Standards, Open Source, Open Community

Reed, Carl
October 2007
GEOWorld;Oct2007, Vol. 20 Issue 10, p22
The author explains the difference between open source and open standards. He cite the purpose of the ten guiding principals for open-source development and use. He mentions the primary objective of special licenses that govern the use and sale of open-source software. He provides a definition of open standards.


Related Articles

  • Open Source Code May Present Licensing Risks.  // Venulex Legal Summaries;2002 Q1, p1 

    The article reports on the effects of open source codes on licensing of products. If software products such as Linux and Eclipse have open source licenses, it may easily be modified and distributed. Open source is not the same as no license term apply. Most for-profit software developers do not...

  • The Law of Code. Verma, Sameer // Decision Line;Jan2008, Vol. 39 Issue 1, p9 

    This article provides a glimpse into the importance of code, the world of software licensing, and the practical implications of moving toward adoption of free or open source software. The author presents an overview of the meaning of code, who should own it, who should license it and how, and...

  • Managing license compliance in free and open source software development. Gangadharan, G.; D'Andrea, Vincenzo; Paoli, Stefano; Weiss, Michael // Information Systems Frontiers;Apr2012, Vol. 14 Issue 2, p143 

    License compliance in Free and Open Source Software development is a significant issue today and organizations using free and open source software are predominately focusing on this issue. The non-compliance to licenses in free and open source software development leads to the loss of reputation...

  • Open Source Software License Agreement -- Definition and Legal Nature. Radovanović, Sanja // Proceedings of Novi Sad Faculty of Law / Zbornik Radova Pravnog ;2010, Vol. 44 Issue 1, p81 

    This paper analyzes the special type of software license agreements - open-source license, as a relatively new instrument of the legal trade of copyrighted software. The importance of this agreement is reflected in its increasing existence on the software market, announces that a new era in the...

  • Getting a handle on open source. Grandchamp, Steven // Network World;11/17/2008, Vol. 25 Issue 45, p36 

    The article focuses on the acquisition of legal standardization to open source technologies among enterprises. According to the author, the goal of having these technologies legalized is to put policies, systems and processes in place to assure standardizing care for its use and by which...

  • Coordination processes in open source software development: The Linux case study. Iannacci, Federico // Emergence: Complexity & Organization;2005, Vol. 7 Issue 2, p21 

    Although open source projects have been subject to extensive study, their coordination processes are still poorly understood. Drawing on organization theory, this paper sets out to remedy this imbalance by showing that large-scale open source projects exhibit three main coordination mechanisms,...

  • When Android Calls Open Source Frontiers in Smartphones. Vickers, Geoffrey P.; Frey Sr., Kelly L. // SciTech Lawyer;Winter2010, Vol. 7 Issue 3, p20 

    The article focuses on the requirements for programmers and developers working on the Android Open Source Project to have an Apache Software License. They are required complete and sign an Individual or Corporation Contributor License Grant. They are not required to relicense their creations...

  • Choosing an Open Source License. Engelfriet, Arnoud // IEEE Software;Jan/Feb2010, Vol. 27 Issue 1, p48 

    The article discusses open source software and its benefits. It defines open source software as freely available software that is licensed for use and modification, including in commercial purposes. It also cites the three basic kinds of licenses, namely, the free-for-all licenses, the keep-open...

  • Marketplace Issues in Software Planning and Design. Messerschmitt, David G.; Szyperski, Clemens // IEEE Software;May/Jun2004, Vol. 21 Issue 3, p62 

    The most recognized return-on-investment (ROI) drivers include the value to users; the cost of development, maintenance, upgrades, and customer support; and the risks of project failure, budget overrun, and revenue shortfall. This article focuses on ROl issues related to positioning software in...


Read the Article


Sorry, but this item is not currently available from your library.

Try another library?
Sign out of this library

Other Topics