Skip to main content

Home/ Document Wars/ Group items tagged formats

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

International Digital Publishing Forum (formerly Open eBook Forum) - Flock - 0 views

www.idpf.org

universal-format

shared by Gary Edwards on 12 Dec 07 - Cached
  • The International Digital Publishing Forum (IDPF) is the trade and standards association for the digital publishing industry.
Gary Edwards

The better Office alternative: SoftMaker Office bests OpenOffice.org ( - Soft... - 0 views

news.idg.no/...art.cfm

shared by Gary Edwards on 30 Jun 09 - Cached
  • Frankly, from Microsoft's perspective, the danger may have been overstated. Though the free open source crowd talks a good fight, the truth is that they keep missing the real target. Instead of investing in new features that nobody will use, the team behind OpenOffice should take a page from the SoftMaker playbook and focus on interoperability first. Until OpenOffice works out its import/export filter issues, it'll never be taken seriously as a Microsoft alternative. More troubling (for Microsoft) is the challenge from the SoftMaker camp. These folks have gotten the file-format compatibility issue licked, and this gives them the freedom to focus on building out their product's already respectable feature set. I wouldn't be surprised if SoftMaker got gobbled up by a major enterprise player in the near, thus creating a viable third way for IT shops seeking to kick the Redmond habit.
    • Gary Edwards
      Gary Edwards on 30 Jun 09
       
      Wow. Somebody who finally gets it. OpenOffice and OpenOffice ODF were not designed to be compatible with Microsoft Office, the MSOffice productivity environment, and, the legacy of binary documents. Softmaker is not the only Office Suite alternative designed for compatibility with MSOffice. ThinkFree Office and Evermore Office are also proof positive that high level compatibility is possible.
Paul Merrell

Gray Matter : Compatibility Pack for Open XML passes 100 million downloads - 0 views

blogs.technet.com/...ses-100-million-downloads.aspx

office 2007 compatibility pack odf-ooxml stats

shared by Paul Merrell on 24 Jun 09 - Cached
  • The Compatibility Pack, software that allows you to open, edit and save Open XML format documents in Office XP and 2003 has now been downloaded over 100 million times.
  • Paul Merrell on 24 Jun 09
     
    Also includes stats in table form indicating that according to Google Search OOXML documents now outnumber ODF documents on the Web, for word processor documents, spreadsheet documents, and presentation documents.
Paul Merrell

untitled - 0 views

www.dpawson.co.uk/...090612.html

ODF specificity quality testability

shared by Paul Merrell on 18 Jun 09 - Cached
  • Most (quality) specifications provide clear instructions using those magic words SHALL, SHALL NOT, and MAY where those words have a defined meaning for an implementor. Paragraphs are clearly identified as either normative or informative. That way an implementor knows what they must and may implement to claim conformance against a specification. This approach has been well established over time as a sensible way for spec writers and implementors to work
  • Most (quality) specifications provide clear instructions using those magic words SHALL, SHALL NOT, and MAY where those words have a defined meaning for an implementor. Paragraphs are clearly identified as either normative or informative. That way an implementor knows what they must and may implement to claim conformance against a specification. This approach has been well established over time as a sensible way for spec writers and implementors to work That is the way quality specifications are written. For example, ISO/IEC's JTC 1 Directives (link to PDF) requires that international standards designed for interoperability "specify clearly and unambiguously the conformity requirements that are essential to achieve the interoperability." With that clarity, conformance is testable and can provide confidence of interoperability. A suite of tests may be developed and applied to an implementation to determine which tests pass, which fail, and hence arrive at an objective pronouncement on conformance of an implementation against the entirety of the specification.
  • In a quality specification, it should be feasible to select a normative paragraph, identify a conformance test for it, and make a clear statement that this test proves that an implementation meets (or fails to meet) that requirement. Call it a test plan: define the tests (test specification), define the expected set of results, and define what constitutes a "pass" of each test that establishes conformance. The plan then provides the matrix of test spec against requirement. Simple.
  • ...4 more annotations...
  • Rob Weir of IBM chaired (apology for the misuse of that last word) the formation list and then simply announced what the charter would be rather than seeking consensus among the list participants. As part of this process before that charter was produced and while I still naively believed that consensus was a goal, I sat down with ODF 1.1 and did a paragraph-by-paragraph review for testability. The numbers were quite revealing. I completely reviewed only the first four major sections and found very few clear requirements. The majority were mere statements with no normative language used to identify what was required or optional. Implementors would have to make their own interpretation.
  • It's ironic that the chair viewed as good news the fact that there were far fewer testable paragraphs than he had predicted. But his prediction of 10,000 test cases is probably far closer to how many testable paragraphs there should be; my counts were actually bad news.
  • All of the above leads to the interesting question of just how the chair expects to accomplish much that is useful in regard to ODF conformance testing before the specification is amended to tighten up the language and add clear requirements. The syntax conformity is already handled by validation against the schema, but the semantics are woefully under-specified.
  • Summary: ODF 1.1 isn't verifiable as a specification. From a fairly cursory review of the latest draft, ODF 1.2 will follow the same path. With OASIS now being more demanding regarding conformance requirements on every specification and with ISO/IEC taking a closer interest in liaison with the ODF TC, I find it hard to see how the ODF TC co-chairs can maintain this view toward verification.
Graham Perrin

Doug Mahugh : Standards-Based Interoperability - 0 views

blogs.msdn.com/...ds-based-interoperability.aspx

interop standard ODF OOXML Excel spreadsheet OpenFormula

shared by Graham Perrin on 28 Jul 09 - Cached
  • Standards-Based Interoperability
  • 05 June 09
  • Interoperability without Standards
  • ...46 more annotations...
  • First, let’s consider how software interoperability works when it is not standards-based. Consider the various ways that four applications can share data, as shown in the diagram to the right.  There are six connections between these four applications, and each connection can be traversed in either direction, so there are 12 total types of interoperability involved.
  • As the number of applications increases, this complexity grows rapidly.  Double the number of applications to 8 total, and there will be 56 types of interoperability between them:
  • through standards maintenance, transparency of implementation details, and collaborative interoperability testing.
    • Graham Perrin
      Graham Perrin on 28 Jul 09
       
      Issues relating to CalDAV are well addressed in these ways.
  • Here’s where those workarounds will need to be implemented: Note the complexity of this diagram.
  • In the real world, interoperability is almost never achieved in this way.  Standards-based interoperability is much better approach for everyone involved,
  • whether that standard is an open one such as ODF (IS26300)
  • or a de-facto standard set by one popular implementation.
  • or Open XML (IS29500)
  • The core premise of open standards-based interoperability is this:
  • each application implements the published standard as written, and this provides a baseline for delivering interoperability.
  • the existence of a standard addresses many of the issues involved, and the other issues can be addressed
  • In the standards-based scenario, the standard itself is the central mechanism for enabling interoperability between implementations: This diagram is much simpler
  • there is no question that users of other products are massively surprised by
  • How this all applies to Office 2007 SP2 I covered last summer the set of guiding principles that we used to guide the work we did to support ODF in Office 2007 SP2.
  • applied in a specific order
  • I’d like to revisit the top two guiding principles
  • Guiding Principle #1: Adhere to the ODF 1.1 Standard
  • Guiding Principle #2: Be Predictable
  • Being predictable is also known as the principle of least astonishment.
  • What about Bugs and Deviations? Of course, the existence of a published standard doesn’t prevent interoperability bugs from occurring.
  • deviations from the requirements
  • different interpretations
  • Our approach to the transparency issue has been to document the details of our implementation through published implementer notes.
  • Interoperability Testing The final piece of the puzzle is hands-on testing
  • What else would you like to know about how Office approaches document format interoperability?
  • a standard (evolved and improved as reality demands) is the proper foundation for resolving interoperabilty
  • All complex software has bugs, and some bugs can present significant challenges to interoperability.  Let’s consider the case that 3 of the 4 applications have bugs that affect interoperability, as shown in the diagram to the right.
  • (1) their spreadsheets having their formulas lost when interchanged with Excel 2007
  • (2) not being able to handle the formulase received in Excel 2007's ODF output.
  • I am creating my own fantasy about the state of affairs
    • Graham Perrin
      Graham Perrin on 28 Jul 09
       
      :-)
  • it is far too early to declare it to be unsuccessful
  • I cannot fault the Microsoft approach as incorrect
  • I was at the year-ago DII meeting where the guiding principles were announced and their application to spreadsheet formulas described.  I applauded the principles and understood the reasoning for formulas.
  • How this would impact various groups of users and non-users (who still want to interoperate) of Office 2007 did not surface in my consciousness.
  • there is NO published standard for ODF spreadsheet formulas yet.
  • Nor is there any de-facto standard that everyone agrees on.
  • the “spaghetti diagram" method, with all of the complexity and risk of bugs that entails
  • No implementer we know of has attempted that
  • In the case of spreadsheet formulas, help is on the way -- OpenFormula is under development for use with ODF 1.2.
  • I’d like to keep this thread on-topic
  • I appreciate the post, very good
  • Visually I would rather frame it in terms of convergence, a spiral.
  • and user satisfaction.
  • I doubt someone would ever find a magic bullet to interoperability
  • New Comments to this post are disabled
    • Graham Perrin
      Graham Perrin on 28 Jul 09
       
      Hurrah!
  • © 2009 Microsoft Corporation
  • Graham Perrin on 28 Jul 09
     
    Diagrams here are eye-catching.
