OpenDocument's feed | Diigo Group

Forget file formats. The battle is Sharepoint | The Open Road - The Business and Politics of Open Source by Matt Asay - CNET Blogs

Thu, 22 May 2008 07:25:07 -0000

Highlights and Sticky Notes:

People are agog that Microsoft has announced support for Open Document Format (ODF), but I'm not sure why. This was a foregone conclusion once Microsoft figured out how to move lock-in above the file level to the content network.

In other words, to Sharepoint.

Microsoft has been hell-bent on getting enterprises to dump content into its proprietary Sharepoint repository, calling it the next Windows operating system. I call it the future of Microsoft lock-in.

Tags: microsoft oasis odf ooxml sharepoint

Posted by: garyedwards

Office 2007 won't support ISO's OOXML - SD Times On The Web

Wed, 21 May 2008 17:02:45 -0000

Highlights and Sticky Notes:

In a surprise move, the company also announced that it intends to participate in the OASIS ODF working group and the corresponding ISO/IEC Joint Technical Committee 1 Subcommittee 34 working groups for ODF, as well as the ISO Technical Committee 171 working group for PDF, said Doug Mahugh, senior product manager for Microsoft Office.

He added that Microsoft would also introduce an API to allow developers to plug their own converters for formats, such as ODF, into Office to make it the default conversion path. ODF 1.1 was chosen over the ISO-standard ODF 1.0 as a practical decision based upon interoperability with existing implementations, Mahugh explained.

The announcement of the new API for others to use for plug-ins is not new news. It was originally made when Microsoft claimed to have gotten religion on interoperability a few months ago. The wookie is that the only conceivable reason for a new API for use by others is that Microsoft does not want to disclose the specs for its existing API. That in turn suggests that the API for use by others will have functionality different from the API used by Microsoft itself, almost certainly far less. posted by marbux

“Customers that are expecting true document fidelity from XML-based, ISO-standard document formats will continue to be disappointed,” said Michael Silver, a Gartner Research vice president. Silver observed that the most compatible formats to use today are Microsoft’s legacy binaries, and he believes that Microsoft will be unlikely to convince customers to move to OOXML in the foreseeable future.

Tags: iso oasis odf ooxml pdf

Posted by: garyedwards

Wizard of ODF: Proposal to amend TC charter, re interoperability with non-conformant ap

Fri, 07 Mar 2008 23:51:09 -0000

Highlights and Sticky Notes:

7. it must provide all feasible functionality required to suppport full fidelity conversions from and to existing office document binary file formats.

Tags: harmonization interop interoperability oasis odf ooxml opendocument

Posted by: garyedwards

Microsoft's OOXML limps through ISO meeting - ZDNet UK

Wed, 05 Mar 2008 07:18:13 -0000

Highlights and Sticky Notes:

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."

Tags: brm ecma geneva iso oasis odf ooxml

Posted by: garyedwards

The Case for Harmonization (that IBM will vote against anyway) « A Frantic Opposition

Sat, 09 Feb 2008 04:30:26 -0000

Highlights and Sticky Notes:

The Case for Harmonization (that IBM will vote against anyway)

In my recent post, I discussed the case for harmonization, mainly due to trying to portray a more kindly, conciliatory face in the “standards krieg” that I was enjoying so much. I have been forced to take a different tack, in light of being hung out to dry by my more business-focused IBM comrades and the work that the enemy has done in sprucing up the spec. However, as my closest friends know, for me, there are no half-victories, so you can rest assured that I will not settle for this weak “harmonization” compromise. I set out my (and IBM’s) stall some time ago on this, and as those on the Open Document Foundation know, any attempt at harmonization shall be met with swift and final retribution. They were ejected from the odf-coven just days after their impudence. I have baited my trap, inviting this “harmonization” in my lair (the OASIS ODF TC) where I can bog them down in a morass of incompetence, bickering and politicking, so no new standard is ever ratified. I have already been practicing for this, as you can see, by the ODF 1.1 and 1.2 specs.

Tags: foundation harmonization interop oasis odf ooxml opendocument openxml

Posted by: garyedwards

Word of recognition from an unexpected side: ODF editor Patrick Durusau supports OOXML - ISO effort

Thu, 07 Feb 2008 19:04:16 -0000

Highlights and Sticky Notes:

The OpenXML project has made a large amount of progress in terms of the openness of its evelopment. Objections that do not recognize that are focusing on what they want to see and not what is actually happening with OpenXML

