Slashdot Mirror


Microsoft Standing Firm On OOXML ISO Vote

christian.einfeldt writes "Microsoft has responded via the industry trade group ECMA to some of the thousands of criticisms of its submission of Office Open XML as an ISO standard. Open standards advocate Russell Ossendryver takes a look at those responses to see if Microsoft has made significant changes in either the substance of OOXML or the manner in which the OOXML specification will be maintained going forward. Ossendryver concludes that Microsoft's position has not significantly changed, but only hardened in place in advance of the Ballot Resolution Meeting which is to occur from February 25 through 29 in Geneva. While no one can say for certain whether Microsoft will succeed in having OOXML win the nod from the international community, Ossendryer thinks that Microsoft's firm stance is likely to backfire."

181 comments

  1. How 'Firm' Would You Stand For 20 Billion A Year? by Anonymous Coward · · Score: 5, Insightful

    I believe Microsoft made 5 billion in revenue from having customers worldwide locked into their proprietary office document format.

    The vendor lockin from Office makes up almost half the company's yearly revenue.

    Microsoft would cease to exist as we know it if the office document lockin revenue went away to an open format.

    Fight? LOL! This is the type of shit Microsoft execs live for.

    Fake grassroots efforts.
    Standards body subversion.
    Paid for media shills.
    Shame studies.
    Mysterious compatibility problems with the competition.

    All in a days work.

  2. this is why we have the borg icon for MS by Anonymous Coward · · Score: 0

    We are the Borg. Lower your shields and surrender your ships. We will add your biological and technological distinctiveness to our own. Your culture will adapt to service us. Resistance is futile. it just seems so descriptive of what MS is trying to do.

    1. Re:this is why we have the borg icon for MS by Anonymous Coward · · Score: 0

      Sheesh that's a stupid comment.

    2. Re:this is why we have the borg icon for MS by erlehmann · · Score: 1

      Seems to me Anonymous is better suited for this battle - first they DDOS the transwarp hubs and then they protest right in gront of the cube- oh nevermind.

  3. This is really quite the stupid move by James_Duncan8181 · · Score: 2, Insightful

    All of the yes with comments votes now have it confirmed that their comments have noit actually been taken involved. The involvement of the EU in investigating MS's practices leading up to the fast track also means that they involved have to be more circumspect about gathering votes, so they really don't need to be annoying people like this.

    Of course, the plan could just be to say "We would have got away with ISO approval, if it wasn't for that pesky IBM". It's a bit odd, but there we are. MS is losing the EU to open standards.

    --
    "To any truly impartial person, it would be obvious that I am right."
    1. Re:This is really quite the stupid move by R3d+Jack · · Score: 1

      MS is losing the EU to open standards.

      Office is one of the products from M$ that I actually (mostly) like. The positive of all this is that M$ is feeling the heat and is responding. Of course, their response is so '90s, but we can't have everything. Hopefully, ISO will rebuff them, and the pressure on them will increase. They can make a (fairly) decent product, if someone else innovates first. Moving them off their proprietary formats (and converters, for their own junk), would make Office better and open the door for alternatives, which would in turn...

    2. Re:This is really quite the stupid move by Wraith,+The · · Score: 1

      All of the yes with comments votes now have it confirmed that their comments have noit actually been taken involved
      That is a lie. Ecma has responded with a disposition to all comments including those of countries that already voted for approval.
  4. well... by siyavash · · Score: 1, Flamebait

    well... as long as it's a real standard, doesn't really matter who came up with it. That's the whole point of standards. They are open and anyone can use them.

    1. Re:well... by MightyMartian · · Score: 5, Informative

      Which OOXML most certainly isn't. There's real doubts that even Microsoft could implement it as it currently stands.

      It's a scam, pure and simple.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    2. Re:well... by Idiot+with+a+gun · · Score: 1

      There's a lot of concern that Microsoft will do a couple things: 1) Make the standard so convoluted, that only they really understand how to implement it, or at least how to implement it well. IE, it being based around how they designed MS Word, not around making it easy to implement. 2) They want to maintain the standard. So, they could decide to add some "Features" but not tell anyone until say, MS Office 2009 is released, leaving anyone else who wants to use this "Open" standard far behind, struggling to catch up.

    3. Re:well... by Anonymous Coward · · Score: 0

      We all hate M$ but that's not what this is about. OOXML just plain sucks ass.

    4. Re:well... by Anonymous Coward · · Score: 0

      "IE, it being based around how they designed MS Word, not around making it easy to implement."

      Geez, using "IE" for that is in the context of talking about Microsoft, MS Word and what not makes you do a double-take on your read.

    5. Re:well... by 99BottlesOfBeerInMyF · · Score: 2, Informative

      IE, it being based around how they designed MS Word...

      I make a point of nat being a grammar nazi, but there does come a time where the meaning you are trying to express is obscured by grammatical errors. IE in terms of Microsoft usually refers to Internet Explorer. IE in terms of ISO means Ireland's TLD. In future you might want to try using "i.e." which the most accepted abbreviation for the latin "id est," meaning "that is; in other words" and is the least confusing way to express your meaning.

    6. Re:well... by charlieman · · Score: 2, Interesting

      What's funny is not everybody can access the standards. ISO sells most of the standards documentation. Around 100$ for a pdf of something that should be open for everyone? come on!

    7. Re:well... by cp.tar · · Score: 5, Interesting

      Which OOXML most certainly isn't. There's real doubts that even Microsoft could implement it as it currently stands.

      It's a scam, pure and simple.

      So what do we do?

      That's right: whenever you receive a .docx, .xlsx and other .*x documents, send them back, asking that they be converted into a readable format.
      Include a link for Sun's ODF plugin for MS Office, if need be.

      Fight fire with fire.

      --
      Ignore this signature. By order.
    8. Re:well... by Idiot+with+a+gun · · Score: 0

      Picky picky picky. You got the meaning, didn't you? Not punctuating that is hardly the most atrocious of grammatical errors I've seen here.

    9. Re:well... by MightyMartian · · Score: 2, Interesting

      Well, the reality is that I've had to install the compatibility pack on our Office 2003 installs. Ironically, most of this is not coming from business contacts, but from people writing from their home PCs with Office 2007 installed. As much as I'd love to tell my coworkers to send back messages saying "Save in Word 2003 format" the reality is that it's my job to make things work, so here comes the compatibility pack, the ultimate admission that whatever the ISO does or doesn't do, in the short-term, at least, we're stuck with Redmond's whims and machinations.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    10. Re:well... by KingMotley · · Score: 1

      Three separate groups have already implemented it. Novell, a sourceforge group doing doc to OOXML, and there is even a plug in for OoO. Those real doubts are just FUD.

    11. Re:well... by MightyMartian · · Score: 4, Informative

      They have partial implementations. Quit making things up. Not even Microsoft has an implemented ECMA-accepted OOXML product out there so how can you justify what you're saying.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    12. Re:well... by Anonymous Coward · · Score: 2, Funny

      I make a point of nat being a grammar nazi


      No kidding
    13. Re:well... by Anonymous Coward · · Score: 2, Informative

      Three separate groups have already implemented it. Novell, a sourceforge group doing doc to OOXML, and there is even a plug in for OoO. Those real doubts are just FUD.


      No. Not at all.

      Even if it were the case that the .docx format created by Office 2007 exactly matched the original 6000 page specification that Microsoft originally submitted to ISO (which is very dubious), since that was rejected with 3500 comments, Microsoft have had to significantly change it since then in order to try to get it accepted.

      So now we have a .docx format of Office 2007 that most decidely does not implement ECMA 376 OOXML.

      The converters you speak of, I believe, are meant for the .docx format. What then is the purpose of the ECMA 376 OOXML specification, which is not used by anything at all ... other than to create the illusion that Microsoft software is standards compliant (when it is not).
    14. Re:well... by Evil+Adrian · · Score: 1

      lol yeah, that's really professional.

      --
      evil adrian
    15. Re:well... by suckmysav · · Score: 1

      I read it, thought what has IE got to do with anything and moved to the next post. The grammar lesson is valid.

      --
      "You can't fight in here, this is the war room!"
    16. Re:well... by GaryPatterson · · Score: 2, Insightful

      You confuse open with free. Both are great, but only the first one is important.

      A standard is open for everyone to implement. ISO doesn't discriminate on who it provides copies to.

    17. Re:well... by 99BottlesOfBeerInMyF · · Score: 2, Insightful

      Picky picky picky. You got the meaning, didn't you?

      Sure, the third time I read it trying to figure out what internet explorer had to do with it.

      Not punctuating that is hardly the most atrocious of grammatical errors I've seen here.

      There are entire books I've read that eschew punctuation and were still understandable. The problem isn't lack of punctuation. The problem is lack of punctuation and improper capitalization used in a context where it makes the phrase you're trying to express not the first thing people associate with your text, nor even the second thing. I generally don't care if people use incorrect grammar. This is a casual forum where I don't proof my submissions and don't expect others to. The problem is when grammatical errors obscure the meaning to a significant extent, such that it is actually difficult to tell what it is you're trying to express.

    18. Re:well... by 99BottlesOfBeerInMyF · · Score: 2, Insightful

      No kidding

      Yep, no kidding. A grammar Nazi is a person who strictly and dogmatically points out grammatical nuances that are fairly immaterial to the readability or understandability of the text presented. This is not such a case. In this case, the error was misleading and made it very difficult for both myself and others to even understand what the writer was trying to express.

    19. Re:well... by Anonymous Coward · · Score: 0

      Does this include .tex?

    20. Re:well... by rdoger6424 · · Score: 1

      You could have at least not capitalized it. Using IE in a microsoft discussion on slashdot is always assumed to mean Internet Explorer. ie is ambiguous, and i.e. is always id est.

      --
      "Hello 911? I just tried to toast some bread, and the toaster grew an arm and stabbed me in the face!"
    21. Re:well... by fwarren · · Score: 1
      There's a lot of concern that Microsoft will do a couple things:

      3) They say they have implemented, and sure enough you can save to OOXML. Other programs that try to read it end up with junk. Everyone thinks their own implementation of OOXML filters are broke. Then 3 years down the road, it is discovered that when Microsoft saves to OOXML, it is not the same specification as they publicly stated it was.

      Seriously, how many years do you think it will take to catch Microsoft if they do a bait and switch?

      --
      vi + /etc over regedit any day of the week.
    22. Re:well... by jhol13 · · Score: 2, Informative

      I wonder ... have you installed ODF plugin? So that those workers using OOo can be supported.

      How about the other, about a million different, formats?

      I would not consider "things to work" if there is several random file formats for word documents.

    23. Re:well... by Anonymous Coward · · Score: 1, Funny

      So what do we do?

      That's right: whenever you receive a .docx, .xlsx and other .*x documents, send them back, asking that they be converted into a readable format.
      Include a link for Sun's ODF plugin for MS Office, if need be.

      Fight fire with fire.


      I sometimes send an answer in ODF format :-)

      Thomas

    24. Re:well... by myxiplx · · Score: 1

      As far as I'm concerned, educating users is part of my job. We deal with dozens of file formats here, adding multiple versions of Office documents to that would just be a nightmare when we have to send files out to third parties.

      So any of our staff who have newer versions of office get shown how to save their documents as Office 2000 compatible files. They only need showing once, and it means I don't need to install compatibility packs on a hundred or so computers, nor do I have to worry about sub-contractors not being able to open documents either.

    25. Re:well... by MightyMartian · · Score: 1

      When I start seeing a flood of ODF documents that my coworkers can't open, then I'll do it. I don't install software on the premise that some file might at some point appear in a user's incoming mail folder, but rather on the fact that such a file has arrived in their incoming mail folder. Even then, if it were just one or two over a long period of time, I'd probably hold off. I have held off on installing the Office 2007 compatibility pack for several months now, but after a week where half a dozen instances of Word 2007 docx files coming in, I figured it was time.

      Believe me, if I had my way, we'd all be moving to OpenOffice.org, but the best I can do is incremental steps. The big step for me is waiting until Evolution can handle Exchange properly (I find the calendar/scheduling handling is still iffy, and it tends to mutilate incoming POP3 messages so they're all but unreadable in Outlook). Once Evolution reaches that point, then I can make the argument that we should not be upgrading to the next version of Office, but rather moving to OO.org and Evolution.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    26. Re:well... by MightyMartian · · Score: 1, Troll

      This isn't about saving documents. Everyone in the office is required to save in Office 2003 formats. It's about incoming documents. I can hardly influence the electronic document policies of outside companies, agencies and individuals, and since my job isn't as Head IT Dictator For Life, I'm bound to make my coworkers' computer experience as easy and trouble-free as possible. If I stand on principle about refusing to install the Compatibility Pack because OOXML is a crappy, proprietary document format that isn't even compliant with horrid ECMA OOXML standard, I'll lose my job. I support Open Source everywhere I can, and as I said in another post, when Evolution reaches a point of interoperability with Exchange that I feel comfortable with, I'll gladly recommend OO.org. I will, however, still have to give some ability for my coworkers to open docx files, because they're out there and getting more common.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    27. Re:well... by calebt3 · · Score: 1

      I have held off on installing the Office 2007 compatibility pack for several months now, but after a week where half a dozen instances of Word 2007 docx files coming in, I figured it was time. Well, OOo does read OOXML files...
      Also, for those occasional ODF files just stick this on a flash drive.
    28. Re:well... by jhol13 · · Score: 2, Insightful

      I am not saying you should move to OOo.

      I am saying you really should have "official" allowed document formats list. And "what people happen to find in mail" is not the way to do this.

  5. Here's for holding onto hope by peragrin · · Score: 4, Interesting

    MSFT has so badly screwed up ISO, I can see many parties who were going to vote yes to change it into No.

    directly because of MSFT the ISO has done nothing but stumble around they can't get the majorities that they need in oder to pass standards. Everything is stagnate. Here's to hope that MSFT gamed the system so hard that it blows up in MSFT's face.

    --
    i thought once I was found, but it was only a dream.
  6. the file format is too important by FudRucker · · Score: 3, Insightful

    the file format from global communications is too important to be left to a for-profit corporation that has a history of manipulating market for maximizing profits...

    truly open file formats are the only resolution for ALL office documents used in business & government. for audio/video multimedia file formats too but office communications it is just simply too important to be left to a private corporation...

    --
    Politics is Treachery, Religion is Brainwashing
  7. Have your say by Ynot_82 · · Score: 5, Informative

    Petition currently running at noooxml.org

    http://www.noooxml.org/petition

    1. Re:Have your say by Anonymous Coward · · Score: 0

      Nice domain name for an anti-xml site. (Nooo!)

    2. Re:Have your say by Anonymous Coward · · Score: 0

      Nice domain name for an anti-xml site. (Nooo!) Is it run by Shia LaBeouf?
    3. Re:Have your say by Anonymous Coward · · Score: 0

      There has been nearly an order of mangitude increase in the rate people are signing the petition since the parent was posted.

    4. Re:Have your say by Anonymous Coward · · Score: 0

      > http://www.noooxml.org/petition

      I look at that domain name, and I can't help but read it as "donotwantxml.org".

  8. Mental Image by Jester998 · · Score: 2, Informative

    All I could think of when reading this is a M$FT rep saying "Come on, we're Microsoft! You can trust us!" while hiding a +10 Spiked Club of Patent Trolling behind their back....

  9. Dear Microsoft, by CSMatt · · Score: 4, Insightful

    Guarantee to me in writing that you will update Office 2007 and Office 2008 so that the version of OOXML that they use will be exactly identical to your ISO submission in every way, and then carry out your promise, and I will join the OOXML camp.

    Sincerely,

    ODF supporter.

    1. Re:Dear Microsoft, by TechForensics · · Score: 1

      Just exactly what do you think that guarantee would be worth, considering the effort of enforcing it?

      --
      Those are my principles, and if you don't like them... well, I have others.
    2. Re:Dear Microsoft, by jhol13 · · Score: 1

      That was funny!

      Issues related to the "leap year bug", VML, compatibility settings such as "AutoSpaceLikeWord95" and others will be extracted from the main specification and relocated to an independent annex in DIS 29500 for deprecated functionality. The intent of this Annex is to enable a transitional period during which existing binary documents being migrated to DIS 29500 can make use of those deprecated features, while noting that new documents should not use them.

      Almost as funny as that.

    3. Re:Dear Microsoft, by mwvdlee · · Score: 1

      Also please guarentee that I'll be able to work, atleast as well as I can do now, with my documents for eternity without any additional expenses ever.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    4. Re:Dear Microsoft, by Anonymous Coward · · Score: 0

      Then, in first security patch in 2009, microsoft will break compatibility. What will you do, then ?

  10. Whats the problem? by hlt32 · · Score: 0, Troll

    OOXML has been fully documented for a long time.

    It works well and plugins for OO.org already exist for it.

    Why not let it be a recognised standard?

    --
    à_à
    1. Re:Whats the problem? by Idiot+with+a+gun · · Score: 1

      See above. The current implementation of OOXML doesn't comply with the proposed standards. And how would you feel if once OOXML got passed as an ISO standard, MS sued our precious Open Office, to ensure the dominance of MS Office? So much for open.

    2. Re:Whats the problem? by ta+bu+shi+da+yu · · Score: 1

      How would they do that?

      --
      XML is like violence. If it doesn't solve the problem, use more.
    3. Re:Whats the problem? by Anonymous Coward · · Score: 5, Informative

      Why not let it be a recognised standard?


      Many reasons:
      1. There is already an ISO standard for this same purpose.
      2. There are exclusions in Microsoft's Open Specification Promise, meaning Microsoft can sue over other parties writing implementations of some of the things that the OOXML standard references (ActiveX and VBA are examples).
      3. OOXML is designed so that fully-compliant applications can only be written by Microsoft, and mostly-complaint applications can be written by other parties but only to run on a Windows platform. Therefore OOXML is not inter-operable with other applications and especially not with non-Windows platforms, and the whole purpose of making something a standard is to facilitate such inter-operation.
      4. OOXML is technically very inferior to the existing standard, ISO 26300. For example, OOXML specifies three different implementations of "a table", instead of just one common to different Office applications. This means that you cannot write a "table handling class" as a library, but instead you have to duplicate equivalent functionality several times over.
      5. OOXML includes deliberately mandating bugs (such as dates before 1900) just to pander to errors in Microsoft software.
      6. OOXML is controlled by just one corporation ... ISO 26300 belongs to ISO.
      7. ISO 26300 already has many implementations by many vendors on multiple platform. OTOH even Office 2007 running on Windows Vista does not implement OOXML ... there is not one compliant application for the OOXML that is being proposed as the standard.
      8. ISO 26300 even works with Microsoft Office (up to Office 2003) using a free plugin written by Sun. Microsoft deliberately broke Office 2007 file filters so that this plugin (or any other plugin not written by Microsoft) would not work in Office 2007.
      9. ISO 26300 has a compliance test suite. You can use this test suite to make sure a given application works properly with ISO 26300. No such thing exists with OOXML.
      10. It makes no sense to have "choice in standards" ... that just costs everybody a lot of money. It is fine to have "choice in applications" ... but ideally they should all read and write to the same standard file format ... and ISO 26300 is by far the best choice for that.
    4. Re:Whats the problem? by Idiot+with+a+gun · · Score: 4, Informative

      They actually hold multiple patents (18 currently held, or pending) that apply to OOXML. My worst fear however, is that they'll maintain the format, and change it continually, not warning anyone when they're going to make a unilateral move. Leaving everyone else who wants to read documents sent to them in that format in the dark.

  11. "Win the nod"? by ZorbaTHut · · Score: 2

    What "nod" are they trying to win? They lost the nod, and they lost it bigtime, if you take a look at the countries who didn't show up just for that one vote. The only question is whether or not they paid enough to "buy the nod".

    I'm hoping that the non-bought votes that voted "yes" last time figure out what's going on and vote "no" this time. We'll see.

    --
    Breaking Into the Industry - A development log about starting a game studio.
    1. Re:"Win the nod"? by Citizen+of+Earth · · Score: 1

      I'm hoping that the non-bought votes that voted "yes" last time figure out what's going on and vote "no" this time. We'll see.

      However, ISO has the same idiotic notion as the UN that all countries are equal, so there are probably a hundred more bullshit dictatorships that Microsoft can pay off to join the vote. I just hope that the bullshit dictatorships Microsoft paid off before make such outrageous demands for a new payoff that Microsoft refuses to pay.

    2. Re:"Win the nod"? by WilliamSChips · · Score: 1

      However, ISO has the same idiotic notion as the UN that all countries are equal Got any better ideas? Population? Oh yeah, letting China and India take 1/3 of the votes is a great idea. Democracy? Well, first, you have to define democracy.
      --
      Please, for the good of Humanity, vote Obama.
    3. Re:"Win the nod"? by rifter · · Score: 2, Interesting

      "However, ISO has the same idiotic notion as the UN that all countries are equal"

      Got any better ideas? Population? Oh yeah, letting China and India take 1/3 of the votes is a great idea. Democracy? Well, first, you have to define democracy.

      This depends on whether you are talking about the ISO or the UN. But with respect to the UN I do think that it would make sense to create a parallel organization that only admits democracies and gives votes based on population. Maybe certain measures would require a given country's delegates (who would be elected) to submit the question to a ballot in their home country. It would take time to work out details, and yeah defining democracy would take awhile (look how long it took them to define a table at the Paris peace talks, or define peace at the Camp David accords) but it would be interesting. The most immediate effect would be that with a lot of world problems being decided in a body that ONLY allows democracies, it would put pressure on other countries to comply with that definition. After all the same countries that started the UN would be in that club right from the start (No not China and probably not Russia. But pretty much all of Europe, a lot of the western hemisphere, Japan, and a whole lot of other important countries).

      Personally I think the UN has proven itself almost as useless as the League of Nations. We (the US) should still participate, but it's become mired in its own faulty institutions. It seems incapable as a body of preventing war or solving conflicts in any other way than war (which was the point of creating the UN in the first place). The members are to blame, but the system itself will need serious hacking to fix the problems that allow the members to muck it up in the first place.

    4. Re:"Win the nod"? by Citizen+of+Earth · · Score: 2, Interesting

      Population? Oh yeah, letting China and India take 1/3 of the votes is a great idea. Democracy? Well, first, you have to define democracy.

      For ISO, I would say that a formula that combines GDP with per-capita GDP would give a good measure of who the real industrial innovators and players are. China has a high GDP but a low per-capita GDP. It has massive internal corruption, but it is still a global player. Per-capita GDP provides a good measure of corruption, since corruptions syphons it off.

    5. Re:"Win the nod"? by Citizen+of+Earth · · Score: 1

      Let's say the ISO votes should be weighted by the country's PPP GDP divided by US$1-trillion plus the per-capita PPP GDP divided by US$20,000. The US would have a voting weight of 16.16; China, 7.31; Germany, 4.55; Canada, 3.18; Russia, 2.81; New Zealand, 1.48; Iran, 1.47; Brunei, 1.29; Cote d'Ivoire, 0.123 [CIA World Fact Book]. It would take quite a number of bullshit dictatorships to match the weight of a smaller first-world country — as it should be.

    6. Re:"Win the nod"? by calebt3 · · Score: 1

      And that's why they wouldn't allow the ISO to adopt this policy. Don't they have some say?

  12. Horse running, cart rolling out of gate by mugnyte · · Score: 4, Insightful

    The horse has left without the cart. Office already saves thousands, if not millions, of documents in OOXML - today. MS cannot change their format - the spec is in the field. I'm somewhat surprised they haven't taken some things into consideration for future releases, but frankly the reality set.

      OOXML is not a standard. It cannot be used to shield any entity from MS's product changes. Also, OOXML extends into nebulous areas where other implementors or translators will be unable to replicate the viewers or editors like Office. Governments or corporations must take it or leave it.

    PS
      I recently received a DOCX from an MS rep and wrote back asking for a DOC format (we've not upgraded). They sent me a PDF. Moral: OOXML isn't a standard. There's no turning back - its a conversion world, not an interoperable one.

    1. Re:Horse running, cart rolling out of gate by Anonymous Coward · · Score: 1, Insightful

      MS cannot change their format - the spec is in the field.
      Of course they can change the format, they changed from binary to Ecma-376 and they'll change it to OOXML (regardless of ISO approval). They could change it to ODF if they wanted.
    2. Re:Horse running, cart rolling out of gate by mugnyte · · Score: 1


        Not if they want to save face. This is a proud and stubborn family, you see. You cannot release Office, start saving a whole bunch of new files for it, then start changing for format too soon. Too much trouble, pklus people's backup have to still work. You have to slowly migrate the features in. Those features are polled and polled from feedback, security, and corporate wallets. Some never make it.

        Really, your best best is to write an Office plugin/addon thingy that makes ODF the default and sticks it into all the menus, doing the conversion in the background live. That tools would make a bundle.

    3. Re:Horse running, cart rolling out of gate by Anonymous Coward · · Score: 0
      Ecma-376 and OOXML allows extensions. Microsoft still get to change significantly without losing face.

      The backups isn't true -- that's just like old binaries being read into a modern app.

      Read the Becta Report about ODF in Microsoft Office for an independent view.

    4. Re:Horse running, cart rolling out of gate by AJWM · · Score: 4, Informative

      Office already saves thousands, if not millions, of documents in OOXML

      It's worse than that -- the MS-OOXML that Office saves documents in is not the same as the OOXML that MS spec'ed out to ECMA and got submitted to ISO. (This should be no surprise to anyone -- when has Microsoft ever produced software that matched the spec?) It's close, but different. Even if you could write software to the ECMA spec (doubtful since it is incomplete and ambiguous in places), it wouldn't interoperate well with MS Office.

      --
      -- Alastair
    5. Re:Horse running, cart rolling out of gate by Anonymous Coward · · Score: 2, Informative

      The horse has left without the cart. Office already saves thousands, if not millions, of documents in OOXML - today.


      Office does no such thing. Office 2007 .docx files are not ECMA 376 OOXML. Do not conflate the two as Microsoft obviously intends you to do.

      MS cannot change their format - the spec is in the field. I'm somewhat surprised they haven't taken some things into consideration for future releases, but frankly the reality set.


      If we take this as given, then let us be absolutely clear here: the result is that there is no applications and no files at all ... anywhere in the world ... that are complaint to the ECMA 376 OOXML format that is to be submitted before the upcoming BRM meeting of the ISO.
    6. Re:Horse running, cart rolling out of gate by MeNeXT · · Score: 1

      Take it or leave it? Then just leave it.

      --
      DRM? No thanks, I'll just get it somewhere else...
    7. Re:Horse running, cart rolling out of gate by mugnyte · · Score: 1

      MS-OOXML that Office saves documents in is not the same as the OOXML that MS spec'ed out to ECMA Wow. News to me.

        Wow. How utterly stupid. Thx for the info
    8. Re:Horse running, cart rolling out of gate by SEMW · · Score: 1

      The MS-OOXML that Office saves documents in is not the same as the OOXML that MS spec'ed out to ECMA and got submitted to ISO. It's close, but different Lots of people have said that in this thread, but Wikipedia has no such claim and I can't find a source for any differences with a quick Google search. Could you possibly cite a difference between the submitted spec and what MS submitted, or point me to a source that does so? Thanks!
      --
      What's purple and commutes? An Abelian grape.
    9. Re:Horse running, cart rolling out of gate by joshuaobrien · · Score: 1

      Office already saves thousands, if not millions, of documents in OOXML

      Millions of documents around the world struggle with open source cancer every day. Won't someone think of the documents?

    10. Re:Horse running, cart rolling out of gate by joelstobart · · Score: 1
      basically Microsoft has suggested over 1000 corrections and modifications to the current specification via ECMA to the ISO. Therefore; the documents you save as .docx are about as ISO OOXML complaint as they are jam. These are just suggested modifications, and no-one really knows what the OOXML standard would look like. in the unlikely event that it managed to become an ISO standard we may then see a copy of the standard many months later.

      If your feeling bored you can read the comments, and the comments about the comments, and the comments about the comments about the comments; here

    11. Re:Horse running, cart rolling out of gate by Wraith,+The · · Score: 1

      It's worse than that -- the MS-OOXML that Office saves documents in is not the same as the OOXML that MS spec'ed out to ECMA and got submitted to ISO.
      You mean similar to OpenOffice.org that is not creating ODF files that match the ISO ODF spec or even not the 1.1 ODF spec or in fact not being fully compatible with any known ODF spec version (and never has been either).
  13. This is why all governments need to fine M$ by Anonymous Coward · · Score: 0

    When they do, they should go after several hundred million per day and redistribute it to all open source projects. If M$ wants the bleeding of cash to stop, then the only stipulation the governments should allow is for M$ to open all source and release all specs to every one of their proprietary formats, both under the GPL 3. But if they refuse to comply then they will lose their whole cash reserves until they are so far in debt they will have no way of staying in business. This will be a win/win for freedom and lose/lose for M$.
    ___________________________________________
    Friends don't help friends install M$ Junk.

  14. Australia has been entirely corrupted by Microsoft by Anonymous Coward · · Score: 0

    Australia has been entirely corrupted by Microsoft. An Ecma employee is attending the BRM on Australias behalf. This makes me ashamed about my country.

  15. Can we get some *new* FUD, please? by harlows_monkeys · · Score: 0, Troll
    Can we get some new anti-OOXML FUD, please? The same old, long refuted, FUD is getting boring. My god, he even cites Stéphane Rodriguez, who makes such amazing arguments as OOXML is defective because Microsoft doesn't have a 64-bit version of Office 2007!? Huh?

    Take out his points that are wrong, and take out his points that are valid but would also apply as well to ODF, and there isn't much left.

    1. Re:Can we get some *new* FUD, please? by Zeinfeld · · Score: 0
      Can we get some new anti-OOXML FUD, please? The same old, long refuted, FUD is getting boring.

      Quite, and the idea that the objections of some anti-Microsoft zelot are objective proof that the standard is satanic evil is ridiculous.

      The fact is that there are plenty of duplicate standards. I have written for both sides of several standards wars. If people are happy with one standard, fine. If people would like more than one thats also fine.

      OOXML and ODF are both thin veneers on particular application products. There is nothing wrong with that. HTML is also a document standard.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    2. Re:Can we get some *new* FUD, please? by erlehmann · · Score: 1

      There is a distinct difference: ODF doesn't "specify" AutoFormatLikeStarOffice5.2 or WrapLinesLikeStarWriter1.0.
      I suggest you read http://ooxmlisdefectivebydesign.blogspot.com/ and see for yourself if OOXML can be considered broken from an objective POV.

    3. Re:Can we get some *new* FUD, please? by Zeinfeld · · Score: 1
      There is a distinct difference: ODF doesn't "specify" AutoFormatLikeStarOffice5.2 or WrapLinesLikeStarWriter1.0.

      Perhaps not, but there are certainly gratuitous hacks like that in plenty of IETF specs. FTP has an enormous amount of crud devoted to ASCII/EBSDIC issues, to the point that the default mode for FTP MUST be character mode and image mode is an explicit switch. Its completely unnecessary and broken of course but it goes on all the time.

      That is exactly the sort of thing I would WANT to see in a 1.0 version of a standard, and hopefully those exceptions would be deprecated and replaced over time.

      Describing the current state of affairs is definitely a best practice for standards writing. If you have the constituency then its fair to ask for an accomodation.

      Standards are not an exercise in abstract perfection.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    4. Re:Can we get some *new* FUD, please? by erlehmann · · Score: 4, Insightful

      Relying on current application behaviour is not bad per se. It is bad not to reveal what the application does. Things like autoSpaceLikeWord95 are referenced but not specified. This is objectively bad. Just think of it: I give a new screw standards paper to the ISO. It simply says that the screw can easily be driven in with my old Bauhaus 95 screwdriver. However, the spec doesn't say what the dimensions of my screwdriver actually are. Do you think ISO should make this a standard ?

    5. Re:Can we get some *new* FUD, please? by Anonymous Coward · · Score: 1, Funny

      I give a new screw standards paper to the ISO. Isn't that what Microsoft submitted?
    6. Re:Can we get some *new* FUD, please? by 99BottlesOfBeerInMyF · · Score: 2, Informative

      OOXML and ODF are both thin veneers on particular application products.

      I call bullshit on this one. I actually did look at both specs. OOXML is indeed a quick and dirty XML-like version of Office formats and doesn't even pretend to try to make functionality generic enough to make it easy for any application to implement. Even for functionality that is designed to interoperate with other types of applications OOXML is written just for the most popular add-on. ODF, on the other hand, makes a reasonable attempt at implementing functionality in a generic way so that it can be easily implemented by not only existing software packages but also new software developers who have no access to the source to existing applications. It certainly isn't perfect, but it is a night and day comparison to OOXML. ODF is already fairly well implemented by software from numerous commercial entities as well as open source projects. OOXML would be very, very hard for any third party to implement as written and it is unclear if anyone will ever be able to write to the spec instead of (as is the current case with MSOffice formats) trying to reverse engineer enough for partial compatibility.

      OOXML is MS's attempt to create something close enough to an open standard to fool some bureaucrats or give them plausible deniability when they're bribed, but at the same time make sure that users don't gain the benefits of a truly open standard, which is to say interoperability with numerous programs so that users can easily switch from one to the other and gain all the benefits of real competition. This is business as usual for MS. If you look at their "shared source" initiative it was very much the same strategy. Customers wanted the advantages of open source software (many eyes to find bugs, competitive bids for new development, guaranteed migration path and future proofing) so MS came up with something sort of like open source that they could claim was "just as good" to people who didn't understand what the benefits really were and just knew that open source was beneficial in some way.

      HTML is also a document standard.

      Yeah HTML is a document standard, but the stuff that you have to hand to IE in order to have it work properly is not HTML because it has to break the standard to work. It also fails to implement pretty much any of the last 6 years of development on HTML and other Web standards. I don't think you picked a very promising example if you're arguing in favor of MS's willingness to use standards. The whole of Web technologies has been artificially retarded by nearly a decade as a way to keep the Web from being a viable alternative platform to Windows. Progress has been crippled and billions of dollars wasted every year in order to insure MS's platform lock-in and avoid fair competition in the marketplace. The whole point of requiring standards compliance in the first place is to insure competition and the other benefits of avoiding a single vendor lock-in for office applications. MS understandably would rather have guaranteed profits than have to actually make a better product, but there is no reason why anyone other than them and people they have paid to go along with it. That is why it is important to have a truly open standard that can be and is fully implement by multiple vendors all of who are truly interoperable. OOXML is clearly an attempt to avoid that.

      Is it really possible that you don't see how ridiculous it is for giant government customers to ask vendors to create products that comply with a specification and to have one monopolist tell the customer that "No we won't make a product that meets those specifications. Unlike everyone else we're going to invent another format that is incompatible and we're going to try to force you to use it using our monopoly influence in several markets." Not only should governments not be accepting OOXML as a standard, they should be charging MS with criminal antitrust violation for trying to foist it upon them.

    7. Re:Can we get some *new* FUD, please? by harlows_monkeys · · Score: 1

      There is a distinct difference: ODF doesn't "specify" AutoFormatLikeStarOffice5.2 or WrapLinesLikeStarWriter1.0.

      Let's do a hypothetical situation, and see how you'd do it in ODF and OOXML. You've got a program that reads WordPerfect 5 files. Your job is to add ODF and OOXML support to it. While writing your WP5 to ODF and OOXML importers, you notice that WP 5 has some line spacing modes that you can't really capture in ODF or OOXML. You'd like to record somehow in the translated file that these modes were used in the original. That way, your program, which knows about those modes, can display files converted from WP 5 the same way they displayed before conversion, and if someone exports one of your ODF or OOXML files back to WP 5, you can use those modes in the exported file.

      So how do you do that? In ODF, what you'd do is define your own tag or attribute, in a namespace you'd define, and use that to mark the parts of the document that originally had WP 5 line spacing. Now you can go back and forth between ODF and WP 5, and the spacing is right, as long as it is your application used to view the documents. If you send a converted WordPerfect document to someone using OpenOffice, it won't use WP5 spacing, but that is OK. That tag of yours was just there to let programs that DO understand WP5 spacing use it if they wish.

      Meanwhile, across town, I'm ALSO changing my old application that handles WP 5 files so that it can translate to ODF and OOXML. I also come up with a tag or attribute, and a namespace. Someone gives me one of your ODF files, and I open it. Hey, guess what--no WP5 spacing. It only works on your applications, because I have no idea what your tags means.

      Not being idiots, we realize that it would make a lot of sense if we were to agree to use the same tag or attribute or WP5 spacing. That way, if someone uses your program to translate a WP5 program, mine can use the resulting ODF document. If we are smart, we publish the tag we are using, so everyone (hopefully) who has a program that understands WP5 can use the same tag to mark places in ODF documents where the original document used WP5 modes that don't translate into ODF.

      So, where should we publish that tag? The best place would be in the standard. That way, everyone who has reverse engineered WP5 will end up using the same tag, and can then have a much better chance of interoperating.

      And that is just what they've done in OOXML. There are a set of compatibility flags, all of which are like what I describe above. They took about a dozen or so things that don't represent well in OOXML (or ODF) that would be common in legacy documents (not just from Microsoft software, BTW...they have some for WordPerfect settings), and basically said "if you have software that understands those old formats, and you are going to tag places in your documents where those old formats used features that aren't in OOXML, then use these tags, so you will interoperate with others who do the same".

      There is no rational way to argue that this is bad.

    8. Re:Can we get some *new* FUD, please? by Bert64 · · Score: 1

      There are many earlier programs all with their own bugs, it makes no sense to encapsulate all of their bugs in a new format.

      If WP5 has some line spacing modes which can't be specified in a new format, then it's worth modifying the new format to handle it. The new format should be flexible enough that line spacing can be specified fairly arbitrarily. Instead of saying "line space like wordperfect 5", it should be possible to do something like "use 1cm line spacing", and specify the spacing in a standard unit of measurement. If it's not then the format should be improved to make it possible to use a generic flag like this, rather than specifically mentioning some older app.

      Programs designed to convert older WP5 documents should know that wp5 does 1cm line spacing, and specify this in the output file. If they want to convert it back, the converter program should know that 1cm line spacing corresponds to default line spacing in WP5...

      As for a rational way to argue this is bad, of course using application specific tags is bad, it's a slippery slope that potentially never ends, what about "format-like-tasword-on-the-sinclair-spectrum" ? How much extra garbage will developers of modern applications be saddled with to support ancient apps?

      If these formatting options are desirable, why not specify them in a generic flexible way, so that line spacing etc can be completely arbitrarily defined, that way you have a single way to do things, files converted from older apps will still look the same, new files can be converted to old formats instead of just existing old files being converted back. Saying "use wp5 line spacing" is lazy and pretty amateurish, saying "space lines by " is far more fitting for a modern standard.

      Why should "wp5 style line spacing" be restricted to old converted documents, what if i want to create a new file that uses wp5 style line spacing?
      Also, if you have "format like old apps" tags, what happens if you create a new document and try to convert it to a format used by these old apps? Would it save properly without these compatibility tags?

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    9. Re:Can we get some *new* FUD, please? by harlows_monkeys · · Score: 1

      Something like a "WP5 line formatting" tag isn't restricted to old documents. If you were writing a new word processor, you could add it. In ODF, you'd make up a tag, and in OOXML, you might be able to use the one they provided. But in neither case, ODF nor OOXML, would anyone else's word processor be required to support WP5 line formatting. For whatever reason, both ODF and OOXML decided not to cover all possible things from legacy documents, and so for both of them, people WILL be going beyond the standard. The difference is in OOXML, they've guessed at a dozen or so places they think this will happen, and tried to make it so different implementations extending the standard for those cases will do it in the same way.

    10. Re:Can we get some *new* FUD, please? by Bert64 · · Score: 1

      Something like a "WP5 line formatting" tag isn't restricted to old documents. If you were writing a new word processor, you could add it. In ODF, you'd make up a tag, and in OOXML, you might be able to use the one they provided. But in neither case, ODF nor OOXML, would anyone else's word processor be required to support WP5 line formatting. For whatever reason, both ODF and OOXML decided not to cover all possible things from legacy documents, and so for both of them, people WILL be going beyond the standard. The difference is in OOXML, they've guessed at a dozen or so places they think this will happen, and tried to make it so different implementations extending the standard for those cases will do it in the same way. Which is what's bad, if such formatting is necessary then it should be implemented in a generic way. If someone would explain exactly what "wp5 line formatting" and the other similarly vague quotes actually meant, it wouldn't be so hard to implement for future versions. Assuming it's really not possible with the current format (we don't know since we don't have full details of what exactly these tags mean).
      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  16. Microsoft's Latest Trick by Anonymous Coward · · Score: 3, Interesting
    1. Re:Microsoft's Latest Trick by Wraith,+The · · Score: 1

      Just because IBM and the ODF alliance (IBM's propaganda channel on ODF) say the rapport is inaccurate it does not have to be. The Burton group has responded to these allegations in several instances: http://ccsblog.burtongroup.com/collaboration_and_content/2008/02/burton-groups-r.html http://ccsblog.burtongroup.com/collaboration_and_content/2008/02/burton-groups-1.html http://ccsblog.burtongroup.com/collaboration_and_content/2008/02/burton-groups-2.html

    2. Re:Microsoft's Latest Trick by meosborne · · Score: 2, Insightful

      The Burton Group responses are a joke. Are you sure you actually read them? To them, Microsoft can do no wrong.

      It is completely disingenuous of them to go on and on about Sun controlling ODF and make no mention at all of Microsoft's control of OOXML. The ECMA TC45 committee charter explicitly stated (and the scope still does) that the OOXML standard had to be fully compatible with the file formats used in Microsoft Office. If that's not total control, then what is?

      The OASIS TC for ODF had no such provision in their charter. There were and are no artificial application dependencies in ODF.

    3. Re:Microsoft's Latest Trick by Wraith,+The · · Score: 1

      It is actually the ODF alliance response I would consider a joke. An anonymous response that looks to have been written by IBM (I even asked about that and IBM did not deny) And on the charter of the OASIS TC for ODF. You do know that this TC was called the OpenOffice XML TC in its first two years and that it's goal was actually to develop a format to make the OpenOffice format more interoperable. Only after the EU asked them to submit the OpenOffice format to ISO they changed the name to OpenDocument (a term used in an EU rapport).

  17. ECMA an RIAA-like organization? by ta+bu+shi+da+yu · · Score: 3, Insightful

    The "Deluge of facts KOs OOXML" article says that the "ECMA [is] a RIAA-like industry group dedicated to advancing its members' interests". wtf? Hardly!

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re:ECMA an RIAA-like organization? by Idiot+with+a+gun · · Score: 1

      I agree that's FUD. I'd argue more that in this case, the ECMA appears more like a rubber stamp, but I honestly don't know about more of their dealings to call it that.

    2. Re:ECMA an RIAA-like organization? by christian.einfeldt · · Score: 1
      ECMA is an industry group focused on advancing the interests of its members, which is the similarity to the RIAA. When people think of the RIAA today, they think of litigation. But the RIAA has always done more that just litigation, much like the MPAA has done more than litigation, including the famous ratings of film. At least that is what I draw from the referenced article. Here is a description of ECMA from the Wikipedia page:

      Unlike national standardization bodies, Ecma is a membership-based organization; it prides itself on the resulting "business-like" approach to standards, claimed to lead to better standards in less time thanks to a less bureaucratic process focused on getting results by consensus.
      Note that ECMA does not pretend to be plenary in scope, unlike ISO, which purports to be a truly world standards body. ECMA feels that its value stems from the business focus that it brings to discussion. It is a basic difference in world view. ISO believes that it is important to have standards that are acceptable to a much wider group; ECMA feels that its business focus can bring "better" standards to the fore in a more timely fashion. It's a continuation of the timeless debate between those who advocate the efficacy of the private sector versus the inclusion of the public sector.
  18. Re:How 'Firm' Would You Stand For 20 Billion A Yea by morgan_greywolf · · Score: 1

    Yeah, well, here's the kicker:

    If they lose, it just proves what I've said all along: in the end, being proprietary and closed will catch up with you and you will become irrelevant. Just ask a company that's had to learn that lesson the hard way over the years.

  19. We have discussed this. by Zombie+Ryushu · · Score: 2, Insightful

    We have discussed this before, and in the end it doesn't matter. Those DOCX Files are out in the wild. I see people at school saving their documents in DOCX all the time. The people using those MS Office can't open ODF Files. The Genie is out of the bottle. The ECMA can say OOXML is completely banned from becoming an ISO format ever and ODF is the true open format as it should be, in the end it makes no difference. M$ will just give the standards board the middle finger and people who use M$ Office will continue to use Office and like it because they have no other choice.

    1. Re:We have discussed this. by AJWM · · Score: 1

      If it will make no difference, then ECMA and ISO may as well give Microsoft the middle finger first and drop MS-OOXML as a proposed ISO standard. Save everyone a lot of trouble.

      But I'm curious. What makes you think that DOCX files bear more than a passing resemblence to what ECMA's proposing?

      --
      -- Alastair
    2. Re:We have discussed this. by MightyMartian · · Score: 4, Insightful

      But it does make a difference. Microsoft isn't doing this just to promulgate yet another document format. This is about the long-term viability of one of their major profit centers; the Office suite. Sure, docx is out in the wild, and sure we're all going to have to deal with until it's dumped and/or heavily modified version-by-version just as the Office 97 formats have been.

      As more and more organizations, and in particular various government agencies around the world start mandating that all documents be saved in an open format, this is where Microsoft's viability in the long term comes into question. If OOXML fails at the ISO (as it appears that it has a good chance of doing) then Microsoft has got a real long-term problem. Adopting ODF means opening up Office to meaningful competition. It means OO.org, KOffice, Google Docs and who the hell knows what else is coming down the pike over the next decade are going to start to eat into Office's huge market share.

      Now I think it's safe to say that in the medium term, Microsoft will continue with OOXML no matter what the ISO does, and it will, even if it adopts to some degree ODF try to mutilate by the "adopt, extend, extinguish" doctrine, and a good many government agencies, regardless of the mandate by politicians and senior bureaucrats, will roll over, but not all, and as long as a few major government agencies in North America and/or Europe refuse to recognize OOXML or whatever Microsoft comes up with next as an open format, the long-term viability of Office is in question.

      We're not talking about next year, or even in the next five years, but I think over the next decade or so, if Microsoft can't fool ISO into accepting its worthless, unimplementable format, then it's going to have a real problem. The whole structure of company is built on the operating system and Office divisions keeping the money rolling in. Everything else doesn't matter, and probably loses money, existing solely in the interests of brand name placement.

      The long-term solution I suspect Microsoft will move towards is some sort of rubber stamp standards commitee to compete with ISO, just like ECMA. The ultimate question is how long governments are going to let it get away with all of this. The EU seems to have a distinct hard-on against Microsoft at the moment, but the US doesn't currently give a damn one way or the other.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    3. Re:We have discussed this. by Corporate+Troll · · Score: 1

      The ECMA can say OOXML is completely banned from becoming an ISO forma

      Just a nitpick: ISO and ECMA are not related.

    4. Re:We have discussed this. by remmelt · · Score: 1

      > Microsoft has got a real long-term problem.

      Agreed. Of course, it will be good for consumers (more choice) and if spun right, good for MS as well: they will have to dig up the binder "Compete on merits, not on lock-in! (for dummies)", blow off the dust, and start making quality products again. I'm positive they can do it. This will make them look that much better, not only to customers but to us techies as well.

    5. Re:We have discussed this. by Elektroschock · · Score: 1

      Slow down, cowboy. They will be forced to support ODF out of the box when governments switch to ODF as the standard format. The DIN conversion study clearly shows that OOXML is not rich enough to represent ODF 1.0 features, not the other way around. All people want is an ODF import and export filter as part of Office09. ODF beeing an ISO standard would make governments to default to ODF.

    6. Re:We have discussed this. by Zombie+Ryushu · · Score: 1

      I know some people who work for the USian government. They don't give a damn what standard bodies certify Documents. They just care that it works.

  20. Can we get some *new* anti-ODF FUD too? by AJWM · · Score: 3, Informative

    OOXML and ODF are both thin veneers on particular application products.

    OOXML may be (or pretend to be), but what application products were you thinking of for ODF? Were you aware that KOffice (no relation at all to OpenOffice.org) also uses ODF as its native document format? The old StarOffice/OpenOffice.org formats (.sxw, .sxc, etc) were vaguly similar to the ODF formats, but not the same. (And of course native formats aside, there are plenty of other office apps that can read/write ODF.)

    The "thin veneer" argument against ODF is just Microsoft FUD.

    --
    -- Alastair
  21. Apple isn't proprieta- NO WAIT ! by erlehmann · · Score: 0, Flamebait

    Yeah Apple is so open and this is the reason i can run OS X on my beige bo- OH WAIT I CANNOT !
    But that's not such an issue at least songs i downloaded with Itunes can be played on my noname mp3 play- OH NOES IT FAILS !
    Well at least Itunes runs on Linux, to- SHIT IT DOESN'T !

    1. Re:Apple isn't proprieta- NO WAIT ! by rifter · · Score: 2, Informative

      Point taken; however ...

      Yeah Apple is so open and this is the reason i can run OS X on my beige bo- OH WAIT I CANNOT !

      Actually you can. There are a bunch of sites explaining how; that is much more useful than running XP on the new Intel Macs, which you can also do.

      But that's not such an issue at least songs i downloaded with Itunes can be played on my noname mp3 play- OH NOES IT FAILS !

      You have to convert them first; you can do that in Itunes.

      Well at least Itunes runs on Linux, to- SHIT IT DOESN'T !

      It works with wine apparently, or Crossover Office.

      Google Knows All.

    2. Re:Apple isn't proprieta- NO WAIT ! by TeacherOfHeroes · · Score: 4, Insightful

      The fact that there are work-arounds for all of these things doesn't negate the fact that they were locked down in the first place.

      The iTunes DRM is roughly equivalant to a false positive for piracy in Windows Genuine Advantage. They've purchased the product, but now there are these digital hand-cuffs keeping them from using it. I doubt anyone saying that "false positives in WGA aren't too bad - there are work arounds. [link]" would get modded up too far, though.

    3. Re:Apple isn't proprieta- NO WAIT ! by Fred_A · · Score: 1

      The fact that there are work-arounds for all of these things doesn't negate the fact that they were locked down in the first place. I don't know where you ever got the idea that Apple was an "open" company. It's stuff is locked up at least as tight as Microsoft's. The Darwin core's openness was a PR stunt at best (just try compiling the current version).

      *However*, and that makes all the difference, Apple does *not* have a monopoly on the desktop. So they are free to do as they please. And apparently whatever it is they are doing, it doesn't bother their customers (yet).

      So comparing Apple to Microsoft is just plain meaningless. In the current context, they have nothing in common.
      --

      May contain traces of nut.
      Made from the freshest electrons.
    4. Re:Apple isn't proprieta- NO WAIT ! by 99BottlesOfBeerInMyF · · Score: 1

      Yeah Apple is so open and this is the reason i can run OS X on my beige bo- OH WAIT I CANNOT !

      You're confusing "open" with "free" (as in freedom). Actually OS X is open enough that you can run it on a beige box. It is, however, not free, so the license prohibits you from doing this legally. If you want to complain about Apple not being open enough, you should have picked something else, like not being able to easily customize the native GUI.

      But that's not such an issue at least songs i downloaded with Itunes can be played on my noname mp3 play- OH NOES IT FAILS !

      Again, this used to be a valid, complaint, excepting the fact that this was a requirement from the RIAA cartel and Apple was actually the company that pressured them into changing that policy... so your complaint falls a little flat. Apple sells non-DRM'd music these days and while it is not in the MP3 format, it is in the MP4 format, which is actually slightly more open in terms of licensing, since the royalty requirements for MP4 are slightly more free (both are equally open as they are both fully documented codecs). If you bought a music player that doesn't support MP4, well that is just as if you bought a really outdated one that doesn't support anything but .WAV files. It isn't Apple's fault as they don't license either codec, the MPEG group does. Most players do support it these days, including even Microsoft's Zune player.

      Well at least Itunes runs on Linux, to- SHIT IT DOESN'T !

      This one sort of applies, in that it is neither open nor free and as a result you can't port it to Linux yourself without getting a license to the code from Apple. This isn't really much of an issue, however, since it is simply a matter of a software company not maintaining a port for platform X (being Linux in this case). I guess you could argue that all software should be free and open, but I doubt if you'll get a lot of investment in commercial end user applications that way. Just use one of the many programs that do support it, or WINE, which runs it just fine.

    5. Re:Apple isn't proprieta- NO WAIT ! by tsa · · Score: 1

      That's not true. As you could see in the posts above, Apple's actions do bother at least some of their customers. I know it annoys me. But they compensate for their practices a lot better a=than MS does by offering a vastly superior OS and beutiful hardware that in some cases is worth the extra money.

      --

      -- Cheers!

    6. Re:Apple isn't proprieta- NO WAIT ! by mcrbids · · Score: 1, Interesting

      > Yeah Apple is so open and this is the reason i can run OS X on my beige bo- OH WAIT I CANNOT !

      Actually you can. There are a bunch of sites explaining how; that is much more useful than running XP on the new Intel Macs, which you can also do. Yeah, you can get it running. If you don't care about security updates. If you take full responsibility for driver problems. If you don't mind dickering with your computer for a day or two. I never could get it to work under either VMWare Player or VMWare Workstation.

      > But that's not such an issue at least songs i downloaded with Itunes can be played on my noname mp3 play- OH NOES IT FAILS !

      You have to convert them first; you can do that in Itunes. Great. Another hack. Wouldn't it be nice if you didn't have to download software of questionable legality? Feeling that Apple love, yet?

      Neither am I.

      > Well at least Itunes runs on Linux, to- SHIT IT DOESN'T !

      It works with wine apparently, or Crossover Office. I'm noticing a pattern, here... Wine is a barely acceptable hackaround of the proprietary Win32 API. Wouldn't it be nice if iTunes actually worked... on Linux!?!?
      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    7. Re:Apple isn't proprieta- NO WAIT ! by Anonymous Coward · · Score: 0

      You don't have to buy DRM'd songs off iTunes. Most of the collection is available without it, and the industry seems to be moving away from it as well. iTunes supports converting directly to MP3 as well, so you the iPod lock in is completely gone now.

      You have always been able to burn a CD in iTunes and rerip to MP3 as well. Try this with your favorite 'other' DRM scheme.

    8. Re:Apple isn't proprieta- NO WAIT ! by Bert64 · · Score: 1

      Apple is more open than they were, OSX is now based on an open source OS whereas =OS9 was based on entirely their own proprietary design, their hardware is now x86 based and fairly standard etc... They are also moving to DRM-free songs on itunes, which certainly can be played on other devices, they are in the standard AAC format (not quite as widely supported as mp3, but still a standard documented format - they play just fine on linux)...
      Companies don't change overnight, Apple are moving in the right direction.
      A probably better example of a formerly totally closed company becoming more open would be IBM...

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    9. Re:Apple isn't proprieta- NO WAIT ! by Bert64 · · Score: 1

      The DRM needed to be closed to satisfy the music companies, otherwise the itunes store wouldn't have had big name bands. Non DRM'd files work just fine...
      The AAC format is also a standard, it's not a proprietary Apple format, only the DRM is proprietary.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    10. Re:Apple isn't proprieta- NO WAIT ! by Anonymous Coward · · Score: 0

      If you think that iTunes DRM is roughly equivalent to WGA, you don't have a clue at all. iTunes doesn't phone home regularly to see if it's pirated, nor does it automatically say you are guilty if it can't phone home. Once you have a copy of a song, it will never stop playing, so there is in fact no possibility of a false positive.

      Also, if your windows installation goes south and you have to reinstall, you've lost everything unless you've made a backup copy of your keys, which I'm sure everyone does. iTunes lets you re-activate any computer because they keep the key for you.

    11. Re:Apple isn't proprieta- NO WAIT ! by rifter · · Score: 1

      Oh I don't disagree that Apple locked these things down in the first place. I just wanted to point out that there are unofficial workarounds to fix the problems. Apple has never locked anything down well enough to prevent clever people from actually doing cool things with the system. That's because a lot of the drive behind locking things down in the first place was to protect the user-friendly experience, not necessarily to stop people from using their computers in an unorthodox fashion.

      As far as that goes, they are miles ahead of Microsoft and some others one could mention. After all they did release the code for the core of their bright shiny new OS .. ok so they entered into agreements that basically meant that the crown jewel that makes it most remarkable remains closed, but the open bits (and embracing more commodity hardware) are what make hacks like the above possible.

    12. Re:Apple isn't proprieta- NO WAIT ! by anothy · · Score: 1

      you've taken the troll's bait and are now playing his game, which is rigged so that he'll win the argument. this is a bad decision. the correct response to this sort of nonsense (other than to ignore it, which is probably best) is to point out that the poster doesn't have any idea what he's talking about. you're starting with "yeah, but..." when the correct response is "no, dummy."

      "open" does not mean "does what i want". to get more specific:
      OS openness: one could actually make a reasonable point here, but the GP doesn't. the interfaces between the OS and the outside world are documented. third parties can develop for OS X in exactly the same way Apple can. it's even possible to create a "clean" implementation (see Gnustep; the fact that they don't have the manpower does nothing to impact the point) for going in the other direction. one could certainly take issue with the control-of-definition issue (Apple has only informal community input), but the documentation gets them a long way there. the open source nature of their core source code gets them a lot further.

      iTunes songs on other hardware: any song you rip from a CD or other locally-imported source will work on any digital audio device supporting either mp3 or AAC (both independent, open standards). many songs you purchase from iTunes Music Store will work the same way (the iTunes Plus tracks; a growing percentage). as for the rest, it's not really Apple's product that he's complaining about, it's the record companies'; Apple just provides the marketplace. and they've provided an easy way to sell compatible, portable product for those who choose that path (and encouraged them to do so). it's worth noting that there's absolutely no issue with taking pretty much any third-party media and playing it on Apple hardware (unlike hardware from a great many other sources).

      iTunes platform support: the weakest point in the bunch. the fact that iTunes doesn't run on your OS of choice has nothing at all to do with openness. i'm willing to bet dollars to doughnuts that your favorite media player doesn't run on my favorite OS, either, despite the fact that mine is OSI-approved "Open Source" and implements multiple open standards from ISO, ANSI, and so on, and yours may well be GPL'd or similar. "open" is not a magic word. iTunes doesn't run on Linux because Apple doesn't consider the cost worth it.

      dummies like the GP see the word "open" and associate it with a very narrow definition of "open source" or, in the worst cases, as seen by the grandparent, linux and/or the GPL. the idea and practice of open standards predates the OSI, FSF, and linux. in OS X, apple has shown very good support for a wide variety of open standards. no OS will ever be absolute in that regard (let's say i've got this great OSF app i want to run on linux... and where's the linux equivalent of the SVID, by the way?).

      --

      i speak for myself and those who like what i say.
    13. Re:Apple isn't proprieta- NO WAIT ! by Fred_A · · Score: 1

      That's not true. As you could see in the posts above, Apple's actions do bother at least some of their customers. I know it annoys me. But they compensate for their practices a lot better a=than MS does by offering a vastly superior OS and beutiful hardware that in some cases is worth the extra money. While that's potentially debatable (I, for one, find that there isn't really all that much difference between Mac OS and Windows, but then I'm a Unix geek so I'm part of a small enough minority that I don't really count, although I'll gladly agree that the hardware is usually good), the *real* point isn't whether one company's actions is or isn't compensated by its hardware (I do use a MS mouse at the moment because that was the only midrange wireless mouse that was available at the nearby shop) but whether it has a monopoly in its market.

      Does Microsoft has a monopoly in the operating system market ? Yes.
      Does Apple ? No (so they can do whatever they like including giving away gold plated laptops in exchange for firstborns)
      Does Microsoft have a monopoly in desktop peripherals ? No (so I did buy a MS mouse even though I resent giving them yet more money after they screwed me out of a Vista licence)
      Does Apple ? No, so feel free to buy "mighty mice" and bury yourself in a pile of them (knobbly but fun).
      Does anybody else ? No. There are major players (like Logitech or MS in that market, but none have 80% of sales, so nobody cares).

      The *problem* is that when I recently had to buy a laptop to replace the iBook G4 which I did *not* like (I like KDE better than Mac OS, can't help it), I had the choice between utterly crappy generic systems that came with Linux, or regular machines that came with Vista. And from what I gathered from the Vista EULA, if you don't agree with it you have to return *everything* (that is including the machine) for a refund. Whereas with the XP EULA you could just say "I don't want this crappy system" and (theoretically) have a refund. And then you'd enjoy your Linux/BSD/BeOS/FreeDOS/Whatever machine -- and maybe get between $60 to $100 out of the deal.

      Me, I just overwrote the Vista disk with another system, figured I'd lost about $100 in the process and that was that. OTOH, I now have a machine that I enjoy using instead of the iBook which did work ok but which I didn't like.

      Anyway, I'm not anti-Apple, of course they use MS tactics. They try to sell their stuff. It's all fair game.
      I'm mostly pro-diversity. If the network was 40% MS, 40% Apple and 20% Linux, it would still be much saner than it is now (although of course I'd rather have 1/3rd for each).
      --

      May contain traces of nut.
      Made from the freshest electrons.
    14. Re:Apple isn't proprieta- NO WAIT ! by tsa · · Score: 1

      And from what I gathered from the Vista EULA, if you don't agree with it you have to return *everything* (that is including the machine) for a refund.

      I can't believe that is legal even in the US. This should be taken to court.

      --

      -- Cheers!

  22. Question : by Anonymous Coward · · Score: 0

    Does anyone have a compiled list of national ISO-bodies to whom we could mail our concerns?
    Some thing like :

    "Hello, Microsofts practice in this whole affair has been ridiculous because (insert reason), it's format is flawed because (insert reason), and if approved it would compete with another ISO-standard constructed for the exact same (claimed) purposes of OOXML. Vote no in Geneva"

    1. Re:Question : by Bayesela · · Score: 1

      Here is a list of NB with delegations at ISO http://www.noooxml.org/delegations

  23. Ozymandias by Frenchman113 · · Score: 0, Troll

    OZYMANDIAS I met a traveller from an antique land Who said: Two vast and trunkless legs of stone Stand in the desert. Near them on the sand, Half sunk, a shatter'd visage lies, whose frown And wrinkled lip and sneer of cold command Tell that its sculptor well those passions read Which yet survive, stamp'd on these lifeless things, The hand that mock'd them and the heart that fed. And on the pedestal these words appear: "My name is Ozymandias, king of kings: Look on my works, ye Mighty, and despair!" Nothing beside remains: round the decay Of that colossal wreck, boundless and bare, The lone and level sands stretch far away. Kind of fitting actually.

  24. Re:Australia has been entirely corrupted by Micros by Aussie · · Score: 1

    Australia has been entirely corrupted by Microsoft. An Ecma employee is attending the BRM on Australias behalf. This makes me ashamed about my country. got any links about this ? It's time to annoy the government :)
  25. OOXML, ODF, and FUD by SEMW · · Score: 2, Insightful
    You make some good points, but some rather bad ones.

    1. There is already an ISO standard for this same purpose. Since, clearly, different competing standards are bad. Which is why there is only one standard type of screw drive head, Flathead. I once heard someone claim that there were other standards, such as Philips (better for automated assembly) and Pozidriv (allows latge torque without gouging the screw); but I reckon they were lying. I mean, how could competition possibly be better than one standard having a monopoly? Everyone knows how good monopolies are.

    4. OOXML is technically very inferior to the existing standard, ISO 26300. For example, OOXML specifies three different implementations of "a table", instead of just one common to different Office applications. This means that you cannot write a "table handling class" as a library, but instead you have to duplicate equivalent functionality several times over. You cite one example where ODF is apparently better than OOXML. And indeed, Wikipedia cites several technical advantages of both ODF over OOXML and, conversely, OOXML over ODF. For example, ODF apparently has only a weakly defined formula syntax, inhibiting ODF spreadsheet implementations based only on the spec (supposedly most implementors just use whatever de facto syntax OO.org decides on). To claim that one format is universally hailed as technically "very inferior" is rather misleading at best.

    6. OOXML is controlled by just one corporation ... ISO 26300 belongs to ISO. That's a circular argument. It shouldn't be an ISO standard because it currently isn't an ISO standard?! (Granted, aspects of the canonical implementation will probably de fact be decided by what MS Office does, but then the same applies to ODF and OO.o -- see previous item...)

    8. ISO 26300 even works with Microsoft Office (up to Office 2003) using a free plugin written by Sun. Microsoft deliberately broke Office 2007 file filters so that this plugin (or any other plugin not written by Microsoft) would not work in Office 2007 That is just plain wrong, and FUD to boot. Not only does a 10 second Google search show that the Sun plugin does support Office 2007, but Microsoft apparently also sponsored their own open-source ODF add-in (hosted on Sourcefourge) for Office, which also supports Office 2007 (& below).

    10. It makes no sense to have "choice in standards" How is this different from your first point? Anyway, see my response to that.
    --
    What's purple and commutes? An Abelian grape.
    1. Re:OOXML, ODF, and FUD by Anonymous Coward · · Score: 5, Informative

      Since, clearly, different competing standards are bad.

      Of course they are. There is, for example, only one ISO standard for paper sizes, ISO 216. http://en.wikipedia.org/wiki/Paper_size#The_international_standard:_ISO_216
      This standard is used in all countries bar two. Becase there are two countries that use a competing non-ISO standard (they use an ANSI standard instead), it causes all sorts of un-necessary costs all around the world.

      For example, ODF apparently has only a weakly defined formula syntax, inhibiting ODF spreadsheet implementations based only on the spec (supposedly most implementors just use whatever de facto syntax OO.org decides on). To claim that one format is universally hailed as technically "very inferior" is rather misleading at best.

      Actually, it is you who is misleading here, and your anti-ODF FUD is from brian Jones in 2005 (when OOXML also lacked any definition of formula syntax). ODF version 1.2, which is currently going through the approval process, has a far more detailed definition of formula syntax, known as OpenFormula, defined by an independent body. http://en.wikipedia.org/wiki/OpenFormula This is what will be formally agreed in the upcoming version of ODF, but it is backward compatible with the (admittedly vauge) syntax definition in earlier versions of ODF, and it is also what all of the ODF applications actually now use.

      OpenFormula is indeed technically superior to the formula syntax of OOXML, for the following reasons: http://en.wikipedia.org/wiki/OpenFormula#OpenFormula_Attributes

      That's a circular argument.

      No, it is not. Before it was an ISO standard, it was an OASIS standard, and Microsoft were part of OASIS. Microsoft were invited to join the development process of ODF, which began in 2002, but Microsoft refused. Apart from the solitary exception of Microsoft, however, ODF otherwise has full industry consensus. In fact, after a long review period where comments from a broad array of interested parties were invited and incorporated, the ODF specification was put to a formal vote for OASIS approval, and it was passed unanimously. Yes, as an OASIS member, Microsoft approved ODF. Further, after that vote, ODF was submitted to ISO for approval as an International standard, via the long-winded PAS process (not fast-track), and after world-wide solicitation of comment and incorporation of recommendations, it was again approved unanimously. Yes, Microsoft approved it a second time ... then refused to implement it.

      That is just plain wrong, and FUD to boot. Not only does a 10 second Google search show that the Sun plugin does support Office 2007, but Microsoft apparently also sponsored their own open-source ODF add-in (hosted on Sourcefourge) for Office, which also supports Office 2007 (& below).

      It wasn't wrong for the original release of Ofice 2007. Full plugins were borked in that release. I'm pleased to see that Microsoft fixed it (now that Office 2007 has a foothold) in SP1. As for Microsoft-sponsored ODF convertors ... they are convertors, not plugins. You cannot use Microsoft's convertors to open & save as ODF ... you must have an OOXML version of your document first, and then you can import & export it as ODF. Microsoft convertors do a terrible job compared to the Sun plugin, and of course you cannot set Office 2007 as the default for .odx file extensions because Office 2007 can't open them directly (without Sun's plugin).

      Anyway, now that Sun's plugin works for Office 2007 ... all the more reason to use ODF (ISO 26300) format and not OOXML.

      Ho

    2. Re:OOXML, ODF, and FUD by TheSeer2 · · Score: 0, Troll

      Your arguments are pot, and I could easily just flip OOXML and ODF (and the related entities) and they'd still apply.

    3. Re:OOXML, ODF, and FUD by Anonymous Coward · · Score: 3, Insightful

      Your arguments are pot, and I could easily just flip OOXML and ODF (and the related entities) and they'd still apply.


      Sorry, but only by stubbornly ignoring all of the facts could you even try to pretend to "flip OOXML and ODF".

      - Only ODF is an agreed, consensus standard, approved as an ISO standard via unanimous vote.
      - Only ODF has multiple implementations by multiple vendors working on multiple platforms.
      - Only OOXML has no implementations at all.
      - Only ODF can be validated against a test suite.
      - Only ODF is truly open.
      - Only OOXML has "exclusions" in associated "promises not to sue".
      - Only OOXML is constrained via proprietary dependencies to run on just one platform.
      - Only OOXML has failed at fast-track approval, and has 3500 as-yet-unresolved objections against it.
    4. Re:OOXML, ODF, and FUD by Anonymous Coward · · Score: 0

      "but Microsoft apparently also sponsored their own open-source ODF add-in (hosted on Sourcefourge [sourceforge.net]) for Office, which also supports Office 2007 (& below)."

      Ha ha, you're a riot. Have you actually tried this plug-in? I have. It, in a word, SUCKS. The only reason for its existence is lip service, because it sure as hell does not faithfully convert documents from OXML to ODF format.

      What a joke. At least *try* to come up with a better Microsoft trolling shill argument, when you know damn well the facts are completely against you.

    5. Re:OOXML, ODF, and FUD by codemachine · · Score: 1

      I see others have replied, but I'll give the shorter version:

      - The table thing is fixed in the latest ODF draft and in current applications.

      - Even if OOXML is somehow approved by ISO, MS has said it will retain control of the standard. This is quite different from ODF, which is not controlled by one company.

      ODF is a community, and therefore the format keeps improving. OOXML is developed and maintained by one company to work with their own product, so they're likely to take the "won't fix" attitude to the format's deficiencies (as this article claims).

    6. Re:OOXML, ODF, and FUD by arkarumba · · Score: 1

      Which is why there is only one standard type of screw drive head, Flathead. I once heard someone claim that there were other standards, such as Philips (better for automated assembly) and Pozidriv (allows latge torque without gouging the screw); but I reckon they were lying. I mean, how could competition possibly be better than one standard having a monopoly?
      Its not too hard to understand the design for a Philips head screw, or Philips head screwdriver.
      Anyone could build either and have a high chance of being compatible with competitors.

      How many pages do you imagine the complete "Philips Head" specification would be, compared to OOXML?
      How easy will it be for OOXML competitors to be compatible?
    7. Re:OOXML, ODF, and FUD by Anonymous Coward · · Score: 0

      Since, clearly, different competing standards are bad. Which is why there is only one standard type of screw drive head, Flathead...
      This is a meaningless and misleading analogy. a) The different types of screw heads are the result of changing manufacturing technique, they were not all proposed as standards at the same time for differing purposes. b) Different standards for labeling the size of a Pozidriv would be a better analogy. Both office format standards address exactly the same problem.

      You cite one example where ODF is apparently better than OOXML. And indeed, Wikipedia cites several technical advantages of both ODF over OOXML and, conversely, OOXML over ODF. For example, ODF apparently has only a weakly defined formula syntax, inhibiting ODF spreadsheet implementations based only on the spec (supposedly most implementors just use whatever de facto syntax OO.org decides on).
      Incompleteness is vastly different than a poorly designed standard. Subsequent standards can always add functionality or clarification (and there is ongoing work to produce a standard for spreadsheet formulas). Nothing can be done about the OOXML table mess once it is a standard. Any change would amount to a new standard as it must conflict with the current one. Such issues are better addressed before it becomes a standard.

      That's a circular argument. It shouldn't be an ISO standard because it currently isn't an ISO standard?
      Your implication that control of any ISO standard must belong to the ISO is incorrect. Microsoft has patents covering portions of the standard. If Microsoft licenses said patents only for versions of the standard that it approves, then ISO has little control over the future of the standard.

      10. It makes no sense to have "choice in standards"

      How is this different from your first point? Anyway, see my response to that.

      You appear to be unable to distinguish between: a) multiple standards that address the same problem as opposed to b) multiple standards that address distinct, but similar needs.
    8. Re:OOXML, ODF, and FUD by makomk · · Score: 1

      For example, ODF apparently has only a weakly defined formula syntax, inhibiting ODF spreadsheet implementations based only on the spec (supposedly most implementors just use whatever de facto syntax OO.org decides on).

      That is, to be honest, Microsoft FUD - for the simple reason that, at the time they said it, the published versions of the OOXML standard didn't specify formulas either. (In fact, the OASIS draft of their formula spec was released several months before Microsoft's formula spec for OOXML, and there were even unofficial drafts before that.)

      Incidentally, the main reason that ODF got away with leaving it out the spec is that most spreadsheet applications' formula syntax was heavily based on how other, earlier spreadsheet apps did it - including OpenOffice.org and Microsoft Office. This is also the main reason it's such a headache - there's various backwards-compatibility cruft in there.

    9. Re:OOXML, ODF, and FUD by Wraith,+The · · Score: 1

      - Only ODF has multiple implementations by multiple vendors working on multiple platforms. That is incorrect. For example OOXML has implementations on all major mobile platforms (Symbian, Palm OS, Windows Mobile and iPhone) and ODF doesn't. Of course OOXML has also implementations on multiple desktop platforms and even in popular on line office suites like Thinkfree. - Only OOXML has no implementations at all. That is just laughable. - Only ODF can be validated against a test suite. There is indeed a test suite for ODF and it actually shows us that not a single implementation supports ODF fully or faithfully. That sure helps. - Only ODF is truly open. ODF is no more open than OOXML - Only OOXML has "exclusions" in associated "promises not to sue". Actually that is incorrect. Sun in their covenant not to sue has excluded any future version of ODF their have not contributed to significantly. If they do not agree with changes and leave the OASIS TC then their promise does not apply to new ODF versions anymore. - Only OOXML is constrained via proprietary dependencies to run on just one platform. That is actually incorrect. For instance ODF supports OLE linking and embedding. - Only OOXML has failed at fast-track approval, and has 3500 as-yet-unresolved objections against it. There were 3500 comments. However those do not contain 3500 unresolved objections as you suggest. About 3000 of those comments contain near identical copies of IBM objections that were spread amongst ISO members and found their way back in the comments making the number of unique comments less than 1000. Also most of the actual about 1000 issues in those comments are simple editorial issues and although you claim they are not resolved their is already a suggestion resolution by Ecma for nearly every comment.

    10. Re:OOXML, ODF, and FUD by Wraith,+The · · Score: 1

      The table thing is fixed in the latest ODF draft and in current applications.
      That is actually not true. Current applications do not use the latest draft. they use the ODF 1.1 version. A version never sumbmitted to ISO. So actually most current application like OOo are not in line with the ISO specifications for ODF.

      The latest draft in OASIS is a 1.2 draft version (it does actually fix the talbe issue) that has been severly delayed and is still not yet finished and it might take years still for it to become an ISO version looking at OASIS trackrecord on submitting new version to ISO.

    11. Re:OOXML, ODF, and FUD by Anonymous Coward · · Score: 0

      1. There is already an ISO standard for this same purpose.
      Since, clearly, different competing standards are bad.


      Aren't they? HD-DVD/blueray, thousands of different types of electronics transformers/power cords, hundreds of different A/V cords.

      I would sure appreciate only one standard, designed to be extensible and 100% backwards compatible.
    12. Re:OOXML, ODF, and FUD by codemachine · · Score: 1

      That is unfortunate. I guess standards shouldn't be changing quickly anyhow, as it defeats the purpose of having a document standard (preservation and compatibility). But when it comes to weaknesses and ambiguities, it'd be nice to see those shored up a bit quicker.

      So as far as I undestand it, spreadsheets are using the "do it like OpenOffice.org" approach in this area, until 1.2 is final. Though this is certainly not ideal (MS will spin it to be the same as "do it like Word 97"), at least the code to OpenOffice is available to inspection, making it possible for other vendors to actually implement it and get interoperability.

    13. Re:OOXML, ODF, and FUD by Wraith,+The · · Score: 1

      [quote]at least the code to OpenOffice is available to inspection, making it possible for other vendors to actually implement it and get interoperability.[/quote] So it isn't actually OpenDocument but OpenOffice document...

  26. AutoSpaceLikeWord95? You do need some new FUD... by SEMW · · Score: 1, Informative

    Things like autoSpaceLikeWord95 are referenced but not specified. You original poster is right, you need to get some new FUD. AutoSpaceLikeWord95 was specified by the 1st January 2008 Czech ECMA response (AutoSpaceLikeWord95 was CZ-0014, more at CZ-0015 to CZ-0025)
    --
    What's purple and commutes? An Abelian grape.
  27. Re:Australia has been entirely corrupted by Micros by Anonymous Coward · · Score: 1, Interesting
    No links, this isn't yet public -- Rick Jelliffe (an Ecma employee) is going with a junior person in Standards Australia to the Ballot Resolution Meeting.

    Start making calls, Aussie.

  28. Re: Ozymandias, properly formatted by SEMW · · Score: 1, Insightful

    Ozymandias
    by Percy Bysshe Shelley

    I met a traveller from an antique land,
    Who said--"Two vast and trunkless legs of stone
    Stand in the desert... Near them, on the sand,
    Half sunk a shattered visage lies, whose frown,
    And wrinkled lip, and sneer of cold command,
    Tell that its sculptor well those passions read
    Which yet survive, stamped on these lifeless things,
    The hand that mocked them, and the heart that fed;
    And on the pedestal, these words appear:
    My name is Ozymandias, King of Kings,
    Look on my Works, ye Mighty, and despair!

    Nothing beside remains. Round the decay
    Of that colossal Wreck, boundless and bare
    The lone and level sands stretch far away."

    --
    What's purple and commutes? An Abelian grape.
  29. Re:AutoSpaceLikeWord95? You do need some new FUD.. by TimSSG · · Score: 1

    Good, I am glad that some of the details are being documented. Tim S PS, I liked your prior signature. I think the irrational fear was funny.

  30. Re:AutoSpaceLikeWord95? You do need some new FUD.. by SEMW · · Score: 1

    Tim S PS, I liked your prior signature. I think the irrational fear was funny. Thanks! (Can't lay claim to making it up, though; it's quite an old maths joke, as is the new one). As to why I changed it, well... Short answer, mysticgoat gave me phobophobia....
    --
    What's purple and commutes? An Abelian grape.
  31. Czech Republic's expert disagrees wholeheartedly by I'm+Don+Giovanni · · Score: 3, Informative
    Sorry, but this is bullshit.
    Quoting from zmotula's post:
    "...see the post by the guy who evaluated the OOXML specification for the Czech Normalization Institute. This means that Czech Republic is most probably going to vote for OOXML when the time comes."

    Read that post and you see that nearly every one of the Czech Republic's objections has been addressed (the only one not satisfactorily addressed was the Czech Republic's complaint that part of the spec has redundant info). Let me quote:

    ECMA already provided proposed resolution for 75 comments (out of total 75 Czech comments). This means that 100.00% of Czech comments were handled by ECMA.

    90.67% of comments were satisfactory resolved.

    8.00% of comments were resolved only partially.

    1.33% of comments were not satisfactory resolved. ... ...
    In fact I was really surprised how many "green boxes" are there at the end. I was expecting that ECMA will properly address only part of our comments. The vast majority of Czech comments was addressed by ECMA so it is time to say yes to OOXML.
    --
    -- "I never gave these stories much credence." - HAL 9000
  32. Re:Australia has been entirely corrupted by Micros by Anonymous Coward · · Score: 0

    Rick Jelliffe (an Ecma employee)

    Oh! That's how Microsoft is paying this guy... I was wondering what was his reason to defend that load of crap. Thanks for clarifying that!

    Phil

  33. Re:Australia has been entirely corrupted by Micros by Anonymous Coward · · Score: 0

    Not to mention that this idiot has a blog at O'Reilly's website. WTF?

  34. Re:Australia has been entirely corrupted by Micros by Anonymous Coward · · Score: 0

    Rick was the guy who submitted most of Australia's comments with their vote in September, he is probably best qualified to work out how valid the responses are.

    He is CTO of an Australian ISV, I can't remember the name.

  35. Re:Australia has been entirely corrupted by Micros by Aussie · · Score: 2, Informative
    Topologi is the company.

    Also came accross this

    Disclosure: In January 2007, Rick became embroiled in a controversy after mentioning in his XML.COM blog an approach from Microsoft for a several-day contract job to correct some Wikipedia entries from a neutral point of view, as an experienced technical writer with credible first-hand knowledge of standards and procedures. This was incorrectly reported as being a secret plot to subvert Wikipedia. With the support of many editors on Wikipedia, with complete transparency, and with care to respect the Wikipedia rules, Rick has started participating on the Wikipedia entries.

    The company that is the co-owner of Topologi has a long-standing training business and will be providing some presenters for some Microsoft sponsored-events in 2007 in Australasia. It is highly likely that Rick will be one of the presenters on standards matters at some of these. link

    Seems he has lots of involvement with MS.
  36. Re:How 'Firm' Would You Stand For 20 Billion A Yea by HangingChad · · Score: 1

    Shame studies.

    I think you meant "sham" studies but I sorta like your way better. It's a sham that's also a shame. ;)

    --
    That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
  37. Re:Australia has been entirely corrupted by Micros by Anonymous Coward · · Score: 0

    No links, this isn't yet public -- Rick Jelliffe (an Ecma employee) is going with a junior person in Standards Australia to the Ballot Resolution Meeting.
    Start making calls, Aussie.


    Rick Jelliffe most decidedly does not represent me.

    To whom and exactly how would I go about making vigorous protest against this guy?
  38. Re:Australia has been entirely corrupted by Micros by Anonymous Coward · · Score: 0
    Who to contact? Not Standards Australia that's for sure. They chose the guy so they must be happy with him.

    Go over their head -- get heads of industry to contact the government (citizens won't hold as much authority as them).

  39. Re:How 'Firm' Would You Stand For 20 Billion A Yea by chgros · · Score: 1

    All in a days work.
    I think you meant "business as usual"

  40. Re:Australia has been entirely corrupted by Micros by Anonymous Coward · · Score: 0
    Most of the comments were from Rick but he has never had a bad word to say about OOXML. He's going to recommend "Yes" regardless of the quality of the responses. That's the problem -- he's not independent, he won't say "no" if the responses aren't of quality, he hasn't supported other nation comments, and he's on Microsoft's payroll via Ecma.

    He certainly won't do what's best for Australia, which is his mandate as a delegate.

    This is a prediction about the future -- it's my educated-guess based on his behaviour.

  41. Oh, man, oh, man. by seebs · · Score: 1

    I have an article in the pipeline on OOXML. I SO hope it shows up in time. It'll be in the XML section on developerWorks.

    KEEP PEELED EYES! Mmmm. Peeled eyes.

    --
    My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
  42. the trenches by sonictheboom · · Score: 1

    M$ won the initial vote in Pakistan. LinuxPakistan is fighting back. Here is the link http://www.linuxpakistan.org/ooxml/index.php

  43. Re:OOXML, ODF, and pro-MS-FUD by Anonymous Coward · · Score: 0

    "1. There is already an ISO standard for this same purpose.

    Since, clearly, different competing standards are bad. Which is why there is only one standard type of screw drive head, Flathead. I once heard someone claim that there were other standards, such as Philips (better for automated assembly) and Pozidriv (allows latge torque without gouging the screw); but I reckon they were lying. I mean, how could competition possibly be better than one standard having a monopoly? Everyone knows how good monopolies are."

    Analogy police called, they want to arrest you for horrendous analogue.

    First: Screws don't interoperate, no need to standardize that
    Second: Screws are installed and forgotten, strict one-time use, no need to care about re-use
    Third: Different screws are for different usages

    Obviously you don't know anything about screws, either. Flat head is the oldest standard and practically extinct now,
    Phillips is newer but rapidly vanishing and new ones use Pozidriv, Supadriv or Torx.

    If you don't know, the threaded part (functional part) of all of these screws is identical, only the head is different. So they are essentially the same anyway, if made for the same purpose.

    A good analogue to OOMXL would be a picture of a screw no-one can make.

  44. Office 2007 .docx seems to use (deprecated) VML by Mathinker · · Score: 2, Informative

    Well, because the "standard" is so convoluted, it's not totally clear.

    The OOXML standard states that use of (proprietary) VML is deprecated, but if you search the web for "VML"+"office 2007" you get lots of info on how most .docx files end up chock full of VML because of linkage with proprietary MS tech. See the "Application-defined" binary blobs for Microsoft Ink(TM) data?

    This may or may not be OK with the standard, the big point is that there is no mode for Office 2007 which warns you when you save .docx using such deprecated or proprietary features (i.e., saving a file which is not interoperable with non-MS products using the OOXML standard). And you have to be some kind of genius to know what not to use.

    "Office 2007 .bin file format" might be interesting to you also.

    1. Re:Office 2007 .docx seems to use (deprecated) VML by Wraith,+The · · Score: 1
      Even though the VML behaviour in Office 2007 is not conforming it does not lead to OOXML files that are non conforming.

      On the other hand there is evident information that ODF files created by OpenOffice.org are actually not conforming to the ODF specification because OpenOffice for instance uses a modified MathML 1.1 whereas ODF specifies that ODF files should be using w3c MathML 2.0. http://idippedut.dk/post/2008/01/Do-your-math---ODF-and-MathML.aspx

      If would seem that that MS Office 2007 is at least as good a representation of OOXML conformance as OOo 2.x is represnetation of ODF.

    2. Re:Office 2007 .docx seems to use (deprecated) VML by Mathinker · · Score: 1

      > Even though the VML behaviour in Office 2007 is not conforming it does not lead to OOXML files that are non conforming.

      I agree totally. So this means that, by your own admission, standard conforming OOXML files are useless for intercompatibility and long-term archiving.

      So what is this loser of a "standard" good for, then? Please explain?

      What's even more amusing about your comment is that the non-conforming ODF files you complain about are actually much better for intercompatibility and long-term archiving, because they do not have obtuse proprietary binary tur.. er, blobs embedded in them. They just have the "wrong" kind of non-proprietary stuff in them.

      In fact, even the non-standard (as in not-an-official-standard) previous file format of OOo was better than OOXML in this way, as long as you archived it along with all the sources of OOo.

    3. Re:Office 2007 .docx seems to use (deprecated) VML by Wraith,+The · · Score: 1

      No, what I am saying is that the use of deprecated VML does not cause OOXML files to be non-interoprabel. And you seem to have little understanding of the formats as ODF is actually a spec that is filled with binary base64encoded blobs elements.

    4. Re:Office 2007 .docx seems to use (deprecated) VML by Mathinker · · Score: 1

      > No, what I am saying is that the use of deprecated VML does
      > not cause OOXML files to be non-interoprabel

      Well, so as far as I can tell, you're wrong. Please explain how a non-MS implementation of the OOXML standard will deal with those conforming files you were talking about when they contain VML blobs encoding proprietary Microsoft Ink data.

      > you seem to have little understanding of the formats as ODF is
      > actually a spec that is filled with binary base64encoded
      > blobs elements.

      You know, attacking me personally makes you look stupid, in that you are totally ignoring my whole point, that no matter how things are encoded in ODF, it contains no proprietary technology whatsoever and it is therefore a much better format for interoperability and long-term archival.

    5. Re:Office 2007 .docx seems to use (deprecated) VML by Wraith,+The · · Score: 1

      Please explain how a non-MS implementation of the OOXML standard will deal with those conforming files you were talking about when they contain VML blobs encoding proprietary Microsoft Ink data. The same as they would when the VML would be in a converted OOXML file where the VML in the format specification was ment for.

      that no matter how things are encoded in ODF, it contains no proprietary technology whatsoever and it is therefore a much better format for interoperability and long-term archival. That however is incorrect. Actually ODF contains very propriety OLE linking and embedding technolgy (a Microsoft technology) and Java applet technology (a Sun technology) and it also contains arbitrary propriety technologies from each implementer in for instance the ODF propriety Office-setting features or contains propriety technology in extensions or in embedded binary or non-binary data. Hmmm, in fact it totally resembles OOXML in that way except that OOXML has the propriety settings fully documented and ODF has not.
    6. Re:Office 2007 .docx seems to use (deprecated) VML by Mathinker · · Score: 1

      > Actually ODF contains very propriety OLE linking

      OK. This will be interesting. Please give us all the page references in the ODF standard where this is specified. Otherwise, cut the bullshit.

    7. Re:Office 2007 .docx seems to use (deprecated) VML by Wraith,+The · · Score: 1
      I'll do you one better.

      I'll copy a XML schema part from the ODF specification paragraph 9.3.3

      <define name="draw-object-ole">
      <element name="draw:object-ole">
      <ref name="draw-object-ole-attlist"/>
      <choice>
      <ref name="common-draw-data-attlist"/>
      <ref name="office-binary-data"/>
      </choice>
      </element>
      </define>
      A nice combination of the OLE objects and the binary blob together in ODF.

      I guess the ODF propaganda machine forgot to mention this part?

      Enjoy.

    8. Re:Office 2007 .docx seems to use (deprecated) VML by Mathinker · · Score: 1

      OK. That checks out. I suppose it's logical also, if ODF didn't include this, the nay-sayers would chime up with "ODF doesn't even allow OLE", "ODF is useless in the real world where people will want to exchange documents including OLE-style proprietary objects", etc. Thanks for pointing this out to me.

      > it totally resembles OOXML in that way except that OOXML has the propriety settings fully documented and ODF has not.

      If the settings are fully documented, in what way are they proprietary? In the sense that Microsoft has some kind of patent on it and may or may not be able to sue you depending upon whether the "covenant not to sue" protects you or not?

      BTW, you meant to say "OOXML totally resembles ODF", right? ODF was there first, which is one of the reasons people are opposed to OOXML. Microsoft had its opportunity to contribute to the standardization process of ODF (it is/was a member of OASIS), but proposes a not-very-new additional standard instead. The whole point of having standards is to use the existing ones (and extend them when necessary), not to invent new standards right-and-left. My understanding of your point is that the ODF spec includes a lot of opportunity for extension, so it would seem that whatever Microsoft needed (which is fit to be in a standard, we're not talking about the deprecated legacy cruft included in OOXML), it could have tacked onto the ODF spec in the form of standardized extensions.

      Now to get back to a point I made earlier, that there is no software which can read/write OOXML which makes it easy for you to save OOXML files without inadvertently including proprietary objects which are bad for interoperability and long-term archival. Now that you've shown us that ODF can include proprietary objects and extensions also, I think it's important to reiterate that it is easy to generate ODF without proprietary stuff. You can do it easily from any standard Linux installation providing OpenOffice.org applications. Of course, you can also do it on Windows if you run Linux in a VM or you run co-Linux.

      I eagerly await your reply, as it is clear you always want to have the last word. :-)

  45. It's called MOOXML [was: Re:well...] by Anonymous Coward · · Score: 0

    Remember, folks. It's MOOXML. Just to make sure we all know what we are talking about...

  46. They still don't get it - or don't want to by Lonewolf666 · · Score: 1
    From the ECMA website:

    Many National Bodies identified specific functionality within the specification that reflected existing product defects or legacy application behaviors. These behaviors are important because they reflect the content in existing documents, but should not be perpetuated when creating new documents from scratch.

    I call bullshit.

    Keeping the old defects in a new standard for reasons of "compatibility" is not a good idea, because it means missing a good opportunity for improvement.
    Keeping them in new versions of the old products is something I can (barely) understand, but declaring bugs to be features for the whole industry is just plain wrong. I think if Microsoft/ECMA keep insisting on that, ISO should reject OOXML outright.
    --
    C - the footgun of programming languages
  47. Re:OOXML, ODF, and pro-MS-FUD by stavros-59 · · Score: 1
    A very poor analogy indeed.

    Since, clearly, different competing standards are bad. Which is why there is only one standard type of screw drive head, Flathead. I once heard someone claim that there were other standards, such as Philips (better for automated assembly) and Pozidriv (allows latge torque without gouging the screw); but I reckon they were lying. I mean, how could competition possibly be better than one standard having a monopoly? Everyone knows how good monopolies are."

    There is no single corporation that provides both the all the screwdrivers and/or all the screws.
  48. "...would make Office better" by Joce640k · · Score: 1

    Yes... but it means they'd have to do some hard work.

    Why bother with that when you can lock up everybody's valuable data then take your time adding just enough new features to get people to upgrade?

    --
    No sig today...
  49. Your "Czech expert" says NOTHING of substance by temcat · · Score: 1

    You bring up this link: http://xmlguru.cz/2008/01/ecma-response-to-czech-ooxml-comments

    Have you actually tried to open the PDF files with "Proposed dispositions" that the page links to? You cannot, because they are password protected. No one knows what these dispositions are, and even if they exist at all. We only have to believe the words of this so called "expert" and have no way to check them.

  50. MODS ON CRACK by Anonymous Coward · · Score: 0

    Seriously, this is not off-topic. I studied this poem many years ago in school, it sums up Microsoft and their current situation perfectly.

    Fucking idiots, read and understand the poem before throwing your mod-points around.

  51. Sarcasm? But there is some truth in it... by Lonewolf666 · · Score: 1

    Because once you have a generally accepted standard and applications that support it, you should be able to use those applications for a very long time.

    If an individual vendor ceases to support the standard, you have a good chance of finding another who will do so. In that case, you may have some expenses for switching applications but you can still can use your document format.

    With Microsoft, your chances of getting either are slim:
    -they often change their document formats, which leads to users of later Office versions sending you documents you cannot use without upgrading.
    -third party support for MS formats usually depends on reverse engineering because the formats are poorly specified. Note that you can usually download some specifications, but those tend to be out of date and incomplete. This leads to third party support that sucks, and I think the Open Office developers did a quite good job by getting it almost right under those circumstances.

    --
    C - the footgun of programming languages
  52. You're forgetting governments by Lonewolf666 · · Score: 1

    Governments have a need to keep documents for pretty long times, and they are increasingly aware of the problems they will get from a vendor that changes the default formats of its applications every few years. If you watch the IT news, you will see a tendency to mandate open document standards for government use.

    Now Microsoft has three options:
    1) Give the standards board the middle finger and lose the government business. Financial ouch, and more importantly companies who work with the government a lot might switch to the same application as the government (like Open Office) for convenience. Great way to erode the dominant position of Microsoft Office.

    2) Use ODF. Might not support all quirks of their old documents (which is a valid concern but not reason enough to support those quirks for eternity). But more importantly, it kills the vendor lock-in. Another great way to erode the dominant position of Microsoft Office.

    3) Try to push a lousy pseudo-standard like OOXML through the standards boards. I will skip the discussion of the details here and just say I think the opponents are right when they say only Microsoft would be able to support OOXML (halfway) well. Result if MS gets away with it:
    Microsoft can claim to save documents in a standardized format, any legal requirements in that regard are satisfied. A great step towards keeping the government business without being really interoperable with others.

    Now guess what Microsoft is trying ;-)

    --
    C - the footgun of programming languages
  53. Re:AutoSpaceLikeWord95? You do need some new FUD.. by Zeinfeld · · Score: 1
    Good, I am glad that some of the details are being documented.

    No you are not, you have not got the slightest interest in implementing this specification regardless of whether it is fully documented or not. This is simply a game that the Slashdot community is playing.

    The real issue is that people think they can force government IT depts to stop using word by preventing OOXML being declared an ISO standard.

    I oppose this because I don't like the idea of top down dictators deciding what tools people use. This is not about free choice for the user, its all about ramming Open Office down the government employees throats whether they want it or not.

    That is not what standards are for. If a tool is good there is no problem getting people to use it. The Mozilla folk have no problem getting people to use their product voluntarily.

    In itself a standards designation, particularly an ISO designation means absolutely nothing. OOXML has an ECMA designation, that is plenty. There is not a single IETF Internet standard that has an ISO designation although this is possible in theory. All an ISO designation means is that people have to pay for the standard in future. Thats the same whether its OOXML or ODF that gets an ISO designation, transfer of the copyright is a mandatory part of the process.

    --
    Looking for an Information Security student project suggestion?
    Try http://dotcrimeManifesto.com/
  54. Standards for screws? Don't get me started! by Anonymous Coward · · Score: 1, Informative

    Standards for bolts and screws? Don't get me started!

    You wrote :-

    [sarcasm ..] different competing standards are bad. Which is why there is only one standard type of screw drive head, Flathead. I once heard someone claim that there were other standards, such as Philips (better for automated assembly) and Pozidriv (allows latge torque without gouging the screw); but I reckon they were lying.

    Are you trying to say that having these these different screw head standards is OK, therefore two document standards will also be OK?

    Low torque screw heads are a good example of why there should only be one standard - Pozidriv in this case. Philips was an earlier cross head, still used by the Far East, but Pozidriv was an improvement on it. And any crosshead is better than flat head - more blade drive area and less likely to slip out.

    Many people do not understand though that such standards are NOT compulsory (except in some safety areas). Even if dropped as a standard, Flathead would always be widely used in special areas - like on camera battery compartments meant to be opened with a coin. Likewise there will be "anti-tamper" heads which are essentially non-standard.

    Note I said "low torque" use. Standards can overlap. There are also standards for hexagon and Allen heads, used for high torque and larger applications. While there can be overlap with low torque applications, they are basically for different applications. ODF and OOXML however are NOT for different applications.

    [sarcasm ..] I mean, how could competition possibly be better than one standard having a monopoly? Everyone knows how good monopolies are.

    Standards don't "have monopolies". Standards are NOT monopolies. In fact, standards are the very opposite idea from monopolies. One idea of ODF is to stop monopoly.

    Standards should enable any company to come along and join in the party without fear of patent or copyright infringement. That is why Microsoft hate standards, because they love their own monopoly. But, recognising that the world is demanding a standard here, they are desparately promoting a crippled half-baked one in OOXML in the hope that their rivals will find hard to implement, and that its control will be retained by themselves.

  55. Can they at least change the #!@$ name? by SCHecklerX · · Score: 1

    That they deliberately named the damned thing to look like a piece of open office is dispicible.

  56. Re:AutoSpaceLikeWord95? You do need some new FUD.. by meosborne · · Score: 1


    Good, I am glad that some of the details are being documented.

    No you are not, you have not got the slightest interest in implementing this specification regardless of whether it is fully documented or not. This is simply a game that the Slashdot community is playing.


    Sigh. If it was fully documented it would be different. Look at the spec. Look at the ECMA TC45 committee charter and scope which states that OOXML must be fully compatible with the formats used in Microsoft Office. How much clearer can it be that this standard is just for Microsoft?

    The real issue is that people think they can force government IT depts to stop using word by preventing OOXML being declared an ISO standard.

    This argument is too funny. Word has been forced on countless numbers of people simply because it was the only way to reliably read .DOC files. I guess that is perfectly OK though.

    OOXML does nothing to improve that. It would merely grant Microsoft even more control than they have now. Microsoft defines the standard.

    ODF is vendor neutral. I want a format that is not controlled by any single company. How about not being forced to use Word?


    I oppose this because I don't like the idea of top down dictators deciding what tools people use. This is not about free choice for the user, its all about ramming Open Office down the government employees throats whether they want it or not.


    You think there is free choice now? Please.

    That is not what standards are for. If a tool is good there is no problem getting people to use it. The Mozilla folk have no problem getting people to use their product voluntarily.

    In itself a standards designation, particularly an ISO designation means absolutely nothing. OOXML has an ECMA designation, that is plenty. There is not a single IETF Internet standard that has an ISO designation although this is possible in theory. All an ISO designation means is that people have to pay for the standard in future. Thats the same whether its OOXML or ODF that gets an ISO designation, transfer of the copyright is a mandatory part of the process.


    Microsoft has stated that they feel no obligation to actually follow the ECMA standard. Indeed, the whole thing is merely a farce.

  57. Great post by BrunoUsesBBEdit · · Score: 1

    You sir are the reason that Anonymous Cowards are permitted.

    Non-moderator +1 from me.

  58. Simple workaround by pimpimpim · · Score: 1
    Implement a slightly buggy ODF reader in MSOffice, just like internet explorer has a slightly buggy html reader. People using MSOffice (because the firm already has a few thousand contracts of MSOffice, and so has it suppliers/partners) will complain that the ODF files from **Office don't work correctly in MSOffice. Expected line of tought: MS is a respectable company, right, so the fault must be with the free program of those stinkin hippies from **Office, better stick to MS. How can a free program be good anyway.

    MS biggest asset is that there are a lot of brainwashed (or brainless?) minds in the budget and management departments to be converted to use free software.

    --
    molmod.com - computing tips from a molecular modeling
  59. Re:AutoSpaceLikeWord95? You do need some new FUD.. by Bert64 · · Score: 1

    It's not about forcing openoffice down anyone's throats...
    It's about giving people the freedom to choose whatever program they want based on their individual benefits, rather than on compatibility with proprietary microsoft formats where other vendors will always be at a disadvantage.

    Firefox is gaining ground because the web is based on standards, with only a relatively small (and decreasing) level of corruption by microsoft. By comparison, their office document formats are entirely controlled and dictated by microsoft and not disclosed to third parties.

    A significant number of organizations have looked at using openoffice, and most of those who decided against it did so because of compatibility concerns. If an open format was dominant, then openoffice would have a significant market share today (even if based on cost alone), the application itself would be significantly better (more users would attract more developers, and less time spent reverse engineering proprietary formats would leave more time to improve other areas) and other competing applications would also be significantly improved in order to compete.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  60. Re:AutoSpaceLikeWord95? You do need some new FUD.. by Zeinfeld · · Score: 1
    It's not about forcing openoffice down anyone's throats... It's about giving people the freedom to choose whatever program they want based on their individual benefits, rather than on compatibility with proprietary microsoft formats where other vendors will always be at a disadvantage.

    Thats not true at all.

    The Massachusetts dictat that all departments had to change to open office forthwith was not a matter of choice, it was an order from the IT dept that was widely praised on Slashdot and elsewhere.

    I don't like central control by IT departments. They get it wrong far too often. They choose products according to features that they like which are typically irrelevant to the end users.

    The reason that the Web took off at CERN was that CN division operated in classic MIS dept. fashion, dictating the use of an obsolete, IBM mainframe to aggrandize its own power. Tim only tells one half of the story, the CERN phonebook was available online before the Web came along - but only on CERNVM which ran a dreadful botch of a DIY operating system CN division cobbled together. The Web made it possible to bypass CERN-VM entirely.

    This is about giving 'freedom' to an abstract set of people by forcing a particular office suite on actual people. Its a rather Trotskyite view of revolution as far as I am concerned.

    --
    Looking for an Information Security student project suggestion?
    Try http://dotcrimeManifesto.com/
  61. Re:AutoSpaceLikeWord95? You do need some new FUD.. by Bert64 · · Score: 1

    They dictated that all departments had to change to the ODF format forthwith, not the openoffice format (as used in openoffice 1.x) which is somewhat different and now deprecated.

    Thus, they require that you use applications which support the ODF format, giving you the choice of using:
    Open Office
    Star Office
    IBM Workplace / Lotus
    KOffice
    MSOffice (with odf-converter plugin)
    MSOffice (with sun odf plugin)
    OSX TextEdit (text documents only)
    AbiWord (text documents only)
    Gnumeric (spreadsheets only)
    Google Docs&Spreadsheets

    As opposed to using microsoft's formats, which gives you the "choice" of using:
    MSOffice

    How exactly are they forcing anyone? They are giving users more choice than they had before, not less.

    What would you prefer the Massachusetts government do, and how would this provide more choice to users?

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!