Skip to main content

Home/ Document Wars/ Contents contributed and discussions participated by Paul Merrell

Contents contributed and discussions participated by Paul Merrell

Paul Merrell

U.S. top court declines to hear Microsoft antitrust case | Reuters - 0 views

  • (Reuters) - The U.S. Supreme Court on Monday brought an end to Novell Inc's antitrust claims against Microsoft Corp that date back 20 years to the development of Windows 95 software. By declining to hear Novell's appeal, the court left intact a 10th U.S. Circuit Court of Appeals ruling from September 2013 in favor of Microsoft.The court of appeals unanimously affirmed the dismissal of Novell Inc's claims that Microsoft violated the Sherman Antitrust Act when it decided not to share its intellectual property while developing its Windows 95 operating system.
  • The Novell case, which was first filed in 2004, was over Microsoft's decision not to share with Novell details about its Windows operating system. Novell claimed that its suite of applications, including WordPerfect, suffered as a result of Microsoft withholding the information.Novell alleged that Microsoft used its market power in operating systems to promote its own applications.
Paul Merrell

EUROPA - Press Releases - Antitrust: Commission opens proceedings against MathWorks - 1 views

  • Brussels, 1 March 2012 - The European Commission has opened a formal investigation to assess whether The MathWorks Inc., a U.S.-based software company, has distorted competition in the market for the design of commercial control systems by preventing competitors from achieving interoperability with its products. The Commission will investigate whether by allegedly refusing to provide a competitor with end-user licences and interoperability information, the company has breached EU antitrust rules that prohibit the abuse of a dominant position. The opening of proceedings means that the Commission will examine the case as a matter of priority. It does not prejudge the outcome of the investigation. The investigation follows a complaint alleging that MathWorks had refused to provide a competitor with end-user software licences and accompanying interoperability information for its flagship products "Simulink" and "MATLAB", thereby preventing it from lawfully reverse-engineering in order to achieve interoperability with these two products.
  • As in the Microsoft case (see IP/04/382 and MEMO/04/70 and MEMO/07/359), the issue of software interoperability is central to this investigation. The Commission's investigation will focus on whether MathWorks' behaviour has prevented competitors from achieving interoperability with its widely used products and thereby hindered competition in breach of Article 102 TFEU. In this context, it is recalled that the European Directive 2009/24/EC on the legal protection of computer programmes also aims to foster interoperability by allowing for reverse-engineering for interoperability purposes provided that the software at issue was lawfully acquired.
  • Background MathWorks' "Simulink" and "MATLAB" software products are widely used for designing and simulating control systems. Control systems are deployed in many innovative industries such as in cruise control or anti-lock braking systems (ABS) for cars. Article 102 TFEU prohibits the abuse of a dominant position which may affect trade and prevent or restrict competition. The implementation of this provision is defined in the Antitrust Regulation (Council Regulation No 1/2003) which can be applied by the Commission and by the national competition authorities of EU Member States. The Commission has informed MathWorks and the Member States' competition authorities that it has formally opened proceedings in this case.
  •  
    Commission v. MIcrosoft Redux.
Paul Merrell

My report on OOXML and ODF | Larsblog - 3 views

  • Work on this in the Norwegian government has been going on for years. I worked on this for four months, producing a 45-page report. This blog posting oversimplifies most of the way through in the interests of brevity.
  • Work on this in the Norwegian government has been going on for years. I worked on this for four months, producing a 45-page report. This blog posting oversimplifies most of the way through in the interests of brevity. The full report is here, and if you can read Norwegian you can post your feedback in the form on that page. Ever since ODF and OOXML burst onto the scene in ISO SC34 I've tried to avoid getting pulled into the mess. I was quite successful at this for several years, until one day one our managers at Bouvet suggested we bid for a contract to write a report for the Norwegian government (strictly speaking, the Agency for Public Management and eGovernment (Difi)). The report was about whether to recommend/require ODF and/or OOXML in the Norwegian public sector. I couldn't come up with any valid excuses for not doing it, and so we sent in a bid, and in the end won the contract.
  • Conclusion By now I guess the conclusion should be obvious. I couldn't recommend either format. Both specs are of very low quality, and for neither format do you have much of a choice of tools. For the public sector this would essentially mean having to agree not on a format, but on a single tool to be used sector-wide. The purpose of creating standards should be to achieve interoperability, but in this case that just hasn't happened yet. Having said that, ODF 1.2 looks like it will satisfy nearly all the shortcomings with ODF 1.1 that my report identifies. Similarly, it looks like the next OOXML version (ISO/IEC 29500:2008 amendment 1) will solve most of the OOXML issues. If the implementors follow up and improve their converters things will look much brighter. Unfortunately, this is going to take a couple of years. So my conclusion in the report is that both standards should be listed as "under observation" for all usage areas.
Paul Merrell

