The Software Freedom Law Center is not the first open source advocate to be skeptical of Microsoft's Open Specification Promise, but it may be one of the most prominent. Last week, SFLC published an analysis detailing why the OSP isn't as open as Microsoft says it is.
ZDNet Australia reports:
The SFLC concluded that the patent protections only apply to current versions of the specifications; future versions could not be covered...Also, software developers who write code based on a Microsoft-derived specification, such as Open XML, could be limited in how that code is used...Finally, the SFLC said that OSP-covered specifications are not compatible with the General Public License.
Microsoft, of course, doesn't agree.https://o1.qnsr.com/log/p.gif?;n=203;c=204663295;s=11915;x=7936;f=201904081034270;u=j;z=TIMESTAMP;a=20410779;e=i
Product manager Gray Knowlton responded to the SFLC's analysis one point at a time.
First, he noted that although the OSP currently applies only to listed specs, "we have already committed to extending it to ISO/IEC DIS 29500 when it is approved in our filing with ISO/IEC." Moreover, new specs can be added to the list as needed.
Second, the OSP does apply to code. As Knowlton put it:
The OSP is a promise to not assert patents that are necessarily infringed by implementations of covered specifications.
Finally, he says that the OSP is not incompatible with the GPL:
As far as we are concerned, we are happy to extend the OSP to implementers who distribute their code under any copyright license including the GPL.