Skip to main content

Home/ Document Wars/ Group items tagged garyedwards

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

Microsoft Closer on \'Office Open\' Blessing - 0 views

www.internetnews.com/...3662681

ecma exchange iso microsoft msoffice oasis odf ooxml opendocument openxml sharepoint vista xml

shared by Gary Edwards on 12 Dec 07 - Cached
  • Opponents to OOXML, which include IBM (Quote) and the Open Document Foundation, have argued that Microsoft's specifications are unwieldy and that the standard application is redundant with the Open Document Format (ODF), which already exists. Microsoft has countered that the OOXML format is valuable because it is closer to Office 2007 and is backwards-compatible with older versions of Office. "Although both ODF and Open XML are document formats, they are designed to address different needs in the marketplace," the company wrote in an open letter published earlier this month.
  • Gary Edwards on 12 Dec 07
     
    Internet News is reporting that Ecma has submitted to the ISO/IEC JTC1 their repsonsess to the 20 "fast track" for Ecma 376 (OOXML) objections.  Nothing but blue skies and steady breeze at their back for our friends at Redmond, according to Ecma's rubber stamper in chief, Jan van den Beld.

    Once again there is that ever present drum beat from Microsoft that ODF can't handle MSOffice and legacy MSOffice features - including but not mentioned the conversion to XML of those infamous billions of binary documents:
    "Microsoft has countered that the OOXML format is valuable because it is closer to Office 2007 and is backwards-compatible with older versions of Office. "Although both ODF and Open XML are document formats, they are designed to address diffe
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

digg / garyedwards / news / dugg - 0 views

digg.com/...dugg

ecma eooxml imported:del.icio.us odf openoffice openstack

shared by Gary Edwards on 12 Dec 07 - Cached
  • Gary Edwards on 12 Dec 07
     
    Alist of news stories i'm tagging at DiGG
  • Gary Edwards on 12 Dec 07
     
    Alist of news stories i'm tagging at DiGG
  • Gary Edwards on 12 Dec 07
     
    Alist of news stories i'm tagging at DiGG
Gary Edwards

My Life As An OASIS ODF Lawn Jockey - 0 views

www.mybloglog.com/...garyedwards

iso mooxml oasis odf opendocument openxml

shared by Gary Edwards on 12 Dec 07 - Cached
  • Gary Edwards on 12 Dec 07
     
Gary Edwards

Quible Correction -- garyedwards@...'s comment on "Microsoft: We were railroaded in Mas... - 0 views

talkback.zdnet.com/5208-3513-0.html

ibm massachusetts microsoft odf railroaded sun

shared by Gary Edwards on 12 Dec 07 - Cached
  • Microsoft was invited, and did join the OASIS Open Office XML File Format TC as a founding member with observer status. Although the name of the TC was changed in September of 2004 (at the request of the EU) to "OpenDocument", Microsoft remains a member with observer status. All that need be done to convert their status from observer to voting member is to notify the TC Chairman of your intentions, show up for two consecutive phone conferences, and you are a voting member. It's that simple.
  • Gary Edwards on 12 Dec 07
     
    This is part of a series of talkback responses i had made to a ZDNet article, "Microsoft: We were railroaded in Massachusetts on ODF".  Andy Updegrove participated in this exchange.

    My comment was picked up by the Heise in a FSF Free Software Foundation Europe article, "The Converter Hoax".

    ~ge~

Gary Edwards

Independent study advises IT planners to go OOXML | All about Microsoft | ZDNet.com - 0 views

blogs.zdnet.com/microsoft

burtongorup cdf css garyedwards maryjo odf okelly ooxml w3c xhtml

shared by Gary Edwards on 20 Jan 08 - Cached
  • “ODF represents laudable design and standards work. It’s a clean and useful design, but it’s appropriate mostly for relatively unusual scenarios in which full Microsoft Office file format fidelity isn’t a requirement. Overall, ODF addresses only a subset of what most organizations do with productivity applications today.” The report continues: “ODF is insufficient for complex real-world enterprise requirements, and it is indirectly controlled by Sun Microsystems, despite also being an ISO standard. It’s possible that IBM, Novell, and other vendors may be able to put ODF on a more customer-oriented trajectory in the future and more completely integrate it with the W3C content model, but for now ODF should be seen as more of an anti-Microsoft political statement than an objective technology selection.”
    • Gary Edwards
      Gary Edwards on 20 Jan 08
       
      Mary Jo takes on the recently released Burton Group Report comparing OOXML and ODF. Peter O'Kelly, one of the Burton Group authors, once famously said, "ODF is a great format if you live in an alternative universe where MSOffice doesn't exist!" This observation speaks to the core problem facing ODF and those who seek to implement the ODF standard: ODF was not designed for the conversion of MSOffice documents. Nor was ODF designed to work with MSOffice applications. Another way of saying this is to state that ODF was not designed to be interoperable with MSOffice documents, applications and bound processes. The truth is that ODF was designed for OpenOffice/StarOffice. It is an application specific format. Both OOXML and ODF do a good job of separating content from presentation (style). The problem is that the presentation - layout layers of both ODF and OOXML remains bound to specific applications producing it. While the content layers are entirely portable and can be exchanged without information loss, the presentation layers can not. Microsoft makes no bones about the application specific design and purpose of OOXML. It's stated right in the Ecma 376 charter that OOXML was designed to be compatible with MSOffice and the billions of binary documents in MSOffice specific binary formats. The situation however is much more confusing with ODF. ODF is often promoted as being application, platform and vendor independent. After five years of development though, the OASIS ODF TC has been unable to strip ODF of it's OpenOffice/StarOffice specific aspects. ODF 1.0 - ISO 26300 had three areas that were under specified; meaning these areas were described in syntax only, and lacked the full semantics demanded by interoperable implementations. Only OpenOffice and StarOffice code base applications are able to exchange documents with an acceptable fidelity. The three under specified areas of ODF are: Lists (numbered), F
1 - 6 of 6
Showing 20▼ items per page