Raul654 writes: Back in 2007/2008, Microsoft used a boatload of dirty tricks to ram its nascent OOXML document standard through the ISO. The ISO approved the standard in two forms — strict (which was to be a clean, fully-open standard), and transitional (which included more than 1,400 pages of legacy support, effectively rendering it unimplementable). At the time it was approved, Microsoft made a series of promises, including a promise that future versions off Microsoft Office would fully support OOXML strict, not create OOXML transitional documents, and that Microsoft would work with ISO the committee to fix more than 3,000 known errors in the standard. In April 2010, Alex Brown, who supervised OOXML's ISO approval process, posted in his blog that Microsoft had broken all of its promises — it was no longer working to refine the standard and had decided to continue the use of OOXML transitional in the next version of its Office Suite. That was more than a year ago. What's the status of OOXML today?
Raul654 writes: In March, the jury in the Novell/SCO case found that Novell owns the copyright to Unix. Now, SCO's lawyers have asked judge Ted Stewart to order Novell to turn over the Unix copyright to them. "SCO contends the jury did not answer the specific issue before Stewart that involves a legal principle called 'specific performance,' under which a party can ask a court to order another party to fulfill an aspect of an agreement."
Raul654 writes: OOXML is the word document format that Microsoft rammed through the ISO last year. Last week, Slashdot ran a story about a blog post by Alex Brown, who was instrumental in getting the OOXML approved by the ISO. Brown criticized Microsoft for reneging on their promise to support OOXML in the upcoming release of Office 2010, and for its lackadaisical approach to fixing the many bugs which still remain in the specification. Now, Doug Mahugh has responded to Brown's post, promising that Microsoft will support OOXML "no later than Office 15."