Skip to main content

Home/ Document Wars/ Group items matching "software" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

OOXML-ODF: The Harmonization Hope Chest | Orcmid's Lair - 0 views

orcmid.com/...f-harmonization-hope-chest.asp

shared by Gary Edwards on 09 Feb 08 - Cached
  • 4. The Reality in the Punchbowl Meanwhile, Sam Hiser offers a different impression of the DIN effort [4]: "The ODF-to-OOXML harmonization effort being hosted by the German standards group, DIN, is Europe's best effort to resolve our Mexican Standoff between Microsoft, Sun and IBM. Even though harmonization is laughably complex and will not work unless the applications are harmonized too, the best and brightest of Germany are left to hope for success."  [emphasis mine: dh] Although the mission of the German effort is translation (Übersetzung), not harmonization, I find there is a very important point that is not made often enough:  People write, read, and edit office documents with little, if any, understanding of the particular format that makes them persistent in digital form.  The XML-based open formats do not change that.   People adapt to the software/device they are using by trial and error.  We train ourselves to obtain the visible results that we want.  Different people obtain superficially similar results by quite different means.   Even when someone has gone to the trouble to create style sheets, forms, macros, templates and other format-impacting aids, it is very loosey-goosey in practice.  And it still does not require paying attention to the file format.  
Gary Edwards

Microsoft: IBM masterminded OOXML failure - ZDNet UK - 0 views

news.zdnet.co.uk/...0,1000000121,39292492,00.htm

shared by Gary Edwards on 31 Jan 08 - Cached
  • "It's a new way to compete," Tsilas said. "They are using government intervention as a way to compete. It's competing through regulation, because you couldn't compete technically."
Gary Edwards

Microsoft: IBM masterminded OOXML failure - ZDNet UK - 0 views

news.zdnet.co.uk/...0,1000000121,39292492,00.htm

shared by Gary Edwards on 31 Jan 08 - Cached
  • "IBM have asked governments to have an open-source, exclusive purchasing policy," Tsilas said. "Our competitors have targeted this one product — mandating one document format over others to harm Microsoft's profit stream." "It's a new way to compete," Tsilas said. "They are using government intervention as a way to compete. It's competing through regulation, because you couldn't compete technically."
Gary Edwards

ODF and OOXML - The Final Act - 0 views

www.idm.net.au/story.asp

din fraunhofer harmonization iso odf ooxml opendocument openxml

