PLANETS (PA/4) Microsoft Conversion Tools Overview and Next Steps Wolfgang Keber/DIaLOGIKa 1 October 2007
Recap of the Current Situation (1) Conversion tools have been identified (binary MS Office formats to OpenXML) ◦ OFC = Office File Converter, part of the Office Migration Planning Manager (OMPM) ◦ Stand-alone tool, i.e. Office applications are not required (only the File Format Compatibility pack) and very fast Tools have been wrapped into a “Transformer Box” ◦ Windows/.NET as the platform Transformer Box (Wrapper) OFC and File Format Compatibility Pack “Binary OpenXML” OFC and File Format Compatibility Pack “Binary OpenXML” TB Interface
Recap of the Current Situation (2) ToooXML GUI for testing WS and WFT offering interoperability in heterogeneous environments Watch Folder Tool (WFT) Web Service (WS) ToooXML (GUI) Transformer Box (Wrapper) “Binary OpenXML” TB Interface TB Interface
Other Platform PLANETS/IF Java Web Service WFT (Integrated in IF Review-Demo) Shared folders bridge the platforms Single file and bulk conversion XML ticket file for conversion result (including document’s meta data) Windows Platform Watch Folder Tool Transformer Box (Wrapper) “Binary OpenXML” TB Inter- face TB Inter- face IN OUT.doc.doc.docx
XML Conversion Report Meta data extracted from document flo Verordnung Annerose Hümbert T14:36:00Z Dialogika OpenXML zip-package reduces file size
Next Steps (1): More Formats Adding more Transformer Boxes (ODF, WordPerfect, WinWord 1/2/6…, what else?) Adding File Format Detection component, e.g. for bulk conversion? Transformer Box (Wrapper) “ODF OpenXML” Transformer Box (Wrapper) “WP OpenXML” Watch Folder Tool Web Service ToooXML (GUI) Transformer Box (Wrapper) “Binary OpenXML” TB Interface TB Interface File Format Detection
Next Steps (2): Interop Bridge ASP.NET web service is feasible/available However ◦ PLANETS/IF provides for Java-based web service ◦ Facilitates single sign on and authentication ◦ Supports logging and error reporting Consequently ◦ Watch Folder Tool (WFT) as the bridge between Java web service and the conversion tools for demo ◦ Other approaches (e.g. “Cross-WS”) would also be feasible and should be tackled in the future as well
Next Steps (3): Deployment Windows platform and prerequisites, e.g..Net Conversion tools ◦ How and where should they be described/documented? (discussed yesterday) ◦ How should they be packaged? ◦ Where should they be uploaded?
Next Steps (4): Misc. Document validation ◦ Package level ◦ XML level Comparative QA ◦ Extracting meta information, e.g. number of footnotes or embedded objects Supporting XC*L work Supporting Testbed
We are committed to support PLANETS in providing and integrating office-related transformation tools. However, we need your feedback. Thank you