Paul Merrell

Screenshots of The First Application That Supports ISO/IEC 29500 - 0 views

xmlguru.cz/...pplication-supporting-is-29500

OOXML ISO_IEC:29500 implementations

shared by Paul Merrell on 04 Jun 09 - Cached
  • Blogosphere has been full of speculations about when and if ever Microsoft will support ISO/IEC 29500 format in MS Office. Some people believe and wish that OpenOffice.org with ISO/IEC 29500 support will be released earlier then MS Office. But don't get fooled, the first application conforming to ISO/IEC 29500 is out, it is neither MS Office nor OpenOffice.org, it is coming from Free Software Foundation and you can see screenshots here.
Alex Brown

Is ODF designed to be not implementable without source code? - Wouter - 0 views

blogs.code-counsel.net/...Post.aspx

shared by Alex Brown on 02 Jun 09 - Cached
  • How come I am the one to notice how deficient ODF really is?
    • Alex Brown
      Alex Brown on 02 Jun 09
       
      "But mummy, he's not *wearing* any clothes ..."
  • Gary Edwards on 02 Jun 09
     
    Exactly! It's not that ODF is under-specified. It's that ODF can't be fully specified until OpenOffice is completely documented and capable of supporting expected features. There is this famous quote from Sun's Svante Schubert that pretty much says it all; "Nothing goes into the ODF specification unless it's supported by OpenOffice". The statement was made at a meeting of the OASIS ODF Metadata SC while discussing the controversial use of "XML ID". IBM's Elias Torres, of RDFa fame, was passionately arguing that use of the XML ID should be left open to all developers. Sun had taken the position that XML ID should be limited to only a handful of elements supported by OpenOffice. The discussion acutally got far worse than the quote would indicate. Elias compromised his arguments suggesting that we should allow developers to have at it with XML ID for at least one year, and then revisit the issue. This suggestion lead to a discussion of how developers implementing elements with metadata would notify the metadata sub committee of their use case. A discussion list was proposed. The idea being that developers would send in their use cases and the oligarchs on the sub c would approve or disprove. Incredibly, this suggestions was shot down by Bruce d'Arcus (OpenDocument Foundation). Bruce thought that any developer needing metadata support for particular elements should have to join the OASIS ODF Metadata SC like everyone else before their needs would be considered. ( i.e. - like the other oligarchs). At the next weeks meeting, Rob Weir showed up with a list of 14 spreadsheet related elements that IBM needed XML ID support for. Sun representatives Svante Schubert and Michael Brauer immediately approved the use, agreeing that OpenOffice would support that implementation. This how things work at OASIS ODF. Ever wonder why SVG or XForms support in ODF is so limited? It's because the specification directly reflects the limits of the OpenOffice implement
  • Gary Edwards on 02 Jun 09
     
    Sorry. Diigo cut my comment off about half way through. I've complained to Wade and Maggie about this problem, especially how it impacts and cripples the "Group Auto-Blog Post" feature . Months have gone by. Yet still the issue remains.
