Skip to main content

Home/ OpenDocument/ Group items tagged denmark

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

Denmark: OOXML vote won't affect public sector. ODF is too costly! | InfoWorld - 0 views

www.infoworld.com/...t-Denmark-public-sector_1.html

brm denmark geneva iso msoffice odf ooxml opendocment openxml

shared by Gary Edwards on 07 Mar 08 - Cached
  • Lebech said Denmark considers OOXML an open standard, regardless whether it is approved by the ISO. "It would be impossible for us to use only ISO standards if we want to fulfill the goal of creating interoperability in the government sector," he said. The Danish Parliament also mandated that public agencies consider the cost of using open formats. One of the main reasons OOXML was included is because Denmark is heavily dependent on document management systems that are integrated with Microsoft's Office products, Lebech said. Denmark also found that requiring agencies to only use ODF would have been too expensive, mostly because of the cost of converting documents into ODF, Lebech said. "We wouldn't have been able to only support ODF," Lebech said. "It wouldn't have been cost neutral."
Gary Edwards

Slamming the door shut on MS OOXML - 0 views

lists.oasis-open.org/...msg00033.html

cdf interoperability iso odf odf-tc officeopenxml ooxml opendocument xml

shared by Gary Edwards on 24 Aug 07 - Cached
  • So your goal is a networked world where metadata is routinely trashed by apps developed by those who are too dumb or otherwise disabled to preserve metadata and only the big boys get to do interoperability, right? So if I send you a document for your editing, I can't count on getting it back with xml:id attributes intact. No thanks, Patrick. That sounds way too much like how things have worked ever since office productivity software first came on the market. In your world, interoperability belongs only to those who can map features 1:1 with the most featureful apps. And that is precisely why OpenDocument never should have been approved as a standard. Your kind of interoperability makes ODF a de facto Sun Microsystems standard wearing the clothing of a de jure standard. Why not just standardize the whole world on Microsoft apps and be done with it? Are two monopolies maintained by an interoperability barrier between them better than one? Fortunately, we don't have to debate the issue because the Directives resolve the issue. You lose under the rules of the game.
  • Gary Edwards on 24 Aug 07
     
    Marbux on metadata and the language of universal interoperability: Few people are aware of the raging debate that has pushed ODF to the edge. The OASIS ODF TC is split between those who support Universal Interoperability, and those who insist on continuing with limited ODF interoperability.

    ODF (OpenDocument), formally known as Open Office XML, began it's standards life in the fall of 2002 when Sun submitted the OpenOffice file format to OASIS for consideration as a office suite XML fiel format standard. The work on ODF did not start off as a clean slate in that there were near 600 pages of application specific specification from day one of the standards work. The forces of universal interop have sought for years to separate ODF from the application specific features and implementation model of OpenOffice that began with those early specification volumes, and continues through the undue influence Sun continues to have over the ODF specification work.

    Many mistakenly believed that submission of ODF to ISO and subsequent approval as an international standard would provide an effective separation, putting ODF on the track of a truly universal file format.

    Marbux is one of those Universal Interop soldiers who has dug in his heels, cried to the heavens that enough is enough, and demanded the necessary changes to ODF interoperability language.

    This post he recently submitted to the OASIS ODF Metadata SC is a devastating rebuttal to the arguments of those who support the status quo of limited interoperability.

    In prior posts, marbux argues that ISO directives demand without compromise universal interoperability. This demand is also shared by the World Trade Organization directives regarding international trade laws and agreements. Here he brings those arguments together with the technical issues for achieving universal interop.

    It's a devastating argument.

Gary Edwards

ConsortiumInfo.org - New Comment Draft of Mass. ETRM Includes OOXML - 0 views

www.consortiuminfo.org/...article.php

shared by Gary Edwards on 02 Jul 07 - Cached
  • this new draft includes Microsoft's OOXML formats as an acceptable "open format." 
  • Gary Edwards on 02 Jul 07
     
    Game Over?  Probably.  I've been expecting Massachusetts to publicly revise the ODF mandate to include OOXML ever since Louis Gutierrez resigned in early October of 2006.  That was as clear a signal that ODF had failed in Massachusetts as anyone needed.

    The only surprise is that it took the new CIO, Beth Pepoli so long to make the announcement that OOXML would be recognized as an officially recognized open XML file format going forward.

    Andy UpDegrove of course does his best to downplay the significance of this announcement.  But how can this not be the deathnell for ODF? 

    The failure of ODF in Massachusetts has resulted in a world wide recognition that it is impossible to implement ODF. 

    This is exactly what happened to ODF mandate legislature in California.  The CIO's in California uniformly rejected both ODF legislation and Sun's hapless effort to set up an ODF Pilot Study based on what had happened in Massachusetts.  If Mass couldn't implement ODF, than they saw no reason for them to try.

    And it does come down to "implementation". 

    Most people think the implementation of ODF is as easy as downloading OepnOffice and converting your legacy docuemnts to ODF as they are used.  Simply fix the artifacts of conversion in process, and never look back.  OOo is free.  So what's not to like?

    Well, the problem is that the world has fifteen plus years of building business processes, line of business integrated applications and other client/server integration on top of the MSOffice application suite.  These business processes are bound hard to MSOffice.

    So the barrier for OpenOffice and ODF is twofold.  Any implementation of ODF must overcome both the binary documents conversion barrier, and, the MSOffice bound business process barrier.

    The cost and disruption of a <font
Gary Edwards

