Skip to main content

Home/ Groups/ OpenDocument
Gary Edwards

Once More unto the Breach: Microsoft Discusses Open Standards (versus Open Source Softw... - 0 views

  • So here are some "Key Messages" from Microsoft's standards team circa 2003 (doing battle with the Australian parliament no doubt) [Emphasis added]: An open standard is a publicly available specification which details certain technical functionality that may be implemented in different products and services.  It is adopted in an open, consensus-based process and must satisfy other criteria for transparency, ease of access, and broad implementation as described below. Open standards exist to facilitate interoperability and data exchange across various products and services in a marketplace of multiple, competing implementations, while ensuring that certain minimum requirements are met. Other types of standards (e.g., “proprietary standards”) and market-based mechanisms exist and are currently used to facilitate interoperability.  However, open standards ensure the highest level of interoperability across the widest range of competing products and services.
Gary Edwards

What Cloud Means to Marketing Forecast - Nick Carr The Big Switch - 0 views

  • The gorilla in this nascent market is Google. It has been spending billions of dollars to build huge data centers, or "server farms," around the world, enabling it to run all sorts of consumer software and store enormous quantities of personal data. Combine that processing muscle with the company's dominance of web searching and advertising, and you have a juggernaut capable of redefining the software business on the media model.
Gary Edwards

OOXML vs ODF: where next for interoperability? | Reg Developer - 0 views

  • 'A diversion from the real end game – the taking of the internet' Gary Edwards of the Open Document Foundation has a fascinating post on the important of Microsoft Office compatibility to the success of the ISO-approved Open Document formats. It is in places a rare voice of sanity: People continue to insist that if only Microsoft would implement ODF natively in MSOffice, we could all hop on down the yellow brick road, hand in hand, singing kumbaya to beat the band. Sadly, life doesn’t work that way. Wish it did. Sure, Microsoft could implement ODF - but only with the addition of application specific extensions to the current ODF specification … Sun has already made it clear at the OASIS ODF TC that they are not going to compromise (or degrade) the new and innovative features and implementation model of OpenOffice just to be compatible with the existing 550 million MSOffice desktops.
Gary Edwards

garyedwards's Discussions at ZDNet.co.uk Community - 0 views

  • garyedwards's Discussions Breaking the Web Talkback: Google: OOXML 'insufficient and unnecessary'
Gary Edwards

ODF Editor Says ODF Loses If OOXML Does | Slashdot - 0 views

  • IMHO, the change in Patrick's position is entirely due to the realization that it is impossible to map between OOXML and ODF. I don't know this for sure, but when i read the German Standards Group (DIN) report on harmonization, authorized by the EU-IDABC and provided to ISO, i couldn't help but wonder how Patrick would react. The report definitively ends his OOXML ODF mapping dream.Many wonder why mapping is impossible. I had more than a few discussions with Patrick on this. His point was that a schema is a schema. As long as the syntax and semantics are fully documented, no problemo. My point is that both ODF and OOXML are application specific; and, both are woefully lacking in "semantic" documentation. Add to this problem that both ODF and OOXML lack an interoperability framework with any semblance of compliance teeth, and the whole mapping issue becomes an impossible solution. Especially if interop is the goal.
  •  
    ge comments about Patrick Durusau and his surprising change of position in support of ISO approval of OOXML
Gary Edwards

Some thoughts on OOXML | Larsblog - 0 views

  • What is to be done? ISO has in a sense put itself in an awkward position here by already approving the rival OpenDocument format as an ISO standard. This makes it harder to reject OOXML, and at the same time makes it difficult to approve OOXML, since it competes with an existing ISO standard. Generally, I'm unhappy with how closely these two standards are tied to existing software. What I would really have liked to see was for OpenDocument and OOXML both to be dropped, and the two communities to sit down and work out a common agreed format that is not tied to any existing software. The Chinese UOF format, for example, might have served as the starting point for this. ODA has also been suggested. Unfortunately, this requires a political will that does not seem to be present, and so this seems unlikely for now.
Gary Edwards

The Charter Dilemma | ODF Editor Says ODF Loses If OOXML Does | Slashdot - 0 views

  • OOXML on the other hand presents ISO with a very different situation. Because of the way the OOXML - Ecma charter is worded, i don't see how ISO JTC-1 could ever fix the OOXML interoperability problems. ISO approval of OOXML would include acceptance of a charter that defines and limits OOXML interoperability to whatever MSOffice determines it to be. If Patrick and the JTC-1 tried to bring OOXML into compliance with existing ISO Interoperability Requirements, they would have to somehow amend a charter duly approved.Given that the JTC-1 has yet to address a two year old ISO directive regarding ODF interop compliance, what are the odds they will dare to amend an approved charter? Not good i think.ISO approval of OOXML is a tragedy for all of us. For sure it's the end of ODF. It's perhaps the end of ISO as a respected standards organization. The issue of open standards itself will become a joke, with the reality of standards by corporation having us all wringing our hands in despair.
  •  
    This commentary follows the Stockholm Syndrom post, which is itself in the thread based on Yoon Kit's Open Malaysia comments concerning the dilemma Patrick Durusau is in; the JTC-1 is now filled with Microsoft OOXML supporters!
Gary Edwards

The Stockholm Syndrom at ISO | ODF Editor Says ODF Loses If OOXML Does | Slashdot - 0 views

  • ISO is bound to the business of "interoperability", and has very strict guidelines for interoperability requirements, that are themselves tied to international trade agreements and legal conventions. In this context, it is beyond surprising that ISO allows the "OASIS PAS" and "Ecma Fast Track" channels to remain open, with specification work remaining under the controlling influence of the vendors.IMHO, the change in Patrick's position is entirely due to the realization that it is impossible to map between OOXML and ODF. I don't know this for sure, but when i read the German Standards Group (DIN) report on harmonization, authorized by the EU-IDABC and provided to ISO, i couldn't help but wonder how Patrick would react. The report definitively ends his OOXML ODF mapping dream.
  •  
    Response to Yoon Kit's comments that Patrick Durusau is caught between a rock and hard place. His ISO JTC-1 group is now overwhelmed with MS OOXML supporters!
Gary Edwards

Open Stack: ISO Does The Unthinkable. How ISO approval of MSOffice-OOXML will break th... - 0 views

  • In August of 2007 we dropped ODF as the da Vinci target conversion format, and moved to the W3C's Compound Document Format (CDF) with an ePUB wrapper.The reason for this move is that we could not establish a reasonable degree of interoperability with OpenOffice ODF unless Sun supported the five generic eXtensions to ODF needed to hit the high fidelity conversion the da Vinci process is capable of.Since da Vinci is a clone of the MSOffice OOXML compatibility Kit, we use the same internal conversion process where imbr (in-memory-binary-representation) is converted to another format: imbr <> OOXML or, imbr <> RTF.While it's entirely compliant to eXtend ODF, without Sun's changes to OpenOffice ODF the application-platform-vendor independent interoperability end users expect would be meaningless.The problem as we see it is this; it is impossible to do a high fidelity conversion between two application specific XML formats. It is however quite possible to do a conversion between an application specific format and a generic (application-platform-vendor independent) format.
  •  
    A summary of my views on ISO approval of MSOffice-OOXML and the impact it will have on the futrue of the open web.
  •  
    In response to a recent question posted to a rather old OpenStack blog, i posted this summary of my views on ISO approval of MSOffice-OOXML and the impact it will have on the futrue of the open web.
Gary Edwards

Carl's Whine Rack: OpenDocument Foundation reversal - Flock - 0 views

  • A major proponent of this format, the OpenDocument Foundation, has evidently recently decided to dump ODF in favor of an obscure alternative called the Compound Document Format, developed by the World Wide Web Consortium. So now I really don't know what to think. I wonder if the foundation will change its name.
Gary Edwards

State's move to open document formats still not a mass migration - 0 views

  • June 08, 2007 (Computerworld) -- Only a tiny fraction of the PCs at Massachusetts government agencies are able to use the Open Document Format (ODF) for Office Applications, despite an initial deadline of this month for making sure that all state agencies could handle the file format.
  •  
    Use of ODF remains minimal on government PCs in Massachusetts
    Eric Lai ....... June 8, 2007

    Bummer!  Do you think IBM is silent on this because they are busy cutting sweetheart deals with MS?  Are they going to hang Sun on this?  I'm sure that by next week IBM will have to respond to ODEF.   This just keeps getting better.  So in both Texas and California they wonder if it's even possible to implement ODF solutions.  No one wants to get into that hole with Massachusetts.

    ~ge~


Gary Edwards

Microsoft Will Support ODF! But Only If ISO Doesn't 'Restrict Choice Among Formats' - 0 views

  • By Marbux posted Jun 19, 2007 - 3:16 PM Asellus sez: "I will not say OOXML is easy to implement, but saying ODF is easier to implement just by looking at the ISO specification is a fallacy." I shouldn't respond to trolls, but I will this time. Asellus is simply wrong. Large hunks of Ecma 376 are simply undocumented. And what's more, absolutely no vendor has a featureful app that writes to that format. Not even Microsoft. There's a myth that Ecma 376 is the same as the Office Open XML used by Microsoft. It is not. I've spend a few hundred hours comparing the Ecma 376 specification (the version of OOXML being considered at ISO) to the information about the undocumented APIs used by MS Office 2007 that recently sprung loose in litigation. See http://www.groklaw.net/p...Rpt_Andrew_Schulman.pdf Each of those APIs *should* have corresponding metadata in the formats, but are not in the Ecma 376 specification.
  •  
    Incredible comment by Marbux!  With one swipe he takes out both Ecma 376 and ODF. 

    Microsoft has written a letter claiming that they will support ODF in MSOffice, but only if ISO approves Ecma 376 as a second office suite XML file format standard.  ODF was approved by ISO nearly a year ago.

    Criticizing Ecma 376 is easy.  It was designed to meet the needs of  a proprietary application, MSOffice, and, to meet the needs of the emerging MS Vista Stack of applications that spans desktop to server to device to web platforms.  It's filled with MS platform dependencies that make it impossibly non interoperable with anything not fully compliant with Microsoft owned API's.

    Criticizing ODF however is another matter entirely.  Marbux points to the extremely poor ODF interoperability record.  If MOOXML (not Ecma 376 - since that is a read only file format) is tied to vendor-application specific MSOffice, then ODF is similarly tied to the many vendor versions of OpenOffice/StarOffice.

    The "many vendor" aspect of OpenOffice is somewhat of a scam.  The interoperability that ODF shares across Novell Office, StarOffice, IBM WorkPlace, Red Office, and NeoOffice is entirely based on the fact that these iterations of OpenOffice are based on a single code base controlled 100% by Sun.  Which is exactly the case with MSOffice.  With this important exception - MOOXML (not Ecma 376) is interoperable across the entire Vista Stack!

    The Vista Stack is comprised of Exchange/SharePoint, MS Live, MS Dynamics, MS SQL Server, MS Internet Server, MS Grove, MS Collaboration Server, and MS Active Directory.   Behind these applications sits a an important foundation of shared assets: MOOXML, Smart Documents, XAML and .NET 3.0.  All of which can be worked into third party, Stack dependent applications through the Visual Studio .NET IDE.

    Here are some thoughts i wou
Gary Edwards

Choice - 0 views

  • With ISO/IEC having standardized Open Document Format (ODF) 1.0 and considering standardizing Ecma Office Open XML (Open XML), there is a lot of public discussion about document formats and whether the world should begin to focus on only one format or continue to see multiple formats developed and used over time. Microsoft believes that users should be able to choose among formats and pick the one that best meets their needs. We also believe in encouraging the continued evolution of computing and data formats. And we support the ratification of Open XML in ISO/IEC. There are several reasons for these views:
  •  
    This the infamous Microsoft letter that many have misconstrued as an announcement of support for OpenDocument.  Only in a Microsoft universe can the statement, "We're not going to attack ODF" be taken as Micrsoft support for ODF.
Gary Edwards

InfoWorld Tech Watch | InfoWorld | Messaging standard OK'd for Web services | June 21, ... - 0 views

  • OASIS considers WS-ReliableMessaging critical for SOA, in that it can handle a variety of SOA requirements. WS-ReliableMessaging can be extended to enable integration with capabilities such as security. SOAP binding for interoperability is included. WS-ReliableMessaging is part of a series of Web services specifications dubbed WS-* that have been championed by companies such as Microsoft.
  •  
    Check out the comments below this article.  There are links to Ian Foster of Globus and to the Marbux license disseration posted with the OpenDocument Foundation's NO VOTE at OASIS.
Gary Edwards

Is Open Source Dying? - 0 views

  • But behind the scenes, things are not quite as rosy. The Commonwealth of Massachusetts, which lived up to its left-leaning credentials (didn't Microsoft CEO Steve Ballmer famously upbraid open-source proponents for being Communists?) broke important ground by mandating that state agencies switch to open-source platforms. There's just one problem: They can't seem to manage the transition. Sources close to the situation tell me that former state CIO Peter Quinn's resignation happened at least in part because of delaying tactics by vendors who publicly support open source but do their best to scuttle it behind the scenes.
  •  
    Interesting topic which i've covered more fully with the OpenStack Blog : Connecting the Dots
Gary Edwards

Xandros, Inc. - Xandros to Provide Enhanced Interoperability Between Standardized XML D... - 0 views

  • Xandros, the leading provider of intuitive Linux solutions and cross platform interoperability tools, today announced it will join Microsoft and other companies to build and ship open source translators between documents stored in Ecma Office Open XML and Open Document Formats. The translators, being developed through the Open XML/ODF Translator project, will be made available to Xandros users via the Xandros Networks update facility. Every Xandros product that includes OpenOffice.org will be equipped with the translators. This announcement underscores the shared view of Xandros and Microsoft that competing office productivity applications should make it easy for customers to exchange files with one another and allow them to use their operating system and office productivity applications of choice. "This is good news for customers. Xandros and Microsoft share the view that competing office productivity applications should make it easy for customers to exchange files with one another," said Tom Robertson, general manager for Interoperability and Standards at Microsoft. "Mixed system environments are becoming more common, and we believe in delivering interoperability by design for the benefit of our customers. Our ongoing collaborative relationships with commercial open source companies like Xandros help us achieve that goal." "We are delighted to join forces with Microsoft and others to provide interoperability between standardized XML document formats," said Andreas Typaldos, Xandros CEO. "The work of the world is done using various document formats as well as operating systems, so it is vital to provide our customers with the means interoperate with ease in this diverse environment."
  •  
    You have to read this!  Xandros is taking this interoperability garbage seriously!
Gary Edwards

The Interoperability Wars :: ODF vs. ... - Google Docs & Spreadsheets - 0 views

shared by Gary Edwards on 21 Jun 07 - Cached
  •  
    This discussion is part of a much larger response to a series of questions from a LiNUX magazine in India.  The mighty Marbux helped answer the questions, so please don't mistake his eloquence for my customary thundering.
Gary Edwards

Microsoft Support for ODF - the Q&A - Google Docs & Spreadsheets - 0 views

shared by Gary Edwards on 21 Jun 07 - Cached
  • Hi Gary,I am a technology journalist with Asia's ONLY Linux-focused magazine, LINUX For You. I am working on a story revolving the recent development of Microsoft supporting ODF Format. I want to understand the equation of the whole development, would you please help me understand: Q1. What do you think drove Microsoft to support the ODF format?
  •  
    This is the full response to Swapnil's seven questions.  It's long.  But we hold back nothing!  Thanks again to Marbux.  He is a peach!
Gary Edwards

BetaNews | Microsoft Will Support ODF If It Doesn't 'Restrict Choice Among Formats' - 0 views

  • None of this is to say that OpenDocument is perfect. Far from it. OpenDocument at present is crippled from an interoperability standpoint. I'm a member of the OASIS OpenDocument Technical Committee and I think the resistance of the big vendors to fixing the interoperability warts is simply outrageous, particularly because they are fairly trivial changes. But the advancement of software users' interests are not advanced by painting OOXML as other than deeply flawed. It is vendor-specific and far from "open." The lesser of the two evils is clearly OpenDocument, which is at least open even if not yet interoperable. The sooner folks can start discussing practical methods of convergence, the better. See e.g., http://ec.europa.eu/idabc/servlets/Doc?id=27956 That set of slides summarizing a conference of some 20 European national governments' IT types says a lot more about the future of office document formats than Mr. Asellus has to offer.
    • Gary Edwards
       
      Marbux hits a homerun! Right ON!
Gary Edwards

Is It Game Over? - ODF Advocate Andy UpDegrove is Worried. Very Worried - 0 views

  • This seems to me to be a turning point for the creation of global standards. Microsoft was invited to be part of the original ODF Technical Committee in OASIS, and chose to stand aside. That committee tried to do its best to make the standard work well with Office, but was naturally limited in that endeavor by Microsoft's unwillingness to cooperate. This, of course, made it easier for Microsoft to later claim a need for OOXML to be adopted as a standard, in order to "better serve its customers." The refusal by an incumbent to participate in an open standards process is certainly its right, but it is hardly conduct that should be rewarded by a global standards body charged with watching out for the best interests of all.
  •  
    Andy UpDegrove takes on the issue of Microsoft submitting their proprietary "XML alternative to PDF" proposal to Ecma for consideration as an international standard.  MS XML-PDF will compliment ECMA 376 (OOXML - OfficeOpenXML) which is scheduled for ISO vote in September of 2007.  Just a bit over 60 days from today.

    Andy points out some interesting things; such as the "Charter" similarities between MS XML-PDF and MS OOXML submisssions to Ecma:

    MS XML-PDF Scope: The goal of the Technical Committee is to produce a formal standard for office productivity applications within the Ecma International standards process which is fully compatible with the Office Open XML Formats. The aim is to enable the implementation of the Office Open XML Formats by a wide set of tools and platforms in order to foster interoperability across office productivity applications and with line-of-business systems. The Technical Committee will also be responsible for the ongoing maintenance and evolution of the standard.   Programme of Work: Produce a formal standard for an XML-based electronic paper format and XML-based page description language which is consistent with existing implementations of the format called the XML Paper Specification,…[in each case, emphasis added]

    If that sounds familiar, it should, because it echoes the absolute directive of the original OOXML technical committee charter, wh
« First ‹ Previous 181 - 200 Next › Last »
Showing 20 items per page