Tags: brm durusau iso oasis odf officeopenxml ooxml opendocument openxml

Posted by: garyedwards

Putting Andy Updegrove to Bed (without his supper) | Universal Interoperability Council

Wed, 06 Feb 2008 03:53:47 -0000

Highlights and Sticky Notes:

In late 2007, an article by OASIS attorney Andy Updegrove claimed that W3C Compound Document Formats: [i] are non-editable formats; [ii] are not designed for conversions to other formats; and [iii] are therefore unsuitable as office formats. Updegrove could not have been more wrong.

But unfortunately, the erroneous Updegrove article was widely publicized by the usual occupants of the IBM cheering section⁽¹⁾ in the stadium where the latest big vendor game for the Incompatible File Format Cup is being played, IFFC Games Stadium.

Tags: cdf ibm interop oasis odf ooxml opendocument openxml

Posted by: garyedwards

Harmonization and Interop: The dizzying dance of ODF, OOXML, and CDF

Wed, 06 Feb 2008 03:49:40 -0000

Highlights and Sticky Notes:

With the ISO BRM fast approaching, the harmonization of ODF and OOXML is all the rage. The legendary marbux takes on this discussion arguing that ODF and OOXML both lack the interoperability framework needed to meet ISO directives describing interop requirements. He argues that interop between MSOffice and OpenOffice can be achieved using CDF.

Tags: cdf ibm interop oasis odf ooxml opendocument openxml uic w3c

Posted by: garyedwards

Wizard of ODF: OASIS invited to join Microsoft in the DIN technical report - harmonization effort. Will they take the bait?

Tue, 29 Jan 2008 08:33:14 -0000

Highlights and Sticky Notes:

the WG is busy working on a first draft. This'll include mainly work in Wordprocessing. Spreadsheet and Presentation is still in the very early work. So help from the ODF TC would be great --- and a liaison would make sense IMHO. To give you an idea why help from the Ã“DF TC would be needed I'll briefly outline some questions which arose: * Need for more use-cases, i.e. feasable interop scenarios * Discussions of unspecified behaviour (e.g numbering in 1.0, spreadsheet formulas, compatibilty options, etc.) and their impact on interop scenarios * Questions regaring generic settings like e.eg. form:control-implementation="ooo:com.sun.star.form.component.Form", or tweaking a la http://www.openoffice.org/issues/show_bug.cgi?id=51726. * Possible interop problems not handled by the specs (e.g. graphics, WMF, EMF, SVM, etc.) or e.g. font metrics and font embedding. As you see there are a lot of overlapping areas with eg. the "ODF interop" we dealt with in the workshop in Barcelona. [This issue is hosted in the Adoption TC, right? Maybe this TC is also suited as a liaison partner?]

Uh Oh. Microsoft and Novell joined the EU's call to harmonize ODF and OOXML, but Sun and IBM refused the invite. Now we have the invite in front of the OASIS ODF TC!. Is there any rock big enough for them to hide under if they also refuse?

And if the OASIS ODF does join the EU-DIN-ISO effort, where doe stha tleave IBM, Sun and their inistance on a politically mandated "rip out and replace" as the only acceptable solution?
posted by garyedwards

Tags: din eu harmonization iso oasis odf ooxml xml

Posted by: garyedwards

office by thread

Fri, 25 Jan 2008 09:01:28 -0000

Highlights and Sticky Notes:

[Fwd: clarification: OpenDocument and SVG]
From Lars Oppermann <Lars.Oppermann@Sun.COM> on 2 Feb 2005 10:31:44 -0000
- Re: [office] [Fwd: clarification: OpenDocument and SVG]
  From Michael Brauer <Michael.Brauer@Sun.COM> on 2 Feb 2005 12:16:44 -0000
  - Message not available.
    - Message not available.
    - Message not available.
    - Re: [office] [Fwd: clarification: OpenDocument and SVG]
      From Michael Brauer <Michael.Brauer@Sun.COM> on 3 Feb 2005 10:14:18 -0000
    - Message not available.
    - Re: [office] [Fwd: clarification: OpenDocument and SVG]
      From Michael Brauer <Michael.Brauer@Sun.COM> on 3 Feb 2005 14:01:24 -0000