Behind Putting the OpenDocument Foundation to Bed (without its supper) : Updegroove | L... - 0 views

linux-foundation.org/...tion-to-bed-without-its-supper

cdf foundation marbux odf ooxml updegrove

shared by Gary Edwards on 30 May 08 - Cached
  • CDF is one of the very many useful projects that W3C has been laboring on, but not one that you would have been likely to have heard much about. Until recently, that is, when Gary Edwards, Sam Hiser and Marbux, the management (and perhaps sole remaining members) of the OpenDocument Foundation decided that CDF was the answer to all of the problems that ODF was designed to address. This announcement gave rise to a flurry of press attention that Sam Hiser has collected here. As others (such as Rob Weir) have already documented, these articles gave the OpenDocument Foundation’s position far more attention than it deserved. The most astonishing piece was written by ZDNet’s Mary Jo Foley. Early on in her article she stated that, “the ODF camp might unravel before Microsoft’s rival Office Open XML (OOXML) comes up for final international standardization vote early next year.” All because Gary, Sam and Marbux have decided that ODF does not meet their needs. Astonishing indeed, given that there is no available evidence to support such a prediction.
  • Gary Edwards on 30 May 08
     
    Uh?  The ODF failure in Massachusetts doesn't count as evidence that ODF was not designed to be compatible with existing MS documents or interoperable with existing MSOffice applications?

    And it's not just the da Vinci plug-in that failed to implement ODF in Massachusetts!  Nine months later Sun delivered their ODF plug-in for MSOffice to Massachusetts.  The next day, Massachusetts threw in the towel, officially recognizing MS-OOXML (and the MS-OOXML Compatibility Pack plug-in) as a standard format for the future.

    Worse, the Massachusetts recognition of MS-OOXML came just weeks before the September 2nd ISO vote on MS-OOXML.  Why not wait a few more weeks?  After all, Massachusetts had conducted a year long pilot study to implement ODF using ODF desktop office sutie alternatives to MSOffice.  Not only did the rip out and replace approach fail, but they were also unable to integrate OpenOffice ODF desktops into existing MSOffice bound workgroups.

    The year long pilot study was followed by another year long effort trying to implement ODF using the plug-in approach.  That too failed with Sun's ODF plug-in the final candidate to prove the difficulty of implementing ODF in situations where MSOffice workgroups dominate.

    California and the EU-IDABC were closely watching the events in Massachusetts, as was most every CIO in government and private enterprise.  Reasoning that if Massachusetts was unable to implement ODF, California CIO's totally refused IBM and Sun's effort to get a pilot study underway.

    Across the pond, in the aftermath of Massachusetts CIO Louis Guiterrez resignation on October 4th, 2006, the EU-IDABC set about developing their own file format, ODEF.  The Open Document Exchange Format splashed into the public discussion on February 28th, 2007 at the "Open Document Exchange Workshop" held in Berlin, Germany.

    Meanwhile, the Sun ODF plug-in is fl
  • Gary Edwards on 30 May 08
     
    Marbux sets the record straight. These are the facts: Putting Andy Updegrove to Bed (without his supper) ..... http://www.universal-interop-council.org/node/4
  • Gary Edwards on 30 May 08
     
    Response from the OpenDocument Foundation setting the record straight. See "copmments" with this bookmark
Gary Edwards

Barr: What's up at the OpenDocument Foundation? - Linux.com - 0 views

www.linux.com/121034

cdf odf ooxml w3c

shared by Gary Edwards on 08 Nov 07 - Cached
  • The OpenDocument Foundation, founded five years ago by Gary Edwards, Sam Hiser, and Paul "Buck" Martin (marbux) with the express purpose of representing the OpenDocument format in the "open standards process," has reversed course. It now supports the W3C's Compound Document Format instead of its namesake ODF. Yet why this change of course has occurred is something of a mystery.
  • Gary Edwards on 08 Nov 07
     
    More bad information, accusations and smearing innuendo.  Wrong on the facts,  Emotionally spent on the conclussions.  But wow it's fun to see them with their panties in such a twist.

    The truth is that ODF is a far more "OPEN" standard than MS-OOXML could ever hope to be.  Sam's Open Standards arguments for the past five years remain as relevant today as when he first started makign them so many years ago.

    The thing is, the Open Standards requirements are quite different than the real world Implementation Requirements we tried to meet with ODF.

    The implementation requirements must deal with the reality of a world dominated by MSOffice.  The Open Standards arguments relate to a world as we wish it to be, but is not.

    It's been said by analyst advising real world CIO's that, "ODF is a fine open standards format for an alternative universe where MSOffice doesn't exist".

    If you live in that alternative universe, then ODF is the way to go.  Just download OpenOffice 2.3, and away you go.  Implementation is that easy.

    If however you live in this universe, and must deal with the impossibly difficult problem of converting existing MSOffice documents, applications and processes to ODF, then you're screwed. 

    All the grand Open Standards arguments Sam has made over the years will not change the facts of real world implmentation difficulities.

    The truth is that ODF was not designed to meet the real world implmentation requirements of compatibility with existing Microsoft documents (formats) and, interoperability with existing Microsoft Office applications.

    And then there are the problmes of ODF Interoperability with ODF applications.  At the base of this problem is the fact that compliance in ODF is optional.  ODF applications are allowed to routinely destroy metadata information needed (and placed into the markup) by other applications.<b
1 - 5 of 5
Showing 20▼ items per page