1Expand
EU's Kroes says further technology antitrust abuse cases pending UPDATE - Forbes.com
I wonder if the EU is aware that there is no such thing as ODF Interoperability? After more than five years of working side by side with Sun on the OASIS ODF TC, there is zero interop between KOffice ODF and OpenOffice ODF! How is it that Microsoft's joining the ODF TC somehow results in a level of application interop that has eluded and defied the efforts of two supposedly open source applications?
The truth is that OpenOffice-ODF and MSOffice-OOXMl are both based on an XML encoding of the application specific binary dump. The content layers are easily exchanged with other applications, but presentation continues to defy any kind of interop. Especially what the EU expects. Check out the quotes:
" The commission said that as part of its antitrust investigation into interoperability with Microsoft Office it will investigate whether the announced support of ODF in Office leads to better interoperability and allows consumers to process and exchange their documents with the software product of their choice.
"Kroes said on Tuesday that the commission keeps a close eye on interoperability and said the market should have the right balance of non-propriety and propriety standards.
'Standards are the foundation of interoperability'. 'Standards may, of course, be proprietary or non-proprietary. Much excellent technical development has been driven by non-proprietary standards - the internet is awash with acronyms for non-proprietary standards: HTTP, HTML and XML'.
more fromwww.forbes.com
1Expand
Three myths Microsoft tells Russia | The Open Road - The Business and Politics of Open Source by Matt Asay - CNET Blogs
OSS Innovation and MS IPR :: OSS Interop vs. MS Interop :: OSS Profit vs. MS Profit
more fromwww.cnet.com
1Expand
OOXML: The next step - Interop at the International Standards legal level | Marbux - Weir - Ian [odf-discuss]
Marbux at his best! Here he responds to Rob Weir's ODF v 1.2 arguments with a legal dissertation on International Standards, ISO, the WTO, and the key issue of interoperability and what it must mean. Excellent!
more fromlists.opendocumentfellowship.com
1Expand
OOXML and ODF: The next step | [odf-discuss] Marbux Responds!
Excellent legal argument by the legendary marbux concerning OOXML and ODF itneroperability. Covers ISO Interop Requirements and the demands of International Trade Agreements. Key to this thread is ODF v 1.2 and what must be done to bring ODF into legal compliance with International demands.
more fromlists.opendocumentfellowship.com
1Expand
Matusow's Blog : More Protocol Documentation - Interop Principles Commitment
more fromblogs.msdn.com
3Expand
Google: OOXML 'insufficient and unnecessary' - marbux - ge comments | ZDNet UK
more fromnews.zdnet.co.uk
1Expand
ODF and OOXML are standards in name only - Google: OOXML 'insufficient and unnecessary' - Talkback at ZDNet UK
more fromwww.zdnet.co.uk
1Expand
Wizard of ODF: Interoperability barriers and the List Proposal Vote Deadline on Wednesday
marbux at his best.
more fromwww.oasis-open.org
1Expand
Wizard of ODF: Proposal to amend TC charter, re interoperability with non-conformant ap
The marbux proposal to ammend the ODF charter to include interoperability with MSOffice
more fromwww.oasis-open.org
1Expand
The Case for Harmonization (that IBM will vote against anyway) « A Frantic Opposition
<p>This very funny satire builds on some harsh realities. The ODF chickens have come home to roost, and it isn't pretty. Very funny, yes. But not pretty for those who continue to believe that somehow ODF is a standard worthy of their support.</p>
<p>The flip side of the coin is that using the same critieria of interoperability, OOXML is worthless. The sad truth is that both ODF and OOXML are applicaiton specific formats that will continue to defy and defeat all efforts at interoperability. Inparticular, it's the presentation layers of ODF and OOXML that remain bound to the layout engines and feature sets of their originating applications.</p>
<p>Just as the presentation layers defy interoperability, they will also defeat harmonization. The only way to harmonize two application specific formats is to harmonize the originating applications. And Microsoft, Sun and IBM are not about to do that.</p>
<p>The links in this satire are stunning!!! They shout loudly as to how Microsoft is going to respond to the ECIS anti trust allegations. So when you stop laughing, make certain you track down the links and read through the various OASIS ODF archive threads. IBM and Sun had their chance to fix ODF interoperability. Now it may be too late.</p>
more fromrobweird.wordpress.com
1Expand
The ODF Alliance puckers up and gets smacked with the CSS question - Where is it? | O'Reilly XML Blog
<p>MS-OOXML supporter Rick Jellife discusses the ODF Alliance response to Ecma's proposed disposition of ISO NB comments on OOXML. The Allaince response has recieved quite a bit of ink, wtih waves of ODF jihadists pointing to it as incontroverible evidence that they are right. Rick provides a lengthy response, most of which presents the ODF jihadis with some difficult issues they must now explain.</p>
<p>More importantly though, RJ uncovers one of the more glaring examples proving that ODF is application specific to the core, and bound to OpenOffice. He points out that OpenOffice ODF could have chosen the W3C's highly portable and infinitely interoeprable CSS as the ODF presentation layer. This would have been a great reuse of existing standards. But that's not what happened!</p>
<p>Instead of the widely used CSS, OpenOffice chose an incredibly application specific presentation model with the unique innovation of <i>"automatic-styles"</i>. And with this choice came years of problematic zero interop as application after application try to exchange ODF documents with little success.</p>
<p>Take for example KDE-KOffice. They've been a member of the OASIS ODF TC for near five years now, almost since the beginning. Yet it's impossible to exchange all but the most basic of documents with any of the OpenOffice derivaties (OpenOffice, StarOffice, Novell Office, and Lotus Symphony - OOo 1.1.4).</p>
<p>If after five years of active particpation and cooperative efforts, KOffice is unable to exchange ODF docuemnts with OpenOffice, how is it that somehow Microsoft Office would be able to implement ODF without similar zero interop results? Isn't the purpose of standardized formats that end users of different applications could effectively exchange documents?</p>
<p>The truth is that both ODF and OOXML are application specific formats. And you can't harmonize, merge, map, or translate between two application specific formats without also having harmonized the applications.</p>
<p>Fear not though. It is possibl
more fromwww.oreillynet.com
1Expand
Putting Andy Updegrove to Bed (without his supper) | Universal Interoperability Council
Great article from the Universal Interoperability Council arguing the case for CDF as a universally interoperable format capable of fully representing desktop productivity environment documents. The UIC arguments are of course opposed by IBM and the lawyer for OASIS, Andy Updegrove.
more fromwww.universal-interop-council.org
1Expand
Harmonization and Interop: The dizzying dance of ODF, OOXML, and CDF
<p>Will the real universal document format please stand up! Comments on the recent article posted by the Universal Interoperability Council: <i>"Putting Andy Updegrove to bed without his supper".</i></p>
<p>The UIC article is well worth your time. It is extremely well referenced and researched. The arguments put forth counter claims by IBM and OASIS that the W3C's CDF format can not be used to represent desktop productivity environment documents. Not surprisingly, IBM and OASIS argue that the OpenOffice specific ODF is the only alternative to Microsoft Office specific OOXML.</p>
<p>The UIC argues that the full range of MSOffice legacy binary documents and emerging XML documents can fully be represented in CDF - something that not even the most ardent of ODF jihadists would claim as an ODF capabilitiy. The truth is that ODF was not designed for the conversion of MSOffice binary and xml documents.</p>
more fromdigg.com
1Expand
IT set to 'take their heads out of the sand' and embrace Web 2.0
more fromwww.computerworld.com
4Expand
War rages on over Microsoft's OOXML plans: Insight - Software - ZDNet Australia
more fromwww.zdnet.com.au
2Expand
Rough Type: Nicholas Carr's Blog: Fat Guy in Salesforce hell - Flock
more fromwww.roughtype.com
Notation: * = Private bookmark and comment|… = Clipping [?] | … = Public highlight [?]
