This article appeared in Technology Licensing Primer
Massachusetts Continuing Legal Education, May 2002
In any technology development project — from short-term contract programming to long-term outsourcing relationships, from product customizations to Web design agreements — the question of who owns the resulting developments is often a source of intense negotiation. It may also be an enormous red herring. Experienced negotiators who understand intellectual property recognize that there are many alternatives to sole and exclusive ownership that may suit either or both of the parties equally well. This article will examine these alternatives as a means to assist negotiators in protecting their (and their client’s) interests in a development relationship without allowing IP ownership disputes to sidetrack the deal.
There are three basic approaches to this issue, namely:
Lying beneath these primary structures are complex issues. For example, if the work product is a derivative work of preexisting elements, or a compilation created out of preexisting components, how does ownership of the IP Rights affect use of these preexisting items? If one party owns the IP Rights and the other receives a license, what are the terms of the license regarding scope, exclusivity, geography, duration and transferability? This article will identify, but not always resolve, these complex issues, by focusing on each of the three basic structures and considering issues that may arise and answers that may be offered.
I. Introduction
II. Developer Owns, Client Licenses
III. Client Owns, Developer Licenses
IV. Client And Developer Co-Own
V. Conclusion
Or for more information, please contact the author Howard G. Zaharoff.
Contact author | Download PDF | Print | Bookmark | Send to friend
Return to top of page
Return to Technology & IP Resources index