Skip to main content

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

Rss Feed Group items tagged

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

On the scalability of a standard - time for a 'Weirotron' - 0 views

  • After the drama of the initial Office 2007 SP2 ODF support was initiated by Rob Weir, related arguments spilled out all over the place.  I got involved in a few places, but then left it alone whilst I got on with some productive work.  There’s only so many ways you can say “it’s does not exist in the standard – admit it, fix it and move on”.
  • I was always under the impression that it was good practice for something that was invalid against the schema to be deemed non-conformant.  Rob shows just what a absolute noob I am to assume that.
  • Now if Alex Brown and various other highly qualified commenters can misread the ODF specification so heinously, needing the expert advice from the ODF Technical Committee Chair himself to put them right, what chance do lowly developers have? It appears from this there is no chance that any developer will be able to interpret the specification properly, since only Rob Weir (and perhaps the folks working on OpenOffice) has the intellectual capacity to navigate this ball of semantic string. 
  • ...1 more annotation...
  • So, the solution to this is clear – we need to implement Rob Weir as a web service, a Weirotron if you like. That way, everyone can query the Weirotron and get back the definitive answer to any ODF question, without having to deal with the obviously labyrinthine spec that has bamboozled so many leading XML experts. In addition, the Weirotron could help solve those pesky interoperability issues that stem from some areas that ODF relies on the OpenOffice source code for, like Formulas, and areas where the spec is a bit light, so to speak, like Change Tracking etc.  I’m sure that this would really assist Microsoft and many other struggling developers in implementing support for ODF (or rather the Weir-approved cod-ODF) correctly, with the inherent blessing of the ODF TC Chair.
  •  
    Gareth Horton offers a satirical view of IBMer Rob Weir's recent arguments but captures the dilemma Weir's arguments put developers in.
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." .
1 - 3 of 3
Showing 20 items per page