Graham Taylor.

Transcription

1 Graham Taylor

2 HOW OPEN CAN EUROPE GET: OPEN DOCUMENT FORMATS OFE COMMENTS NICK WOOD-DOW GOVERNMENT ADVISOR OPENFORUM EUROPE

3 AGENDA Introduction Graham Taylor Director, OFE Keynote Presentations Doug Heintzmann, IBM Tim Bray, SUN David Stevenson, ADOBE Discussion

4 Graham Taylor

5 Mission To accelerate the market take-up of Linux and other Open Source Software in business and public sector markets, within the context of open verifiable standards Structure Not-for Profit, Independent, Non evangelic, with members drawn from user and supplier communities. Single voice but not necessarily single opinion Approach Not anti any one company, achieving a new business model more effective, lower cost, more choice based on hard business evidence

6 OFE White Paper Main Conclusions Technical interoperability not enough, define from user s perspective Interoperability aligned with Openness Open, verifiable standards OSS new business model OSS differentiated in areas of semantic,organisational interoperability OSS supports by - Way software can be developed - How it encourages sharing - How it can be openly verified

7 How Open can Europe Get? Interoperability is aligned with Openness which itself is the driver of the greater flexibility, access and responsiveness between government and the community. A pragmatic definition to the definition of Open Verifiable Standards provides the primary route to conformance. Open, verifiable standards broadly cover the technical issues of interoperability, and should be enforced by every government for its use. Failure to do so increase the danger of lock in to a single supplier, limits choice, and restricts competition.

8 Further reading:

9 IBM Software Group For Business Open computing for an on demand world Doug Heintzman, Director, Technical Strategy IBM Software Group

10 IBM Software Group The Principles of Open Computing Permit interoperability by using published specifications for API's, protocols and data and file formats The specifications must be published without restrictions that limit implementations, or require royalties or payments ( other than reasonable royalties for essential patents) Open Computing Open Standards Open Architecture Open Source

11 IBM Software Group OPEN Computing Goals Ensure flexibility Ensure interoperability Avoid vendor lock-in Drive cost effectiveness Ensure future access to information Ensure a level playing field for competition Maximize freedom of action

12 IBM Software Group Open Standards Published without restriction (other than reasonable royalties for essential patents) Freely available for adoption by the industry Control by an open industry organization Implemented by offerings available in the market Standards evolution Initiator Core group Standards body

13 IBM Software Group Evolution to an Open Standard Need Initiator Core group Standards body Open Customer need for technical solution to known problem Lack of industry accepted technical solution May be competing technical approaches or single proprietary solution Lack of interoperability A company, individual or group of companies or individuals agree to address issue Resources devoted to developing best technical solution, often in collaborative fashion Interested parties publish specifications Specifications publicly available sufficient to enable implementation, interoperability Can be implemented with little or no restrictions; IPR either RAND or Royalty free. Developers may create reference or commercial implementation Standards body reviews technical solution, adopts as standard Specifications publicly available are sufficient to enable implementation, interoperability Can be implemented with little or no restrictions; IPR either RAND or royaltyfree. Standards body open to broad participation, open decision making process Developers declare intent to have solution accepted as standard Standard implemented in competing IT products by multiple vendors.

14 IBM Software Group The Open File Format Alternative Functionally rich Fully published Open industry control Await finalization of OASIS specification Numerous vendors are implementing draft specification

15 IBM Software Group The Microsoft Alternative Not really open Single vendor control Mature technology well suited for standardization TAC recommendations are not sufficient.doc remains dominant.doc remains default Networking effects Office 2003 XML schemas are incomplete Proprietary extensions Non standard XML tags Binary extensions Proprietary, platform specific, non portable

16 IBM Software Group Public Administration Policy Roadmap 1. Insist on open standards as a matter of policy... be pragmatic about it. 2. Focus on interoperable ICT systems. 3. Avoid procurement of proprietary, non-open standards based solutions. 4. Evaluate open source solutions on equal footing with commercial solutions. 5. Reject mandates or preferences based on development model. 6. Insist on open File formats 7. Adopt open computing as an underlying philosophy. Insist on openness, but make pragmatic business oriented decisions based on features, training cost, availability of skill, interoperability and value for money.

17 Office Document Formats: The Goal, the Present, the Future Tim Bray Sun Microsystems

18 The Goal Office documents are your intellectual capital and you worked hard to produce it for your citizens. Sun doesn t own it, Microsoft doesn t own it, you own it. That means it should be stored in a well-designed, long-lived, open, and shareable data format that is open and is not anyone s competitive weapon.

19 The Goal Office documents are your intellectual capital and you worked hard to produce it for your citizens. Sun doesn t own it, Microsoft doesn t own it, you own it. That means it should be stored in a well-designed, long-lived, open, and shareable data format that is open and is not anyone s competitive weapon.

20 Well-Designed The OpenOffice.org format has been under continuous development for over five years, first by the StarOffice group, now by a group of experts from several vendors. There are many independent attestations of its design quality.

