Skip to main content

Home/ Document Wars/ Group items tagged odef

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

Sun Supports OOXML as an ISO Standard? - 0 views

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

iso odef odf ooxml openwave xhtml xml

shared by Gary Edwards on 12 Dec 07 - No Cached
  • Sun Microsystems Inc., largely considered an avowed opponent of Open XML because of its own development and support for the competing, ODF-based StarOffice suite, found itself in the unexpected position of stating its support for ratifying Open XML -- albeit after some changes in the proposal are made.
  • Gary Edwards on 12 Dec 07
     
    Quote: Sun Microsystems Inc., largely considered an avowed opponent of Open XML because of its own development and support for the competing, ODF-based StarOffice suite, found itself in the unexpected position of stating its support for ratifying Open XML -- albeit after some changes in the proposal are made. "We wish to make it completely clear that we support DIS 29500 becoming an ISO Standard and are in complete agreement with its stated purposes of enabling interoperability among different implementations and providing interoperable access to the legacy of Microsoft Office documents," Jon Bosak, a Sun representative to V1, wrote in an e-mail to other committee members over the weekend. "Sun voted No on Approval because it is our expert finding, based on the analysis so far accomplished in V1, that DIS 29500 as presently written is technically incapable of achieving those goals, not because we disagree with the goals or are opposed to an ISO Standard that would enable them." Sun "found itself in the unexpected position of stating its support for ratifying OOXML"?  What???? This is the official position of Sun?

    For the near five years that i have been a member of the OASIS ODF TC, Sun has opposed
Gary Edwards

Real World Government Open Source - Bill Welty and Government OSS Technology - 0 views

www.govtech.com/...101651

iso odef odf ooxml opensource openwave xhtml xml

shared by Gary Edwards on 12 Dec 07 - Cached
  • Welty gave a rapid-fire look at the realities of open source in government. "The doors have been blown open in California," he said. "In 2004 when Governor Schwarzenegger signed the California Performance Review a section called State Operations #10 specifically authorized the use of open source." Operations #10 says: "Departments should take an inventory of software purchases and software renewals in the Fiscal Year 2004-2005 and implement open source alternatives where feasible."
  • Gary Edwards on 12 Dec 07
     
    If there is an Open Source hero in government, it's Bill Welty.  This article pulished in Government Technology covers the GOSCON 2006 conference where Bill spoke to the realities of open source software in government.  Bill will also be speaking at the October 2007 GOSCON Conference in Portland Oregon.  He doesn't pull his punches :)  Even with Microsoft, IBM, Novell, and Sun sitting across the table.
Gary Edwards

Butcher this! -- Microsoft legislatively TKO's open document formats. - 0 views

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

documents government iso odef odf officeopenxml ooxml opendocument

shared by Gary Edwards on 12 Dec 07 - Cached
  • The question we should be asking is why State CIO's and IT divisions are not backing the legislative proposals? It's not the lobbying that is killing ODF. It's the lack of support from those who would have been left with the challenge of implementing ODF solutions. The silence of the CIO's is deafening.
  • Gary Edwards on 12 Dec 07
     
    The title here has nothing to do with the content.  The original title is, "Politics is only a small part of this story". 

    It's been a while since i last posted to the ZDNet TalkBack, and was totally thrown by the TalkBack formating needs.  My first post dropped all line breaks, and came out as one long run on sentence.

    Now maybe that's the way i write, (and think), but at least with some formatting i can hide that fact!

    Still, "Butcher This!" is not a bad title. 

    ~ge~

Gary Edwards

Microsoft Support for ODF - the Q&A - 0 views

docs.google.com/Doc

ecma eu-idabc iso oasis odef odf officeopenxml ooxml opendocument xml

shared by Gary Edwards on 12 Dec 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?
  • Gary Edwards on 12 Dec 07
     
    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

The Interoperability Wars :: ODF vs. OOXML - 0 views

docs.google.com/Doc

ecma eu-idabc iso oasis odef odf officeopenxml ooxml opendocument xml

shared by Gary Edwards on 12 Dec 07 - Cached
  • Gary Edwards on 12 Dec 07
     
    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 Will Support ODF! But Only If It Doesn't 'Restrict Choice Among Formats' - 0 views

www.betanews.com/...1181922127

ecma-376 interoperability iso marbux microsoft odf officeopenxml ooxml opendocument xml

shared by Gary Edwards on 12 Dec 07 - Cached
  • 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.
  • Gary Edwards on 12 Dec 07
     
    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

Linux Foundation Legal : Behind Putting the OpenDocument Foundation to Bed (without its... - 0 views

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

cdf foundation odf ooxml updegrove

shared by Gary Edwards on 12 Dec 07 - 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 12 Dec 07
     
    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
‹ Previous 21 - 27 of 27
Showing 20▼ items per page