Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Microsoft Releases Specs for Binary Formats

Posted by Zonk on Thu Jan 17, 2008 11:21 AM
from the thanks-for-the-hand-up dept.
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."
+ -
story

Related Stories

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • The important stuff (Score:5, Informative)

    by ccguy (1116865) * on Thursday January 17 2008, @11:22AM (#22081336) Homepage
    The important stuff from the TFA:


    Microsoft agreed to:
    * Initiate a Binary Format-to-ISO/IEC JTC 1 DIS 29500 Translator Project on the open source software development web site SourceForge (http://sourceforge.net/ ) (...) The Translator Project will create software tools, plus guidance, showing how a document written using the Binary Formats can be translated to DIS 29500. The Translator will be available under the open source Berkeley Software Distribution (BSD) license (...). The Translator Project will start on February 15, 2008.
    * Make it even easier to get access to the Binary Formats documentation by posting it and making it available for a direct download on the Microsoft web site no later than February 15, 2008. The Binary Formats have been under a covenant not to sue and Microsoft will also make them available under its Open Specification Promise (see www.microsoft.com/interop/osp) by the time they are posted.
    • by tritonman (998572) on Thursday January 17 2008, @11:46AM (#22081746)
      ok, so if it's all binary formats only, does this mean they won't be releasing the specs for the notepad format? I've been waiting for this forever.
      • .LOG file format... (Score:5, Informative)

        by DarthStrydre (685032) on Thursday January 17 2008, @03:01PM (#22084298)
        The only Notepad specific "file type" is a .LOG text file, where the ASCII '.', 'L', 'O', 'G' is the file magic in the first four characters (might require after, I forget). It appends the date and time whenever you open the file. It's still "ANSI" format, but it does special stuff if it is there.
      • by hullabalucination (886901) on Thursday January 17 2008, @04:14PM (#22085342) Journal

        Not to fear. I'm 9eveloping my own open so4rce reverse-engineere9 implementation of the NotePa9 format, calle9 OpenPa9. I estimate that I've got abo4t 96% of the format fig4re9 o4t. As a matter of fact, my post here was compose9 originally in OpenPa9 then copie9 an9 paste9 into the Slash9ot comment s4bmission page.

        * * * * *

        Oh, squi9beaks!

    • by MrNemesis (587188) on Thursday January 17 2008, @12:02PM (#22081974) Homepage Journal
      February 15th? Are they merely trying to recruit the programmers who attempted suicide the previous evening on account of not getting lucky?

      "Decoding MS binary formats - it's better than death!" ;)
        • by Chris Burke (6130) on Thursday January 17 2008, @12:23PM (#22082286) Homepage
          They must be worried sick about the ISO meeting in February, scheduled for a week after this grand opening. It's make or break time for MS-OOXML.

          Meaning there won't be enough time to fully investigate whether these specs are actually useful or just PR BS like every other "Open" thing MS has done. Forgive me for preemptively assuming the latter.
        • Please note that the slogan I gave was from their marketing department. Any resemblance the actual decoder work has with pure, unadulterated hellfire of the anus that makes you wish you and everyone you'd ever met was dead is purely coincidental and not covered by their "CompilesForSure!" guarantee.
      • by Locutus (9039) on Thursday January 17 2008, @12:41PM (#22082480)
        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 [opendocume...owship.com]

        LoB
          • by Locutus (9039) on Thursday January 17 2008, @04:25PM (#22085518)
            This Goliath is afraid of his own shadow. This Goliath stomps on any bit of movement in his vicinity. When the wind blows, this Goliath musters all of its mass and vaporized the limb that caused the wind to blow. There is no movement in this game with Goliath, it is not allowed. If this Goliath were in an archery competition, instead of firing an accurate shot, this Goliath would first step on the competitor to eliminate the possibility of anything but his own arrow being shooting toward the target.

            As you said, there is no level playing field and businesses need to understand this. Microsoft has for 20 something years prevented many many other companies from providing solutions to businesses using these monster crushing tactics. Unfortunately most don't even know this. They just think that Microsoft got where it is because it had/has the best product(s). Regardless of how it got its size, its use of that size has destroyed many companies who attempted to get products into the desktop computer market place. Same goes for handhelds.

            Oh, and if Goliath was in a race to the moon with someone else, they'd just make sure the others in the race couldn't get the parts for their rocket or materials to build the launch pad. Goliath would probably not make it to the moon either. Instead, he would build something which couldn't even escape out atmosphere but since he was the only one in the race, all observers think he is an amazing genius and vastly skilled.

            So if the whining somehow opens someones eyes to how bad for everyone Goliath is, then the whining is being productive. People need to know the beast they are funding, the beast they are enabling, the beast they are almost glued to because of their choices in a partnership.

            I do agree that there is way too much time wasted in discussions when it would be better spent supporting valid opposition. Talking with fresh college graduates exposed me to the naivety(?) of Microsofts business tactics and what it means to dictating how businesses leverage the IT toolbox. Since showing off better technology seldom gets accepted because of the "everyone else is using Windows" mentality, explaining why their success is limited by Microsoft's market control sometimes opens them up to what all these other tools are and the 'other' value they bring to the table.

            LoB
          • The underdogs always cry foul and always want someone, some government agency, some legal entity, to come to their aid and "level the playing field". Hogwash I say.

            It's not Microsoft's competitors who want open document formats.

            It's their customers.

            Microsoft is bitterly fighting the entire world's demands to adopt formats that will allow businesses, governments and private individuals choice in their software. Customers want to be able to choose lower priced tools or tools which are more focused on their specific needs, not just one bulky, expensive, rarely updated suite.

            Microsoft is fighting to keep them locked in to high prices and minimal improvement.

  • by ccguy (1116865) * on Thursday January 17 2008, @11:24AM (#22081378) Homepage
    From the TFA:

    Initiate a (...) Project on the open source software development web site SourceForge The Translator Project will start on February 15, 2008.
    I believe it's quite considerate to give both network teams enough time to unblock each other' IP ranges :-)
    • by WK2 (1072560) on Thursday January 17 2008, @12:02PM (#22081968) Homepage
      This isn't the first project that Microsoft has released on Sourceforge. They also released WiX, which is a program to build windows installation executables (similar to Nullsoft's nsis). Sourceforge is available to everybody who wants to publish an open source project, even mega-corps like Microsoft. I wouldn't suggest it any other way.
        • by whatever1856 (985063) on Thursday January 17 2008, @01:54PM (#22083424)
          It relies on Visual studio being present though, Nullsofts nSis (which I use) cares not for such restrictions. no it doesn't. It can be used with VS but you don't have to. When we started using WiX, I just used an XML editor create the files and then ran the WiX compilers and linkers from the command line. It's convenient to use it via Visual Studios, but by no means necessary.
  • Whoops (Score:5, Funny)

    by ProteusQ (665382) <proteus71@gm[ ].com ['ail' in gap]> on Thursday January 17 2008, @11:26AM (#22081410) Journal

    And they will even an Open Source converter implementation.


    Yes, I'm they will!
  • by AmaDaden (794446) on Thursday January 17 2008, @11:26AM (#22081422)
    Satan: Why did it just get so cold in here?
    • by Jason Levine (196982) on Thursday January 17 2008, @11:54AM (#22081860) Homepage
      I don't know. I'm too busy dodging those stupid flying pigs. Ack! Another one!
      • positive for Microsoft, negative for those who want to own the rights to view the contents of their data. FYI, there's 20 years of history to show that what Microsoft giveth, Microsoft taketh away. Remember, they once said that ISO will control changes to the MS Office OXML spec if standardized but in the past couple of months, changed that and said they would control changes to the spec. There is no way in hell Microsoft is not going to use this to keep changing the format and keep all others behind them
  • Intermediate steps (Score:4, Insightful)

    by autophile (640621) on Thursday January 17 2008, @11:27AM (#22081426)

    I hope these intermediate steps that they're eliminating include packaging the documents in an .exe file, and requiring MS Office to be installed. I'm looking at you, Word format!

    --Rob

  • by BigHungryJoe (737554) on Thursday January 17 2008, @11:28AM (#22081442) Homepage
    And they will even an Open Source converter implementation

    i find myself doing this all the time at work now, and it's embarrassing. I leave entire words out of emails, IMs, etc. I never used to do that. I must be getting old.

    Many times, I'll leave out a negating word, like "not", causing me to communicate the wrong idea.
    • by Locutus (9039) on Thursday January 17 2008, @12:11PM (#22082100)
      what's worst is when you proof read it before hitting the [send] button and only after seeing it in another form do you see you once again you out another word. Yup, the brain does funny things to us.

      LoB
         
  • by EMB Numbers (934125) on Thursday January 17 2008, @11:28AM (#22081446)
    This has to be good. Right ? How will this work with specifications that say "render text like Word 98?" Will Microsoft now document how Word 98 renders ?
    • by adpsimpson (956630) on Thursday January 17 2008, @11:58AM (#22081922)

      How will this work with specifications that say "render text like Word 98?"

      As covered in this link [xmlguru.cz], it appears that most of these specifications have either been removed or documented. What this does mean is that perhaps it will be possible to truly understand what these formatting hooks refer to, not what MS have documented them as referring to...

      (Thanks to zmotula [slashdot.org] for the link)

    • by Locutus (9039) on Thursday January 17 2008, @12:57PM (#22082672)
      "This has to be good. Right ?
      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 /windows/system/explorer.dll
      4)take the resulting array of 8bit vectors and sequentially call winConvertToBlob[0-255](LoByte(DWORD)) in /windows/system/kernel.dll
      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
  • carrot (Score:3, Insightful)

    by apodyopsis (1048476) on Thursday January 17 2008, @11:30AM (#22081474)
    thats the carrot then. so where's the stick?
  • Woohoo! (Score:4, Funny)

    by MisterSquirrel (1023517) on Thursday January 17 2008, @11:30AM (#22081492)
    Wow! It sounds like Microsoft has seen the light! It's only a matter of time now before they start giving away all their software for free.
    • Re:Woohoo! (Score:5, Funny)

      by Anonymous Coward on Thursday January 17 2008, @12:04PM (#22081986)
      About time. I have for years been giving away all their software for free. ;-)
  • by afidel (530433) on Thursday January 17 2008, @11:31AM (#22081508)
    Because it ensures that the very real possibility of bitrot for the majority of documents written in the last 15 years is now greatly reduced.
  • APRIL FOOL! (Score:5, Insightful)

    by MrNemesis (587188) on Thursday January 17 2008, @11:32AM (#22081526) Homepage Journal
    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.
  • by denis-The-menace (471988) on Thursday January 17 2008, @11:34AM (#22081556)
    Disclaimer:IANAL
    The docs are released under MS' own "Open Specification Promise" *cringes*
    http://www.microsoft.com/interop/osp/default.mspx [microsoft.com]

    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...
  • by jgarra23 (1109651) on Thursday January 17 2008, @11:35AM (#22081566)
    ...and since this is slashdot, it's not good enough until they've also:

    1. refunded all money earned through use of these formats
    2. allow people to fork them and then demand that their idiot-forks get recombined into the trunk and incorporated into MS Office 09
    3. #2 isn't good enough, Microsoft must even make sure that they are in the next release of OO even though they have nothing to do with that product
    4. Clipart of Steve Ballmer throwing chairs is included
    5. it is released under the GPLv3 license
    6. the EU gets to fine them another trillion euros (with a lower-case e) for every day since 1980 that the formats have not been open
    7. none of the above points matter because Microsoft sucks anyway and no one @ slashdot uses MS Office, they all use OO (yea, right!)

    so go ahead, mod me down you fuckers.
  • by JeanBaptiste (537955) on Thursday January 17 2008, @11:37AM (#22081598)
  • by Bongfish (545460) on Thursday January 17 2008, @11:37AM (#22081600)
    Note that these specs have been available previously, royalty free, just by e-mailing MS (or so they claim), meaning that anybody who wanted them has got them, or can get them.

    The only interesting thing here is the converter they're proposing, assuming nobody beats them to it with a better one.
  • by dtjohnson (102237) on Thursday January 17 2008, @11:46AM (#22081734)
    Microsoft is releasing the specs for binary document formats. This will help those who want to support and maintain those formats so this is a gift from Microsoft. Fellow residents of Troy, let us be grateful and embrace this great offering.
  • by Locutus (9039) on Thursday January 17 2008, @11:47AM (#22081766)
    or there's no way they'd be doing this. Well, it is Microsoft so there are likely to be some problems. For instance, they could post 10,000 lines of assembly or just plain crappy C code and say, 'there you go, it's open'. Not so bad in itself but not very easy to use none the less.

    But what is really probably happening here is that ODF is getting adopted around the world by governments and once you go ODF, it's going to be a tough sell back to the pull-the-rug-out-from-under-your-feet Microsoft way. Anyways, if Microsoft really sees ODF as a credible threat, getting MS Office OXML through ISO is important, very important. But, once they can do that and gain back credibility, there is NOTHING to stop them from releasing software which others are not privy too. ie, change the format and keep everyone else chasing them.

    Remember, ISO will not be in control of the changes to the spec, Microsoft will be.

    So watch out for this good-guy mask being applied. We've seen nothing to say there isn't anything but the same old Microsoft hiding behind it. And no, I would not accept this as a first step and something to trust. ODF and open access to your own created data is too important to let a simple trick undermine it all. IMO.

    LoB
  • Exchange (Score:5, Interesting)

    by abigor (540274) on Thursday January 17 2008, @11:53AM (#22081856)
    Wait a second, does this include Exchange? If so, that's huge.
    • Re:Exchange (Score:4, Informative)

      by Anonymous Coward on Thursday January 17 2008, @01:35PM (#22083200)

      Wait a second, does this include Exchange? If so, that's huge.
      RTFA. It's .doc, .xls and .ppt.
  • In another news... (Score:4, Informative)

    by Anne Honime (828246) on Thursday January 17 2008, @12:08PM (#22082062) Homepage
    ... Lucifer has announced the launch of a massive advertisement campaign to promote the opening of his new snow park under the brand "Hell Inc."
  • by ShadowOfMe (919646) on Thursday January 17 2008, @12:52PM (#22082612)
    From wiki: a representation for numbers using only two digits (usually, 0 and 1) Nex week Microsoft will release specs for Octal format We're expecting full disclosure for Hexadecimal to follow soon.
    • by TeknoHog (164938) on Thursday January 17 2008, @11:41AM (#22081658) Homepage Journal

      thats just about every file MS Applications and OS creates no ? unless files are saved in plain ini/text/xml/humanreadable format isnt everything else a form of binary ?

      Even plain ini/text/xml etc. is eventually stored as ones and zeros. And I think I saw a 2...

    • by ByOhTek (1181381) on Thursday January 17 2008, @11:50AM (#22081808) Journal
      Try opening a word file in the plain text editor of your choice. There's actually a lot of plain text in there, it seems the binary is mostly from formatting (and embedded binary objects - like images).

      I've had an occasion or two where a word document got corrupted and office wouldn't fix it. Out of curiosity, I opened it in notepad. I cut out all the formatting bytes, and cleaned up some areas where spaces were added between characters in a section of text (WTF?), and saved the plain text. Nothing of my document was missing (since I didn't have pictures in it or anything like that).

    • "Binary Formats" is being used as a proper noun for a specific set of file formats. It is a defined term in the document:

      Documenting the Microsoft Office "binary" file formats (i.e., .doc, .xls, and .ppt) (the "Binary Formats") is not the intention or in the scope of DIS 29500.