Microsoft Finds Fault With Google Upgrade -- Redmondmag.com - 2 views

  • Google's announcement this week that it had improved its Google Docs Web apps drew ridicule from a Microsoft official on Wednesday.
  • Kisslo also accused Google of not following the OpenDocument Format (ODF) spec with fidelity in Google Docs applications. The Google spokesperson called that claim "ironic" for Microsoft. (Microsoft has had its own issues staying true to the ISO/IEC-standardized version of its Office Open XML document format spec. However, the company did previously announce support for ODF in Office 2007.) This seemingly minor spat between the two companies has deep implications. At stake may be much of Microsoft's empire, based on its two cash cows: Microsoft Office and Windows.
Paul Merrell

Microsoft opens Outlook format, gives programs access to mail, calendar, contacts - 0 views

  • Microsoft on Monday said it will provide patent- and license-free use rights to the format behind its Outlook Personal Folders opening e-mail, calendar, contacts and other information to a host of applications such as antimalware or cloud-based services.
  • Documenting and publishing the .pst format could open up entirely new feature sets for programs such as search tools for mining mailboxes for relevant corporate data, new security tools that scan .pst data for malicious software, or e-discovery tools for meeting compliance regulations, according to Microsoft officials.
  •  
    The ripples from the European Commission v. Microsoft decision continue to flow. The catch, of course, is that the patent rights will almost certainly be subject to the Microsoft Open Specification Promise, a weasel-worded document that actually grants no rights. http://law.bepress.com/unswwps/flrps/art71/ But someone with some clout will push that issue sooner or later.
Paul Merrell

i4i-Microsoft battle over Word coming to a head - 0 views

  • "The implications going forward are immense," i4i Chairman Loudon Owen said. "We were accused initially of wanting to shut down Word. We don't want to shut down Word, we want to open it up."
Paul Merrell

Federal future cloudy for Microsoft Word -- Government Computer News - 0 views

  • “We have explained [to federal agencies] ways of moving from Microsoft Word to an i4i implementation of custom XML,” said Michael Vuple, i4i’s founder. “If agencies want custom XML, we are prepared, and we are working on a way for them to use our technology.” The company hasn’t been actively marketing that approach to government so far because it didn’t want to take advantage of the current “unfortunate situation,” he said. But with agencies likely to be asking the question, he said i4i will probably have to take a more proactive stance in the future.
Paul Merrell

'Custom XML' the key to patent suit over Microsoft Word | All about Microsoft | ZDNet.com - 0 views

  • The short version of the story so many are talking about today: A Texas judge is barring Microsoft from selling Microsoft Word due to alleged patent infringement and fining the Redmondians multiple millions as part of the case. But most synopses of the case seem to be omitting a key part of the ruling: the concept of “Custom XML.” According to the press release from the lawyers for plaintiff i4i: “Today’s permanent injunction prohibits Microsoft from selling or importing to the United States any Microsoft Word products that have the capability of opening .XML, .DOCX or DOCM files (XML files) containing custom XML.” What is “Custom XML”? Is it a (supposedly) unremo
Paul Merrell

Microsoft offers Office 2010 file format 'ballot' to stop EU antitrust probe - 0 views

  • In a proposal submitted to the European Commission two weeks ago, Microsoft spelled out a range of promises related to Office, its desktop and server software, and other products to address antitrust concerns first expressed by officials in January 2008.
  • Beginning with the release of Office [2010], end users that purchase Microsoft's Primary PC Productivity Applications in the EEA [European Economic Area] in both the OEM and retail channel will be prompted in an unbiased way to select default file format (from options that include ODF) for those applications upon the first boot of any one of them," Microsoft said in its proposal [download Word document]
  •  
    Microsoft's proposed undertaking for resolving the ECIS complaint to the European Commission regarding its office productivity software can be downloaded from this linked web page. I've given it a quick skim. Didn't see anything in it for anyone but competing big vendors. E.g., no profiling of data formats for interop of less and more featureful implementations, no round-tripping provisions. Still, some major concessions offered.
Paul Merrell

Article - WSJ.com - 0 views

  • When Oracle Corp.(ORCL) acknowledged two weeks ago that the U.S. Justice Department was extending an antitrust review of its planned merger with Sun Microsystems Inc. (JAVA), the software giant maintained the deal would still close by the end of August. But pressing through a second-request investigation in such an abbreviated time frame would buck the odds, according to Justice Department statistics and antitrust experts, even as Sun's financial results as an independent entity skid to surprising lows. Sun will hold a special shareholder meeting on Thursday, where it is expected to receive approval to accept Oracle's $5.6 billion buyout bid.
Paul Merrell

Gray Matter : Compatibility Pack for Open XML passes 100 million downloads - 0 views

  • The Compatibility Pack, software that allows you to open, edit and save Open XML format documents in Office XP and 2003 has now been downloaded over 100 million times.
  •  
    Also includes stats in table form indicating that according to Google Search OOXML documents now outnumber ODF documents on the Web, for word processor documents, spreadsheet documents, and presentation documents.
Paul Merrell

