SCO: Tip of the Iceberg?



Email    print   
October 15, 2003 —  (Page 1 of 2)
In an impressive show of unity, the open-source community has roundly condemned SCO's lawsuit, which alleges copyrighted source code was placed in the Linux source tree. Every pundit, analyst and user has inveighed on the topic.

However, we must do more than fulminate about the SCO problem. Consider the possibility that SCO might be just the tip of the iceberg. Given the recording industry's decision to go after users who downloaded copyrighted works, a greater enforcement of copyrights is likely to be the norm, and SCO is not a one-time problem. We need to start formulating over-arching solutions.

Three categories of problems lurk: trade secrets, patents and, of course, copyrights.

Let's start with trade secrets. Say a disgruntled programmer "contributes" a key piece of source code that reveals a trade secret. Another firm picks it up not knowing its origins and develops a successful competing product. When the original company discovers the leak, it can no longer close the barn door because the trade secret has been distributed worldwide. What can that company do? And what are the obligations of all the other companies-such as Red Hat in the case of Linux-that might have profited from the sale of products containing the code?

Patents are a different problem. They are frequently violated unintentionally, and accountability can be demanded long after the violation took place. Let us recall Unisys' pursuit of licensing fees for GIF files (due to a patent on GIF's compression algorithms) long after GIFs had become an accepted standard.

Equally astonishing was the discovery that using XOR to reverse pixels for displaying an image was a violation. But patent 4,197,590, filed in 1980 made it so. In fact, the inadvertent violation of patents and delayed enforcement are often a remedy to patent suits: The typical scenario is that someone sues IBM for patent violations, IBM responds by finding one of its 10,000 patents violated in the accuser's software, and they settle the suit by licensing the technologies to each other. However, in the case of open-source products, how would such a quid pro quo work?




Pages 1 2 


Share this link: http://sdt.bz/27455
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Zeichick's Take: SCO: Not the Victory I Wanted
This week's news that a judge ruled that Novell, not SCO, owned the copyrights to Unix and UnixWare Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb