Commentary

Thomas Claburn
 

Do Software Makers Have to Protect Rivals?

In "Microsoft Search Compromise Could Hinder Innovation," Boston University law professor Keith Hylton raised the issue of how the government's case against Microsoft appears to have expanded antitrust law to include an obligation on the part of software companies to protect rivals. This is not an endorsement of Microsoft's behavior or criticism of Google's complaint about how Vista handles search. Rather, it's an observation about the possible direction of future antitrust lawsuits.

In "Microsoft Search Compromise Could Hinder Innovation," Boston University law professor Keith Hylton raised the issue of how the government's case against Microsoft appears to have expanded antitrust law to include an obligation on the part of software companies to protect rivals.

This is not an endorsement of Microsoft's behavior or criticism of Google's complaint about how Vista handles search. Rather, it's an observation about the possible direction of future antitrust lawsuits.The idea that dominant software companies -- those against which a plausible antitrust suit might be brought -- could face legal jeopardy if their code puts a rival at a disadvantage is intriguing. It suggests that the antitrust law now includes an implicit endorsement of openness.


More Internet Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Now, openness may well make a lot of sense from a market point of view. Customer demand has been one of the driving forces behind IT interoperability, but there's a case for closed systems, too.

The question is whether Microsoft and Apple will see their ability to control their respective operating systems continue to diminish as rivals demand interoperability and equal access to computing resources.

Indeed, it's plausible that this argument could be applied to online companies like Google.

We won't know until the right lawsuit comes along, but for now it looks a lot like the network has beaten the computer.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links