Skip to main content

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

Rss Feed Group items tagged

Paul Merrell

IBM's Rob Weir on the ad hominem fallacy - 0 views

  • Ah, and there is the source of your confusion. Excel 2007 SP2 does not write out document that conform to the ODF 1.1 standard.
  • I lay out the facts, the logic and then draw conclusions. I put my reputation on the line in every post. You could dispute the facts I present. You could argue against my logic if you wish. But you have done neither. You merely resort to ad hominen attacks. I'll take that as an expression of your frustration at not finding a hole in my argument.
  •  
    Here, we learn that Rob Weir understands that ad hominem attacks are usually a fallacy, a way of changing the subject rather than addressing the merits of what was said. We may therefore deduce that when Rob Weir employs the ad hominem attack himself, he does so knowing that he is arguing a fallacy.
Paul Merrell

Notes on Document Conformance and Portability #4 - 0 views

  • It seems you like to ignore requirements in order to defend Microsoft
  • Do you get paid to spread FUD like this, or is it merely a dilettantish pursuit?
  • I am unable to even imagine that you would be ignorant of basic standards terminology. So why do you persist in intentionally misleading your readers?
  • ...2 more annotations...
  • But at all relevant times you knew that you could not respond on the merits if Alex took the time to write the same analysis I did. I call foul. Foul 1: You accused Alex of ignorance and deceit. Foul 2: You had no informed basis for those insults.Foul 3: You knew you had no informed basis for your insults.Foul 4: You have put me to the work of repeating the conversation we already had. Shame on you, Rob Weir. The position you took was unprincipled. You are the one who has intentionally misled Alex's readers. You are caught. If you are a principled person, you will immediately retract your insults and apologize to Alex Brown for your deceit in as public a manner as you inflicted your deceit. If you do not do so, the undeniable record lies here of a man who is not man enough to take responsibility for his wrongs and apologize.
  • Ah, Marbux, what circus is complete without the clowns?
  •  
    Here on a single page, we see several Rob Weir ad hominem attacks, including his ad hominem circumstantial innuendo suggesting that Alex Bown's motive in writing a bug report is to defend Microsoft's implementation of ODF. There is also a notable accusation that Brown is intentionally misleading his readers, which attacks Brown's honesty.
Paul Merrell

Fallacy: Ad Hominem - 0 views

  • Translated from Latin to English, "Ad Hominem" means "against the man" or "against the person." An Ad Hominem is a general category of fallacies in which a claim or argument is rejected on the basis of some irrelevant fact about the author of or the person presenting the claim or argument. Typically, this fallacy involves two steps. First, an attack against the character of person making the claim, her circumstances, or her actions is made (or the character, circumstances, or actions of the person reporting the claim). Second, this attack is taken to be evidence against the claim or argument the person in question is making (or presenting).
  •  
    The ad hominem fallacy is a tactic frequently employed by IBM and its followers, most notably by Rob Weir, against those who disagree with IBM's positions and goals. Those who advocate for repairing the badly broken ODF standard or prepare bug reports on that standard are among the most frequently targeted victims of IBM's ad hominem fallacy attacks.
  •  
    As will be seen in other bookmarks, many IBM staffers' arguments relevant to office document format specifications have been based on variations of the ad hominem fallacy, more commonly known as the "personal attack." .
Paul Merrell

Balance of interest ~= Broader representation - O'Reilly Broadcast - 0 views

  • Rick, on the other hand, by my count, with his various calls for greater "balance", has racked up the impressive total of zero new members. Standards activist? Certainly not an effective one.
  •  
    Rob Weir racks up another ad hominem attack, this time against Rick Jelliffe.
Paul Merrell

Schematron-Report patented? - O'Reilly Broadcast - 3 views

  • Were you in that public benefactor frame of mind when Microsoft offered you money to edit Wikipedia pages for their standards, or when they were paying you to promote their disgraced OOXML standard?
  •  
    IBM's Rob Weir does it again. What's to be done when your company is caught patenting methods implemented in an open standard for years? Change the subject in an attempt to kill the messenger who bears the news. Score another vitriolic ad hominem attack for Rob Weir. 
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

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: 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

Fallacy: Circumstantial Ad Hominem - 0 views

  • A Circumstantial ad Hominem is a fallacy in which one attempts to attack a claim by asserting that the person making the claim is making it simply out of self interest. In some cases, this fallacy involves substituting an attack on a person's circumstances (such as the person's religion, political affiliation, ethnic background, etc.).
  •  
    As will be seen in other bookmarks, one of IBM staffers' frequently employed tactics is the circumstantial ad hominem fallacy. Often, the IBM fallacious argument takes the form of suggestions or innuendos that a speaker is biased by their employer's identity or innuendos suggesting that someone is acting in an IBM competitor's interests.
1 - 10 of 10
Showing 20 items per page