• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

An Antic Disposition

  • Home
  • About
  • Archives
  • Writings
  • Links
You are here: Home / Archives for Rob

Rob

ODF at 5 Years

2010/05/01 By Rob

Five years ago today, on May 1st, 2005 OASIS approved Open Document Format 1.0 as an OASIS Standard.  I’d like to take a few brief minutes to reflect on this milestone, but only a few.  We’re busy at work in OASIS making final edits to ODF 1.2.  We’re in our final weeks of that revision and it is “all hands on deck” to help address the remaining issues so we can send it out for final public review.  But I hope I can be excused for a short diversion to mark this anniversary.

I won’t talk much about the 5 years since ODF 1.0 was approved.  The ODF Alliance and their “ODF Turns Five” [pdf] does a good job there.  But I would like to talk a little about ODF and why it is so important that it came about when it did, why it was so timely.

To fully appreciate the significance of ODF you need to understand the market climate in which it was created, and to understand that you need to understand a little of the history of word processors.  The following time line illustrates the introduction dates of word processor applications over the past 30 years or so.  You will notice some familiar and not-so-familiar names:

We can divide this time line into four time periods, each one driven by a pivotal development.

The first period was the “Pioneering Age”, when the first steps toward the modern word processor were taken.  This was research-driven, primarily by Xerox PARC, who developed the first WYSIWYG word processor, Bravo as well as the first GUI word processor, Gypsy.  Except for the line editor vi, which still has some adherents among the troglodyte cave dwellers, none of these first-generation applications survived, though their influence did.  For example, Charles Simonyi, after working on Bravo at Xerox, went to Microsoft to develop Word.  (Ah, the days before software patents…)

The next wave of word processor applications, the “Personal Computer Age” came in the 1980s with the new platforms of the IBM PC (1981) and the Apple Macintosh (1984).  New platforms require apps, either new or ported,  and you will see several familiar names introduced in that fruitful period.

Then we have a gap.  From around 1990 to 1999 we do not see many new word processor introductions.  This was the “Lost Decade”.  New word processor introductions died off.  Unchallenged by competition, even Microsoft Word advanced relatively little in this decade, compared to innovations before or since.

A few forces were at play here.  First, there was a platform shift, from MS-DOS to MS-Windows 3.1 (1991) and Windows 95 (1995).  Few companies were able to successfully port their applications to Windows.  Also, the market changed significantly with the introduction of Microsoft Office as a suite of applications.  Suddenly it was not enough to have a good word processor, say WordPerfect, or a good spreadsheet, say 1-2-3, or a good presentation package, say Harvard Graphics.  To be competitive you needed to have all three suite components.  And few companies did.  Finally, there was the preferential access to operating system technical information Microsoft gave to their own applications teams, allowing Microsoft apps to run better on Microsoft operating systems than their competitors could.  The decade closed with word processor competition wiped out.    Analysts stopped tracking and reporting market share data when Office’s share exceeded 95%.  And file formats?  There were the binary DOC, XLS and PPT.  And the file format documentation was only available under license from Microsoft, and only if you agreed not to make a competing word processor.

That was the shape of the market around 2000.  Or more properly the state of the Microsoft monopoly.

So what happened that made ODF possible?  In one word, the Internet.  Well, not so much the technology of the internet itself, but widespread access to the internet via the web.  This enabled the open source movement as we know it today to scale.  Although open source existed before the web, unless you were at a major university or research centers, sharing source code and working collaboratively on software was very difficult.  But with widespread access to email, ftp, web, eventually version control, we had the tools needed to scale open source from small teams to large teams.  And to write a competitor to Microsoft Word you need a substantial team.

Why was open source so important?    Because no rational profit-seeking entity would compete against a monopoly, especially one maintained by restricting access to technical information needed to interoperate.  Lacking effective government regulation, the market was revived by open source.  You see the same thing happen with Linux and with web browsers.

