Group Bookmarks tagged
You are here: Diigo Home > Groups > OpenDocument > Bookmarks > Group Bookmarks tagged odf,ooxml
Rick "Van Winkle" Jellife discovers the fatal interop flaw in the ODF "foriegn elements" implementation - The infamous compliance clause "Section 1.5". One question, where was Rick back in 2006 when the Massachusetts ODF pilot was on the rocks, and the OpenDocuemnt Foundation was claiming that there was no possible way to roundtrip documents between a da Vinci MSOffice ODF and OpenOffice ODF?
more from news.oreilly.com
The myths that ODF is an open standard, that Lotus Symphony is open source, and that Microsoft is the only company that manipulates "open" standards for unlawful competitive advantage continue to propagate.
more from www.technewsworld.com
Stephane is right on target. This is a must read for anyone trying to understand ISO approval of OOXML, and the sudden change of mind at Microsoft to support ODF!
more from ooxmlisdefectivebydesign.blogspot.com
Stephane Rodriquez sums it up: Microsoft has won ... "Future of OOXML? There are two answers. Frankly, who freaking cares the paper? This paper will ALWAYS be at odds with the actual Office implementation. We have a good example for the time being, but it has always been the case. What about the actual file format then? It will be the subject of reverse engineering from implementers whose only recourse is to catch up all the undocumented stuff. Make no mistake though, now it's about applications, not documents anymore." "Conclusion : if you are still in the OOXML conspiracy game, about time to move on guys. "
more from ooxmlisdefectivebydesign.blogspot.com
This is nonsense. Whether an organizations standardizes on ODF or OOXML, the "interoperability" they seek will still be based on every desktop running the same application. Neither format enables the interchange of documents between different applications - even if those applications properly implement the format standard. Anyone can prove this for themselves. Simply shuttle a few OpenOffice ODF documents between Symphony, Novell Office and Google Docs. Then weep. At least with MSOffice-OOXMLyou can exchange documents between different versions of MSOffice. Even though OpenOffice, Symphony and Novell Office are based on the same code base, interop might as well be zero. Besides; what end users really want from a modern desktop office suite is collaborative editing of web ready documents. This discussion is so last century - 1995!
more from ec.europa.eu
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 from www.forbes.com
Response from the OpenDocument Foundation setting the record straight. See "copmments" with this bookmark
more from linux-foundation.org
"FDIS" stands for "final draft international standard," which puts this standard at the final voting stage. I suspect that this document will be frequently cited in the efforts to harmonize ODF and OOXML at the presentation layer. Unfortunately, it looks like you have to be a member of a national standardization body to come up with a copy.
more from www.nssn.org
In light of the Microsoft announcement of ODF support, a prescient July, 2007 blog article by Rick Jelliffe deserves revisiting. Jelliffe surveyed the pressure points for various players that he saw in the File Format War and made a set of suggestions that bear a remarkable resemblance to subsequent events. The goal he recommended for eGovernment and open standards advocates was to push to get ODF and OOXML out of the hands of Ecma and OASIS and into the hands of ISO for harmonization work, arguing that it is the most vendor-neutral eligible forum for such work.
more from www.oreillynet.com
Microsoft to support PDF, ODF 1.1 and ISO OOXML in MSOffice 14. The company will also join the OASIS ODF TC and working group for ISO PDF.
more from www.sdtimes.com
Alex identifies the difficulties between ISO member nations and the officials at the ISO JTCS-34 responsible for MSOffice-OOXML and OpenOffice-ODF. The member nations really want MSOffice XML formats locked down at ISO. But they are short on both ideas and the authorization needed to make this work. Alex concludes that maybe it's time to start all over; from scratch. The Foundation developers working on the da Vinci plug-in for MSOffice concluded that it was far easier to target existing (X)HTML-CSS using the ePUB wrapper to get that higher level of interop everyone seeks. Waiting for ISO to sort things out is not a solution. But iunderstand Alex's position. Harmonizing ODF and OOXML is probably not possible. Leastways not without some major compromises at the applicaiton level by both OpenOffice and MSOffice. It would be far easier to demand that both OpenOffice and MSOffice support and implement the ePUB (X)HTML-CSS web ready format. The simple truth is that both OpenOffice-ODF and MSOffice-OOXML are application specfic XML formats suffering the same darkness: there is no standardization or sufficient documentation of the "presentation" - layout model. It is here that the highly portable CSS model is lightyears ahead of both.
more from www.adjb.net
Strange demands from Andy Updegrove: "I call on Ecma to withdraw OOXML from ISO and keep control of it themselves. We need it for legacy documents...." Why would anyone want Ecma to take back control of MSOffice-OOXML from ISO? The best circumstance would be for OASIS to turn OpenOffice-ODF over to the same ISO JTC-S1, where they can finally begin the difficult (if not impossible) harmonization process. Let me add on other thing; the place for ISO to begin harmonization is "presentation". We desperately need a standardized presentation model useful to MSOffice-OOXML, OpenOffice-ODF, XHTML and HTML. I suggest they start with CSS 3, and work back into ODF - OOXML. But that's just me :)
more from www.consortiuminfo.org
Rob Weir gets royally spanked. And so does the notion that ODF is somehow "interoperable". Big Time.
more from www.griffinbrown.co.uk
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.
more from openstack.blogspot.com
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 from lists.opendocumentfellowship.com
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 from lists.opendocumentfellowship.com
Gary Edwards (343)
marbux (24)
Jesper Lund Stocholm (9)
mazyar hedayat (4)