IPcentral Weblog
  The DACA Blog
  Institutions
     
  Tanks
     
  Blogs
     
  Mags
     

Thursday, January 27, 2005

 
Digital Europe
(previous | next)
 

PFF's Digital Europe web page, describing the activities we will be undertaking in Europe next month, went up this week. The events we will be co-hosting in Milan and Brussels will focus on Interoperability in the Digital World - a subject that encompasses a lot of issues. One idea that will be examined during the course of these conferences is the notion that open source software (OSS) is more conducive to "openness" and interoperability than proprietary software.

In fact, there are very strong incentives for firms in network industries generally, including the proprietary software industry, to maintain interoperability, as the economics literature demonstrates quite clearly. The reason is simple. Maintaining interoperability with complementary systems increases the value of a firm's product to its customers. There are some exceptions to this rule, but even these exceptions do not necessarily violate economic efficiency.

Software developers can pursue interoperability in a variety of ways--on their own or through voluntary industry standard-setting groups that develop common technical standards that can be used across industries in different products. This type of activity has been around for a very long time and is now being adapted to the information technology world.

Ironically, open source runs into trouble in the standard-setting process, precisely because it requires companies to share their intellectual property. Proprietary software developers are willing to share because they can receive royalties, frequently under "reasonable and non discriminatory" (RAND) terms. However, the charging of royalties is inconsistent with most OSS licenses--e.g., the GPL. Therefore, it would be difficult, if not impossible, to incorporate OSS technology in a consensus standard that also utilized proprietary technology that was subject to a royalty. Similarly, propriety software would not be shared in a standard with GPL software, if that (which it would) precluded charging royalties.

posted by Tom Lenard @ 3:28 PM | Digital Europe , IP

Link to this Entry | Printer-Friendly | Email a Comment | Post a Comment(0)

Post a Comment:





 
Blog Main
RSS Feed  
Recent Posts
  Cato Unbound Debate: Lessig's Code at Ten (Part 1: Declan's Lead Essay)
The "Firstness" of the First Amendment
Supreme Court Decision in FCC v. Fox (Part 6: Other Articles & Opinions)
Supreme Court Decision in FCC v. Fox (Part 5: The Dissents)
Schneier on Data Collection and "Deception"
NTIA names Online Safety Technical Working Group members
Supreme Court Decision in FCC v. Fox (Part 4: The Thomas Concurrence)
Supreme Court Decision in FCC v. Fox (Part 3: The Majority Decision)
Supreme Court Decision in FCC v. Fox (Part 2: Initial Thoughts)
Supreme Court Decision in FCC v. Fox (Part 1: The Decision)
Archives by Month
  May 2009
April 2009
March 2009
February 2009
  - (see all)
Archives by Topic
  - A La Carte
- Advertising
- Antitrust
- Books & Book Reviews
- Broadband
- Cable
- Campaign Finance Law
- Capitalism
- Capitol Hill
- China
- Commons
- Communications
- DACA
- Digital Americas
- Digital Europe
- Digital Europe 2006
- Digital TV
- E-commerce
- e-Government
- Economics
- Education
- Electricity
- Energy
- Events
- Exaflood
- Free Speech
- Gambling
- General
- Generic Rant
- Global Innovation
- Googlephobia
- Googlephobia
- Human Capital
- Innovation
- Internet
- Internet Governance
- Internet TV
- Interoperability
- IP
- Local Franchising
- Mass Media
- Monetary Policy
- Municipal Ownership
- Net Neutrality
- Ongoing Series
- Online Safety & Parental Controls
- Podcasts
- Privacy
- Privacy Solutions
- Regulation
- Software
- Space
- Spectrum
- Sports
- State Policy
- Supreme Court
- Taxes
- The FCC
- The FTC
- Think Tanks
- Trade
- Trademark
- Universal Service
- VoIP
- Wireless
- Wireline
Archives by Author
PFF Blogosphere Archives
We welcome comments by email - look for a link to the author's email address in the byline of each post. Please let us know if we may publish your remarks.
 










The Progress & Freedom Foundation