Alex Brown

OOXML is defective by design: Microsoft's latest aggression on ODF, codenamed "cast lead" - 0 views

ooxmlisdefectivebydesign.blogspot.com/...-latest-aggression-on-odf.html

shared by Alex Brown on 17 May 09 - Cached
  • nazis
    • Alex Brown
      Alex Brown on 17 May 09
       
      "Nazis", "genocide", "white phosphorous" -- and all about a file format implementation ...
Alex Brown

Lotus Symphony gets some OOXML support : News : Software - ZDNet Asia - 0 views

www.zdnetasia.com/...0,39044164,62055288,00.htm

shared by Alex Brown on 03 Jul 09 - Cached
  • Symphony 1.3, released last week, now enables imports of documents using Microsoft's Office Open XML (OOXML) format. However, the free-of-charge office suite does not yet let users save documents in OOXML.
    • Alex Brown
      Alex Brown on 03 Jul 09
       
      shhhhh
Alex Brown

Is There Life After Office? | BNET Technology Blog | BNET - 0 views

industry.bnet.com/...is-there-life-after-office

shared by Alex Brown on 02 Jul 09 - Cached
  • Kafkaesque joke exemplifying vendor ambition, inexperience and stupidity
    • Alex Brown
      Alex Brown on 02 Jul 09
       
      Sounds familiar
  • Paul Merrell on 02 Jul 09
     
    Glynn Moody, who is quoted in the article, obviously does not understand what was involved in Massachusetts. Sam Hiser, also quoted, was deeply and personally involved. OOXML wasn't even on the horizon then. Microsoft Office 2003 wrote to a flat XML format that was irrelevant in any event. What Massachusetts wanted --- and deserved from the ODF community --- was an ability to integrate OpenOffice.org with business processes that were already thoroughly bound to Microsoft Office. The problem was in fact solved by the OpenDocument Foundation's ODF plug-ins for Microsoft Office, but the project had to be ditched because Sun would neither adapt OOo nor allow ODF to be adapted for the purpose. Gary Edwards and I wrote an in-depth and heavily-referenced article on why ODF failed in Massachusetts. http://www.linuxworld.com/news/2007/072307-opendocuments-grounded.html (.) Those who do not comprehend that integration of data created by end point solutions and stored in legacy data silos is a fundamental requirement in service oriented architectures will never comprehend why interoperability is so vitally important. They wind up being unwitting advocates of incredibly expensive rip out and replace solutions. Good luck, particularly in the current economic climate. The wonderment is why anyone believes that Microsoft Office can be toppled by ODF from its monopoly position without ultra-high fidelity interoperability with Microsoft Office. Too much "what works well enough for me works well enough for anyone" mindset, I suspect.