Propsal regarding the use of the SVG namespace in OpenDocument
From Michael Brauer <Michael.Brauer@Sun.COM> on 3 Feb 2005 13:49:10 -0000
- Use of SVG namespace
  From Patrick Durusau <Patrick.Durusau@sbl-site.org> on 7 Feb 2005 13:34:56 -0000

Tags: archives oasis odf openoffice

Posted by: garyedwards

[office-comment] ODF Public Comment - Where's the Interop Guys? What the hell happened here?

Fri, 25 Jan 2008 09:01:28 -0000

Highlights and Sticky Notes:

Regarding section 1.5 itself: The Open Office TC decided to use the term MAY rather than MUST (or will) at the mentioned location, because it wanted to ensure that the OpenDocument specification can be used by as many implementations as possible. This means that the format should also be usable by applications that only support a very small subset of the specification, as long as the information that these applications store can be represented using the OpenDocument format. A requirement that all foreign elements and attributes must be preserved actually would mean that some applications may not use the format, although the format itself would be suitable. Therefor, we leave it up to the implementations, which elements and attributes of the specification they support, and whether they preserve foreign element and attributes. Some more information about this can be found in appendix D of the specification.

Tags: oasis odf opendocument ouch

Posted by: garyedwards

Podcast: ODF, OOXML and CDF .... The OpenDocument Foundation Responds | Between the Lines | ZDNet.com

Mon, 21 Jan 2008 19:13:19 -0000

Comments:

Dragged through the mud posted by garyedwards

Highlights and Sticky Notes:

David continues his deep dive into the curious case of the OpenDocument Format and the OpenDocument Foundation.

Tags: cdf foundation ibm iso oasis odf ooxml opendocument openoffice sun symphony

Posted by: garyedwards

Whoops?! IBM products support Microsoft's Open XML doc format! Lotushpere

Sun, 20 Jan 2008 23:52:45 -0000

Highlights and Sticky Notes:

Nobody has invested more to defeat Microsoft Corp.'s Open XML document format than IBM Corp.

So why is IBM supporting Open XML in a handful of its products?

According to technical documentation on IBM's own Web sites, Big Blue already supports Open XML, the native file format of Microsoft Office 2007, in at least four of its software.

However, Microsoft Office users interested in testing or switching to Lotus Symphony, IBM's upcoming challenger to Office, may be disheartened by signs that IBM won't budge from its stance that it will only support documents created in Office 2003 and prior versions.

Tags: cdf ibm iso oasis odf ooxml opendocument openoffice sun symphony

Posted by: garyedwards

Look what Google can do now: OOXML!

Sun, 20 Jan 2008 23:52:43 -0000

Highlights and Sticky Notes:

Instead of dialing 411 on your phone and paying the service fee, dial 800-GOOG-411

Send the name of the business and the city or the ZIP code to GOOGLE. (Type GOOGLE into the address or number field, like you would if you were using a phone number.) Google will text you back with the address and phone number.

Tags: cdf google ibm iso oasis odf ooxml opendocument openoffice sun symphony

Posted by: garyedwards

5 Things Microsoft Must Do To Reclaim Its Mojo In 2008 -- InformationWeek

Fri, 11 Jan 2008 18:38:30 -0000

Highlights and Sticky Notes:

Instead of fighting standards, Microsoft (NSDQ: MSFT) needs to get on board now more than ever. With open, Web-based office software backed by the likes of IBM (NYSE: IBM) (think Lotus Symphony) and Google (NSDQ: GOOG) now a viable option, users—especially businesses frustrated by Microsoft's format follies (many are discovering that OOXML is not even fully backwards-compatible with previous versions of Microsoft Word)--can now easily switch to an online product without having to rip and replace their entire desktop infrastructure.

This article discusses how Microsoft might change their ways and save the company. This particular quote concerns Microsoft support for standards, and their fight to push MS OOXML through ISO as an alternative to ISO approved ODF 1.0.

The thing is, ODF was not designed for the conversion of MSOffice documents, of which there are billions. Nor was ODF designed to be implemented by MSOffice. ODF was designed exactly for OpenOffice, which has a differnet model for impementing basic docuemnt structures than MSOffice.

So a couple of points regardign this highlight:

The first is that IBM's Lotus Symphony is NOT Open Source. IBM ripped off the OpenOffice 1.1.4 code base back when it was dual licensed under both SSSL and LGPL. IBM then closed the source code adding a wealth of proprietary eXtensions (think XForms and Lotus Notes connections). Then IBM released the proprietary Symphony as a free alternative to the original Open Source Community "OpenOffice.org".

