01290nas a2200121   4500008004100000022001400041245004000055210003700095260004200132520094200174100001701116856003501133       2007                        eng d  a1913-610200aEditorial: Licensing (October 2007)0 aEditorial Licensing October 2007  aOttawabTalent First Networkc10/20073 aIn 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's not suprising that open source licenses are often regarded with suspicion. How is it possible for a company'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'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.1 aLavigne, Dru  uhttp://timreview.ca/article/62