shared by Gary Edwards on 04 Feb 08 - Cached
  • The format war between Microsoft’s Open Office XML (OOXML) and the open source OpenDocument Format (ODF) has flared up again, right before the looming second OOXML ISO vote in March.
  • “ISO has a policy that, wherever possible, there should only be one standard to maximise interoperability and functionality. We have an international standard for digital documentation, ODF,” IBM’s local government programs executive Kaaren Koomen told AustralianIT.
  • ODF has garnered some criticism for being a touch limited in scope, however, one of its strengths is that it has already been accepted as a worldwide ISO standard. Microsoft’s format on the other hand, has been criticised for being partially proprietary, and even a sly attempt by the software giant to hedge its bets and get in on open standards while keeping as many customers locked into its solutions as possible.
    • Gary Edwards
      Gary Edwards on 04 Feb 08
       
      A "touch limited in scope"? Youv'e got to be kidding. ODF was not defined to be compatible with the billions of MSOffice binary (BIN) documents. Nor was it designed to further interoperability with MSOffice.
      Given that there are over 550 million MSOffice desktops, representing upwards of 95% of all desktop productivity environments, this discrepancy of design would seem to be a bit more than a touch limited in scope!
      Many would claim that this limitation was due to to factors: first that Microsoft refused to join the OASIS ODF TC, which would have resulted in an expanded ODF designed to meet the interoperability needs of the great herd of 550 million users; and second, that Microsoft refused to release the secret binary blueprints.
      Since it turns out that both IBM and Sun have had access to the secret binary blueprints since early 2006, and in the two years since have done nothing to imptove ODF interop and conversion fidelity, this second claim doesn't seem to hold much water.
      The first claim that Microsoft didn't participate in the OASIS ODF process is a bit more interesting. If you go back to the first OASIS ODF Technical Committee meeting, December 16th, 2002, you'll find that there was a proposal to ammend the proposed charter to include the statemnt that ODF (then known as Open Office XML) be compatible with existing file formats, including those of MSOffice. The "MSOffice" reference was of course not included because ODF sought to be application, platform and vendor independent. But make no mistake, the discussion that day in 2002 was about compatibility and the conversion of the legacy BIN's into ODF.
      The proposal to ammend the charter was tabled. Sun objected, claiming that people would interpret the statement as a direct reference to the BIN's, clouding the charter's purpose of application, platform and vendor independence. They proposed that the charter ammendment b
    • Gary Edwards
      Gary Edwards on 04 Feb 08
       
      Will harmonization work? I don't think so. The problem is that the DIN group is trying to harmonize two application specific formats. OpenOffice has one way of implementing basic document structures, and MSOffice another. These differences are directly reflected in the related formats, ODF and OOXML. Any attempts to harmonize ODF and OOXML will require that the applications, OpenOffice and MSOffice, be harmonized! There is no other way of doing this unless the harmonized spec has two different methods for implementing basic structures like lists, tables, fields, sections and page dynamics. Not to mention the problems of feature disparities. If the harmonized spec has two different implementation models for basic structures, interoeprability will suffer enormously. And interoperability is after all the prupose of the standardization effort. That brings us to a difficult compromise. Should OpenOffice compromise it's "innovative" features and methods in favor of greater interoperability with MSOffice and billions of binary documents? Let me see, 100 million OpenOffice installs vs. 550 MSOffice installs bound to workgroup-workflow business processes - many of which are critical to day to day business operations? Sun and IBM have provided the anser to this question. They are not about to compromise on OpenOffice innovation! They believe that since their applications are free, the cost of ODF mandated "rip out and replace" is adequately offset. Events in Massachusetts prove otherwise! On July 2nd, 2007, Sun delivered to Massachusetts the final version of their ODF plug-in for MSOffice. That night, after reviewing and testing the 135 critical documents, Massachusetts made a major change to their ETRM web site. They ammended the ETRM to fully recognize OOXML as an acceptable format standard going forward. The Massachusetts decision to overturn th
  • ...1 more annotation...
    • Gary Edwards
      Gary Edwards on 04 Feb 08
       
      The Burton Group did not recommend that ISO recognize OOXML as a standard! They pointed out that the marketplace is going to implement OOXML by default simply because it's impossible to implement ODF in situations where MSOffice dominates. ISO should not go down the slippery slope of recognizing application-platform-vendor specific standards. They already made that mistake with ODF, and recognizing OOXML is hardly the fix. What ISO should be doign is demanding that ODF fully conform with ISO Interoeprability Requirements, as identified in the May 2006 directive! Forget OOXML. Clean up ODF first.
  • Gary Edwards on 04 Feb 08
     
    Correcto mundo! There should be only one standard to maximise interoeprability and functionality. But ODF is application specific to the way OpenOffice works. It was not designed from a clean slate. Nor was the original 2002 OpenOffice XML spec designed as an open source effort! Check the OOo source code if you doubt this claim. The ONLY contributors to Open Office XML were Sun employees! What the world needs is in fact a format standard designed to maximise interoperability and functionality. This requires a total application-platofrm-vendor independence that neither ODF or OOXML can claim. The only format that meets these requirements is the W3C's family of HTML-XML formats. These include advancing Compound Docuemnt Framework format components such as (X)HTML-5, CSS-3, XForms, SVG and SMiL.. The W3C's CDF does in fact meet the markeplace needs of a universal format that is open, unencumbered and totally application, platform and vendor independent. The only trick left for CDF is proving that legacy desktop applications can actually implement conversions from existing in-memory-binary-representations to CDF without loss of information.
Gary Edwards

Notes on Breaking the Web to Ride the Fifth Wave - 1 views

community.zdnet.co.uk/...,1000000565,2000542666b,00.htm

ie-8 iso microsoft msoffice odf ooxml sdk xaml

