@article {62,
	title = {Editorial: Licensing (October 2007)},
	journal = {Open Source Business Resource},
	year = {2007},
	month = {10/2007},
	publisher = {Talent First Network},
	type = {Editorial},
	address = {Ottawa},
	abstract = {In his book Open Source Licensing: Software Freedom and Intellectual 
Property Law, Lawrence Rosen defines licensing as "the legal way a copyright and patent owner grants permission to others to use his intellectual property". When you consider that  the bread and butter of a company usually revolves around its intellectual property, it{\textquoteright}s not suprising that open source licenses are often regarded with suspicion. How is it possible for a company{\textquoteright}s interests to be protected by a license written by another party? And how can a company provide "open" access to its intellectual property without "giving away the store"?

Simon Phipps, Chief Open Source Officer for Sun Microsystems, once stated in an interview: "While open source licensing lets people have access...this doesn{\textquoteright}t have to mean that chaos ensues." This issue of the OSBR provides insights to help navigate the chaos that is often associated with open source licenses.},
	issn = {1913-6102},
	url = {http://timreview.ca/article/62},
	author = {Dru Lavigne}
}
