Skip to main content

Home/ OpenDocument/ Group items tagged interoperability

Rss Feed Group items tagged

Gary Edwards

How A PAID IBM Lobbyist Orchestrates The Worldwide Search for a Standard Document Format - 0 views

  • Open Means Open For a document format to be considered "open," it should be fully implemented by many different vendors, interoperable, fully published, and available royalty free without intellectual property restrictions. Microsoft's OOXML continues to fail this test. For example, the comments from the British Standards Institute pointed out that "there was no other proven implementation of OOXML apart from Office 2007." Unless and until there is another proven implementation, any government beginning to use OOXML would be faced with only one option. This is contrary to the objective of government open standards policies. Open standards policies are proliferating as governments seek to create IT architectures that rely on open standards to allow multiple vendors to compete directly based on the features and performance of their products. What governments obviously need are open standards that enable technology solutions that are portable and that can be removed and replaced with that of another vendor with minimal effort and without major interruption.
Gary Edwards

War rages on over Microsoft's OOXML plans: Insight - Software - ZDNet Australia - 0 views

  • "We feel that the best standards are open standards," technology industry commentator Colin Jackson, a member of the Technical Advisory committee convened by StandardsNZ to consider OOXML, said at the event. "In that respect Microsoft is to be applauded, as previously this was a secret binary format." Microsoft's opponents suggest, among a host of other concerns, that making Open XML an ISO standard would lock the world's document future to Microsoft. They argue that a standard should only be necessary when there is a "market requirement" for it. IBM spokesperson Paul Robinson thus describes OOXML as a "redundant replacement for other standards". Quoting from the ISO guide, Robinson said that a standard "is a document by a recognised body established by consensus which is aimed at achieving an optimum degree of order and aimed at the promotion of optimum community benefits". It can be argued that rather than provide community benefit, supporting multiple standards actually comes at an economic cost to the user community. "We do not believe OOXML meets these objectives of an international standard," Robinson said.
  •  
    "aimed at achieving an optimum degree of order .... and .... aimed at the promotion of optimum community benefits:. Uh, excuse me Mr. Robinson, tha tsecond part of your statement, the one concerning optimum community benefits - that would also disqualify ODF!! ODF was not designed to be compatible with the 550 million MSOffice desktops and their billions of binary docuemnts. Menaing, these 550 million users will suffer considerable loss of information if they try to convert their existing documents to ODF. It is also next to impossible for MSOffice applications to implement ODF as a fiel format due to this incompatbility. ODF was designed for OpenOffice, and directly reflects the way OpenOffice implements specific document structures. The problem areas involve large differences between how OpenOffice implments these structures and how MSOffice implements these same structures. The structures in question are lists, fields, tables, sections and page dynamics. It seems to me that "optimum community benefits" would include the conversion and exchange of docuemnts with some 550 million users!!!! And ODF was clearly not designed for that purpose!
  •  
    I don't agree with this statement from Microsoft's Oliver Bell. As someone who served on the OASIS ODF Technical Committee from it's inception in November of 2002 through the next five years, i have to disagree. It's not that Microsoft wasn't welcome. They were. It's that the "welcome" came with some serious strings. Fo rMicrosoft to join OASIS would have meant strolling into the camp of their most erstwhile and determined competitors, and having to ammend an existing standard to accomodate the implementation needs of MSOffice. There is simply no way for the layout differences between OpenOffice and MSOffice to be negotiated short of putting both methodologies into the spec. Meaning, the spec would provide two ways of implementing lists, tables, fields, sections and page dynamics. A true welcome would have been for ODF to have been written to accomodate these diferences. Rather than writing ODF to meet the implementation model used by OepnOffice, it would have been infinitely better to wrtite ODF as a totally application independent file format using generic docuemnt structures tha tcould be adapted by any application. It turns out that this is exactly the way the W3C goes about the business of writing their fiel format specifications (HTML, XHTML, CSS, XFORMS, and CDF). The results are highly interoperable formats that any applciation can implement.
  •  
    You can harmonize an application specific format with a generic, applicaiton independent format. But you can't harmonize two application specific formats!!!!
    The easy way to solve the document exchange problem is to leave the legacy applications alone, and work on the conversion of OOXML and ODF docuemnts to a single, application independent generic format. The best candidate for this role is that of the W3C's CDF.
    CDF is a desription of how to combine existing W3C format standards into a single container. It is meant to succeed HTML on the Web, but has been designed as a universal file format.
    The most exciting combination is that of XHTML 2.0 and CSS in that it is capable of handling the complete range of desktop productivity office suite documents. Even though it's slightly outside the W3C reach, the most popular CDF compound is that of XHTML, CSS and JavaScript. A combination otherwise known as "AJAX".
