Open Document Format V1.2 The Standard for Office Documents OASIS ODF Adoption TC

Agenda What is the Open Document Format? Brief history At OASIS & ISO; what's going on now? ODF 1.2 overview and roadmap ODF Interoperability and Conformance – explained ODF toolkits

ODF is an example of a bigger change Application Information Old Style Information is closely linked to the application that created it. Control is with the software developer not the customer. Application Information New Style Information is represented using a real open standard not under the control of a single vendor, and multiple applications can create and access it interchangeably. Control is with the customer not the software provider.

We started to see this in the 1990s Application Information Old Style Information is closely linked to the application that created it. Control is with the software developer not the customer. Browser The Web New Style Information is represented using a real open standard not under the control of a single vendor, and multiple applications can create and access it interchangeably. Control is with the customer not the software provider.

The trend will accelerate in the 2000s and beyond... Application Information Old Style Information is closely linked to the application that created it. Control is with the software developer not the customer. Office AppsWeb AppsNew Apps Documents New Style Information is represented using a real open standard not under the control of a single vendor, and multiple applications can create and access it interchangeably. Control is with the customer not the software provider.

ODF Attributes... It is not dictated by a single vendor. It is not required to be compatible with a single vendor's commercial products. It is not a forced commitment to either proprietary or open source software.

ODF Attributes... It is not a limitation of your choices for applications to create and process your information, now and in the future, by everyone who should have access to it. It is not being fully implemented by Microsoft, although Office 2007 with SP2 is a good start!

dd month yyyy 3 ODF Technical Committees ODF TC (the standard authors) Adoption TC (the educators) Interoperability and Conformance TC (the bridge builders)

OASIS Explained Organization for the Advancement of Structured Information Standards Formally called “SGML Open”, Founded in corporation/organizations represented 5,000 participants from 100 countries 70 active technical committees (TC's) DITA, DocBook, ebXML, Election Markup Language, SAML, UBL, WebCGM

OASIS ODF TC Founded 2002 ~12 regular attendees including corporations, academia, and government representative Three formal subcomittees meet independently: Accessibility OpenFormula Metadata

OASIS ODF TC Voting members from industry, and academia... DeltaXML IBM Individuals from academia Institute for Defense Analyses Microsoft Nokia Novell Open Document Format Alliance Oracle Stichting Centrum voor Wiskunde & Informatica

ODF Specification Coverage Storage formats for: Text documents Spreadsheet documents Presentation documents And the templates for the above Interesting subsets: Drawings Charts Out of scope: Database (OpenOffice Base) format Clipboard formats Runtime API's as used by scripts Scripting languages User Interface

13 ／ ODF's reuse of web standards “If I have seen a little further it is by standing on the shoulders of Giants.” Isaac Newton, letter to Robert Hooke, 1676 Choose reuse because: Reduced time to write specification Higher quality specifications Can leverage existing community expertise Can leverage existing education materials Better interoperability Network effects – synergy is good

14 ／

ODF 1.2 – New Features & Work Items Digital Signatures RDFa-based metadata framework (see: ) OpenFormula 50+ other member and public proposals 100's of defects fixed General redrafting to ISO Directives, Part 2 Split into 3-parts New conformance clauses

dd month yyyy Conformance vs Interoperability Conformance Does it adhere to the specification ? Interoperability Do implementations work together ? " Conformance is a means to achieve the goal of interoperability" More Info:

17 ／ Interoperability begins with the standard But it doesn't end there. Standards define the technical conventions to be followed by applications Validators help implementors check that their documents are correctly following the standard. Test suites help implementors check that they property handle valid documents. Plugfests bring implementations together to work on on real-world interoperability scenarios. Implementation notes document implementation-defined behaviors and deviations from the standard Reference implementations provide a definitive interpretation of the standard, helping identify discrepancies between the standard and and the test suites. An independent, user-focused watchdog organization to monitor, report and where necessary scold vendors for poor interoperability.

18 ／ What is an OASIS interoperability demo? “...are public interoperability demonstrations that showcase multi-vendor implementations of approved OASIS work. Usually hosted in connection with a conference... OASIS InterOps are official Consortium activities, endorsed by one or more OASIS Technical Committees (TCs) and mutually supported by OASIS staff and InterOp participants.”

19 ／ Why an ODF InterOp Demo? Required by OASIS Liaison Policy Enables submission for adoption of OASIS ODF to other standards organizations; e.g. ISO/IEC JTC1

dd month yyyy ODF 1.2 Interop Demo >3 implementations of ODF 1.2 Real world use case from the Louvre Museum ● Centre de Restauration & de Recherche des Musées de France ● Held in conjunction with the OpenOffice.org Conference, September 2, 2010, Budapest Hungary

dd month yyyy ODF Plug-fests Goal is to achieve maximum interoperability by running scenario-based tests in hands-on labs Ongoing series of vendor-neutral events, bringing together implementers and other stakeholders of the standard Periodic face-to-face 'plug-tests' – (5) to date Focus on de-bugging application implementations of ODF Broad industry and open source developer participation

ODF for the Application Developer Challenge Opportunity >1,000 page ODF Standard No objections to it as a specification – it is what it needs to be Written from the perspective of word processor implementors Too much to ask the average app developer to master Create an ODF API to accelerate application developer productivity For example: “Create a loan amortization spreadsheet in 30 lines of code”

ODF Toolkit Union Overview Apache 2 - Open source licensing A convergent effort – bring together the projects that are already working in this area Wide range of language bindings, Java, Python, Ruby, C++, etc. Evaluate the API itself for standardization Build and make available the SDK for the industry to consume at The ODF Toolkit becomes the preferred way of working with ODF, directly driving new innovation adjacent, but not dependent on traditional office productivity application suites.

ODF Toolkit Projects Today  Simple Java API for ODF  ODFDOM  AODL (C#)  ODF Conformance Tools –ODF Validator  ODF Applications and Tools –ODF XSLT Runner

25 ／ ODF Resources OASIS ODF TC OASIS ODF Interoperability and Conformance TC OASIS ODF Adoption TC Open Document Formant Focus Area Open Document Alliance Open Docs Society ODF Plug-fest - Brussels October , 2010 ODF Plug-fest – Maidenhead, UK, February 24 – 25, 2011

ODF Community Site