Skip to main content

Home/ OpenDocument/ Group items tagged jtc-sc34

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Jesper Lund Stocholm

Publicly Available Standards - 0 views

standards.iso.org/...index.html

ISO

shared by Jesper Lund Stocholm on 27 May 08 - Cached
  • ISO/IEC 26300:2006 XHTML version 1st Information technology -- Open Document Format for Office Applications (OpenDocument) v1.0 XHTML version
  • The following standards are made freely available for standardization purposes. They are protected by copyright and therefore and unless otherwise specified, no part of these publications may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, microfilm, scanning, reproduction in whole or in part to another Internet site, without permission in writing from ISO. Requests should be addressed to the ISO Central Secretariat.
  • ISO/IEC 29500-1:2008 Electronic inserts 1st Information technology -- Document description and processing languages -- Office Open XML File Formats -- Part 1: Fundamentals and Markup Language Reference JTC1/SC34 ISO/IEC 29500-2:2008 Electronic inserts 1st Information technology -- Document description and processing languages -- Office Open XML File Formats -- Part 2: Open Packaging Conventions JTC1/SC34 ISO/IEC 29500-3:2008 1st Information technology -- Document description and processing languages -- Office Open XML File Formats -- Part 3: Markup Compatibility and Extensibility JTC1/SC34 ISO/IEC 29500-4:2008 Electronic inserts 1st Information technology -- Document description and processing languages -- Office Open XML File Formats -- Part 4: Transitional Migration Features JTC1/SC34
    • Jesper Lund Stocholm
      Jesper Lund Stocholm on 15 Jan 09
       
      Remenber also to download the electronic inserts containing e.g. reference schemas in electronic form.
  • Paul Merrell on 27 May 08
     
    Most ISO and IEC standards are only available for purchase. However, a few are publicly available at no charge. ISO/IEC:26300-2006 is one of the latter and can be downloaded from this page in XHTML format. Note that the standards listed on the page are arranged numerically and the OpenDocument standard is very near the bottom of the page. This version of ODF is the only version that has the legal status of an international standard, making it eligible as a government procurement specification throughout all Member nations of the Agreement on Government Procurement.
Paul Merrell

New OASIS Discussion List: oiic-formation-discuss - 0 views

lists.oasis-open.org/...msg00003.html

iic tc interop odf odf tc sc 34 w3c

shared by Paul Merrell on 03 Jun 08 - Cached
  • The proposed discussion list name is "oiic-formation". (2) A preliminary statement of scope for the TC whose formation the list is intended to discuss. It is the intent of the ODF Implementation, Interoperability and Conformance (IIC) TC to provide a means for software implementors and service providers to create applications which adhere to the ODF specification and are able to interoperate. As such, the purpose of the IIC TC includes the following:
  • It is the intent of the ODF Implementation, Interoperability and Conformance (IIC) TC to provide a means for software implementors and service providers to create applications which adhere to the ODF specification and are able to interoperate. As such, the purpose of the IIC TC includes the following: 1. To publish test suites of ODF for applications of ODF to check their conformance with the Standard and to confirm their interoperability; 2. To provide feedback, where necessary, to the ODF TC on ways in which the standard could improve interoperability; 3. To produce a set of implementation guidelines; 4. To define interoperability with related standards by the creation of profiles or technical reports; 5. To coordinate, in conjunction with the ODF Adoption TC, OASIS InterOp demos related to ODF; The IIC TC may also liaise with other standard bodies whose work is leveraged in present or future ODF specifications. These include, but are not limited to, the W3C and ISO/IEC JTC1/SC34.
  • 1. To publish test suites of ODF for applications of ODF to check their conformance with the Standard and to confirm their interoperability; 2. To provide feedback, where necessary, to the ODF TC on ways in which the standard could improve interoperability; 3. To produce a set of implementation guidelines; 4. To define interoperability with related standards by the creation of profiles or technical reports; 5. To coordinate, in conjunction with the ODF Adoption TC, OASIS InterOp demos related to ODF; The IIC TC may also liaise with other standard bodies whose work is leveraged in present or future ODF specifications. These include, but are not limited to, the W3C and ISO/IEC JTC1/SC34.
Jesper Lund Stocholm

Alex Brown on the ODF Zero Interop problem: The discussion to limit the use of Foreign ... - 0 views

lists.oasis-open.org/...msg00009.html

odf interop alex-brown

shared by Jesper Lund Stocholm on 09 Mar 09 - Cached
  • So I think users need to understand, very clearly, that an ODF document/app of *either* conformance class has an EXTREMELY WEAK CLAIM TO INTEROPERABILITY. The "pure ODF conformance" sticker would be at best valueless and at worst positively misleading. So what I'd like to see is some real effort from the TC going into resolving this problem ...
    • Jesper Lund Stocholm
      Jesper Lund Stocholm on 22 Mar 09
       
      The sad thing is that with the agreement between JTC1 and OASIS regarding ODF, it seems that SC34 has been completely cut out of the loop in terms of "fixing ODF", as you put it. I cannot see how SC34 will be able to play any part in this - besides rubber-stamping ODF 1.2 when it comes our way.
  • Gary Edwards on 09 Mar 09
     
    So I think users need to understand, very clearly, that an ODF document/app of *either* conformance class has an EXTREMELY WEAK CLAIM TO INTEROPERABILITY. The "pure ODF conformance" sticker would be at best valueless and at worst positively misleading. So what I'd like to see is some real effort from the TC going into resolving this problem ... Alex Brown What Alex fails to mention is that the "foreign elements and alien attributes" components in the ODF Section 1.5 "Compliance and Conformance" clause was originally put there in early 2003 to provide a compatibility layer for MSOffice binary documents. Without this clause, it would be impossible to convert the billions of legacy MSOffice binary documents to ODF without breaking the fidelity. Now th OASIS ODF TC wants to limit the use of the compatiblity clause. An action that would seriously cripple Microsoft's efforts to implement ODF in MSOffice 14. No surprises here. It was only a matter of time until IBM and Sun ganged up on the newest TC member, Microsoft.
  • Jesper Lund Stocholm on 22 Mar 09
     
    So I think users need to understand, very clearly, that an ODF document/app of *either* conformance class has an EXTREMELY WEAK CLAIM TO INTEROPERABILITY. The "pure ODF conformance" sticker would be at best valueless and at worst positively misleading. So what I'd like to see is some real effort from the TC going into resolving this problem ... Alex Brown What Alex fails to mention is that the "foreign elements and alien attributes" components in the ODF Section 1.5 "Compliance and Conformance" clause was originally put there in early 2003 to provide a compatibility layer for MSOffice binary documents. Without this clause, it would be impossible to convert the billions of legacy MSOffice binary documents to ODF without breaking the fidelity. Now th OASIS ODF TC wants to limit the use of the compatiblity clause. An action that would seriously cripple Microsoft's efforts to implement ODF in MSOffice 14. No surprises here. It was only a matter of time until IBM and Sun ganged up on the newest TC member, Microsoft.
Gary Edwards

Griffin Brown Weblog - ODF validation for the cognoscenti - 0 views

www.griffinbrown.co.uk/...PermaLink.aspx

brown iso jtc-sc34 odf ooxml weir

shared by Gary Edwards on 06 May 08 - Cached
  • ODF validation for the cognoscenti Just when it seemed like nobody was interested in the ODF conformance smoke test posted a few days ago, IBM's Rob Weir weighs in with a lengthy piece in response.
  • Gary Edwards on 06 May 08
     
    Rob Weir gets royally spanked. And so does the notion that ODF is somehow "interoperable". Big Time.
1 - 4 of 4
Showing 20▼ items per page