Gary Edwards

BetaNews | Course Change for OpenDocument Developers Seen as Emerging Rift - Scott Fulton - 0 views

  • A presentation made two weeks ago by two members of OASIS' OpenDocument technical committee, and founding members of the OpenDocument Foundation, made it clear that the foundation would be turning its attention away from developing the ODF format and translators for it. Instead, in a course change instigated as far back as last May, the Foundation is steering back toward a project launched in 1995 by the World Wide Web Consortium, in hopes of recapturing the momentum toward document interoperability for all existing word processor users.
Gary Edwards

ODF and differences of opinion | John Carroll | ZDNet.com - 0 views

  • the OpenDocument Foundation had decided to back away from work on ODF in favor of CDF (a W3C-backed standard) out of a belief that ODF wouldn’t achieve the real-world interoperability goals the OpenDocument Foundation was originally created to achieve
Gary Edwards

OpenDocument Foundation drops support for ODF, backs obscure W3C format - Flock - 0 views

  • The OpenDocument Foundation has decided to end its support for OASIS's OpenDocument Format (ODF) and instead support W3C's Compound Document Format (CDF), which is currently described in the Web Integration Compound Document Core 1.0 draft. This move reflects growing concerns within the interoperability advocacy community about the long-term viability of both ODF and Microsoft's Office Open XML (OOXML).
Gary Edwards

open...: Oh, Tell Me the Truth About...the ODF Bust-Up - 0 views

  • Oh, Tell Me the Truth About...the ODF Bust-Up The recent decision by the OpenDocument Foundation to shift its energies away from ODF to CDF has naturally provoked a lot of rather exaggerated comment. I wrote a piece for LWN.net (now out from behind the paywall) exploring what exactly was going on, and found out that there are bigger issues than simply document interoperability at play.It turns out to be all about Microsoft's Sharepoint - software that I am beginning to see as one of the most serious threats to open source today. Read it and be very afraid.
Paul Merrell

Doug Mahugh : ODF Implementation Notes for Office 2007 SP2 - 0 views

  • Microsoft has today published our first set of document-format implementation notes, for the ODF implementation in Office 2007 SP2. These notes, which are available on the DII web site, provide detailed information about the design decisions that went into our implementation of ODF 1.1.
  • Doug, The list of elements and attributes "not supported in core Word/Excel/PowerPoint 2007" is quite long. Can you tell us what will happen, when Office 2007 encouters an unsupported element. Will it simply be ignored? When roundtripping - will it be deleted or preserved?
  • Doug, The list of elements and attributes "not supported in core Word/Excel/PowerPoint 2007" is quite long. Can you tell us what will happen, when Office 2007 encouters an unsupported element. Will it simply be ignored? When roundtripping - will it be deleted or preserved?
  • ...1 more annotation...
  • Jesper, On load, Office 2007 SP2 will simply ignore the unsupported elements and attributes in ODF files.  We do not attempt to round trip unsupported elements and attributes, they will be removed from the ODF file if you resave it using Office 2007 SP2.  This is consistent with our implementation principles and our desire to provide predictable behavior.   We considered trying to roundtrip elements and attributes that we do not understand or support, but we found if we did this that we could not be sure the resulting files were internally consistent and conformant ODF files.   As an aside, there are some cases where we write elements or attributes on save that we do not support on load, for the sake of better interoperability with other applications that use ODF.   Those cases are described in the implementer notes as well.
  •  
    Jesper Lund Stocholm asks a right-on-the-mark question. Peter Amstein answers for Microsoft. What do you expect when a specification ends its conformance section with the statement, "There are no rules regarding the elements and attributes that actually have to be supported by conforming applications, except that applications should not use foreign elements and attributes for features defined in the OpenDocument schema?"
Gary Edwards

The Document Interoperability Initiative: "DII" - 0 views

  •  
    Vendor - developer group sponsored by Microsoft ... "What's seriously lacking is a conversion or locking of scripts, macros, OLE, data - media bindings, and security settings .... the logic parts so important to any business process or productivity environment setting embedded in the original MSOffice document."
Paul Merrell