21 Long-Lived The OpenOffice.org format is based on XML, which is based on SGML (ISO Standard 8879). The first SGML documents, created pre-1986, are 100% usable today.

22 Open The OpenOffice.org format is controlled by the governing OASIS Technical Committee. There are absolutely no patents, licensing considerations, or intellectual-property issues to consider.

23 Shareable To share data, you need shared syntax and semantics. The OpenOffice.org format is based on XML, which provides shared syntax. The OpenOffice.org schemas and specifications provide shared semantics.

24 Current State of Play March 2004: OASIS publishes committee draft of OpenOffice.org format. March-September: Multiple implementations, many issues raised. September 2004: Revised draft will be published. Roadmap: Under discussion.

25 Pedro Ortún to Jonathan Schwartz (July 19) Transparency and accessibility requirements dictate that public information and government transactions avoid depending on technologies that imply or impose a specific product or platform on businesses or citizens.

26 Pedro Ortún to Jonathan Schwartz (July 19) The Commission feels that standardization is the most appropriate mechanism through which industry consensus can be generated... the TAC recommends that the submission of the format to an official standardization body should be considered.

27 Pedro Ortún to Jonathan Schwartz (July 19) The Commission feels that standardization is the most appropriate mechanism through which industry consensus can be generated... the TAC recommends that the submission of the format to an official standardization body should be considered. Sep. 1: Sun notified OASIS of intent to take OpenOffice.org to ISO. Karl Best, Vice President of OASIS, replies supporting the idea. Sep. 6: Initial approval from OASIS TC.

28 Pedro Ortún to Jonathan Schwartz (July 19)... industry should provide filters that allow documents based on Microsoft's WordML specifications and the emerging OASIS Open Document Format to be read and written to other applications and that these filters should be made available for all products and platforms.

29 Pedro Ortún to Jonathan Schwartz (July 19)... industry should provide filters that allow documents based on Microsoft's WordML specifications and the emerging OASIS Open Document Format to be read and written to other applications and that these filters should be made available for all products and platforms. Sun has developed WordML and ExcelML filters, they will be in the next releases, StarOffice 8 and OpenOffice.org 2.0. They are Open Source.

30 The Future The technical obstacles to rich, open, longlived, shareable Office Document formats have been overcome. However, the legal and business obstacles remain to be addressed.

31

32 PDF An Open Document Format? OFE Breakfast Briefing David Stevenson Technology Strategist 9 th September Adobe Systems Incorporated. All Rights Reserved. bc

33 Adobe Systems Incorporated Helping people and businesses communicate better for more than twenty years Adobe Systems Incorporated. All All Rights Reserved. bc

34 Agenda Purpose of PDF Adobe standards activities PDF in context of open documents Looking forward 2004 Adobe Systems Incorporated. All Rights Reserved. bc

35 PDF - Portable Document Format Secure distribution and exchange of electronic documents and forms PDF is a universal, platform independent file format Preserves fonts, images, graphics and layout of any source document PDF files are compact and complete, and can be shared, viewed, and printed by anyone with free Reader software 2004 Adobe Systems Incorporated. All Rights Reserved. bc

36 History & Philosophy PDF invented by Adobe introduced to the market in 11 years ago A direct descendant of PostScript Published specification Wide support from third parties Compare with TIFF Free to consume Free Adobe Reader on virtually every platform 2004 Adobe Systems Incorporated. All Rights Reserved. bc

37 The Ecosystem of PDF and Reader >1,800 solution partners Half a billion licenses of Adobe Reader 60% of PDAs bundled with Reader Distributed by top 10 PC manufacturers 2004 Adobe Systems Incorporated. All Rights Reserved. bc

38 Beyond de facto PDF/X - ISO 15929, , : Exchange of digital advertising information : Using CMYK data : Complete exchange for colour managed workflows PDF/A - ISO/TC171/SC2 N 226 E Long term preservation and archiving of digital records ISO certification expected Spring 2005 PDF/E Under development Document exchange for engineering drawings & specifications PDF/Access WG launched 3/04 PDF/is IEEE Image-Streamable Internet Fax Transmission Transmission of high quality image-only documents to and from internet fax devices 2004 Adobe Systems Incorporated. All Rights Reserved. bc

39 One size does not fit all The requirements for a document format change over time Early in the document lifecycle Ease of making changes is key During document lifecycle Control is key Access, versioning etc. Collaboration When document is published Document security 2004 Adobe Systems Incorporated. All Rights Reserved. bc

40 PDF foundation for current and future developments Improved tools for creating structure Accessibility, reusability Attachments PDF as a container XMP Adobe metadata specification XFA Adobe XML forms architecture Intelligent document Presentation Business logic XML schema support 2004 Adobe Systems Incorporated. All Rights Reserved. bc

41 bc 2004 Adobe Systems Incorporated. All Rights Reserved. bc