shared by Gary Edwards on 22 Mar 08 - Cached
  • garyedwards's Discussions Breaking the Web Talkback: Google: OOXML 'insufficient and unnecessary'
  • Gary Edwards on 22 Mar 08
     
    Somehow i got involved in this discussion and ended up posting a number of comments explaining the how and why behind Microsoft's push for ISO approval of MS-OOXML. I have been working on a paper titled, "Breaking the Web to Ride the Great Wave". Breaking the Web is what will happen once ISO approves MS-OOXML. The MIcrosoft Stack of Web Servers (Exchange, SharePoint, MS-SQL Server) are integrated into the MSOffice-Outlook desktop. The MS desktop dominates much of the document workflows and business processes of the commercial world. ISO approval of the MSOffice specific MS-OOXML will legitamize MSOffice as an editor of standardized web ready docuemnts. But how MS-OOXML docuemnts become "Web REady" is tricky. In the December 2007 MSOffice SDK beta, we see how this is done. The SDK provides a conversion component for the quick high fidelity conversion of MS-OOXML documents to XAML. XAML is a proprietary part of the WPF (Windows Presentation Foundation) layer of the .NET framework, and is easily paried with Silverlight. Sometimes XAML is referred to as "fixed/flow". XAML is an MS proprietary replacement for the W3C's (X)HTML. Billions of MSOffice docuemnts will make their way to the Web using this SDK converter. The path for transitioning the monopolist hold on desktop business processes to the monopolist stack of web servers is set with this converter. ISO approval of MS-OOXML will enable Microsoft to dodge brining their desktop editor into compliance with advancing W3C standards such as (X)HTML, CSS 3, XForms, SVG and RDF. Instead of these open standards, transitioning business processes will be locked into MS only dependencies; XAML, Silverlight, WinForms, and Smart Tags. The breaking of the web results in a consumer/business cloud dependent on MS proprietary technologies that are out of the reach of Firefox, Apache, Java, and Adobe technologies. Google won't be able to penetrate the business stack, and will be kept very busy trying to defen
Gary Edwards

Sun and Microsoft confirm data center lovechild | The Register - 0 views

www.theregister.co.uk/...sun_microsoft_lab

microsoft server-farms sun viridian

shared by Gary Edwards on 22 Mar 08 - Cached
  • Microsoft has been less offensive to McNealy and Sun ever since it forked over about $2bn to settle disputes, agreed to an interoperability pact and helped chuck Windows on Sun servers. Now the companies plan to expand their mutual admiration society via an Interoperability Center. Sun will send a bunch of servers and storage boxes up to the Redmond-based center. Engineers from both companies will work on testing Microsoft's server software with the gear. We're told that such work could lead to breakthroughs in 64-bit database technology and amazing e-mail servers.
Gary Edwards

Microsoft's OOXML limps through ISO meeting - ZDNet UK - 0 views

news.zdnet.co.uk/...0,1000000121,39362112-2,00.htm

brm ecma geneva iso oasis odf ooxml

shared by Gary Edwards on 07 Mar 08 - Cached
  • Gary Edwards, former president of the Open Document Foundation, an industry group that promoted ODF but then rejected both approaches and closed itself down in November 2007, said: "Ecma and Oasis are vendor consortia where the rules governing standards specification work favour vendor innovation over the open and transparent interoperability consumers, governments and FLOSS efforts demand... Shutting that door on Ecma OOXML is proving very difficult exactly because the primary and fundamental rule of ISO interoperability requirements has been breached."
Gary Edwards

Google: OOXML 'insufficient and unnecessary' - marbux - ge comments | ZDNet UK - 0 views

news.zdnet.co.uk/...0,1000000121,39348282,00.htm

google interop odf ooxml opendocument zd-uk

shared by Gary Edwards on 07 Mar 08 - Cached
  • Google's technical analysis of the OOXML specification — which notoriously runs to 6,000 pages of code, compared with ODF's 860 pages — has led the company to believe that "OOXML would be an insufficient and unnecessary standard, designed purely around the needs of Microsoft Office", Bhorat claimed.
  • ODF and OOXML are standards in... Marbux
  • Interoperability and the binary ODF conversion di... garyedwards Sorry, the comment was cut short. Here'... garyedwards
