1 / 12

PLANETS (PA/4) Microsoft Conversion Tools Overview and Interoperability Aspects

PLANETS (PA/4) Microsoft Conversion Tools Overview and Interoperability Aspects. Natasa Milic-Frayling/Microsoft & Wolfgang Keber/DIaLOGIKa 13 July 2007. Conversion Tools Requirements. Conversion from binary MS Office formats to OpenXML Single document and bulk conversion

iona-norman
Download Presentation

PLANETS (PA/4) Microsoft Conversion Tools Overview and Interoperability Aspects

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PLANETS (PA/4)Microsoft Conversion ToolsOverview and Interoperability Aspects Natasa Milic-Frayling/Microsoft & Wolfgang Keber/DIaLOGIKa 13 July 2007

  2. Conversion Tools Requirements • Conversion from binary MS Office formats to OpenXML • Single document and bulk conversion • Extensibility: Support for other formats (e.g. ODF or WordPerfect) in later phases • Re-usable conversion engine, e.g. in web services • Logging option • Result validation • Catching critical situations, e.g. corrupted documents

  3. OFC as the Conversion Engine • OFC = Office File Converter • OFC is part of the Office Migration Planning Manager (OMPM) • Advantages • Stand-alone tool, i.e. Office applications are not required (only the File Format Compatibility pack) • Reliable (no surprises with pop-ups) • Very fast • Creates “compatibility mode” OpenXML documents, thus, higher fidelity to source documents • However, cumbersome configuration options via INI-file • Consequently, OFC is wrapped into a pluggable and interoperable component

  4. Conversion Tools Architecture (1) • Conversion engine based on OFC • Wrapped into a Transformer Box • Offering a “usable” interface • Input • Output • Parameters • Timeout • Windows/.NET as the platform • However, interoperable, e.g. via web services TB Interface Transformer Box (Wrapper) OFC and File Format Compatibility Pack “Binary  OpenXML”

  5. Conversion Tools Architecture (2) • Plugging in more applications and systems • Interoperability in heterogeneous environments TB Interface ToooXML (GUI) Web Service Transformer Box (Wrapper) “Binary  OpenXML” Watch Folder Tool

  6. Conversion Tools Architecture (3) • Adding more Transformer Boxes (ODF, WordPerfect, …) • Adding File Format Detection component ToooXML (GUI) TB Interface File Format Detection Web Service Transformer Box (Wrapper) Transformer Box (Wrapper) Transformer Box (Wrapper) “ODF  OpenXML” “WP  OpenXML” “Binary  OpenXML” Watch Folder Tool

  7. The Interop Bridge • ASP.NET web service is 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 • Other approaches (e.g. “Cross-WS”) would also be feasible and might be tackled in the future

  8. WFT Architecture • Shared folders bridge the platforms • Single file and bulk conversion • XML ticket file for conversion result (including document’s meta data) Windows Platform Other Platform IN Transformer Box (Wrapper) PLANETS/IFJava Web Service “Binary  OpenXML” TB Inter-face Watch Folder Tool .doc OUT .docx

  9. XML Conversion Report (1) • Contains global or job-related data <convReport xmlns="http://www.planets.org/preservation/openxml/conversion-report/"> <convSummary> <result> <code>0</code> <description>Success</description> </result> <startTime>2007-07-13T13:54:31</startTime> <endTime>2007-07-13T13:54:34</endTime> <fileNum>7</fileNum> </convSummary> The whole conversion took 3 sec. Seven documents were converted

  10. XML Conversion Report (2) • Document-related conversion information for each file (1) <files> <file no="1"> <result> <code>0</code> <description>Success</description> </result> <startTime>2007-07-13T13:54:31</startTime> <endTime>2007-07-13T13:54:31</endTime> <names> <input>BMJ_LW_Verordnung120.doc</input> <output>BMJ_LW_Verordnung120.docx</output> <actual>BMJ_LW_Verordnung120.docx</actual> </names> Conversion of first file took < 1 sec.

  11. XML Conversion Report (3) • Document meta data for each file (2) <fileInfo> <inputSize>105984</inputSize> <outputSize>33329</outputSize> <pages>1</pages> <words>2570</words> <characters>19971</characters> <lines>1109</lines> <paragraphs>433</paragraphs> <charactersWithSpaces>22108</charactersWithSpaces> <creator>flo</creator> <title>Verordnung</title> <subject /> <keywords /> <description /> <lastModifiedBy>Annerose Hümbert</lastModifiedBy> <revision>2</revision> <created>2006-07-07T14:36:00Z</created> <modified>2006-07-07T14:36:00Z</modified> <company>Dialogika</company> </fileInfo> </file> OpenXML zip-package reduces file size

  12. Next Steps • Document validation • Package level • XML level • Comparative QA • OpenXML and XC*L work

More Related