If Microsoft had similarly ripped off an open source community, there would be hell to pay.

Another point here is the mistaken assumption that users can easily switch from MSOffice to an on-line product like Google Docs or ZOHO "without having to rip our and replace their entire desktop infrastructure."

This is a ridiculous assumption defied by the facts on the ground. Massqchusetts spent two years trying to migrate to ODF and couldn't do it. Every other pilot study known has experienced the same difficulties!

The thing about Web 2.0 alternatives is that these services can not be integrated into existing business processes and MSOffice workgroup bound activities. The collaborative advantages of Web 2.0 alternatives are disruptive and outside existing workflows, greatly marginalizing their usefulness. IF, and that's a big IF, MSOffice plug-ins were successful in the high fidelity round trip conversion of workflow documents, there could in fact be seamless integration of Web 2.0 services into existing business processes. But that's not the case. As Massachusetts discovered.

posted by garyedwards

Microsoft in 2008 could make a bold statement in support of standards by admitting that its attempt to force OOXML on the industry was a mistake and that it will work to develop cross-platform compatibility between that format and the Open Document Format

It's impossible to harmonize two application specific file formats. The only way to establish an effective compatibility between ODF and OOXML would be to establish a compatibility between OpenOffice and MSOffice.

The problem is that neither ODF or OOXML were developed as generirc file formats. They are both application specific, directly reflecting the particular implementation models of OOo and MSOffice.

Sun and the OASIS ODF TC are not about to compromise OpenOffice feature sets and implmentation methods to improve interop with MSOffice. Sun in particular will protect the innovative features of OpenOffice that are reflected in ODF and stubbornly incompatible with MSOffice and the billions of binary documents. This fact can easily be proven be any review of the infamous "List Enhancement Proposal" that dominated discussions at the OASIS ODF TC from November of 2006 through May of 2007.

So if Sun and the OASIS ODF TC refuse to make any efforts towards compatibility and imporved interop with MSOffice and the billions of binary docuemnts seekign conversion to ODF, then it falls to Microsoft to alter MSOffice. With 550 million MSOffice desktops involved in workgroup bound business processes, any changes would be costly and disruptive. (Much to the glee of Sun and IBM).

IBM in particular has committed a good amount of resources and money lobbying for government mandates establishing ODF as the accepted format. this would of course result in a massively disruptive and costly rip out and replace of MSOffice.

Such are the politics of ODF.

posted by garyedwards

Tags: cdf ibm iso oasis odf ooxml opendocument openoffice sun symphony

Posted by: garyedwards

Can IBM save OpenOffice.org from itself?

Fri, 11 Jan 2008 18:38:30 -0000

Comments:

This quote from Chalres Schultz is ridiculous. Because Novell is not allowed to commit code to OpenOffice, they must maintain a separate code base of extensions and improvements. With each build of OpenOffice, Novell must reintegrate their changes into the code base, making for a managerial nightmare.

When Novell does have improvements that Sun wants though, there is no end to the hoops of fire the Sun developers will jump through to get it. The Field Enhancement routine written by Novell's Florian Router is one of those improvements that Sun had to have. Sun even went so far as to arguing for changes in the way ODF implements fields to accomodate the Novell improvements!

It's important to note however that Sun did not support the ODF Field Enhancements UNTIL Novell agreed to donate Florian's code to OpenOffice!!!!!! Proving conclusively what i have been arguing for years: Sun does not allow for any changes to ODF unless and until those changes can be implemented by OpenOffice.

The ODF Field Enhancements needed by Florian's fix to OpenOffice were originally proposed on July 12th, 2006, when Florian was the CTO of the OpenDocument Foundation. These changes to the way ODF implements fields were needed by the da Vinci plug-in as part of our efforts to save ODF in Massachusetts.

so here we have a rather direct example of Sun refusing improvements to ODF when needed by another application (da Vinci), but supporting those exact same changes when it is OpenOffice that can be improved!!!

The arguments that the OpenOffice.org Community isn't open also apply to the OASIS ODF TC work!!!!!!
posted by garyedwards
Good catch by Eric!

This link is to the infamous Sun statement of support for MS OOXML issued by Jon Bosak when ISO DIS 2900 was voted on by the US delegation to ISO.

The statement is important because it directly references the core issue: MS OOXML was written for MSOffice and the billions of binary docuemnts bound to that application suite. ODF on the other hand was written to OpenOffice.

