Skip to main content

Home/ IBM: Standards and Double Standards/ Group items tagged double

Rss Feed Group items tagged

Paul Merrell

How Microsoft Ratted Itself Out Of Office | BNET Technology Blog | BNET - 0 views

  • Also, you have the problem that OOXML does not define details like scripts and macros, the very essence of integrating documents with business processes. So although you may now know how Office stores bold and italics, but these are not exactly the crown jewels of Office compatibility.
  •  
    Here, IBM's Rob Weir takes OOXML to task for not specifying scripts and macros. But nary a mention of the fact that OpenDocument suffers from the same weakness. Yet another IBM double standard. He also tacks on an ad hominem attack against Gary Edwards, in lieu of addressing the merits of what Edwards said.
Paul Merrell

The conspiracy to save ODF from being so crappy - O'Reilly Broadcast - 0 views

  • I hope you will verify these facts, if needed, and correct your misstatements regarding OASIS process and the ODF's TC's work. Then you can go back to telling us again how you and Alex are not spreading lies about ODF. -Rob
  •  
    Here we learn two things about IBM's Rob Weir. First, score another ad hominem attack for him because of his innuendo suggesting that Rick Jelliffe and Alex Brown are liars. Second, we learn that Mr. Weir expects a retraction to be made when inaccurate statements are brought to a blog author's attention. Having been recently outed for rewriting history to call Alex Brown and Wikipedia names and having confessed to silently editing his blog in relevant regard, will Mr. Weir correct his own blog article? See http://www.adjb.net/post/No-one-supports-ISO-ODF-today.aspx and Weir's confession in the comments on that page. Or are retractions yet another case of an IBM double standard?
Paul Merrell

An Antic Disposition: Compatibility According to Humpty Dumpty - 0 views

  • But none of that is really 100% compatibility with legacy anything. That is really just saying that OOXML is compatible with code that Microsoft is writing months after OOXML was standardized by Ecma. But the qualities of the format were set the day the standard was approved by Ecma. The standard does not gain capabilities by Microsoft writing code. Microsoft applications may gain capabilities, but the standard is what it is, and is as compatible as it is going to get the day it was standardized. If OOXML was really compatible with legacy binary formats then they would work without requiring code changes or customer upgrades.
  •  
    In 2007, IBM's Rob Weir roundly criticized OOXML because the principle justification for having a largely duplicative international standard was compatibility with the billions of extant legacy Microsoft Office documents in binary formats, yet the specifications for the binary formats were not included in the OOXML specification. Just how committed IBM management was to that position may be seen in the fact that IBM later instigated an antitrust investigation of Microsoft Office by the E.U.'s DG Competition through the European Committee on Interoperable Systems, alleging monopoly abuse by Microsoft on the same grounds, an investigation still ongoing. \n\nIn this blog post comment, IBM's Rob Weir takes a hard line position that the sufficiency of the OOXML standard's specificity must be determined on the basis of what is stated in the standard itself, as opposed to Microsoft's subsequent recoding of Office to remove compatibility defects between Microsoft's implementation of OOXML and the binary formats.\n\nThe quoted passage may be usefully compared to later IBM arguments and actions in regard to the OpenDocument.standard that will be included in later bookmarks. For example, Weir has been unyielding that vendor-defined extensions to the ODF standard must be classified as conformant in ODF 1.2, yet their specifications are definitionally not part of the ODF specification. As another example, in 2009 Weir attacked Microsoft for having implemented ODF 1.1 using formula markup different from that used by OOo, despite ODF 1.1's lack of specifications for spreadsheet formulas. Weir's rationale: that vendors must collaborate to code around holes in the standard. He came very close to arguing that data gaps in a standard are irrelevant. See e.g., http://www.robweir.com/blog/2009/05/battle-for-odf-interoperability.html \n\nHypothesis: IBM's treats ODF as a double standard rather than a standard. What IBM argues in effect is that what is required for OOXML does not apply
