The
morning session was titled “IP Protection for Software” which covered the legal
regimes that might be brought bear on software. The session offered some great primers of
the various technical terms and copyright laws as well as some metaphors for
explaining free versus proprietary software. It also included a case studies, most notably the SCO vs Linux case
which Zittrain, running out of time, condensed into 15 minutes.
Some basic terms were defined:
Source
code: Source is a recipe, a set of
instructions to get at something tasty. The recipe can be passed around and shared. There are comments in code which as Zittrain
notes, “Are for the programmers when they come down from the caffeine high the
night before and help them understand what they did the night before.”
Object
code: Is the cake. Executable code for a
operating system. The stuff the runs on
the machine.
More: “Sequence, structure, and operation” – make
reflect creativity.
The
categories are starting to blur. They
initially existed for technical convenience. Lawyers seized on these distinctions to
determine how protection should work.
Public
Domain: There is object code and source
code, but chances are that you have to re-engineer the object code. The development model is one person. The license: “I’m not going to assert my copyright rights.” However, it isn’t so easy to introduce in
the public domain as Creative Commons has learned – it requires research,
memos. The other way is if the copyright
expires. For software, it is 95
years. Think what happens in 2095-97,
Windows 95 is in the public domain. People can improve it!
Free Copyleft: There is cake and a recipe. So, there are no guessing games. You get the ability to play with the recipe. The license is “GPL” or “General Public
License.” Lots of examples on www.opensource.org. The development model is like an Amish Barn
raising. (Irina got the actual photo in the presentation, my camera battery was dead.) The community is responsible
for the building. While you could have
one person write and release under GPL, but it is collective authoring. (Zittrain mentioned there is some HBS
research in how big the community needs to be. I asked him later and he gave me the name of the researcher and email, but couldn't share paper yet because it is still being written.)
Proprietary: There is cake, but not the recipe. You are getting to run it, not the schematic of
which it was built. Who knows what is
under the hood? There are many
different types of licenses …”Here’s the cake, eat it. Now, put down that fork and step away from
the cake.” Pointed to an example in
Microsoft Server software license that you can share benchmarking
information. There is an evolving hybrid
called: Shared source program. This is how
proprietary companies can jump on the os bandwagon. You can look at the recipe, but can’t make it
better. You can understand it. You can’t do a lot with it. The development model is “firm-based.” Our
community will build the barn of your dreams and we’ll give you a number to
call if the barn leaks.
Turning
to the law:
Described
the legal mechanisms that a proprietary software developer would use for
protection. They want to assert as much
control as possible. But what
activities do they want to prevent?
- Consumer reproduction of
object code
- Commercial reproduction of object code: Competitor making a copy of the code and selling them. “privacy”
- Nonliteral Copying: Other people from building from scratch a program that does the same thing or looks to the user that does the same
thing.
- Incorporation of source code
in new programs – “follow-on copying” – taking the best and building something new. Modestly improved versions of the original or slices of the original and incorporating in a larger application.
Four
Legal Tools
Trade Secrecy: Until 1980s
Contracts: until 1980s
Copyright
Protection: Slowly gathers popularity and becomes the most effective and common
mechanism after 1980
Patent:
increasing
Describe
the history of copyright law which go this in 1994: “Computer programs whether object or source
code shall be protected as literary works under the Berne Convention.”
Copy Left: The General Public License
Zittrain
described the origins. The natural
instinct for MIT programmers, “I’ve got something cool, let’s share it and send
it out. Not - Eureka, where’s the lawyers.?”
The GPL
is if you bake a cake with someone’s recipe, you have to share the recipe, and
if you make a cooler cake, you better send the recipe out there. You
can still charge for physical copies of the work – once you get it and you can
make copies of it. “Handling fee.”
The GPL
is a unilateral permission. If you want
to make copies, it is okay – I won’t come after you. But you must do xyz.
Covered the case study: Sco vs Linux
- What are the larger strategies at work in the war between free and proprietary?
- Should we care who wins?
- What the international implications?
Technorati Tags: ilaw