Ben Laurie, a major contibutor to internet security through his work at Apache, and now at Google, is generally positive about OSP but has questions: <\/p>\n
“Kim Cameron announced that Microsoft are making it possible for anyone to implement Infocard-compatible systems<\/font><\/a> (and other systems the depend on the same protocols), via the Open Specification Promise<\/font><\/a>.<\/p>\n
“First off, let me say that this is a huge step forward – there\u00e2\u20ac\u2122s been a great deal of uncertainty around WS-* and friends because of the various patents various companies own. Microsoft taking this step definitely helps.<\/p>\n
“But, there are some details that worry me – firstly I am curious why Microsoft have taken the approach of this promise rather than an explicit licence. I\u00e2\u20ac\u2122ve talked to various lawyers about it, and the general feeling I get is that they\u00e2\u20ac\u2122d be more comfortable with a licence, but they can\u00e2\u20ac\u2122t point to anything obviously wrong with the promise approach.”<\/p><\/blockquote>\n
So I need to make it absolutely clear that if anyone feels more comfortable with a RANDZ (Reasonable and Non-Discriminatory Zero Royalty) License rather than the Open Specification Promise, Microsoft will be happy to provide them with one. The goal was simply to provide a simple, clear alternative for those who wanted one. Ben continues:<\/p>\n
“Secondly, there\u00e2\u20ac\u2122s this definition:<\/p>\n
\u00e2\u20ac\u0153’Microsoft Necessary Claims’ are those claims of Microsoft-owned or Microsoft-controlled patents that are necessary to implement only the required portions<\/em> of the Covered Specification that are described in detail<\/em> and not merely referenced<\/em> in such Specification. ‘Covered Specifications’ are listed below.<\/div>\n“(my italics). Now, I\u00e2\u20ac\u2122ve implemented a lot of software from protocol specifications, and there are two things that are extremely common:<\/p>\n
\n
- “The specifications include many optional parts. These parts will not be covered by Microsoft\u00e2\u20ac\u2122s promise.<\/li>\n
- “The specifications reference other specifications for vital parts of their implementation. These parts will not be covered by Microsoft\u00e2\u20ac\u2122s promise.<\/li>\n<\/ul>\n
“Now, exactly what affect these considerations have on Microsoft\u00e2\u20ac\u2122s promise and implementations of WS-* et al is something I have not had the time or energy to assess – perhaps others with more intimate knowledge of the specs could help me out there? I\u00e2\u20ac\u2122d love to hear that, in fact, this is a non-problem.”<\/p><\/blockquote>\n