Because ODF was not designed for the conversion of those billions of MSOffice documents, conversion is next to impossible. The implementation of ODF in MSOffice is next to impossible. The loss of information, especially the presentation-layout information, is so severe as to be intolerable in the real world.

This leaves the real world, where MSOffice dominates over 550 million desktops, unable to implement ODF. In light of this real world problem, Sun's Bosak urges support for MS OOXML as an ISO standard!!!

So we have this situation at OASIS ODF where Sun is in control of both ODF and OpenOffice, refusing in all cases to compromise the linkage or accomodate the much needed interoperability enhancemnts seeking to improve the conversion of billions of documents to ODF. And publicly supporting MS OOXML as the only pragmatic alternative to the situation Sun is responsible for!

posted by garyedwards

Tags: cdf ibm iso oasis odf ooxml opendocument openoffice sun symphony

Posted by: garyedwards

Can IBM save OpenOffice.org from itself?

Fri, 11 Jan 2008 18:38:30 -0000

Comments:

Heintzman must be referring to the Rob Weir -OASIS ODF Adoption (cough marketing-lobbying) TC event called the "ODF Interoperability Workshop".
This was a day long event demonstrating for all the world to see that there is no such thing as ODF interoperability. The exchange of documents between OpenOffice 2.0, KOffice and Lotus Symphony is pathetic.

The results of the day long event were so discouraging that Rob Weir took to threatening developers who attended in his efforts to keep a lid on it. I think this is called damage control :). From what i hear, it was a very long day for Rob. but that's no excuse for his threatening anyone who might publicly talk about these horrific interop problems. The public expects these problems to be fixed. But how can they be fixed if the issues can't be discussed publicly?
posted by garyedwards
Lotus Symphony is based on the OpenOffice 1.1.4 code base that IBM ripped off back when OpenOffice was under dual license - SSSL and LGPL.
posted by garyedwards

Highlights and Sticky Notes:

In e-mailed comments, Heintzman said his criticisms about the situation have been made openly.

"We think that Open Office has quite a bit of potential and would love to see it move to the independent foundation that was promised in the press release back when Sun originally announced OpenOffice," he said. "We think that there are plenty of existing models of communities, [such as] Apache and Eclipse, that we can look to as models of open governance, copyright aggregation and licensing regimes that would make the code much more relevant to a much larger set of potential contributors and implementers of the technology....

"Obviously, by joining we do believe that the organization is important and has potential," he wrote. "I think that new voices at the table, including IBM's, will help the organization become more efficient and relevant to a greater audience.... Our primary reason for joining was to contribute to the community and leverage the work that the community produces.... I think it is true there are many areas worthy of improvement and I sincerely hope we can work on those.... I hope the story coming out of Barcelona isn't a dysfunctional community story, but rather a [story about a] potentially significant and meaningful community with considerable potential that has lots of room for improvement...."

What Heintzman is refering to here is the incredibly disastrous "ODF Interoperability WorkShop" held at the OpenOffice Confernece in Barcelona, Spain.

The Interop WorkShop was organized by IBM's Rob Weir. Incredilby he still has his job. RW put on display for all to see that special brand of ZERO interop unique to ODF. What's really surprising is that in the aftermath of this tragic display of interop illiteracy, RW initiated a new interoperabilitysub committee at the OASIS ODF Adoption TC!

Interop is a technical problem, as was embarassingly demonstrated in Barcelona. Yet here they are setting up the interop solution at a marketing group! Which is a strong indication that rather than taking on the politically difficutl and vendor adverse task of binding an interoperability framework to the ODF specification, they've decided to shout down anyone who might point out that the emperor indeed has no clothes.

What a sad day for ODF.
posted by garyedwards

Tags: cdf ibm iso oasis odf ooxml opendocument openoffice sun symphony

Posted by: garyedwards

Standardization by Corporation | Can big application vendors be stopped from corrupting open standards and open source?

Tue, 11 Dec 2007 23:17:07 -0000

Comments:

Will ISO follow either the AFNOR or Brittish proposals to merge ODF and OOXML? I think so. If they continue on their current path of big vendor sponsored document wars, ISO will beocme irrelevant. Sooner or later the ISO National Bodies must take back the standards process from corporate corruption and influence.

One thing is clear. Neither Microsoft or IBM is about to compromise. IBM has had many chances to improve ODF's interoperability with Microsoft Office and the Office documents, but has been steadfast in their stubborn refusal to concede an inch.