The other thing the internet and the web brought was a new platform based on open standards, HTML, CSS,  XML, Javascript, allowing an interactive style of web application called “AJAX”.  And since this new platform was based on open standards, Microsoft was less effective in preventing competition in this area.  Certainly they tried.  From ActiveX to Silverlight, from poor standards support in Internet Explorer, to the infamous memo by Bill Gates in 1998: “One thing we have got to change in our strategy – allowing Office documents to be rendered very well by other peoples browsers is one of the most destructive things we could do to the company. We have to stop putting any effort into this and make sure that Office documents very well depends on PROPRIETARY IE capabilities”, they tried, but ultimately failed to “take back the web” and turn it into a proprietary Microsoft platform.

With the new web application platform came new web-based word processors, some of which are charted above.

The net effect is that since 2000 or so we have a new diversity of word processors, open source, web-based, even the revival of commercial competition.  It was against this backdrop, the history of competition and diversity all but wiped out but then restored in the new millennium, that ODF was born.  Today every word processor of note supports ODF, including Microsoft Word.  As Microsoft’s National Technology Director, and former CIO of Washington State, Stuart McKee said, “ODF has clearly won“.  We’ve scaled the steep walls of monopoly and planted a new flag.  Our former opponents are now our colleagues, working with us on ODF 1.2. We’ve shown we can win. But now we need to show that we can rule.  This is the challenge.  We need to continue to evolve ODF to meet user needs — and these are diverse needs — as well as accommodate a wide range of application models, from traditional heavy-weight desktop applications, to mobile apps, to web based apps, while realizing that these platforms themselves are shifting and possibly converging.  Standards advance at glacial speed, while technological and competitive forces move at faster speeds.  Allowing flexibility and extensibility while at the same time preserving interoperability among ODF implementations — this is a hard task, and one that is not entirely technological.  The key value of ODF is to support interoperability in a market of diverse applications.  This is the choice that users want.

But enough of the reflection.  Time to get back to my work on ODF 1.2.   I need to figure out linear depreciation according to the French accounting system so we can specify the AMORDEGRC spreadsheet function properly.

Filed Under: ODF, Standards Tagged With: word processors

The Naming of Standards

2010/04/28 By Rob 2 Comments

I am occasionally asked, what is the correct name of the ODF standard?  Is it “OpenDocument Format”?  Or is it “Open Document Format”, with a space between “Open” and “Document”?

I’d like (hopefully) to clear this up.

The naming decision happened back in 2004.  At that point Sun had contributed their specification for the OpenOffice XML format to OASIS,  and a new TC was using that specification as the basis for developing a new standard.  But what should the new standard be called?

Some wanted it to be called “OfficeDocument”, emphasizing its primary scope of use.  Others wanted to call it “OpenDocument”, making its openness (a new thing in the office-document world at that time) more central, and acknowledging that its applicability was for more than just office editors.

So, as only a committee can do, a compromise was forged incorporated both ideas.  The resulting official name of the standard became, “OASIS Open Document Format for Office Applications (OpenDocument)”.

If you are citing the standard for official reasons, that is the name to use.  (Or the ISO name which is even longer).  But clearly, that name is too long for casual use, or even use in technical writing,  so we need a shorter, more convenient name.  I’ll note the terms I’ve seen used, as well as my personal thoughts on whether they are  a good idea:

  • ODF — This is what you’ll hear it called in OASIS, where the term is unambiguous.  However, in other circles ODF can mean other things, from “Organ Donation Foundation” to “Oregon Department of Forestry”.  So, in writing, even on this blog, I will typically use a longer form first, and only then use the acronym.  This is also more search-engine friendly.
  • Open Document Format — This is certainly always correct and is my preferred longer form.
  • OpenDocument — This is also correct, the short name explicitly given in the standard.  We use it, for example, in the registered MIME content types for ODF.  I tend to see this more used to refer to the technology rather than the format itself.  So, “OpenDocument applications” or “OpenDocument toolkits”.  But if I had omnipotent powers, I’d eliminate this short name and make the short name official “ODF”.
  • OpenDocument Format — This is less correct, using the official short name and then appending a proper case “Format” after it.  It is hard to justify, but it does occur in many places.
  • OpenDoc — This is absolutely wrong.  OpenDoc is the name of an unrelated technology Apple developed in the 1990s.

