IBM Position on Microsoft XML Schema
This week I've been analyzing the Microsoft XML Schema Ecma commitment and covenant not to sue. Here are IBM's questions on the same topic
What’s happening in the world of consortia, standards,
and open source software
The Standards Blog tracks and explains the way standards and open source software impact business, society, and the future. This site is hosted by Gesmer Updegrove LLP, a technology law firm based in Boston, Massachusetts, USA. GU is an internationally recognized leader in creating and representing the organizations that create and promote standards and open source software. The opinions expressed in The Standards Blog are those of the authors alone, and not necessarily those of GU. Please see the Terms of Use and Privacy Policy for this site, which appear here. You can find a summary of our services here. To learn how GU can help you, contact: Andrew Updegrove
This week I've been analyzing the Microsoft XML Schema Ecma commitment and covenant not to sue. Here are IBM's questions on the same topic
In a recent op/ed piece on the Massachusetts legislature's attempt to strip Peter Quinn of his policy power I asked whether the State House would prove to live up to the Commonwealth's ideal of a City on a Hill, or down to Tammany Hall. An article in today's Globe suggests the wrong answer.
NOTE: The Microsoft covenant that is analyzed below has been amended several times by Microsoft. As a result, the promise at is appears at the Microsoft site is not identical to the one that I reviewed in writing this post. Further, there is no change history at the Microsoft site. As a result, the following analysis is no longer complete or current, and should therefore not be relied upon.
In a previous post, I compared the Microsoft XML Schema covenant not to sue with that offered by Sun in favor of ODF, and concluded it fell short. But how does Microsoft's covenant compare to its old XML Schema? From that perspective, its a real improvement.
NOTE: The version of the covenant that is currently posted at the OSP page of the Microsoft Web site has been amended multiple times since this blog entry was written. Accordingly, it should not be regarded as a current or complete as to the OSP as it applies today. Just a few minutes ago, Microsoft posted its "covenant not to sue" implementes of its Office formats. I was able to get an advance copy, and here is a line by line legal analysis and comparison to the Sun covenant that supports ODF. Sun's wins by a mile.
The dust hasn't settled yet, but more of Microsoft's strategy is becoming clear. Here is a comprehensive review of what's become available so far.
China's Open Source Software Promotion Union says that it will be introducing "its own Linux standard" next year - and the association representing traditional software vendors in China doesn't like it. Only in the Massachusetts government are people still thinking that way today in these parts.
Ever since I interviewed Microsoft's Alan Yates back in September in connection with the Massachusetts/ODF story I've been wondering what Microsoft's strategy has been to fend off the challenge to Microsoft Office that the OASIS format standard presented. Today we found out.
19,000 people went to Tunis to figure out how to bridge the Digital Divide between the first and the third world. How could the hundreds of press representatives there have found virtually nothing about open source worth reporting?
In the run up to the Tunis Summit, someone blinked on the face-off over Internet governance. The questions is, who - the U.S.? The opposition? Or maybe both? For now, its all spin.
Linda Hamel, the General Counsel of the Massachusetts Information Technology Division (ITD) has filed her brief in support of the ITD's ODF policy. Here it is.