Why Microsoft's "open" protocols may be wise to avoid

Microsoft made thousands of pages of documentation on its protocols and APIs open to all. Here's why taking a look may be bad business.

Still plowing through Van Lindberg's excellent book on open-source software law, and he discusses a court case that I somehow missed in three years of law school.

Van references IBM's efforts to keep PC clones out of the market. IBM apparently made its BIOS information (and source code) widely available as a way to poison the well. In other words, any engineers who saw the BIOS code and then attempted to reverse engineer it would be in violation of IBM's copyrights.

Hmm....While I believe Microsoft made its protocols available for public inspection due to pressure from the European Commission, the effect on developers is very similar to the IBM BIOS case. If I use the Microsoft documentation to reverse engineer or otherwise integrate Microsoft code or ideas into my own, I'm highly susceptible to a lawsuit.

This is why making information freely available, without associated IP grants freely available, perhaps does more harm than good. Code without rights is a lawsuit waiting to happen.

Featured Video
This content is rated TV-MA, and is for viewers 18 years or older. Are you of age?
Sorry, you are not old enough to view this content.

New Google OnHub router is one of a kind

Reviewing the search giant's sleek and super-cool OnHub home router (while totally and completely trusting Google with personal info).

by Dong Ngo