When the IBM Terminology group contacted me on this (and yes we apparently have such a group) my advice to them — and I commend  the same to you — is:

  1. When citing the standard, use the official name “OASIS Open Document Format for Office Applications (OpenDocument) v1.1”.
  2. When referring to the format in general, call it “Open Document Format”  at its first use in a document, and then feel free to abbreviate it as “ODF”.

There are those who say that standards also have a THIRD NAME, a secret name that they use only for themselves.  What deep and inscrutable name ODF calls itself is a matter of some speculation.

Filed Under: ODF

IBM Software Consumability Survey

2010/04/28 By Rob Leave a Comment

We (IBM’s Software Group) are doing a survey of user perceptions of the “consumability” of our products.  “What is consumability?” you might well ask.  It is a new word for an old idea.  It describes the end-to-end customer experience, the consistency and cohesion of our products and solutions, from acquisition, prototyping, through integration, deployment, maintenance and upgrade.  The idea is ancient.  Vitruvius, in De Architectura wrote of Firmess, Commodity and Delight (firmitas, utilitas and venustas) as the ideals of a building.  Commodity here used in the sense of commodius or serviceable, convenient, well-adapted to its purpose, etc.  I think that “consumability” is the modern buzzword for that ancient architectural virtue.

But I digress.

If you use IBM products, and can spare 20-30 minutes to take an online survey you first-hand experiences with software consumability, then I encourage you to head over to this page, and share your thoughts.  The survey is available in 10 languages (English, Brazilian Portuguese, Simplified Chinese, Traditional Chinese, Korean, Japanese, German, Spanish, French, and Italian).

I’m told that earlier forms of this survey resulted in 1400 product suggestions, 900 of which are reflected in currently shipping products.  So this is good way to get your opinion heard and acted on.

Thanks!

Filed Under: IBM

Weekly Links #7

2010/04/24 By Rob Leave a Comment

  • lpOD — languages & platforms OpenDocument – lpOD 0.9.1 “Granada” is released – View

    “lpOD 0.9.1 “Granada” is released

    lpOD 0.9.1 has just been released, together with its documentation. You can download lpOD 0.9.1 here.”

    tags: ODF

  • Workshop on Document Freedom – Presentations | Open Technologies Resource Center

    “OTRC organized one day workshop regarding Free Document Formats on Document Freedom Day (31st March, 2010). The program targeted IT focal persons from different ministries of Nepal Government and other Open Document enthusiasts.

    The following presentations were delivered during the event.

    1. Welcome and Introduction – Jwalanta Shestha
    2. FOSS in Nepal and Open Documents – Subir Pradhanang
    3. Why Document Freedom – Laxmi Khatiwads
    4. Open Document: The Essence – Abhishek Singh
    5. Role of Document Freedom in eGovernance – Bibek Paudel
    6. Nirvikalpa CD Demo – Suraj Sapkota”

    tags: ODF, DFD

  • jOpenDocument Homepage

    “Version 1.2 beta 3, April 13, 2010 jOpenDocument-1.2b3-jdk5.jar (Java 5)”

    tags: ODF

  • EU eGovernment push ‘threatens Microsoft supremacy’ | EurActiv

    “EU telecoms ministers took an important step towards diluting the market dominance of Microsoft’s Office software on Monday (19 April) when they agreed to roll out online services using more interoperable document formats, according to Brussels-based competition lawyers.”

    tags: ODF

  • Notes from ODF Plugfest in Granada, Day One

    “The ODF Plugfest is a Conference whose goal is to to achieve the maximum interoperability between competing applications, platforms and technologies in the area of digital document sharing, and to promote the OpenDocument format (ODF). This page, as the others that will follow on this website, is a short technical summary, primarily aimed at developers, of what happened during the first day of the conference.”

    tags: ODF

  • Final Notes from the ODF Plugfest in Granada
  • “The second day of the Plugfest followed the same general scheme of the first one (covered in a separated page): a non-technical introduction followed by lots of hacking, feature analysis and product anticipations.”

    tags: ODF

