Commentary

Serdar Yegulalp
 

Does Microsoft's TomTom Beating Bode Ill For Open Source?

Open source folks are nervous about a Microsoft lawsuit against in-car GPS maker TomTom, allegedly because of possible implications for Linux.

Open source folks are nervous about a Microsoft lawsuit against in-car GPS maker TomTom, allegedly because of possible implications for Linux.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Most of the issues seem to revolve around several patents that Microsoft filed regarding file systems. Two patents cover the use of the 8.3 file-naming convention, designed for backward compatibility between file systems that support both long and short file names. Another handles a file system for flash memory, so that a block-programmable flash device can be handled as if it were a byte- or bit-addressable file system.

So are these lawsuits against Linux or some GPL software per se? It's not clear, partly because the suit is directed at TomTom's implementations of Linux and other GPL technologies, and not at any other agency. Much of the speculation revolves around this being the tip of the sword about to run through the FOSS community, etc., but I seriously doubt Microsoft would attempt to do something that stupid and self-destructive this late in the game.

A few things are worth noting. One is that Microsoft claims it's been trying to reach an agreement with TomTom for more than a year regarding these patent claims and that it's falling back on a lawsuit as a last resort. The other is that back in 2004, TomTom ran into trouble with the gpl-violations project, apparently for modifying the Linux kernel in its TomTom GO product and not publishing the changes back to the community. Based on that, it sounds like TomTom has a generally bad history of dealing with intellectual property, period.

If this is more TomTom's fault than Microsoft's, fine. The problem, again, is that with Microsoft, people don't think that there's a clear line as to what's safe to do and what's not -- whether or not doing something wholly innocuous could get you sued. It's made all the more complicated by Microsoft's recent strides toward the open source community, where it's putting on a more conciliatory face and trying to attract many of the very people it was scaring off.

It'd be in Microsoft's best interest to come out and say, definitively, what this means vis-à-vis Linux and FOSS generally. Of course, there's always the chance that even it doesn't know -- which is in itself scary.


InformationWeek has published an in-depth report on overhauling Microsoft. 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