Jesper Lund Stocholm

Groklaw - Digging for Truth - 6 views

www.groklaw.net/comment.php

shared by Jesper Lund Stocholm on 05 Oct 09 - Cached
  • You harmed us and our families. You harmed the public, and you will have to live with that judgment from us.
    • Jesper Lund Stocholm
      Jesper Lund Stocholm on 05 Oct 09
       
      Legendary comment ... :o) "You harmed our families. You harmed the public and you will have to live with that judgement from us"
  • Gary Edwards on 06 Oct 09
     
    What an amazing conversation. It's true that ODF was NOT designed to be compatible with MSOffice and the legacy binary format. That's not to say there were not considerable efforts within the OASIS Open Office XML TC (ODF) pushing for compatibility. But Sun successfully held off these efforts, insisting that ODF was not designed to be compatible with MSOffice or the MSOffice binaries. Many asked the obvious question, "How are end users supposed to convert their information (billions of legacy "in-process" binary documents) to ODF if ODF is not designed for that conversion?" Stellent, represented by Phil Boutros, and Corel, represented by Paul Langille and Tom Magliery, were particularly obsessed with this problem. Without "compatibility", how were end users supposed to convert their documents? Needless to say, Sun prevailed. ODF is 100% perfectly compatible with OpenOffice/StarOffice, by design. It is not compatible with the billions of "in-process" compound business documents essential to world trade, commerce and information exchange. What a shame, ~ge~
Alex Brown

An Antic Disposition: Asking the right questions about Office 2010's OOXML support - 1 views

www.robweir.com/...ht-questions-about-office.html

shared by Alex Brown on 17 Nov 09 - Cached
    • Alex Brown
      Alex Brown on 17 Nov 09
       
      ... and we can expect similar censure for people claiming to support "ODF"?
  • Remember, the conformance language of OOXML is so loose that even a shell statement of "cat foo.docx > /dev/null" would qualify as a conformant application.
    • Alex Brown
      Alex Brown on 17 Nov 09
       
      Think you're confusing ODF and OOXML here Rob; hint - look at OOXML "application descriptions"
  • ...6 more annotations...
  • But that is not what WG4 was recently told in Seattle, where they were told that Office would not write out Strict documents until Office 16
  • In other words, will Office 2010 be "strictly conformant" with the ISO/IEC 29500:2008 standards?
    • Alex Brown
      Alex Brown on 17 Nov 09
       
      interesting made up concept, this "strictly conformant", for a standard which contains an extensibility mechanism ...
    • Alex Brown
      Alex Brown on 17 Nov 09
       
      err, news to me ... and I was at the meeting.
  • To do otherwise is to essentially specify a require for the use of Microsoft Office and Microsoft Office alone.
    • Alex Brown
      Alex Brown on 17 Nov 09
       
      or any of those other applications which support that format (including some from IBM even) ...
Graham Perrin

FR: Advocacy group protests government's approving of OOXML - - 0 views

www.osor.eu/...governments-approving-of-ooxml

2009 2009-11 2009-11-21 Office Open XML

shared by Graham Perrin on 21 Nov 09 - Cached
  • FR: Advocacy group protests government's approving of OOXML
  • Nov 20, 2009
  • Gijs Hillenius
  • ...6 more annotations...
  • April, a French free and open source software advocacy group, is protesting the French government's approval of Microsoft's OOXML as a government document standard, alongside the open document format ODF.
  • General interoperability framework for public administrations and local governments, RGI
  • Référentiel Général d'Interopératibilité
  • We have just missed a historical opportunity to support openness and innovation in the software market
  • calling on members of the French parliament to clarify the RGI
  • The RGI does not resolve the controversy between software publishers and supporters of free software. Both standards office are placed 'under observation', and their use remains at the discretion of each administrative authority.
  • Graham Perrin on 21 Nov 09
« First ‹ Previous 241 - 253 of 253
Showing 20▼ items per page