untitled - 0 views

  • Most (quality) specifications provide clear instructions using those magic words SHALL, SHALL NOT, and MAY where those words have a defined meaning for an implementor. Paragraphs are clearly identified as either normative or informative. That way an implementor knows what they must and may implement to claim conformance against a specification. This approach has been well established over time as a sensible way for spec writers and implementors to work
  • Most (quality) specifications provide clear instructions using those magic words SHALL, SHALL NOT, and MAY where those words have a defined meaning for an implementor. Paragraphs are clearly identified as either normative or informative. That way an implementor knows what they must and may implement to claim conformance against a specification. This approach has been well established over time as a sensible way for spec writers and implementors to work That is the way quality specifications are written. For example, ISO/IEC's JTC 1 Directives (link to PDF) requires that international standards designed for interoperability "specify clearly and unambiguously the conformity requirements that are essential to achieve the interoperability." With that clarity, conformance is testable and can provide confidence of interoperability. A suite of tests may be developed and applied to an implementation to determine which tests pass, which fail, and hence arrive at an objective pronouncement on conformance of an implementation against the entirety of the specification.
  • In a quality specification, it should be feasible to select a normative paragraph, identify a conformance test for it, and make a clear statement that this test proves that an implementation meets (or fails to meet) that requirement. Call it a test plan: define the tests (test specification), define the expected set of results, and define what constitutes a "pass" of each test that establishes conformance. The plan then provides the matrix of test spec against requirement. Simple.
  • ...4 more annotations...
  • Rob Weir of IBM chaired (apology for the misuse of that last word) the formation list and then simply announced what the charter would be rather than seeking consensus among the list participants. As part of this process before that charter was produced and while I still naively believed that consensus was a goal, I sat down with ODF 1.1 and did a paragraph-by-paragraph review for testability. The numbers were quite revealing. I completely reviewed only the first four major sections and found very few clear requirements. The majority were mere statements with no normative language used to identify what was required or optional. Implementors would have to make their own interpretation.
  • It's ironic that the chair viewed as good news the fact that there were far fewer testable paragraphs than he had predicted. But his prediction of 10,000 test cases is probably far closer to how many testable paragraphs there should be; my counts were actually bad news.
  • All of the above leads to the interesting question of just how the chair expects to accomplish much that is useful in regard to ODF conformance testing before the specification is amended to tighten up the language and add clear requirements. The syntax conformity is already handled by validation against the schema, but the semantics are woefully under-specified.
  • Summary: ODF 1.1 isn't verifiable as a specification. From a fairly cursory review of the latest draft, ODF 1.2 will follow the same path. With OASIS now being more demanding regarding conformance requirements on every specification and with ISO/IEC taking a closer interest in liaison with the ODF TC, I find it hard to see how the ODF TC co-chairs can maintain this view toward verification.
Paul Merrell

Screenshots of The First Application That Supports ISO/IEC 29500 - 0 views

  • Blogosphere has been full of speculations about when and if ever Microsoft will support ISO/IEC 29500 format in MS Office. Some people believe and wish that OpenOffice.org with ISO/IEC 29500 support will be released earlier then MS Office. But don't get fooled, the first application conforming to ISO/IEC 29500 is out, it is neither MS Office nor OpenOffice.org, it is coming from Free Software Foundation and you can see screenshots here.
Paul Merrell

PC Pro: News: Google Docs accommodates Office 2007 file formats - 0 views

  • Google has added support for the DOCX and XLSX file formats to the Google Docs office suite.
  • Google has now rectified this situation following the ratification of the Open XML standard last year, but anybody looking to import the PPTX files used by PowerPoint 2007 will need to wait. The files can be converted into a Google Docs-friendly format, but you'll lose formatting, themes and transition effects.
Paul Merrell

Rob Weir is caught in a deceit - 0 views

  • Ah, Marbux, what circus is complete without the clowns?
  • 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?
  • ...1 more annotation...
  • 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?
Paul Merrell

GullFOSS - 0 views

  • I normally don't post my ODF Plugin news and information on GullFOSS, but so many people complain (everywhere, including in OOo mailing lists) about the bad ODF support in Microsoft Office 2007 SP2, that I thought it might be a good idea to post some information about the ODF Plugin here... The Sun ODF Plugin for Microsoft Office, which is based on OpenOffice.org, adds support for ODF to Microsoft Office 2000 and newer versions. So you don't have to use the very latest Microsoft Office 2007 SP2 version (in case you really need Microsoft Office for some reason) , where ODF support is insufficient anyway.
  •  
    Like IBM, Sun bad mouths Microsoft ODF support rather than repairing the relevant defects in the ODF specification. This despite no one yet having come forward with an example of non-conformance that withstands scrutiny. So what should have been bug reports filed against the specification is instead wielded as an advertising weapon against competitors. This is simply more "OOo defines what is valid ODF" horse puckey.
Paul Merrell

Los Angeles Times - latimes.com - 0 views

  • The Obama administration put large companies on notice that it would be tougher on mergers and attempts to stifle competition, restoring the type of aggressive antitrust enforcement of the 1990s that led to the landmark government case against Microsoft Corp.
  • Among those likely to feel the heat of federal inquiries are technology companies, such as chip maker Intel Corp., Internet giant Google Inc. and longtime tech leader IBM Corp.
1 - 20 of 20
Showing 20 items per page