Paul Merrell

An Antic Disposition: Those who forget Santayana... - 0 views

  • Those who control the exchange format, can control interoperability and turn it on or off like a water faucet to meet their business objectives.
  •  
    Here we learn that when it comes to OOXML IBM's Rob Weir says that it is those in control of the data formats who control interoperability. But one may usefully juxtapose that view with Weir's statements that it's Microsoft's fault for breaking interoperability in its implementation of ODF 1.1 formulas. Weir had it right the first time; it's those who control the data formats who control interoperability. And that places the responsibility for the ODF 1.1 interop mess squarely at the feet of the IBM and Sun-dominated ODF TC. So we have yet another IBM double standard. One truth when it's OOXML being discussed but its opposite when it is ODF subjected to examination.
Paul Merrell

When Did IBM Know? And Why That Matters ... | Universal Interoperability Council - 0 views

  • When did IBM learn that Microsoft would not implement Excel spreadsheet formulas in OpenDocument Formats ("ODF") v. 1.1 the same way OpenOffice.org does? And why does that timing matter?
  • Why then did IBM wait nearly seven months, until May 3, 2009 — after Microsoft's ODF 1.1 native support was coded in Office 2007 SP2 — to mount the Big Blue attack on Microsoft's ODF 1.1 implementation of formulas?
  • If the IBM goal were in fact interoperability via ODF 1.1 between Microsoft Office and other ODF implementations, would it not have been more timely for IBM to raise its formula stink before the Office 2007 ODF support was coded so that Microsoft management might have been persuaded to do formulas as OpenOffice.org does, back when there was still time to influence the decision?
  • ...1 more annotation...
  • One might reasonably infer from such circumstances that ODF interoperability was far less important to IBM than was preserving its ability to attack the quality of Microsoft's ODF support after it was hard-coded. Or put another way, IBM appears in this instance to be more committed to double standards than to ODF interoperability.
Paul Merrell

An Antic Disposition: ODF Lies and Whispers - 0 views

  • This certainly is an interesting statement. There is nothing I can point to that is false here. Everything here is 100% accurate. However, it seems to be reckless in how it neglects the most relevant facts, namely that the proposals did not make it into ODF 1.2 at Microsoft's sole election. It is as if Lee Harvey Oswald had written a note: "Went to Dallas and saw a parade today. Tried to see a movie, but had to leave early. Heard later on the radio that the President was shot". This would have been 100% accurate as well, but not the "whole truth".
  • Ask the questions in public places and seek a public, on-the-record response. More people are willing to lie than face of consequences of being caught lying. That is the ultimate weakness of lies. They cannot stand the light of public exposure. Sunlight is the best antiseptic.
  •  
    Here we find IBM's Rob Weir condemning less than the "whole truth," advocating public exposure as the best remedy for lies, and observing that "[m]ore people are willing to lie than face of [sic] consequences of being caught lying." These statements may be usefully contrasted with Weir's actual practice in relevant regard. See e.g., the dismantling of a key fact in his same article in the blog post and comments here. http://www.adjb.net/post/No-one-supports-ISO-ODF-today.aspx Also notice there just how far Weir goes to avoid telling the "whole truth" in his own comments.
Paul Merrell

Twitter / Rob Weir: @jackschofield Sorry you m ... - 0 views

  • @jackschofield Sorry you missed the postscript with the OOXML data. ODF still smaller by 18%. Calling names is boorish and unprofessional. 8:32 AM Oct 4th via TweetDeck in reply to jackschofield rcweir Rob Weir
  •  
    Now we learn that IBM's Rob Weir can't stand the heat of his own most frequently deployed weapon in debate with those who want less interop talk from IBM and more interop walk. See other quotes and links in this group."Calling names is boorish and unprofessional," he pronounces. A great quote to replay the next time Rob wilds the ad hominem fallacy as his weapon.  
1 - 7 of 7
Showing 20 items per page