Office for Mac and the interoperability divide
I was reading the latest issue of Mac|Life tonight (I liked it better as Mac Addict, by the way), and it struck me how dependent Apple is on Microsoft. For all the cool things that come with Mac hardware and OS X, a large swath of the Mac user population would be crippled or wiped out if Microsoft decided to stop supporting Office for Mac.
The Mac faithful (of which I am part) won't like to hear this, but it's true. OpenOffice is an excellent program (It actually is now--three years ago it was rubbish), but many of us simply couldn't use it "in production." Sure, I could run Office for Windows in Parallels' coherence mode (and almost certainly would), but that's an unnecessarily roundabout way of solving something best done directly.
This is a relatively small problem for Mac users, right? I suppose so. The same thing, however, is true in the enterprise. Many prefer to run Linux for an increasing array of server-based applications. But they don't want to be stranded, just as I would be on my Mac without Office. Net net: interoperability is a Very Good Thing. It's good for open source, but it's also good for Microsoft (and everyone else, because no one has a complete lock on any particular area of enterprise software).
All of which makes me wish we could, as an industry, talk about interoperability with more candor. More honesty. This isn't a dig at Microsoft, though it has been guilty of conflating patents (a desire to get paid) with interoperability (a desire to get along). The two don't necessarily go together.
No, the problem goes much farther than Microsoft, and hurts Microsoft as much as it hurts Red Hat, SAP, Oracle, MySQL, etc. As an industry we are childish in how we approach interoperability. We squabble over standards, each of us trying to make sure our standard is the chosen one. And then we squabble over whom should "go first" and risk standardization.
In my world, customers are asking that Sharepoint repositories interoperate with Alfresco repositories interoperate with Documentum repositories interoperate with...In the database world, enterprise customers want their Oracle, PostgreSQL, DB2, Ingres, MySQL, etc., databases to work together (indeed, EnterpriseDB is building a solid business by offering drop-in compatibility with Oracle). In e-mail, more applications (open source and proprietary) should interoperate with Exchange.
It just shouldn't be so hard. Especially since, historically, markets dramatically expand as interoperability/standards permeate them. We are better off when we work together, even when it appears that we'll lose in the short term. When customers win, vendors win.
I believe it is the open-source world that needs to be doing more to be driving interoperability. It should be the open-source world that "opens the kimono" on interoperability, in part because it's easier for us to do so. We don't need to worry about what the kimono is hiding because, by definition, open source has nothing to hide.
A good start would be joining forces to push leading incumbents like Microsoft, Oracle, etc., to develop programs to work with open-source companies. Microsoft has come closest to this (SugarCRM, Zend, MySQL, JBoss, etc.) but has yet (to my knowledge) to develop a programmatic (read: safe) way of working with the company, and its patent noise has muddied the water a bit.
We in the open-source world want to interoperate with the proprietary world. Would some of us prefer to have the proprietary world open up? Of course. I'm in that camp. But in the meantime, we want consistent ways to partner with incumbent vendors to bring value for our mutual customers. I, personally, would love to help proprietary vendors figure out how to engage open-source communities and companies without getting burned, so that there's mutual trust and respect. I'm thinking a small caucus is in order to hash out some ideas...
Meet me on the mountain biking trails of Deer Valley in September. Let's figure this out.
Matt Asay brings a decade of in-the-trenches open-source business and legal experience to The Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure. You can follow Matt on Twitter @mjasay. 
Craig Kitterman
Interoperability Program Manager
Microsoft Corporation
http://blogs.msdn.com/craig
Thanks for helping raise awareness around this. The OSA (www.opensolutionsalliance.org) has been focusing on interoperability since we launched... Admittedly we've focused more on interop within the commercial open source world, and less on interop with private-source/legacy technology, which is what you're advocating in this post. Nonetheless this is something we're hearing from customers is important and we want to take it on, bandwidth and resources permitting.
Actually we've had positive informal conversations with Microsoft's open source interop group about doing something like you suggest, notably with Sam Ramji, but the patent fud coming from the "parent org" gave us pause.
Anyhow, here's what we are thinking. You ask how to "help proprietary vendors figure out how to engage open-source communities and companies without getting burned". It's easy for them to get burned given how fragmented we are, collectively. There are tens of standards bodies out there, hundreds of viable commercial open source companies, and thousands of viable communities. Where to start? We propose to provide them with one "common front", one organization that can adequately represent the interoperability interests of a sufficient subset of the commercial open source ecosystem. That organization must, of course, operate as transparently and collaboratively as the word "open" would imply, thus having the necessary credibility, and it should also act pragmatically, by always keeping customers' interests in mind and not reinventing wheels. We're doing this with the OSA. So, our suggestion is to help the OSA act as the "point person" for commercial open source, and help us reach out to the "open source beachheads" within each major proprietary vendor. (Microsoft clearly has one, as does Oracle.)
Your thoughts welcome, as always. Feel free to respond here, or privately, or, if you're serious about kicking something off in Deer Valley, then please count us in. FYI- We're kicking off a Customer Forum Series this month, and proprietary interoperability requirements discussion is on the agenda, so we'll soon have a lot more real-world data to go by.
- European Commission
- by anyoneu July 9, 2007 8:35 AM PDT
- "In my world, customers are asking that Sharepoint repositories interoperate with Alfresco repositories interoperate with Documentum repositories interoperate with...In the database world, enterprise customers want their Oracle, PostgreSQL, DB2, Ingres, MySQL, etc., databases to work together (indeed, EnterpriseDB is building a solid business by offering drop-in compatibility with Oracle). In e-mail, more applications (open source and proprietary) should interoperate with Exchange."
- Like this Reply to this comment
-
(3 Comments)Ummm Matt. That's what the European Commission v Microsoft is about. Microsoft embraced and extended open standards and made billions off keeping their encrypted protocols secret. If you go and make deals outside of the EC decision, you're going to make MS very happy, and that's not good for open source and GPL'd software.
BTW, since Microsoft can't even get their Mac Business Unit to produce an OOXML converter (and Office 12008 won't have VBA, unlike the Windows version), I don't think MS standards mean much.
http://www.microsoft-watch.com/content/business_applications/the_pointless_office_converter_delay.html
"he Mac faithful (of which I am part) won't like to hear this, but it's true. OpenOffice is an excellent program (It actually is now--three years ago it was rubbish), but many of us simply couldn't use it "in production." "
Have you tried NeoOffice, the new native Mac Openoffice.org or the LanguageTool grammar checker addon?
http://neooffice.org
http://www.linux.com/articles/6171
http://www.languagetool.org/
http://www.linux.com/articles/61714