Group items tagged

POI 3.5 beta 3, and Office Open XML Support (2008-07-18) now supported by Microsoft through the Document Interoperability Initiative Project (DII) The Apache POI Project is currently working to support the new Office Open XML file formats, such as XLSX and PPTX, which were introduced in Office 2007. The POI project consists of APIs for manipulating various file formats based upon Microsoft's OLE 2 Compound Document format, and Office OpenXML format, using pure Java. In short, you can read and write MS Excel files using Java. In addition, you can read and write MS Word and MS PowerPoint files using Java. POI is your Java Excel solution (for Excel 97-2007). However, we have a complete API for porting other OLE 2 Compound Document formats and welcome others to participate. OLE 2 Compound Document Format based files include most Microsoft Office files such as XLS and DOC as well as MFC serialization API based file formats. Office OpenXML Format based files include the new (2007+) xml based file formats, including Microsoft office files such as XLSX, DOCX and PPTX.

Through the Document Interoperability Initiative (DII) global forums, technology leaders have been working together to promote interoperability between different document format implementations to provide greater value and choice to customers, and the events - including one held in Belgium this week - are yielding practical results. Interoperability solutions announced today translate Open XML documents to a Web page (HTML) allowing readability on Web-friendly browsers such as Firefox, improve translations between different formats through optimized templates, and enable features that provide greater choice for customers and opportunities for independent software developers as they create and use business applications built on Java that manipulate business documents. At the DII events, discussions were also held about developing document test libraries and schema validators, and vendors had the opportunity to test their implementations of document formats in a lab environment to identify potential issues to be addressed.

On Dec 3, Microsoft officially announced the availability of its Open XML Document Viewer, Open XML/ODF Translators Version 2.5 and the Apache POI Java SDKfor OpenXML.

What Bruce doesn't explain in this highlighted clip is that Sun decided to limit the "extra metadata" developer might need to just a handful of elements Sun and IBM needed to use in OpenOffice. The original OpenDocument Foundation metadata proposal was to open up the use of metadata to the extent that metadata could be used for all aspects of presentation (formatting AND layout!).

This vendor specific - application specific limiting ended the last hope we had for ODF interoperability and backwards compatibility with the billions of "in-process" MSOffice documents known to be populating business processes the world over. In fact, the problem ODF adoption faces is primarily that of MSOffice bound business processes, reflected in these billions of workgroup-workflow documents.

Proposal to have a standard packaging for combining application specific XML formats, Open HTML, and PDF. Great comments. This July 2007 article links to a January 2009 article: http://broadcast.oreilly.com/2009/01/packaging-formats-of-famous-ap.html

Short slide deck of Barbara Held's February 28th, 2007 EU IDABC presentation. She introduces ODEF, the "Open Document Exchange Format" which is designed to replace both ODF and OpenOfficeXML. ComputerWorld recently ran a story about the end of ODF, as they covered the failure of six "legislative" initiatives designed to mandate ODF as the official file format. While the political treachery surrounding these initiatives is a story in and of itself, the larger story, the one that has world wide reverberations, wasn't mentioned. The larger ODF story is that ODF vendors are losing the political battles because they are unable to provide government CIO's with real world solutions. Here are three quotes from the California discussion that really say it all: "Interoperability isn't just a feature. It's the basic requirement for getting your XML file format and applications considered"..... "The challenge is that of migrating our existing documents and business processes to XML. The question is which XML? OpenDocument or OpenXML?" ....... "Under those conditions, is it even possible to implement OpenDocument?" ....... Bill Welty, CIO California Air Resource Board wondering if there was a way to support California legislative proposal AB-1668. This is hardly the first time the compatibility-interoperability issue has challenged ODf. Massachusetts spent a full year on a pilot study testing the top tier of ODF solutions: OpenOffice, StarOffice, Novell Office and IBM's WorkPlace (prototype). The results were a disaster for ODF. So much so that the 300 page pilot study report and accompanying comments wiki have never seen the light of day. In response to the disastrous pilot study, Massachusetts issued their now infamous RFi; a "request for information" about whether it's possible or not to write an ODF plugin for MSOffice applications. The OpenDocument Foundation responded to the RFi with our da Vinci plugin. The quick descriptio

Sun claims there are 220 million OpenOffice.org users.