Gary Edwards

» Getting enveloped by the potential of Cloud computing | Web 2.0 Explorer | ZDNet.com - 0 views

blogs.zdnet.com/web2explorer

client-server cloud-computing realestate web20

shared by Gary Edwards on 25 Jan 08 - Cached
  • By taking a fundamentally Web-based approach to the development of applications, we shift from bolting Web capabilities onto the silo toward a mode in which data and functionality are native to the Web: a mode in which the design decisions are more about modelling business requirements for limiting the ways in which data flows from one point to another rather than trying to anticipate the places in which it might be needed in order to design those pathways into software from the outset.
  • How do we change the mindset of today’s application developers, in order that they stop building ‘old’ applications in the new world?
Gary Edwards

Q&A: Nicholas Carr on the big switch to utility computing - 0 views

www.computerworld.com/...article.do

carr cloud switch utility web-platform

shared by Gary Edwards on 25 Jan 08 - Cached
  • I think we’re at the early stages of a fundamental shift in the nature of computing, which is going from something that people and businesses had to supply locally, through their own machines and their own installed software, to much more of a utility model where a lot of the computer functions we depend on are supplied from big, central stations, big central utilities over the Internet.
Gary Edwards

Criticism mounts over Birmingham's Linux project - ZDNet UK - 0 views

news.zdnet.co.uk/...0,1000000121,39284758,00.htm

birmingham imported:del.icio.us massachusetts migration moox msecma munich odf

shared by Gary Edwards on 12 Dec 07 - Cached
  • Gary Edwards on 12 Dec 07
     
    Wrack up another loss for the forces of freedom. Birmingham is lucky to get out cheap. Munich raced by the $3,000 per PC mark with no end in sight. Massachusetts is lost in never never land. Sowhat's going on? Why is it so costly to move off the Wind
  • Gary Edwards on 12 Dec 07
     
    Wrack up another loss for the forces of freedom. Birmingham is lucky to get out cheap. Munich raced by the $3,000 per PC mark with no end in sight. Massachusetts is lost in never never land. Sowhat's going on? Why is it so costly to move off the Wind
  • Gary Edwards on 12 Dec 07
     
    Wrack up another loss for the forces of freedom. Birmingham is lucky to get out cheap. Munich raced by the $3,000 per PC mark with no end in sight. Massachusetts is lost in never never land. Sowhat's going on? Why is it so costly to move off the Wind
Gary Edwards

The Joel on Software Discussion Group - Microsoft's ridiculous Office Open XML - 0 views

discuss.joelonsoftware.com/default.asp

ecma imported:del.icio.us iso microsoft mooxml msoffice oasis odf

shared by Gary Edwards on 12 Dec 07 - Cached
  • Gary Edwards on 12 Dec 07
     
    A legthy discussion of the MSOffice bound MOOXML file format. that was triggered by Rob Weir's infamous blog, "How to Hire Guillame Portes".  Lots of comments, pro and con, as to whether or not the applications specific tags used so extensibvely by MOOXML are needed, or not.

    Many argue that the application bound tags should have been fully described.  That every tag in the specification should also include the informaiton needed to implement it.  Agreed!  Otherwise, the specification does not qualify as a standard.  It's simply a vendor specific, and in this case highly proprietary and encumbered file format.

    Others argue that the app bound tags are the only way for Microsoft to provide backwards compatibility with the billions of binary documents bound to MSOffice through proprieatry and secret binary file formats.  These people argue that embedding an application specific binary in the XML file format, instead of converting it to proper XML, is the only way to insure backwards compatibilty.  BS.  There is no technical reason not to convert it to proper XML.  But that would mean fully describing the binary objects, including the nature of their application dependency.  Something Microsoft is quite reluctant to do.

    The truth of the matter is that if the binary object is to be part of a specification submitted to ISO for standards consideration, then it should be fully described, including how to implement it.  Otherwise, MOOXML is just a standard for one.  A standard for Micrsoft only since they are  the only ones with the secret blueprint as to how to implement these binary objects.

  • ...1 more comment...
  • Gary Edwards on 12 Dec 07
     
    A legthy discussion of the MSOffice bound MOOXML file format. that was triggered by Rob Weir's infamous blog, "How to Hire Guillame Portes". Lots of comments, pro and con
  • Gary Edwards on 12 Dec 07
     
    A legthy discussion of the MSOffice bound MOOXML file format. that was triggered by Rob Weir's infamous blog, "How to Hire Guillame Portes". Lots of comments, pro and con
  • Gary Edwards on 12 Dec 07
     
    A legthy discussion of the MSOffice bound MOOXML file format. that was triggered by Rob Weir's infamous blog, "How to Hire Guillame Portes". Lots of comments, pro and con
