Home -> Law Blog Directory -> Intellectual Property Law Blogs -> Groklaw

Intellectual Property Law

: Groklaw

Another Reason Microsoft's OSP Isn't Good Enough

By Pamela Jones et al.

We've seen the reasons given by the Free Software Law Center as to why Microsoft's Open Specification Promise, or OSP, provides no assurance for FOSS developers. But what about everyone else?

Here's an issue that affects everyone, not just FOSS developers, as explained by the Free Software Foundation South America in a long discussion of OOXML and why NBs should not approve it:

It carries a number of dependencies on earlier Microsoft decisions, not all of which are part of the already-huge specification, and Microsoft's promise covers only fully-compliant implementations. But Microsoft Office isn't fully compliant with the OOXML (Office Open XML) specification, therefore those who seek interoperability with Microsoft's software won't be covered by its promise.

Eek. I understand that to be saying that there are gaps in OSP coverage. You'll get documents you can't legally open unless you are using Microsoft's software, because the extensions found in Office but not in OOXML proper, so to speak, are not covered. Let me explain what I think they are saying this means.

Full post as published by Groklaw on March 27, 2008 (boomark / email).