ODF for Interoperability of Public Document in Indonesia

Total Page:16

File Type:pdf, Size:1020Kb

ODF for Interoperability of Public Document in Indonesia ODF for Interoperability of Public Document in Indonesia 1I Made Wiryana, 2Arrummaisha Adrifina, 3Juwita Utami Putri, 4Harya Iswara A.W 1,2,3,4Gunadarma University 1,2,3,4{mwiryana, arrum, jutami, harya}@staff.gunadarma.ac.id Abstract Open standards are widely considered to have a lot of benefits. This has led many governments to consider implementing open standards for document formats, such as the OpenDocument Format (ODF). This paper will discuss aspects of the importance of proper document format for a document that must be long lasting and can be used by different organizations in the government. ODF is a document format that meet the criteria for office applications document storage. By moving to open standards, governments will see that they would benefit from choice, competition, and the ability to substitute different vendor implementations. Keywords: government, Indonesia, interoperability, ODF, open standards 1 Introduction • Old documents can not be read because the vendor change its format in the new version Today, information and communication technology of the program. Thus the selection of the (ICT) architectures need to be flexible. They must document should also consider the age of the be modular, plug-able and easy to set up, fast to document for document preservation needs. integrate and fast to take down and re-purpose for governments and businesses alike to meet the de- • Government agencies can not communicate mands of their citizens and customers. The archi- because it uses a different version/product of tectures need to be built around agreed standard word processor or using a format specified by protocols and information needs to flow seamlessly the vendor. So it takes a standard document across different applications and platforms. which can be used again by another govern- A document format is a particular way that in- ment agency without being tied to one partic- formation is encoded for storage in a computer file. ular product type. Document format can not be considered as sim- Public availability of documentation for early file ple or just follow what is usually used by people. formats varied. Some application vendors made Especially for documents belonging to government their formats available on demand or published agencies that must be used by the public. Several them in book form. Others released them un- technical aspects must be considered, such as: der restrictive licenses that limited use by competi- • Open life-cycle tors. Through the years of 1980s and 1990s, office documents were primarily exchanged as printed • Open availability copies. Where exchanges occurred electronically, • Multiple implementation they were most often between known parties, such as workers in the same office, using the same soft- • Interoperability across different systems ware. Electronic document exchanges was straight- • Following a good document storage standard. forward because the authors assumed that people whom they correspondence with are using the same Besides, there are several considerations on non- version of software running in the same version of technical aspects: operating system. Interoperability among different • Avoiding government agencies to "force" the software was difficult and trivial [5]. public to buy certain word processing pro- The difference between old style format and grams that can interact electronically. Be- new style format is shown in figure 1. In old style cause basically a document granted by a format, information is closely linked to the applica- government agency to the public should be tion. Only the developers of these applications can opened without any provision to use a certain understand the structure of the document. But the type of software. new trend has been started. One of the concepts developed is the concept of document formats with From figure 2 we can see that if someone want open standards (open document format). Informa- a reusable file, so the file model should be closed to tion is represented using a real open standard not SGML (Standardized General Mark-up Language). under the control of a single vendor, and multiple Figure 2 also explain why document in LaTex for- applications can create and access it interchange- mat is reusable if we compare it with wordproces- ably. So that the document does not depend on an sor in 1990’s. application, documents can be opened and edited When the organization have to determine which using a variety of applications. file is used as a standard in all parts, they have to make a standardization of file types. Talk about a standard format, generally people do not refer to the same thing. There are two types of standard formats that are known in public[Mwiryana, 2010], they are: . Old style New Style • De facto Standard. This standard is some- thing popular or used by many people in com- Figure 1: Old and new style of documents[4] munity. It is considered as a standard because it is known by many people, but not a stan- Open Document Format (ODF) as one of the dard from any institution and also untested. format of office application, supports information There is no guarantee from the application retrieval and exchange of documents without re- vendor to not to stop the support in future lating to the application or platform used when version since there is no standard from any creating the document, either by using proprietary legal institution. For example, program that software and using Free/Open Source Software support some format in their old version, do (FOSS). Many state governments around the world not support the old format in their new ver- have adopted ODF, which is an open standard doc- sion. We can call this as a pragmatic approach ument format. What about the Indonesian gov- in defining a standard for document format. ernment? Why the Indonesian government should start to adopt ODF? In this paper, we will look on • Defined Standard. This standard specified in document format selection, problem arised in se- detail and associated with one standard orga- lecting document format, what ODF is, why ODF, nization (ex: ISO and ECMA). For open stan- what benefits can be obtained, so that the Indone- dard, every one can implement that standard sian government can consider ODF as their stan- free. dard document format for data exchange. Government institution usually use de facto stan- dard to determine document format because they 2 Approach in Selecting Docu- thought every body have the application to open the document, but in reality is not true. ment Format Beside that, from case study, document format that was choosen by de facto standard in year Generally, document storage model is based on 1990’s can not be opened with recent application. two spectrums, interface location (page image) and This example can be take as consideration in de- context/structure. Figure 2 shows us this condition termine document that will be used in government . institution. Government institution, in using document to communicate with public, have to think about ac- cessbility. Accessibilty is a chance for people to ac- cess the document in public area. Because of that, public may not be bound with some program to open and edit the document. 3 Problem of Pragmatic Ap- proach Problem of pragmatic approach in which techni- cal appraisal of the material is used to preserving one format over another. These approach provides Figure 2: Spectrum of document storage for nine principles to consider as part of appraisal. These principles balance economically sustainable 1. the proliferation of file formats; preservation and intellectual ’value’ with the practi- calities of working with specific, and especially pro- 2. the use of proprietary file formats, and prietary, file formats. 3. formats becoming obsolete, either by being Technical factors are only part of the real- incompatible with later versions of the appli- ity assessment of material for inclusion in collec- cations that created them, or by those appli- tions. Other factors such as intellectual content, cations no longer existing. significance of the document, significance of the donor/creator and any relationship to material al- This assumes that proprietary formats are more ready also play a part. Document considers ’orig- problematic to preserve as their structure and com- inal’ formats accepted for long-term preservation, position are not known, which hinders preservation and does not consider formats appropriate for dis- intervention by imposing the necessity for specialist semination. expertise. Moreover, as new software is created, so A Company or Nation looking to preserve born new file formats proliferate, and consequently exac- digital document permanently and have little con- erbate the problem. The primary way to solve this trol over the formats in which document is trans- is by creating and adopting standards. This is what ferred or deposited. Nowadays internet member- makes the issue of interoperability become impor- ship succeed to connect people all over the world, tant. A good document format will facilitate the there is a change in the document distribution pat- achievement of interoperability in the use of soft- tern. Authors can now easily upload documents in ware. With the method and good storage format, any format to the next can be downloaded by any- then a file will be used by various software. one. Each documents format can be opened only Acceptability of any format is based on each per- by using certain software. When the person down- son’s ability to manage and preserve that format
Recommended publications
  • XXX Format Assessment
    Digital Preservation Assessment: Date: 20/09/2016 Preservation Open Document Text (ODT) Format Team Preservation Assessment Version: 1.0 Open Document Text (ODT) Format Preservation Assessment Document History Date Version Author(s) Circulation 20/09/2016 1.0 Michael Day, Paul Wheatley External British Library Digital Preservation Team [email protected] This work is licensed under the Creative Commons Attribution 4.0 International License. Page 1 of 12 Digital Preservation Assessment: Date: 20/09/2016 Preservation Open Document Text (ODT) Format Team Preservation Assessment Version: 1.0 1. Introduction This document provides a high-level, non-collection specific assessment of the OpenDocument Text (ODT) file format with regard to preservation risks and the practicalities of preserving data in this format. The OpenDocument Format is based on the Extensible Markup Language (XML), so this assessment should be read in conjunction with the British Library’s generic format assessment of XML [1]. This assessment is one of a series of format reviews carried out by the British Library’s Digital Preservation Team. Some parts of this review have been based on format assessments undertaken by Paul Wheatley for Harvard University Library. An explanation of the criteria used in this assessment is provided in italics below each heading. [Text in italic font is taken (or adapted) from the Harvard University Library assessment] 1.1 Scope This document will primarily focus on the version of OpenDocument Text defined in OpenDocument Format (ODF) version 1.2, which was approved as ISO/IEC 26300-1:2015 by ISO/IEC JTC1/SC34 in June 2015 [2]. Note that this assessment considers format issues only, and does not explore other factors essential to a preservation planning exercise, such as collection specific characteristics, that should always be considered before implementing preservation actions.
    [Show full text]
  • International Standard Iso/Iec 26300-2
    This is a previewINTERNATIONAL - click here to buy the full publication ISO/IEC STANDARD 26300-2 First edition 2015-07-01 Information technology — Open Document Format for Office Applications (OpenDocument) v1.2 — Part 2: Recalculated Formula (OpenFormula) Format Technologies de l’information — Format de document ouvert pour applications de bureau (OpenDocument) v1.2 — Partie 2: Titre manque Reference number ISO/IEC 26300-2:2015(E) © ISO/IEC 2015 ISO/IEC 26300-2:2015(E) This is a preview - click here to buy the full publication COPYRIGHT PROTECTED DOCUMENT © ISO/IEC 2015 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form orthe by requester. any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of Case postale 56 • CH-1211 Geneva 20 ISOTel. copyright+ 41 22 749 office 01 11 Fax + 41 22 749 09 47 Web www.iso.org E-mail [email protected] Published in Switzerland ii © ISO/IEC 2015 – All rights reserved This is a preview - click here to buy the full publication ISO/IEC 26300-2:2015(E) Open Document Format for Office Applications (OpenDocument) Version 1.2 Part 2: Recalculated Formula (OpenFormula) Format OASIS Standard 29 September 2011 Specification URIs: This version: http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.odt (Authoritative) http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.pdf
    [Show full text]
  • A Key for Document Interoperability?
    ELAN Electronic Government and Applications Feature Based Document Profiling - A Key for Document Interoperability? Bibliografische Information der Deutschen Nationalbibliothek: Die Deutsche Nationalbibliothek verzeichnet diese Publikation in der Deutschen Nationalbibliografie; detaillierte bibliografische Daten sind im Internet über http://dnb.d-nb.deabrufbar. 1.Auflage Juni 2012 Alle Rechte vorbehalten © Fraunhofer-Institut für Offene Kommunikationssysteme FOKUS, Juni 2012 Fraunhofer-Institut für Offene Kommunikationssysteme FOKUS Kaiserin-Augusta-Allee31 10589 Berlin Telefon: +49-30-3436-7115 Telefax: +49-30-3436-8000 [email protected] www.fokus.fraunhofer.de Dieses Werk ist einschließlich aller seiner Teile urheberrechtlich geschützt. Jede Ver- wertung, die über die engen Grenzen des Urheberrechtsgesetzes hinausgeht, ist ohne schriftliche Zustimmung des Instituts unzulässig und strafbar. Dies gilt insbesondere für Vervielfältigungen, Übersetzungen, Mikroverfilmungen sowie die Speicherung in elektronischen Systemen. Die Wiedergabe von Warenbezeichnungen und Handels- namen in diesem Buch berechtigt nicht zu der Annahme, dass solche Bezeichnungen im Sinne der Warenzeichen-und Markenschutz-Gesetzgebung als frei zu betrachten wären und deshalb von jedermann benutzt werden dürften. Soweit in diesem Werk direkt oder indirekt auf Gesetze, Vorschriften oder Richt-linien (z.B. DIN, VDI) Bezug genommen oder aus ihnen zitiert worden ist, kann das Institut keine Gewähr für Richtigkeit, Vollständigkeit oder Aktualität übernehmen. ISBN 978-3-00-038675-6
    [Show full text]
  • ODF Workshop
    ODF Workshop ODF: The Past, Present and Future Michael Brauer, Sun, ODF TC Chair ODF Accessibility Pete Brunet, IBM, ODF Accessibility Subcommittee ODF Programmability Rob Weir, IBM, ODF TC Michael Brauer, Sun, ODF TC Chair ODF Interoperability Alan Clark, Novell, ODF Adoption TC Rob Weir, IBM, ODF TC ODF Adoption Don Harbison, IBM, ODF Adoption TC Co-Chair OASIS OpenDocument ISO/IEC 26300 The Past, the Present, and the Future Michael Brauer Technical Architect Software Engineering StarOffice/OpenOffice.org Sun Microsystems About the Speaker Technical Architect in Sun Microsystem's OpenOffice.org/StarOffice development OpenOffice.org/StarOffice developer since 1995 Main focus: Office application development/file formats and XML technologies OpenOffice.org XML project owner OASIS OpenDocument Technical Committee chair Agenda The Past - History of OASIS OpenDocument format The Present – Sub Committees, Work in Progress The Future – OpenDocument v1.2 The Past 1999 Development of “StarOffice XML” file format starts Primary goal: interoperability 2000 Sun contributes StarOffice to OpenOffice.org “StarOffice XML” becomes “OpenOffice.org XML” open source community project First OpenOffice.org XML working draft publicly available 2001 OpenOffice.org XML is used as default file format for OpenOffice.org 1.0/Sun StarOffice 6.0 software 2002 Foundation of OASIS OpenDocument Technical Committee (TC) Basis of TC's work: OpenOffice.org XML file format OpenDocument TC Charter (Extract) The purpose [...] is to create an open, XML-based file format specification for office applications. [it] must meet the following requirements: it must be suitable for office documents containing text, spreadsheets, charts, and graphical documents, it must retain high-level information suitable for editing the document, it must be friendly to transformations using XSLT or similar XML-based languages or tools, it should 'borrow' from similar, existing standards wherever possible and permitted.
    [Show full text]
  • Comparing Libreoffice and Apache Openoffice Libreoffice and Apache Openoffice Both Are Derived from the Former Openoffice.Org Project
    Comparing LibreOffice and Apache OpenOffice LibreOffice and Apache OpenOffice both are derived from the former OpenOffice.org project. Over the years, the differences have grown and these documents offer a list of all the changes. This document is the starting point for the information comparing the two office suites. Time line showing the various releases AOO 3.4 4.0 4.1 LO 3.3 3.4 3.5 3.6 4.0 4.1 4.2 4.3 4.4 … 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 10 11 12 13 2010 2011 2012 2103 2014 2015 Each ApacheOpenOffice release gets one update Each LibreOffice release typically gets 6 or 7 updates links to release information wiki.documentfoundation.org/ReleaseNotes/3.4 wiki.documentfoundation.org/ReleaseNotes/3.5 cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Release+Notes wiki.documentfoundation.org/ReleaseNotes/3. 6 wiki.documentfoundation.org/ReleaseNotes/ 4.0 cwiki.apache.org/confluence/display/OOOUSERS/AOO+ 4 . 0 +Release+Notes wiki.documentfoundation.org/ReleaseNotes/ 4.1 wiki.documentfoundation.org/ReleaseNotes/ 4.2 cwiki.apache.org/confluence/display/OOOUSERS/AOO+ 4 . 1 +Release+Notes wiki.documentfoundation.org/ReleaseNotes/ 4.3 wiki.documentfoundation.org/ReleaseNotes/ 4.4 Simply the office suites are composed of 3 'layers' 1.
    [Show full text]
  • Open Document Format for Office Applications (Opendocument) Version 1.2
    Open Document Format for Office Applications (OpenDocument) Version 1.2 Part 2: Recalculated Formula (OpenFormula) Format OASIS Standard 29 September 2011 Specification URIs: This version: http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.odt (Authoritative) http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.pdf http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part2.html Previous version: http://docs.oasis-open.org/office/v1.2/csd06/OpenDocument-v1.2-csd06-part2.odt (Authoritative) http://docs.oasis-open.org/office/v1.2/csd06/OpenDocument-v1.2-csd06-part2.pdf http://docs.oasis-open.org/office/v1.2/csd06/OpenDocument-v1.2-csd06-part2.html Latest version: http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2-part2.odt (Authoritative) http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2-part2.pdf http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2-part2.html Technical Committee: OASIS Open Document Format for Office Applications (OpenDocument) TC Chairs: Rob Weir, IBM Michael Brauer, Oracle Corporation Editors: OpenDocument-v1.2-os-part2 29 September 2011 Copyright © OASIS Open 2002 - 2011. All Rights Reserved. Standards Track Work Product Page 1 of 234 David A. Wheeler Patrick Durusau Eike Rathke, Oracle Corporation Rob Weir, IBM Related work: This document is part of the OASIS Open Document Format for Office Applications (OpenDocument) Version 1.2 specification. The OpenDocument v1.2 specification has these parts: OpenDocument v1.2 part 1: OpenDocument Schema OpenDocument v1.2 part 2: Recalculated Formula (OpenFormula) Format (this part) OpenDocument v1.2 part 3: Packages Declared XML namespaces: None.
    [Show full text]
  • Libreoffice 7.1 Calc Guide | 3 Chart Wizard
    Copyright This document is Copyright © 2021 by the LibreOffice Documentation Team. Contributors are listed below. You may distribute it and/or modify it under the terms of either the GNU General Public License (http://www.gnu.org/licenses/gpl.html), version 3 or later, or the Creative Commons Attribution License (http://creativecommons.org/licenses/by/4.0/), version 4.0 or later. All trademarks within this guide belong to their legitimate owners. Contributors To this edition Steve Fanning Felipe Viggiano Kees Kriek Jean Hollis Weber Vasudev Narayanan To previous editions John A Smith Jean Hollis Weber Martin J Fox Andrew Pitonyak Simon Brydon Gabriel Godoy Barbara Duprey Gabriel Godoy Peter Schofield John A Smith Christian Chenal Laurent Balland-Poirier Philippe Clément Pierre-Yves Samyn Shelagh Manton Peter Kupfer Andy Brown Stephen Buck Iain Roberts Hazel Russman Barbara M. Tobias Jared Kobos Martin Saffron Dave Barton Olivier Hallot Cathy Crumbley Kees Kriek Claire Wood Steve Fanning Zachary Parliman Gordon Bates Leo Moons Randolph Gamo Drew Jensen Samantha Hamilton Annie Nguyen Felipe Viggiano Stefan Weigel Feedback Please direct any comments or suggestions about this document to the Documentation Team’s mailing list: [email protected]. Note Everything you send to a mailing list, including your email address and any other personal information that is written in the message, is publicly archived and cannot be deleted. Publication date and software version Published May 2021. Based on LibreOffice 7.1 Community. Other
    [Show full text]
  • Hisham Hashem Muhammad Dataflow Semantics For
    Hisham Hashem Muhammad Dataflow Semantics for End-user Programmable Applications Tese de Doutorado Thesis presented to the Programa de Pós–graduação em Informática da PUC–Rio in partial fulfillment of the requirements for the degree of Doutor em Informática. Advisor: Prof. Roberto Ierusalimschy Rio de Janeiro April 2017 Hisham Hashem Muhammad Dataflow Semantics for End-user Programmable Applications Thesis presented to the Programa de Pós–graduação em Informática da PUC–Rio in partial fulfillment of the requirements for the degree of Doutor em Informática. Ap- proved by the undersigned Examination Committee. Prof. Roberto Ierusalimschy Advisor Departamento de Informática – PUC–Rio Prof. Renato Fontoura de Gusmão Cerqueira IBM Research – Brazil Profª. Raquel Oliveira Prates Departamento de Ciência da Computação – UFMG Prof. Edward Hermann Haeusler Departamento de Informática – PUC-Rio Profª. Simone Diniz Junqueira Barbosa Departamento de Informática – PUC-Rio Prof. Márcio da Silveira Carvalho Vice Dean of Graduate Studies – PUC–Rio Rio de Janeiro, April the 28th, 2017 All rights reserved. Hisham Hashem Muhammad The author graduated in Computer Science from Universidade do Vale do Rio dos Sinos — Unisinos in 2002, and obtained the degree of Mestre at Pontifícia Universidade Católica do Rio de Janeiro — PUC-Rio in 2006. He obtained the degree of Doutor at PUC-Rio in 2017, where he worked in the field of programming languages. Bibliographic data Hashem Muhammad, Hisham Dataflow Semantics for End-user Programmable Ap- plications / Hisham Hashem Muhammad; advisor: Ro- berto Ierusalimschy. – 2017. v., 184 f: il. color. ; 30 cm Tese (doutorado) - Pontifícia Universidade Católica do Rio de Janeiro, Departamento de Informática. Inclui bibliografia 1.
    [Show full text]
  • TOWARD XML-BASED OFFICE DOCUMENTS Contents 1. What Is
    TOWARD XML-BASED OFFICE DOCUMENTS (A BRIEF INTRODUCTION) JACEK POLEWCZAK Contents 1. What is happening? 1 2. Changing attitudes 2 3. ODF 3 4. OOXML 4 5. What about PDF? 6 6. Conclusions and recommendations 6 References 7 1. What is happening? Recent trends in office document formats indicate a move towards open and standard-based XML formats. Major government agencies and public and private institutions started look- ing for office documents formats that assure compatibility with open standards, that are vendor neutral, cross-platform interoperable, and non-binary (i.e., XML-based). Although the pressure to embrace open file formats has been felt for many years, Microsoft, with the dominant role in office documents formats, has been reluctant to move from its pro- prietary, binary formats to open document standards. The situation only seemingly changed in November 2005 when Microsoft, with a number of industry partners and supporters, took steps to produce an open specification for their own Office file formats. In December 2006, the specification was approved by ECMA International (European Association for Standard- izing Information and Communication systems) as ECMA-376: Office Open File Formats (OOXML). In April 2008, OOXML (as ISO/IEC DIS 29500) received necessary votes in the ISO (International Organization for Standardization) for approval as an international standard. However, in developing OOXML, Microsoft have chosen not to support ISO/IEC 26300: Open Document Format for Office Applications (ODF), submitted to ISO by OASIS (Or- ganization for the Advancement of Structured Information Standards), and approved by ISO as international standard in May 2006. The benefits of OOXML, Microsoft argued, are concentrated on backwards compatibility with its legacy binary file formats.
    [Show full text]
  • A Comparative Study for Open Document Formats R
    A Comparative Study for Open Document Formats R. Mohamed Abdel Azim*, H. Farouk Ali** Project Manager, eContent program eContent Initiative Director, eContent program Ministry of Communication & Information Technology (MCIT), Cairo, Egypt Abstract — Many technical specifications that are restrict their use of the term "standard" to technologies sometimes considered standards are proprietary rather than approved by formalized committees that are open to being open, and are only available under restrictive contract participation by all interested parties and operate on a terms (if they can be obtained at all) from the organization that consensus basis, while others do not. owns the copyright for the specification. In this paper, we present a comparative study for the most common open An open format is a published specification for storing document format, OASIS Open Document Format and digital data, usually maintained by a non-proprietary Microsoft OXML standards organization, and free of legal restrictions on use. For example, an open format must be implementable Index Terms — Open Standards, XML, Open XML, by both proprietary and free/open source software, Open Format, OASIS, Open Office using the typical licenses used by each. In contrast to open formats, proprietary formats are controlled and I. INTRODUCTION defined by private interests. Open formats are a subset of open standards. Open Standards are publicly available and The primary goal of open formats is to guarantee long- implementable standards. By allowing anyone to obtain term
    [Show full text]
  • Suggestions for Interoperability Undertaking
    Ms. Neelie Kroes Commissioner DG COMPETITION Bourgetlaan 1 1140 Evere Bruxelles/Brussel SUBJECT: Suggestions for Interoperability Undertaking The Hague, September 28th 2009 Dear Commissioner Kroes, We read with interest the article in several media published last week1 where you were quoted as saying that the Commission is near to closing a deal on a number of issues in the case against Microsoft. We think that this inquiry is of great importance, and that restoring a level playing field in this area is essential for the future ambitions of Europe. On behalf of OpenDoc Society we would like to respond to the "Interoperability Undertaking"-proposal2 from Microsoft that was made to the European Commission, hoping that this will be of help to you in finding effective remedies to the issues that matter most in this case. OpenDoc Society is an international member-based not-for-profit organisation headquartered in Europe, with individual and organisational members around the planet. Our organisational members range from large software vendors and open source communities to small and medium sized enterprises, from (also European) government organisations to academia and research, and from education and cultural institutions up to special needs groups, registered charities and the military. Our goal is to promote best practises for productivity applications, most notably in the area of open standards, document exchange and processing. In this document, we will respond to the Undertaking from our expert knowledge in this domain and make a number of proposals to improve that document in order to make it effective given the purposes it is drafted for.
    [Show full text]
  • XML-Based Office Document Standards by Walter Ditch
    Technology & Standards Watch XML-based Office Document Standards by Walter Ditch Version 1.0 First published August 2007 Publisher JISC: Bristol, UK Copyright owner Higher Education Funding Council for England To make sure you are reading the latest version of this report, you should always download it from the original source. Original source http://www.jisc.ac.uk/techwatch © HEFCE 2007 JISC Technology and Standards Watch, Aug. 2007 XML-based Office Documents Executive Summary Historically, standardisation of the office document formats we use in our everyday working environment has been achieved through the widespread adoption of products from a very small number of suppliers. Initially this was helpful as it meant that a kind of de facto interoperability was achieved, but it has also created a form of vendor lock-in, which requires users to have purchased a particular brand of software product in order to be able to undertake everyday office tasks. This use of de facto, proprietary standards has become increasingly unacceptable, especially within the public sector, where information has to be provided to members of the public without requiring them to have bought software from a particular vendor. Policy moves from within the EU and elsewhere are driving the use of open standards to encourage open and inclusive document exchange. With current trends in office document file formats showing a strong move towards open, standards-based XML formats and away from closed solutions, and with major government and corporate software contracts increasingly demanding compatibility with open standards (many of which are based on the ubiquitous XML), competing software vendors have understandably been keen to have their own preferred office file formats endorsed as open standards.
    [Show full text]