Microsoft Releases Specs for Binary Formats
skolima writes "In response to requests for even easier access to the Binary Formats, Microsoft has agreed to remove any intermediate steps necessary to get the documentation. They're going to just post it, making it directly available as a download on the Microsoft web site. Microsoft will also make the Binary Formats subject to its Open Specification Promise by February 15, 2008. They're even planning to include an Open Source converter implementation."
Wait, what? Brain not comprehending this. Unless TFA is a complete pack of lies, I'm going to have to give tentative applause. Perhaps the only interesting thing I can think of is that "royalty free" != "we won't sue you into oblivion if we think you're trespassing on our patents". Sorry MS, you taught me to be cynical.
Moderation Total: -1 Troll, +3 Goat
Disclaimer:IANAL
The docs are released under MS' own "Open Specification Promise" *cringes*
http://www.microsoft.com/interop/osp/default.mspx
If you do a search on GPL you get:
Q: Is this Promise consistent with open source licensing, namely the GPL? And can anyone implement the specification(s) without any concerns about Microsoft patents?
A: The Open Specification Promise is a simple and clear way to assure that the broadest audience of developers and customers working with commercial or open source software can implement the covered specification(s). We leave it to those implementing these technologies to understand the legal environments in which they operate. This includes people operating in a GPL environment. Because the General Public License (GPL) is not universally interpreted the same way by everyone, we can't give anyone a legal opinion about how our language relates to the GPL or other OSS licenses, but based on feedback from the open source community we believe that a broad audience of developers can implement the specification(s).
I don't get warm and fuzzy feelings reading this and I think that's the idea...
Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
The new format is one of the MS Office Open XML( MS-OOXML ) formats. And my guess is that this current revelation has been in the plans for some time. After all, patching Microsoft Office and disabling the OPENING of the older file formats is the perfect example of why people need an open file format. People are being shut out from using their older formats. But, out comes Microsoft saying that they'll open up those older formats and release converter code so everyone can convert to MS-OOXML. Yup, sure looks like the has been planned for quite some time.
But then there is probably a document or two inside Microsoft which shows the many paths to limit and/or destroy ODF support and to gain back any lost market due to MS-OOXML spec acceptance. For over 20 years Microsofts business model has been to beat the competition by attacking their revenue stream(s) by leveraging the 100's of millions of systems sold annually with pre-loaded Windows. Seldom has it ever used superior product attributes to win the market. I see no reason to think some switch has magically been thrown and now Microsoft wants to compete for customers in an open and level playing field. I don't think they would even know how to do this because without a complete management replacement, it's in their blood to go after the business and not the customers. Destroy the business and the customers will go to the shinny light that is Microsoft. IMO.
Regarding those new formats, there is a nice 6,000 page document that tells you how simple the new formats are so it should be very easy to implement an application which can read and display everything the spec covers. Why would you ever need code from Microsoft to help you access files based on that spec? If they can do it, anybody can. FYI, so far, there is one vendor who has applications with high levels of support of the spec and that is Microsoft.
Just look at how many apps now have a high level of support for the ODF spec:
http://opendocumentfellowship.com/applications
LoB
"Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
"This has to be good. Right ?
/windows/system/explorer.dll /windows/system/kernel.dll
How will this work with specifications that say "render text like Word 98?" Will Microsoft now document how Word 98 renders ?"
I'm sure there'll be some nice documents to tell you exactly how each of these statements work. You know, things like:
1)open file
2)scan for 0x06660666
3)take the next 128 bytes and pass them to winRulesAll(*DWORD) in
4)take the resulting array of 8bit vectors and sequentially call winConvertToBlob[0-255](LoByte(DWORD)) in
5)concatenate the results from those calls and send to sysDecryptWord95Text(URL,*DWORD) in mplayer.dll with URL=http://microsoft.com/secretdoor.asp
6)replace those 128 bytes with the results from the call or, if failed, render text like Word 95.
Easy as pie.
LoB
"Anyone who stands out in the middle of a road looks like roadkill to me." --Linus