1) The Belgian mirror group finds it very unfortunate for ISO to support and develop different office document description standards (such as ISO/IEC 26300 and ECMA 376) offering a number of similar functionalities. The group furthermore has been informed that for some of these standards future extensions are being proposed, which should further increase the overlap between their functionalities. The group therefore urges the organizations promoting those separate standards to work together, to develop a common set of functionalities and to integrate them into a unique common base that every document description standard should understand. 2) To facilitate this objective, the Belgian mirror group proposes to deal separately with the issue of backwards compatibility with existing legacy documents, which is also a very useful objective.

ge

Proposed Disposition of DIS 29500 Comment BE-0001 (Modified: 2008-01-04) There are currently several XML-based document formats in use, each designed to address a different set of goals or requirements. These include ISO/IEC IS 26300 (ODF), China’s UOF, and ECMA-376 (DIS 29500 ­ Open XML). All these formats have numerous implementations in multiple tools and multiple platforms (Linux, Windows, Mac OS, hand-held devices). The Ecma Response Document from the Fast Track 30-Day contradiction phase for DIS29500 addressed the question of harmonization by explaining the differences between the ODF and Open XML formats as follows: “… one must recognize that creating a single “merged” format to address the user requirements of both ODF and OpenXML is a much more difficult goal–one that is hindered by fundamental obstacles comparable to what one might encounter while merging HTML and ODF or HTML and PDF. This is because of sheer difference of scope, feature and architecture. Ecma believes that one format cannot simultaneously meet the requirements that would come from the merge of the two formats and the stringent requirements of backward compatibility that drive the design of OpenXML. First, while both formats share the high-level goal, to represent documents, presentations, and spreadsheets in XML, their low-level goals differ fundamentally. OpenXML is designed to represent the existing corpus of documents faithfully, even if that means preserving idiosyncrasies that one might not choose given the luxury of starting from a clean slate. In the ODF design, compatibility with and preservation of existing Office documents were not goals. Each set of goals is valuable; sacrificing either at the expense of the other may not be in the best interest of users. Second, the resulting differences are not merely variances in scope that could be resolved by adding capabilities to one or the other. They are structural and architectural in nature. Where functionality overlaps, the corresponding elements nonetheless differ in precise meaning, usage, capabilities, options, and interaction with other elements. Even more importantly, the corresponding elements do not exist in isolation, but are components of whole document models, with different rules and constraints for such things as page/slide layout, flow, style inheritance, event processing, relative positioning, calculation order, formula dependencies, chart construction, graphic templates, animations, and so on. The resulting variations are not merely cosmetic. They compound to create qualitative disparities that, although perfectly acceptable for much of the user base, can be significant for organizations that require high fidelity in layout, content, or editability. Differences between the implicit page style model of ODF and the explicit page style model of OpenXML, differences in the models for splitting table cells, differences in the style information associated with spreadsheet cells, and differences in the full formula specification used in spreadsheets are only small examples of the hundreds of explicit design decisions that ensure the information included in the existing formats is represented faithfully in the OpenXML format.” There are many translation tools already in existence that enable interoperability between different formats by providing useful translation capabilities between ODF, Open XML and UOF. We note that the German national standards body, DIN, has a committee, NIA-01-34 (see http://www.fokus.fraunhofer.de/fokus/fokus/presse/meldungen_fokus/2007/05/DIN-E.pdf ), that is preparing a Technical Report on the translation of documents between the IS 26300 and DIS 29500 formats. The members of NIA-01-34 include format experts from a number of countries, working together to define the numerous differences between these formats. Ecma strongly supports any harmonization effort that enables better sharing of information and allows better translation between the formats in the following way: Ecma believes that the work of the DIN (NIA-01-34) committee is essential to any harmonization effort. The work of DIN (NIA-01-34) will enable the industry at large to understand the detailed differences between the formats. Based on this detailed understanding, the ODF and Open XML formats could be extended in the future in order to enable better sharing of information and allow future translations tools to provide even better translation and interoperability between the formats. Harmonization would require functional changes to two International Standards and would fall under the JTC 1 procedures for new work within SC 34 and could be done in the future. Such work should not be done in this Fast-Track process and should not impede the adoption of DIS 29500. Similar Comments: CH-0013 , CL-0001 , DE-0119 , KR-0001 , NZ-0003 , PE-0010 , ZA-0003

Tag and Go

2 Comments

  1. hAl September 22, 2007 @ 8:06 pm

    Fluff

  2. Chris Puttick November 29, 2007 @ 8:03 am

    While part (1) is a gwnerally worded persuader that might be described as fluff, part (2) is actually similar in intent to other comments submitted (BSI, for one, I think) which is that the scope of Ecma 376 fast track submission is one of the major problems.

    The scope should be worded such that it reflects the potential strength of the submitted specification, that strength being the preservation of Microsoft legacy binary formats (this strength does require the support of a mapping of the binary formats to the new format, included as an appendix).

    Chris

Leave a comment

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>

  • Argentina (1)
  • Australia (30)
  • Austria (1)
  • Belgium (1)
  • Brazil (64)
  • Bulgaria (3)
  • Canada (79)
  • Chile (217)
  • China (1)
  • Colombia (237)
  • Czech Republic (75)
  • Denmark (168)
  • Ecma (76)
  • Ecuador (1)
  • Finland (15)
  • France (592)
  • Germany (162)
  • Ghana (12)
  • Greece (113)
  • India (82)
  • Iran (58)
  • Ireland (12)
  • Israel (33)
  • Italy (2)
  • Japan (82)
  • Jordan (1)
  • Kenya (81)
  • Malaysia (23)
  • Malta (5)
  • Mexico (7)
  • New Zealand (54)
  • Norway (12)
  • Peru (10)
  • Philippines (7)
  • Poland (4)
  • Portugal (118)
  • Singapore (2)
  • South Africa (17)
  • South Korea (25)
  • Spain (1)
  • Switzerland (19)
  • Thailand (1)
  • Tunisia (3)
  • Turkey (1)
  • UK (635)
  • Uruguay (18)
  • USA (288)
  • Venezuela (73)