Posted from Diigo. The rest of my favorite links are here.

Filed Under: Weekly Links

Why I like Oracle’s $90 ODF Plugin

2010/04/21 By Rob 13 Comments

There has been a flurry of news articles about Oracle’s price change on their (formerly Sun’s) ODF Plugin for MS Office.  What was previously free (as in beer), at least for individual use, is now sold for $90 and with a minimum quantity of 100.  The broad coverage (ZDNet, BusinessWeek, CNET,  NBC, IDG, etc.)  of this minor story suggests someone was shopping this story around.  I wonder who?

At the risk of pouring oil on the fire, let me say that I think this is an exciting development for ODF.  We have three solutions for providing ODF support in MS Office:

  1. Oracle’s Plugin
  2. CleverAge Add-in
  3. Microsoft’s native ODF support

These three solutions have always varied in terms of quality of conversion, versions of MS Office supported, versions of ODF supported, level of integration into MS Office, etc.  And now they vary based on price.  This is a good thing.  It is called “competition”.  I like it.

Although I personally think that Oracle has set the price too high, I realize that we have a market to sort these things out.  If they act rationally (and I assume they will) they’ll charge an amount that maximizes their return.  If they are not already at a profit-maximizing price point, they will adjust.  That is how prices are set in a free market.   But if Oracle can really get $90 per copy, with a minimum quantity of 100, then all the power to them.  I just hope that some of that money gets plowed back into their development of this and other ODF-related tools.  That is how we grow stronger and more powerful ODF tools.  Someone needs the impetus to make that investment.  If the profit motive drives investment in ODF,  then Praise be to Mammon!  And remember, if Oracle’s Plugin gets more people to use ODF, then that is a larger audience for your open source ODF tool.  This is a good thing.  The important thing is we’re growing the number of people using ODF.

We should want companies to invest in ODF tools.  We should want the demand for ODF to be such that ODF-based goods and services have value, can be sold based on that value, and that there is competition again in the market, something we have not seen in this area in many years.

2009-04-23 — Some further thoughts

It is probably worth reflecting why the Sun Plugin was necessary in the first place.  If Microsoft Office supported ODF fully, in a well-integrated and interperable fashion, then surely no ODF Plugin would be necessary. You would gain your ODF support simply by purchasing your MS Office license.  In effect, you are already paying for ODF support (along with all other Office features) when you purchase MS Office. If you are buying Oracle’s $90 Plugin, remember that you are essentially paying for ODF support twice: once to Microsoft and once to Oracle.

If I were paying twice for the same feature, I’d be upset as well.  But is the solution really for Oracle to continue subsidizing MS Office users by giving away their Plugin for free?  Or maybe Microsoft customers should ask their vendor why their Office ODF support is not adequate?  Ideally there would be no need for a Plugin because the out-of-the-box ODF support would meet customer requirements.  I’m sure Microsoft, like any other vendor, would value such feedback from their customers.   But to me it seems perverse to blame Oracle for no longer subsidizing their competitor’s product.

Filed Under: ODF

  • « Go to Previous Page
  • Page 1
  • Interim pages omitted …
  • Page 17
  • Page 18
  • Page 19
  • Page 20
  • Page 21
  • Interim pages omitted …
  • Page 69
  • Go to Next Page »

Primary Sidebar

Copyright © 2006-2026 Rob Weir · Site Policies