Slashdot Mirror


Microsoft Releases Pre-2007 Binary File Format Specs

An anonymous reader writes "Microsoft has released the specifications for the binary file formats used by pre-2007 Microsoft Office applications. They're accurate this time! Honest! While the documents are enormous (Word alone requires 533 pages; Excel runs over 1000 plus another 850 pages for the Office 2007 binary format), they hopefully will be useful to developers trying to create or extract information from Microsoft Office files (which despite their flaws, have been the de facto standard in many fields for some time now)."

78 of 269 comments (clear)

  1. ,,, or undo file corruption? by MickLinux · · Score: 5, Interesting

    I know it's old hat by now, but back in the Office 98 days, file corruption was a big deal.

    I wonder what was going on, but it occurs to me that now I could concievably actually back out
    the errors, and figure the thing out.

    --
    Correct Horse Battery Staple: 72 bits of entropy. Enter "Correct H" into google. When it generates the phrase, that's
    1. Re:,,, or undo file corruption? by Anonymous Coward · · Score: 2, Interesting

      It might have been software state corruption unrelated to the file format, and so this might not help (I'm not asserting it does help either way).

      If this is anything like their previous documentation it will be full of errors and omissions. Wait until this has been reviewed by engineers who reverse engineer their formats and then you'll know if this is more useful than (for example) the KOffice source code, or OpenOffice.org, Abiword, Gnumeric, etc.

    2. Re:,,, or undo file corruption? by stewbacca · · Score: 2, Informative

      Not trying to troll, but why is it that only Microsoft products get "corrupted"? Seriously, I use three platforms (Windows, Solaris, and OSX) and I don't ever recall a corrupted file in anything that was NOT made by Microsoft.

    3. Re:,,, or undo file corruption? by Architect_sasyr · · Score: 2, Interesting

      Work in an office with other people using the same stuff. It happens all the time. I just got back into my own office from being upstairs repairing a designers OS X.5 permissions. It happens everywhere, but because we all detest Microsoft we make more of a note of it.

      Continuing off topic for a moment: I actually notice that there are a stack of bugs I come across all the time on my Debian or CentOS boxes that I just fix and move on without ever really registering that they occured - it's a technical skill thing I think.

      --
      Me failed English...
      FreeBSD over Linux. If my comments seem odd, this may explain...
    4. Re:,,, or undo file corruption? by PitaBred · · Score: 3, Interesting

      Considering that the Office files are almost binary dumps of the software state, you're saying the same thing ;)

  2. So that's only about 2400 pages! by Anonymous Coward · · Score: 5, Interesting

    A far cry from the 6,000 pages for OOXML ..

    1. Re:So that's only about 2400 pages! by peragrin · · Score: 3, Insightful

      actually that's inaddition to the 6,000 pages for the OOXML spec since the OOXMl spec references that data.

      --
      i thought once I was found, but it was only a dream.
    2. Re:So that's only about 2400 pages! by Anonymous Coward · · Score: 2, Interesting

      You're not counting the documents for Powerpoint and various other supporting components (VBA, Forms, etc.). When all of that is included, the total is around 5000 pages. And I don't think that that counts the OLE file format specification.

    3. Re:So that's only about 2400 pages! by kestasjk · · Score: 3, Insightful

      Because "pages" are a great way to measure a specs size..

      What about line spacing, detail of information, number of examples? If the spec is clearest when fully expanded who cares if they can squeeze it onto a single page in microfilm by cutting out helpful documentation?

      Rather than looking at the number of pages why not look at the number of distinct node types/attributes? Surely that would give a better idea of spec size?

      --
      // MD_Update(&m,buf,j);
    4. Re:So that's only about 2400 pages! by chrispugh · · Score: 2, Funny

      Because "pages" are a great way to measure a specs size..

      Exactly. How many Libraries of Congress is this?

  3. How freaking "open" of them... by clang_jangle · · Score: 5, Insightful

    ...to finally share proper doc of the old standards. This just means they feel confident that MS Office 2007 will take firm enough root to ensure that the old game of catch up for FOSS projects will stay the same.
    And wasn't it just yesterday some twits had an artice about how MS is changing/will change? I sure wouldn't hold my breath!

    --
    Caveat Utilitor
    1. Re:How freaking "open" of them... by 10scjed · · Score: 5, Informative
      Not that Open...

      Some of the Microsoft protocols include patented inventions, and others do not. You may benefit from a patent license if you are distributing implementations of these protocols commercially or if you use an implementation of any of the protocols covered by Microsoft patents. For more information, contact the Microsoft Open Protocols Team.

      Check out the patent maps here

      --
      --10scjed IANAL,AFAIK
    2. Re:How freaking "open" of them... by _xeno_ · · Score: 2, Insightful

      It's useful for people who want to generate Word documents. A project I worked on wanted to generate Excel spreadsheets as a way to download reports from a web application. We got it to work using Apache POI's HSSF, which while it doesn't implement everything reverse-engineered enough for it to work.

      ...Wait a moment. Allowing people to generate documents using old formats that work with the current Office actually helps Microsoft's Office monopoly, doesn't it? And here I thought they were just being kind.

      --
      You are in a maze of twisty little relative jumps, all alike.
    3. Re:How freaking "open" of them... by clang_jangle · · Score: 2, Informative

      Thanks, good info for those who will not RTFA. Same old self-serving MS...

      --
      Caveat Utilitor
    4. Re:How freaking "open" of them... by KokorHekkus · · Score: 5, Informative
      To be fair, the article also adds:

      It is important to note that open source developers, whether commercial or non-commercial, will not need a patent license for the development of implementations of these protocols or for the non-commercial distribution of these implementations, according to Microsoft's Patent Pledge for Open Source Developers.

    5. Re:How freaking "open" of them... by Anonymous Coward · · Score: 2, Insightful

      A project I worked on wanted to generate Excel spreadsheets as a way to download reports from a web application.

      Or you could NOT be a fucking retard and just use CSV.

      But then it would be interoperable with every spreadsheet and you wouldn't be able to make the Microsoft bash. So I guess that wouldn't serve your purpose.

    6. Re:How freaking "open" of them... by Lord+Crc · · Score: 3, Insightful

      ...to finally share proper doc of the old standards. This just means they feel confident that MS Office 2007 will take firm enough root to ensure that the old game of catch up for FOSS projects will stay the same.

      I guess that whole ISO voting stuff on OOXML just passed you by?

    7. Re:How freaking "open" of them... by neokushan · · Score: 5, Insightful

      If they keep hold of the spec and don't release it, you'll bitch about them not being very friendly.

      If they release the spec to everyone and promise not to go after any Open Source projects that may take advantage of it, you'll bitch about them still trying to line their own pockets.

      Really, Microsoft has no chance of pleasing you, do they? Just accept that it's good for everyone to have open standards, regardless of the possible ulterior motives involved.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    8. Re:How freaking "open" of them... by Anonymous Coward · · Score: 2, Insightful

      not playing devil's advocate here but csv is just that: "comma separated values." he might want to include formatting, simple formulae, etc. in the generated excel file.

    9. Re:How freaking "open" of them... by smittyoneeach · · Score: 5, Funny

      Yeah, but at least they offer the appearance of wanting to feel like changing...

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    10. Re:How freaking "open" of them... by Enderandrew · · Score: 2, Informative

      Yes and no. DOCX is based on OOXML's early concept, but it does not represent that standard that MS was pushing. So technically, no one, not even Microsoft, has a product that can create or read the OOXML standard.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    11. Re:How freaking "open" of them... by Fallus+Shempus · · Score: 4, Funny

      Or you could just tab delimit it and stick a .xls on the end...

    12. Re:How freaking "open" of them... by Z34107 · · Score: 2, Insightful

      Sigh. Microsoft can never do anything right, can they?

      A week or so ago people were whining that they wouldn't release the specs. Well, they've started external documentation for the 2003 binaries - and your link has documentation links for 2007 as well.

      At least they warn you that they might have patents - this isn't some kind of submarine patent trolling operation. For commercial products, they even give you a link to some Nice People who will help you wade through the minefield.

      Not perfect, amazing, miraculous, or complete, but surely we can agree that this is a Good Thing. It definitely doesn't hurt anything.

      --
      DATABASE WOW WOW
    13. Re:How freaking "open" of them... by jsebrech · · Score: 5, Informative

      Really, Microsoft has no chance of pleasing you, do they? Just accept that it's good for everyone to have open standards, regardless of the possible ulterior motives involved.

      The point is that MS's patent licenses (and therefore their specs), due to the non-commerce clause, are not GPL compatible. See, MS is not threatened by a BSD license, because if a BSD product takes off, they can just embrace, extend, extinguish. They're really worried about GPL though, because any GPL project that succeeds is a true competitive threat.

      In short, I don't think they've opened the specs. Documented them, yes, published them, sure, but they have NOT opened them.

    14. Re:How freaking "open" of them... by Xtifr · · Score: 5, Insightful

      It is important to note that open source developers, whether commercial or non-commercial, will not need a patent license for the development of implementations of these protocols or for the non-commercial distribution of these implementations,

      So...commercial developers can develop as long as they don't distribute. Boy, that's helpful/useful. About as helpful and useful as a kick in the nuts. :)

      I still say the idea that a protocol can be patented is silly to the point of almost being an oxymoron. We can, perhaps, debate whether an implementation of a protocol can be patented, but the idea that the protocol itself can be patented seems like blatant abuse of the patent system, even if you're one of those who believes that software or business-method patents are a valid notion.

      Fortunately, it does seem to be getting easier to challenge patents. Now if only we could get MS to admit what patents they think various open source projects might be violating, so we can start the search for prior art.... :)

      (Alternatively, maybe we can keep them muttering vague threats about their patents without being specific long enough that we can ask for estoppel or laches if they ever do try to get specific. The rumblings help because that way they can't pretend that they didn't know about the supposed violations all along, a vital point in raising a defense of laches.)

    15. Re:How freaking "open" of them... by hostyle · · Score: 3, Funny

      And at least you offered the appearance of what feels like an insightful post...

      --
      Caesar si viveret, ad remum dareris.
    16. Re:How freaking "open" of them... by DickBreath · · Score: 5, Insightful

      > Sigh. Microsoft can never do anything right, can they?

      They *could* do something right, but they choose not to. It would work against their business model.

      They *could* release specs unencumbered by patents. They simply don't want to.

      True interoperability is the last thing that they truly want.

      This has happened before. It will happen again. See IBM decades ago. The entrenched monopolist is never in favor of true interoperability -- nevermind whatever they may say. Everybody else who lives on the scraps is in favor of interoperability. Who you think is right depends on whether you think the currently in power monopolist has the God given right to be the only one in the business.

      --

      I'll see your senator, and I'll raise you two judges.
    17. Re:How freaking "open" of them... by smittyoneeach · · Score: 2, Insightful

      The rest of the captives and I are keen on feeling the Rorshachian "Yes We Can" zietgiest so prevalent in modern politics and this Microsoft announcement, as we sit chained to the oar.

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    18. Re:How freaking "open" of them... by K.+S.+Kyosuke · · Score: 2, Interesting

      F***ing bullshit, I say! Nice of them to give us precise royalty rates, but "patented" and "applied for patents" ticks instead of patent numbers? Is there *any* sane way to get to the list of USPTO patent numbers in question at all? For me, this is another FUD along the lines of "pay for something but do not ask for what you are paying (and why) otherwise we might sue you". I am so happy to live in Europe (and, at the same time, afraid that this might change really soon with all those US companies' attempts to export this crap).

      --
      Ezekiel 23:20
    19. Re:How freaking "open" of them... by Koiu+Lpoi · · Score: 2, Funny

      Even with the links, I had no idea what you said.

    20. Re:How freaking "open" of them... by sirsnork · · Score: 2, Informative

      Or you could setup Excel to trust that spreadsheet (or it's location) so that you don't get prompted with warnings etc everytime. Very easy to do and would remove, what seems to be your biggest gripe.

      --

      Normal people worry me!
    21. Re:How freaking "open" of them... by SirSlud · · Score: 2, Insightful

      Theoretically, you can't sell a product that operates natively on their data formats. But if free tools are available to translate from MS format to format X, that seems to free up commercial software to provide free translators to translate to native or other open formats.

      --
      "Old man yells at systemd"
    22. Re:How freaking "open" of them... by spitzak · · Score: 2

      Yep, they want to make sure everybody thinks "open source" and "non-commercial" are the same thing. Same old Microsoft.

    23. Re:How freaking "open" of them... by spitzak · · Score: 3, Informative

      Actually the non-commercial clause is incompatible with the BSD license as well.

    24. Re:How freaking "open" of them... by clang_jangle · · Score: 3, Insightful

      I believe he meant that this announcement from MS would give some "hostages" who wish to feel more optimistic about MS becoming less evil some false hope to brighten their dreary day.

      --
      Caveat Utilitor
    25. Re:How freaking "open" of them... by smittyoneeach · · Score: 2, Interesting

      Hostyle's sig, "If Caesar were alive, you'd be chained to an oar" inspired me.
      We're all galley slaves in this modern economy, so, as with the kool-aid vendors in the presidential campaign with their smarmy little ads, we should accept this MS announcement and decide to feel good about it.
      And that, my friend, is the Straight Audacity of a Hope Talk Express for Change You Can Wonder About.

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    26. Re:How freaking "open" of them... by ozmanjusri · · Score: 2, Informative
      It's not about implementation.

      It's about distribution.

      --
      "I've got more toys than Teruhisa Kitahara."
    27. Re:How freaking "open" of them... by dreamchaser · · Score: 2, Insightful

      You are making a mountain out of a molehill. There is no reason a standalone utility couldn't be distributed for free that works with any of those platforms.

      MS also couldn't use GPL code in their OS without issues. It works both ways. MS didn't have to releases these specs at all. I'm glad they did; it's a step in the right direction. No need to be politically militant about it.

  4. interesting... by AmaDaden · · Score: 5, Interesting

    Did anyone else notice this is coming out on the first business day at MS that is Gates free...?

    1. Re:interesting... by AmaDaden · · Score: 2

      90% joke and 10% honest question. As unlikely as it is they could have been writing/gathering these behind his back and now that he's gone he can't do anything about it. However the anti-trust ruling makes far more sense.

    2. Re:interesting... by Spy+der+Mann · · Score: 4, Funny

      Indeed. This is a strange new move by the borg.

      This reminds me the episode of House M.D. when he started acting nice one day and everyone began freaking out.

      You should chill out and think of this being more of a partial victory than an enemy's plan.

    3. Re:interesting... by jkabbe · · Score: 4, Informative

      This isn't new. MS posted an earlier revision on February 20 this year. Today's announcement is mostly about the fact that it's out of "beta".

    4. Re:interesting... by IntlHarvester · · Score: 2, Informative

      Gates is still chairman of the board and the largest stockholder.

      --
      Business. Numbers. Money. People. Computer World.
  5. I think the real question by bragolach · · Score: 5, Funny

    is WHEN are they going to release the source code to the Flight Sim in Excel 98?

    1. Re:I think the real question by MiniMike · · Score: 5, Funny

      That's actually hidden in the released documents. You have to go to a specific page of the Excel portion, and by starting at a specific line and skipping the correct numbers of lines between read lines, the spec will be revealed. The exact details are left as an exercise for the morbidly curious.

  6. wouldn't touch it with a ten foot pole... by advocate_one · · Score: 3, Interesting

    the "license" conditions no doubt will contain several pitfalls for anyone who actually wants to use it to implement a file input/output filter in conjunction with free software... and the other problem is once having seen the specification, you'll never be able to safely work on other free software projects again...

    --
    Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
  7. Old News by nmb3000 · · Score: 3, Informative

    Isn't this old news? I mean, it's been covered on Slashdot at least twice now. (Dear timothy, I'd like to introduce you to my friend Google.)

    Yes, the formats are large and complicated, but for a variety of good, if antiquated, reasons. I'd suggest anyone interested read Joel Spolsky's blog post on it (which, being posted last February, isn't news either but hey, this is Slashdot).

    --
    "What do you despise? By this are you truly known." --Princess Irulan, Manual of Muad'Dib
    /)
  8. Honest Attempt by clampolo · · Score: 4, Insightful

    I honestly believe that they are trying to give out complete information. It's just that they have 20 years of spaghetti code to somehow shape into an API document. I doubt if anyone at Microsoft really knows how the code works.

    With a 1000 page document describing how to list off spreadsheet information, I shudder to think about how organized their kernel is.

    1. Re:Honest Attempt by kentrel · · Score: 2, Interesting

      It's just that they have 20 years of spaghetti code to somehow shape into an API document. I doubt if anyone at Microsoft really knows how the code works

      Really? Care to provide some evidence for that "20 years of spaghetti code" comment. If MS can make Office 07 faster and more efficient for me to use than OpenOffice with its painfully slow operation, then surely its a miracle that they can do that despite using 20 year old spaghetti code

    2. Re:Honest Attempt by Blakey+Rat · · Score: 4, Informative

      Read this article:

      http://www.joelonsoftware.com/items/2008/02/19.html

      Summarizing how Office file formats were made super complex without anybody necessarily doing anything wrong, or anybody writing bad code.

    3. Re:Honest Attempt by syousef · · Score: 4, Insightful

      Joel on Software my arse. I do wish people would stop quoting that shill. He's a Microsoft apologist who in the past has managed to present Bill Gates' unprofessional attitude (swearing at staff etc) as some kind of misunderstood genius. No Joel, your boss was an unprofessional asshole.

      As for this article. No intern should have been working on Microsoft's flagship product even 15 years ago. That's 1992 we're talking about, not 1982. It's entirely possible to write efficient code that isn't unreadable spaghetti and it's not always a good solution to use Office automation to read office documents.

      --
      These posts express my own personal views, not those of my employer
    4. Re:Honest Attempt by Koiu+Lpoi · · Score: 2, Informative

      And everything I can do in word I can do in LaTeX - and more. Strangely enough, the LaTeX specs don't make my head spin. As much.

  9. The catch by Anonymous Coward · · Score: 4, Funny

    The released specifications are in a pre-2007 MS Office binary file format.

    1. Re:The catch by MBGMorden · · Score: 2, Funny

      You laugh, but I remember seeing someone upload (to a BBS many years ago) a copy of PKZip in .zip format . . .

      --
      "People who think they know everything are very annoying to those of us who do."-Mark Twain
  10. Kudos to them by Enderandrew · · Score: 4, Insightful

    I can't understand the negativity. Sure Microsoft has an unpleasant past, but this is a good move on their part and should be met with nothing less than praise.

    We want to encourage more behavior like this.

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
  11. Chicken and Egg by BobNET · · Score: 5, Funny

    The only problem? They released them in Word format...

    (Okay, not really -- someone must have realized that that would be silly.)

  12. Yay for Microsoft! by Tumbleweed · · Score: 2, Funny

    Wait ... what did I just say? ...

    I don't think I'm feeling well. I'm gonna go lie down now.

  13. Holy Crap! by erroneus · · Score: 4, Interesting

    Or is it Wholly Crap?

    I guess we'll see. I'm rather shocked by this. This is a kind of "giving in" gesture that is MOST uncharacteristic of Microsoft. Is this was the "Post-Gates" Microsoft will be like? How much more cooperative spirit will the community enjoy?

  14. By following the links.... by Anonymous Coward · · Score: 3, Informative

    From here -> You or anyone else has nothing to worry about. Microsoft has changed its tune.:

    Microsoft irrevocably promises not to assert any Microsoft Necessary Claims against you for making, using, selling, offering for sale, importing or distributing any implementation to the extent it conforms to a Covered Specification (âoeCovered Implementationâ), subject to the following. This is a personal promise directly from Microsoft to you, and you acknowledge as a condition of benefiting from it that no Microsoft rights are received from suppliers, distributors, or otherwise in connection with this promise. If you file, maintain or voluntarily participate in a patent infringement lawsuit against a Microsoft implementation of such Covered Specification, then this personal promise does not apply with respect to any Covered Implementation of the same Covered Specification made or used by you. To clarify, âoeMicrosoft Necessary Claimsâ are those claims of Microsoft-owned or Microsoft-controlled patents that are necessary to implement only the required portions of the Covered Specification that are described in detail and not merely referenced in such Specification. âoeCovered Specificationsâ are listed below.

    1. Re:By following the links.... by temcat · · Score: 5, Informative

      This has been dissected and shown to promise nothing - because it's impossible to clearly see what exactly the "necessary claims" are, and because useful implementation of the spec without the "merely referenced" stuff may be impossible.

    2. Re:By following the links.... by temcat · · Score: 2, Insightful

      You can't say it promises nothing if you haven't actually ATTEMPTED an implementation.

      This does not make sense. Their promise or non-promise is in no way contingent on my actions. It's me who has to consider what they promise before acting. If I find ambiguities, I'd better not act until these are clarified. And there are plenty of ambiguities. If you really can't see what they are, there are links to the analysis on Groklaw.

      I personally saw the ambiguities immediately when I read the CNS. And remember, it's non-lawyers who are going to implement the spec, so the covenant must be as clear as possible.

  15. 2 things though... by hee+gozer · · Score: 4, Insightful

    a) Does this mean the standard GNU response is now invalid?

    b) If someone writes a FOSS implementation of a .doc/.xls viewer, does that mean MSFT could more easily throw their weight to declaring .doc a standard? (Since a standard ought to have multiple implementations, although maybe office 2003 and 2007 counts as two, or office and word/excel/powerpoint viewer :p )

    1. Re:2 things though... by Sloppy · · Score: 2, Insightful

      I don't think it has made GNU's response invalid, just a little weaker. It used to be somewhere in between legally impossible and nearly impossible, to implement Microsoft's format. Now it is "merely" pragmatically impossible. It's still a joke-of-a-format, with absurdly-unnecessary complexity.

      I don't think anyone will ever write a reliable and complete (*) viewer for these formats, but I guess I shouldn't misunderestimate the amount of money someone like Novell or Sun might throw into something like that. I ain't holding my breath, though.

      (*) I have to throw in those qualifiers, because OO does often do an amazing job. The key word is "often."

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  16. Re:unusually bloated ? by IamTheRealMike · · Score: 2, Insightful

    If you think Word is only dealing with "saving text" you need to spend some time learning what it can do. The format specs are big because their users needs are big.

  17. Re:unusually bloated ? by sdpuppy · · Score: 2, Funny

    Perhaps they have a few of:


    "This Page Intentionally Left Blank"
    :-)

  18. This is old news by mastropiero · · Score: 2

    I knew about this since august 2007 and even submitted it to slashdot twice, although it didn't get picked for front page. See http://developers.slashdot.org/~mastropiero/journal/

    This is definitely useful for app developers of free software.

  19. Why the documents are so long by SnappyCrunch · · Score: 2, Interesting

    Raymond Chen (well known Microsoft blogger) linked to Joel on Software today about Why the MS Office file formats are so complicated

  20. Yes, kudos for this ... but not for MS's past by KWTm · · Score: 4, Insightful

    I can't understand the negativity. Sure Microsoft has an unpleasant past, but this is a good move on their part and should be met with nothing less than praise.
    We want to encourage more behavior like this.

    You are right. This is a great step forward. However, I think the Slashdot community, with its cynical eye on Microsoft, is reminding us to take this in the proper context. It remains to be seen whether this is the beginning of a slow but steady change of course for the world's largest software company, or whether this is a fake-out to fool people into thinking that Microsoft is nice.

    Personally, I suspect that this reflects internal conflict within Microsoft, with some portions of the behemoth trying to do something good, while another faction still trying to squeeze money out of Microsoft's unique position in the software world.

    In any case, remember how some people would say, "You always complain about Microsoft! What would it take for you to admit that Microsoft is doing something good?"

    #2 on the list was: Stop hijacking the HTML standard and make a compliant browser! Then they put out IE7. (Not perfect, but a heckuva lot better than IE6!)

    #1 on the list was: Open up the Word document file format. Okay, so they've done that. (Again, not perfect, but a heckuva lot better than what went on before!)

    Congrats, Microsoft. You did it. A little late in coming, and you really didn't impress us with your OOXML fiasco waving that money around, but I'm willing to adopt a wait-and-see attitude to see whether it's still those same money-grubbing upper level managers that are in control, or whether this really is a new day at Microsoft.

    --
    404555974007725459910684486621289147856453481154 in hex is "You sank my Battleship?"
    [GPG key in journal]
  21. Visio by llzackll · · Score: 4, Insightful

    Where is Visio ?

  22. free software .. by rs232 · · Score: 2, Insightful

    "This is definitely useful for app developers of free software"

    You mean as in you work on the implementation for free and Microsoft benefits from any commercial developments.

    --
    davecb5620@gmail.com
  23. Still, don't expect a converted Scrooge from that. by Spy+der+Mann · · Score: 2, Insightful

    I'm sure this move was somewhat forced to please the European Union or something.

    In any case, I'm sure this would be just what Sun needs to make OpenOffice(.org) more compatible with MS Office than MS Office itself :)

  24. are we clear ? by rs232 · · Score: 5, Funny

    Crystal clear to me .. :)

    --
    davecb5620@gmail.com
  25. It's a Trap! by stox · · Score: 4, Funny

    20 years ago, at what was the world's largest software project, we used to joke that if we wanted to ruin our competition, we would send them a copy of our specs. It looks to me that Microsoft got the same idea.

    --
    "To those who are overly cautious, everything is impossible. "
  26. Meh.. /.-ers by comm2k · · Score: 4, Insightful
    for all those thinking that this has anything to do with Gates leaving - you're wrong, its neither right nor interesting AND CERTAINLY NOT 5+ INSIGHTFUL.
    Microsoft releases api/ protocol specs | Feb. 2008
    http://www.theregister.co.uk/2008/02/21/microsoft_goes_open/
    Microsoft releases further specs | April. 2008
    http://www.theregister.co.uk/2008/04/08/microsoft_posts_protocol_documents/

    And they state that more will come after gathering feedback between then and June.

    Between now and June it will garner feedback from the developer community. Then, at the end of June, Microsoft will publish the final versions of technical documentation - along with definitive patent licensing terms.

  27. Has no one noticed that they're covered by "OSP"? by Anonymous Coward · · Score: 4, Informative

    This means, as far as I know, that GPL implementations are not allowed. So it's an even worse situation than before, because Free Software developers can't even look at this documentation to verify any of the conclusions of their reverse engineering.

  28. Re:Flaws by Enderandrew · · Score: 2, Interesting
    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
  29. What makes you think so? by Bearpaw · · Score: 4, Funny

    Just because Lucy has always jerked the football away doesn't mean Charlie Brown won't get to kick it this time.

  30. Re:CSV is crap by tjstork · · Score: 3, Interesting

    Wise man say building all corporate data on excel spreadhseets is building a house of cards.

    I couldn't agree with you more, but the more recent trend is to use Excel as the presentation layer, which is much, much safer. You build a web site that pumps the data out of the database, create Excel sheets dynamically, and you got a lot of happy Excel junkies.

    --
    This is my sig.