Gary Edwards

The better Office alternative: SoftMaker Office bests OpenOffice.org ( - Software ) - 0 views

news.idg.no/...art.cfm

shared by Gary Edwards on 30 Jun 09 - Cached
  • Frankly, from Microsoft's perspective, the danger may have been overstated. Though the free open source crowd talks a good fight, the truth is that they keep missing the real target. Instead of investing in new features that nobody will use, the team behind OpenOffice should take a page from the SoftMaker playbook and focus on interoperability first. Until OpenOffice works out its import/export filter issues, it'll never be taken seriously as a Microsoft alternative. More troubling (for Microsoft) is the challenge from the SoftMaker camp. These folks have gotten the file-format compatibility issue licked, and this gives them the freedom to focus on building out their product's already respectable feature set. I wouldn't be surprised if SoftMaker got gobbled up by a major enterprise player in the near, thus creating a viable third way for IT shops seeking to kick the Redmond habit.
    • Gary Edwards
      Gary Edwards on 30 Jun 09
       
      Wow. Somebody who finally gets it. OpenOffice and OpenOffice ODF were not designed to be compatible with Microsoft Office, the MSOffice productivity environment, and, the legacy of binary documents. Softmaker is not the only Office Suite alternative designed for compatibility with MSOffice. ThinkFree Office and Evermore Office are also proof positive that high level compatibility is possible.
Paul Merrell

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

blogs.technet.com/...ses-100-million-downloads.aspx

office 2007 compatibility pack odf-ooxml stats

shared by Paul Merrell on 24 Jun 09 - Cached
  • 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.
  • Paul Merrell on 24 Jun 09
     
    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

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

xmlguru.cz/...pplication-supporting-is-29500

OOXML ISO_IEC:29500 implementations

shared by Paul Merrell on 04 Jun 09 - Cached
  • 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

GullFOSS - 0 views

blogs.sun.com/...etter_odf_support_in_microsoft

shared by Paul Merrell on 15 May 09 - Cached
  • 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.
  • Paul Merrell on 15 May 09
     
    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.
Alex Brown

IBM Lotus Symphony - Buzz: Document interoperability in Lotus Symphony - 0 views

symphony.lotus.com/...web_DisPlayPlugin

shared by Alex Brown on 28 Apr 09 - Cached
  • Office 2007 ( OOXML ) import support will be in the next release this quarter.
    • Alex Brown
      Alex Brown on 28 Apr 09
       
      IBM confirms Symphony will support OOXML (at least to read)
Alex Brown

Moved by Freedom - Powered by Standards » Blog Archive » News of the Weird (April issue) - 0 views

standardsandfreedom.net/...news-of-the-weird-april-issue