Microsoft hides behind their legacy installed base of over 550 million MSOffice desktops. There simply isn't a pragmatic or cost effective way of transitioning the installed base to ODF without either seriously re writing and replacing those applications, or, changing ODF to be compatible.

The marketplace is clear on what they intend on doing. Pragmatism will rule. Productivity trumps standards initiatives whenever they are out of sink.

In the face of this clear marketplace intent, one would think IBM might compromise on ODF. No way! They are intent on using ODF to force a market wide rip out and replace of MSOffice.

Most people assume that there are two opposing groups at war here; the Microsoft OOXML group vs. the IBM ODF group. This isn't an accurate view at all. There is a third, middle group of developers working the treacherous space of conversion - the no man'sland between OOXML MSOffice and ODF OpenOffice.

The conversion group know the problems involved, and are actually trying to dliver marketplace facing solutions. The vendors of course are in this war to the bitter end, and could care less about the damage they cause to end users.

It's also true that the conversion group seeks to bridge desktop productivity into the larger, highly interoeprable web platform.

It's also possible that ISO will chose to merge ODF and OOXML, as proposed by the French AFNOR plan as well as by the British. To do this they must first remove entirely the coproarate vendor influence of Ecma and OASIS, and perfect the merger entirely at ISO. The big vendors will of course fully oppose this approach.

My post just happened to coincide with ISO Governor Mark Bryan's "Standardization by Corporations" letter where he expresses a derpressing but nevertheless very true concern.

In fact, the OpenDocument Foundation was created specifically to address our concerns about the undue influence big application vendors were exerting on ODF following the April 30th, 2005 approval of ODF 1.0 (which went on to become ISO 26300).

~ge~
posted by garyedwards

Highlights and Sticky Notes:

Standardization by Corporation

Maybe i spoke to soon. This just came in from ISO, the resignation letter of the SC34WG1 Chairman who has completed his three year term.

There is a fascinating statement at the end of the Martin Bryan letter. "The disparity of rules for PAS, Fast-Track and ISO committee generated standards is fast making ISO a laughing stock in IT circles. The days of open standards development are fast disappearing. Instead we are getting “standardization by corporation”, something I have been fighting against for the 20 years I have served on ISO committees. I am glad to be retiring before the situation becomes impossible..."

When corporations join open standards or open source efforts, they arrive with substantial but most welcome financial and expert resources. They also bring marketshare and presence. And, they bring business objectives. They have a plan.

As long as the corporate plan is aligned with the open standards - open source community work, all is fine. In fact it's great. For sure though there will come a time when the corporate plan asserts it's direction, and there is possible conflict. At this point, the very same wealth of resources that were cause for celebration can become cause for disappointment and disaster.

One of the more troubling things i've noticed is that corporations treat everything as a corporate asset to be traded, bartered and dealt for shareholder advantage and value. This includes patents and interoperability issues which not surprisingly are wrapped into open standards and open source efforts. Rather than embrace the humanitarian – community of shared interest drivers of open standards and open source, corporations naturally plot to get maximum value out of the resources they commit.

A primary example of this is Sun's use of OpenOffice, ODF, and an anti trust settlement disaster that left them at the mercy of Microsoft.

Tags: bryan cdf ecma ibm iso mary-jo microsoft oasis odf ooxml opendocument sun w3c zdnet

Posted by: garyedwards

Sun-Bosak "Yes" Vote on ISO approval of MS OOXML

Sat, 03 Nov 2007 23:15:32 -0000

Highlights and Sticky Notes:

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.

Read it and weep! Sun agrees that ODF was not designed for and is unable to meet these important market requirements posted by garyedwards

Tags: bosak ecma iso microsoft oasis odf officeopenxml ooxml opendocument openxml

Posted by: garyedwards

Former OpenDocument advocates bolt for W3C standard | Martin Lamonica

Mon, 29 Oct 2007 18:41:09 -0000

Comments:

Great comments!
posted by garyedwards

Highlights and Sticky Notes:

Adding a twist to a high-stakes conflict over document formats, some advocates for OpenDocument, or ODF, are abandoning the standard in favor of the World Wide Web Consortium's Compound Document Formats standard.

The reason? Technical limitations in sharing ODF files with Microsoft Office applications.

Tags: cdf iso ms-ooxml oasis odf opendocument openofficexml

Posted by: garyedwards