Commentary

Serdar Yegulalp
 

Open Invention Network Snags Microsoft Patents

The title says it all: the Open Invention Network, an open source coalition "formed to promote Linux by using patents to create a collaborative environment", has grabbed up a few of Microsoft's patents.

The title says it all: the Open Invention Network, an open source coalition "formed to promote Linux by using patents to create a collaborative environment", has grabbed up a few of Microsoft's patents.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The details are sketchy right now, since no official release has yet been produced. TG Daily and the Wall Street Journal (subscription link) have some preliminary details. From what little has been divulged, the patents in question aren't vital -- but that's Microsoft speaking. They might well be related to things like the FAT file system, which is commonly used in Linux and elsewhere without actually being licensed from Microsoft.

Software patents are perennially touchy territory in the open source world. Like technology itself they can be used for good or ill, and they rarely remain neutral forces. I'm wondering now if the sentiment will swing from "ditch software patents altogether" to "put them in the hands of trusts that serve people and not oppress them" -- such as a nonprofit foundation. That way, the patents in question could be licensed to various entities in different implementations: an open source implementation could be governed by different rules as a closed-source one.

Right now, though, most of the relevant patents that could benefit from an arrangement like this are behind closed doors. I find it unlikely a good percentage of them could be liberated by being bought out -- if only because of the sheer amount of money that would have to change hands. But why not start small?

InformationWeek has published an in-depth report on Google's upcoming Chrome OS. Download the report here (registration required).

Follow me and the rest of InformationWeek on Twitter.


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