shared by Alex Brown on 21 Apr 09 - No Cached
  • I just don’t get it
    • Alex Brown
      Alex Brown on 21 Apr 09
       
      Neither do I: but then this is not the first signal of a less than unanimous attitude towards document formats from the Old Firm.
  • The Durban 2 conference in Geneva makes me think of a bizarre mashup of the first Durban conference and what I experienced at the OOXML BRM
    • Alex Brown
      Alex Brown on 21 Apr 09
       
      Not the first time somebody seems to have got confused between issues of tynanny and totalitarianism, and ... document formats. What price perspective?
    • Jesper Lund Stocholm
      Jesper Lund Stocholm on 21 Apr 09
       
      Actually I didn't know Charles participated in the BRM?
    • Alex Brown
      Alex Brown on 21 Apr 09
       
      He didn't - this is something that Andy Updegrove published at the tim too. What price reality?
  • Alex is right. National transposition is a procedural relic. We should get the specs right out of software vendors and just skip this standardization crap that only justifies to pay useless consultants whose status is construed as some kind of impartial judge. This kind of failed processes have led us to believe that standards and norms could be somehow trusted; as it unfortunately turns out, it stops to be true when strongly applied pressure by one large private monopoly meets the weak morals of the ones in charge of ensuring the process is being duly respected. Thank you Alex, for spelling out the truth. Your lack of impartiality and your strange behaviour during the OOXML standardization process have clarified how poorly qualified you are at patronizing others and lecturing on the ISO and other standards bodies’ processes. I wish you good luck for your next job at Microsoft.
    • Alex Brown
      Alex Brown on 23 Apr 09
       
      Ah, the sound of a dummy being being spat out ...
Alex Brown

Groklaw - When Would You Use OOXML and When ODF? -- What is OOXML For? - 0 views

www.groklaw.net/article.php

shared by Alex Brown on 28 Apr 09 - Cached
  • If you say Groklaw is an echo chamber, for example, it has insulting connotations
    • Alex Brown
      Alex Brown on 28 Apr 09
       
      It's also true; but never mind
  • Groklaw deserves respect
    • Alex Brown
      Alex Brown on 28 Apr 09
       
      The level of self-delusion here is truly scary
  • on a committee set up to help a national body
    • Alex Brown
      Alex Brown on 29 Apr 09
       
      Oh? I'd be interested to know which NB was nuts enough to appoint Groklaw as an advisor!
  • ...2 more annotations...
  • among others
  • Microsoft (and Alex Brown) are working within JTC1/SC34
    • Alex Brown
      Alex Brown on 11 Jun 09
       
      Aha, a new line of attack. It is, though, the Countries who want to have the Standard reflect the documents they actually have ...
  • Paul Merrell on 28 Apr 09
     
    The more interesting issue to me is whose voice Groklaw echoes. On the document format war, it's seemed since I stopped contributing articles to Groklaw a few years ago that it is the IBM public relations department's voice being echoed. I'll save for another day the topic of whether the echo chamber is self-delusional or deliberately intended to delude readers.
  • Alex Brown on 29 Apr 09
     
    ... and who it's aimed at. It's not as if Groklaw carries any weight (is it?)
  • Paul Merrell on 30 Apr 09
     
    Groklaw throws a pretty good punch. E.g., it launched ODF vs. Microsoft XML formats as a public issue. The blog is very influential with trade press reporters who are sympathetic to open source software. And Groklaw has done some good reporting, albeit with evident bias. Its chronicles of the SCO vs. IBM and Novell saga is undoubtedly the most thorough out there. But on ODF and OOXML, the coverage has been presented entirely as a black hat/white hat issue, ODF being perfect and designed for interoperability but OOXML as being pure evil. See e.g., http://www.groklaw.net/article.php?story=20080417104016186 (""If you want true interoperability, you need to implement ODF. Seriously. Any limitations to interoperability are entirely on Microsoft's side of the aisle, and the whole world knows it"). Intended or not, Groklaw justly deserves much credit for forestalling public oversight of the ODF TC's utter failure to deal with interoperability issues effectively and credit for keeping the oversight focus solely on OOXML. You'll find no coverage of ODF bugs on Groklaw, only ODF hugs and kisses. I see the blog as having substantially delayed ODF's repair. Groklaw has an enormous readership and particularly among citizen activists who approach ODF as a political cause rather than as a technical specification. But the Groklaw flavor of ODF v. OOXML propaganda remains consistent with that of IBM VP Bob Sutor.
Paul Merrell

Article - WSJ.com - 0 views

online.wsj.com/...BT-CO-20090715-713503.html

Sun Oracle merger antitrust ODF OOo

shared by Paul Merrell on 16 Jul 09 - Cached
  • 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.
« First ‹ Previous 81 - 100 of 108 Next ›
Showing 20▼ items per page