Conference Mailing List

If you would like to receive GOSCON announcements, please subscribe to our GOSCON mailing list.

Conference Hosts

OSU

OSU Open Source Lab

Should intraoperability be limited to a single platform or should it include platform interoperability?

Should intraoperability be limited to a single platform or should it include platform interoperability?

To: Jason
From: Shaun Savage
By:

Answer

-> Back to Questions

Submitted by Jim King on Fri, 11/16/2007 - 6:24pm.

It is extremely frustrating to have something sent to you as a MAC user that you cannot open because the product involve is Windows only. Sure you want cross platform interoperability if by platform you mean operating system.

There will never be a computer or OS that 100% of everyone uses. There is always a 10-30% market product that keeps the big guy honest.

I have had the frustration of sending a file to a group of 15 people to do some cooperative work upon only to find that 2 cannot open it. This kills the whole process. You have to fax it to them or get them to buy the software, or ... .

Submitted by Arnaud Le Hors on Tue, 11/20/2007 - 12:32pm.

Intraoperability is based on a hub and spokes model where one player or component is given a central role. OOXML is designed around this model.

OOXML is about allowing other people to interact with files that are primarily generated and manipulated with Microsoft Office. It is not about full interoperability, which would enable competition with Microsoft Office, for obvious reason.

In this context, although it'd still be better if it were platform independent, whether it is or not may not be as important. No matter what, you are subjected to a set of constraints imposed by the hub.

When interoperability is sought, then yes, platform independence certainly adds value.

Post new comment

The content of this field is kept private and will not be shown publicly.