Matusow's Blog : Open XML, ODF, PDF, and XPS in Office - 0 views

    • Paul Merrell
       
      Whoopee! Everyone gets to add vendor-specific extensions to standards like ODF to enable some quality of Sharepoint/Exchange/Outlook interop in their apps, just as soon as Microsoft gets around to offering adequate specfications. History teaches that may be a very long time, and of course the relevant Microsoft patent RAND terms apply, because the disclosures are made outside the context of a standard that requires otherwise. And of course the OASIS RF on RAND policy does not forbid new ODF features subject to RAND terms and the policy is silent on the subject of vendor-specific extensions. Methinks FOSS may have just lost its "open standard" ODF.
  • Office is NOT implementing ODF 1.0 from ISO. That spec is not representative of the marketplace today, it is not what is implemented in OpenOffice, it is not what IBM is using for Symphony, and it is not referenced in the Massachusetts ETRM policy.
    • Paul Merrell
       
      As I have been arguing, there are no full featured implementations in existence of the ISO/IEC:26300 OpenDocument standard and every government that has adopted the international standard as its own internal standard or procurement specification is subject to legal challenge because of the lack of implementations.
  • In my opinion, the continued interest in innovation presented by those solutions will speak much louder than the formats themselves.
    • Paul Merrell
       
      You can have standards and you can have innovation. But you can't have interop if you embrace and extend standards. The need for stable, fully-specified formats for document interchange purposes apparently is not part of Microsoft's plan. Scant wonder, neither ODF nor OOXML is designed for document interchange among competing vendors' apps. They are both standards designed to allow a single vendor to maintain dominant market share among implementors of those standards. Microsoft will soon diominate market share in both so-called "standards." The embrace of a standard is necessary to extend and extinguish it.
  • ...3 more annotations...
  • While this is a big deal announcement for the Office product team (check out Doug Mahugh's blog), my take on it is predictably focused on the longer-term interoperability factors.
  • the API that will allow ANY document format to register itself with Office and be set as the default will be made available as planned. Additionally, the work with DAISY and other specialized document formats will move forward as well.
    • Paul Merrell
       
      I was wrong. The API is for more than ODF plugo-ins.
  • The documentation of client/server protocols for Office-related technologies (such as SharePoint and Exchange/Outlook communications) will remain available to the public.
  •  
    "Clearly the Press Announcement today from Microsoft will bring about another wave of discourse on the future of document formats. " Jason Matusow presents the long-term view of the announcement's significance.
Jesper Lund Stocholm

OOXML is defective by design: Microsoft latest bullshit : native support of ODF in Offi... - 1 views

  • I wanted to post a quick reaction to the latest Microsoft bullshit announcement, in which they reportedly plan to "add native support for ODF 1.1". The way they put is very succinct, intentionally probably, and it opens the door for wild guesses.First of all, Microsoft is a huge Office licensing monopoly. It's so big it even surpasses Windows in sales. Any decline in Office licensing would be dramatic for Microsoft's future. With that alone, you know that any announcement from Microsoft that they are willing to interoperate with other people's software, namely applications, should be taken with a grain of salt.Here is how, with the release of Office 2007, Microsoft intends to keep their monopoly in Office licensing :
  • Likewise, since Office 2007 is not a native XML application (the internal representation is a bunch of binary structure, not XML DOM)
    • Jesper Lund Stocholm
       
      Do any of you guys know if applications like OOo has a different internal object model? Is an ODF-document loaded into something equivilant to an XML DOM?
  •  
    Stephane is right on target. This is a must read for anyone trying to understand ISO approval of OOXML, and the sudden change of mind at Microsoft to support ODF!
Jesper Lund Stocholm

ISO - News - ISO and IEC approve OpenDocument OASIS standard for data interoperability ... - 0 views

  • The OpenDocument Format OASIS standard that enables users of varying office suites to exchange documents freely with one another has just been approved for release as an ISO and IEC International Standard.
    • Jesper Lund Stocholm
       
      ODF approval in ISO
Graham Perrin

Doug Mahugh : Working with ODF in Word 2007 SP2 - 0 views

  • ODF in Word 2007 SP2
  • Service Pack 2 for Office 2007
  • You can make ODF the default
  • ...18 more annotations...
  • ODF can’t represent 100% of the things we can do in Word
  • differences between the default line-spacing
  • fixed-layout format for published documents
  • and a flow-oriented layout
  • work well for dynamic editing
  • flow-oriented format during document authoring and editing
  • ODF or Open XML
  • differences in Word and OpenOffice’s default styling for hyperlinks
  • longer in OpenOffice
  • text-wrap margins around the inserted image also differ
  • decided to not implement tracked changes
  • indents were incorrect
  • Office SP2 .docx to .odt is the best
  • OOo developers
  • further improvements planned/started for 3.2
  • version 3.1 will solve several problems
  • Update on ODF Spreadsheet Interoperability
  • spreadsheets that can be manipulated with MS Office ONLY
« First ‹ Previous 161 - 172 of 172
Showing 20 items per page